The 3 AM call is a product decision
Most solo founders treat incidents like weather. They happen to you. But the agencies and SaaS teams that keep their customers through a bad night all have three written artifacts, and none of them cost money:
1. A paging rule. Written before the incident. What is page-worthy at 3 AM, what waits for morning. If it is not on the list, it waits. A rule you invent at 3 AM is a panic attack, not a rule.
2. A handoff script. Six lines: current status, blast radius, what was tried, what is next, when the next update lands, who owns it. You can write it half-asleep because you wrote it once, at a desk, calm.
3. An escalation tree. Minute 10: ping the on-call human. Minute 30: invoke the vendor's support tier you pay for. Minute 60: post a status page note. Most "we lost the customer" stories are actually "nobody was called until the customer called us."
Here is the uncomfortable part: agencies selling "24/7 support" to their clients often have none of the three. They sell the promise and improvise the night. That is a billable gap you can close today — our 3 AM incident runbooks (paging rules, shift handoffs, escalation trees) are written to be rebranded: drop your logo, ship with the managed contract, charge for it.
One-time download, no subscription, no per-seat fees:
→ The 24/7 Agent Ops Runbook
→ Free: the backup-drill runbook
If your on-call night went fine last time, good — write the handoff script now, while you are calm. That is the whole trick.
Top comments (0)