On-Call When You're a Team of One: What Actually Matters for Solo Founders
Almost everything written about on-call assumes a rotation: multiple people, a handoff schedule, an escalation policy that eventually reaches someone else if the first person doesn't respond. None of that applies to a solo founder running their own infrastructure. There's no one to rotate to, no one to escalate to, and no handoff — just one person and a phone that either wakes them up or doesn't.
The real problem isn't routing
Most on-call tooling is built to answer "who should this page go to." For a team of one, that question has exactly one answer, every time, and it's not interesting. The actual problem is narrower and more concrete: will the alert reliably reach the one person who can act on it, especially at 3am when a phone is on silent, face-down, or nearly dead. Sophisticated routing logic solves a problem a solo founder doesn't have. Reliable delivery solves the one they do.
What actually matters at this scale
Two things are worth getting right, and neither of them is complicated:
A repeating alert, not a single notification. One push notification is easy to sleep through — a phone briefly lighting up and going quiet again asks nothing of a sleeping brain. An alert that repeats every couple of minutes until it's acknowledged behaves more like an alarm clock, which is exactly the right model when there's no backup person for it to fall through to. If it's not acknowledged, the only fallback is that it keeps trying, louder and more often, until it succeeds.
A second channel in case the first one fails. Push notifications can get killed by the OS, missed because Do Not Disturb was left on from the day before, or simply not arrive because of a flaky connection. A secondary channel like SMS, sent automatically if the primary alert goes unacknowledged for a couple of minutes, covers the specific failure mode where a single-channel setup goes completely silent for reasons that have nothing to do with whether the founder is actually reachable.
What's safe to skip for now
Escalation policies, on-call schedules, and groups all solve real problems — for a team with more than one person on the rotation. Setting any of them up for a team of one is pure overhead: there's no second person to escalate to, no schedule to rotate through, no group beyond "me." It's tempting to configure all of it anyway because it feels like doing things properly, but the actual leverage for a solo founder is entirely in delivery reliability, not routing sophistication that has nowhere to route to yet. That's worth revisiting the day a second person joins — not before.
Where this fits
This is a case where PingParrot's default behavior already matches the actual need: pages repeat automatically until acknowledged, delivery isn't locked to a single channel, and the free tier includes three pagers with no feature gating — escalation and the API are there if they become useful later, but nothing needs to be configured just to get a reliable, repeating alert working today. For a team of one, the tool should stay out of the way until it's actually needed for more than that.