Draft, not yet published
What an hour of downtime actually costs a solo-founder SaaS
7 July 2026· 6 min read · by Stackbastion
Your app went down, or you’re worried it might, and you’re trying to work out whether it’s worth spending money to prevent that. The enterprise “downtime costs $5,600 a minute” stats are useless to you. You’re a solo founder with a small SaaS. So let’s build a real number from the pieces that actually apply to you.
There’s no single true figure. Anyone who quotes you a precise universal cost is guessing. But you can reason it out honestly for your own app, and the exercise usually shows that the cost isn’t the lost sales during the outage. It’s what happens after.
The four costs of an outage
Downtime hits you in four places. Three are obvious and small. The fourth is the one that matters.
1. Lost revenue during the outage (usually small)
If people can’t buy or sign up while you’re down, you lose those sales. But do the math honestly. Say you make €3,000 a month. Spread evenly, that’s about €4 an hour. A one-hour outage “costs” roughly €4 in directly lost sales, and most of those customers would just come back and buy later anyway. For a small SaaS, this line is almost noise.
The exception: if your outage lands during a launch, a big traffic moment, or a specific window when people were going to buy and now won’t, this number spikes. A steady subscription app loses little to an hour down. A shop mid-flash-sale loses a lot.
2. Refunds and credits (small but real)
If you offer an SLA or just do the decent thing, a visible outage means some customers ask for a credit or a refund, and you give it. On a small base this is a handful of euros to maybe a few tens of euros per incident. Small, but unlike lost sales, it’s cash that actually leaves.
3. Your time (bigger than you think)
This is the cost founders never put in the spreadsheet, and it’s often the biggest one for a single incident. An outage eats your day:
- Diagnosing and fixing it, often under stress, often at a bad hour.
- Answering the support messages and “is it down?” emails.
- Writing the apology, updating the status, calming people down.
- The rest of the day you lose because you’re rattled and behind.
Call it 3 to 6 hours for a real incident, sometimes a whole day. If your time is worth €50 an hour, that’s €150 to €300 gone, per incident. And that’s time you can’t get back and can’t spend building. For a solo founder, this is usually the largest single-incident cost by a wide margin.
4. Churn and reputation (the real one, and the hardest to price)
Here’s the cost that outlasts the outage. Some customers who hit the downtime don’t complain. They just quietly decide you’re not reliable, and they leave, now or at their next renewal. Others tell someone, or leave a review, or don’t refer the friend they were about to.
You can’t measure this precisely, so reason it as a risk. Suppose an outage nudges just 2 extra customers to churn who otherwise wouldn’t have. If each pays €30 a month and would have stayed a year, that’s 2 × €30 × 12 = €720 in lost lifetime value from one outage. You’ll never see it on an invoice, which is exactly why it’s dangerous. It’s the biggest number here and the one that never shows up as a line item.
A worked back-of-envelope
Pull it together for a €3,000/month SaaS with a small paying base, one bad hour of downtime:
| Cost | Rough figure | Notes |
|---|---|---|
| Lost sales during outage | ~€4 | Trivial for steady subscriptions |
| Refunds / credits | €10 to €50 | Cash that actually leaves |
| Your time | €150 to €300 | 3 to 6 hours, biggest single-incident cost |
| Churn / reputation risk | €0 to €700+ | Invisible, and potentially the largest |
| Rough total | ~€150 to €1,000+ | Dominated by your time and churn risk |
So an hour of downtime for a small SaaS isn’t €4. Realistically it’s somewhere from a couple of hundred euros to over a thousand, and the spread is driven almost entirely by two things you can’t put on an invoice: your lost day and the customers who quietly leave.
Run your own numbers. Change the revenue, the customer count, the churn assumption. The shape holds: the direct lost sales are noise, and your time plus churn risk are the whole story.
What this means for prevention spend
Now the practical question: is it worth paying to prevent this? Compare the cost of one bad outage against what reliability actually costs.
If a single incident realistically costs you €150 to €1,000 in time and churn, and you have even a few incidents a year, that’s a four-figure annual cost. Against that, tested backups, monitoring that pages you before users notice, and a setup that restarts itself are cheap. The point of prevention isn’t zero downtime, nobody gets that. It’s fewer incidents, and shorter ones, because monitoring caught it in 5 minutes instead of you finding out from an angry email 3 hours later. That difference alone changes the time cost from “lost day” to “20 minutes.”
The worst version of this is downtime plus data loss, when the outage is a database problem and the backup turns out to be untested. Then the cost isn’t an afternoon, it’s an existential event. We wrote up how that plays out in an untested-backup postmortem.
Or, we do it for you
If you’d rather not be the one paged at 3am, or find out about downtime from a customer, get a free production audit and we’ll tell you honestly where your app is likely to go down and what tested backups and monitoring would actually cover.
FAQ
How much does an hour of downtime really cost a small SaaS?
There’s no universal number, but for a small SaaS the honest range is often a couple hundred to over a thousand euros per incident. The surprise is that directly lost sales are tiny. The cost is dominated by your time fixing it and handling support, plus the customers who quietly churn afterward.
Why isn’t lost revenue the main cost?
Because a steady subscription app loses very little to a single hour offline, most customers just come back and buy later. The real damage is your lost day and the churn and reputation hit that outlast the outage. Those don’t show up as missed sales on any dashboard, which is why they get ignored.
Is it worth paying to prevent downtime?
If a single incident costs you a few hundred to a thousand euros in time and churn, and you get a handful a year, that’s a four-figure annual cost. Tested backups and monitoring cost far less than that. The goal isn’t zero downtime, it’s catching problems in minutes instead of hours, which slashes the time and churn cost.
What’s worse than downtime?
Downtime combined with data loss. If the outage is a database failure and your backup was never tested, you can lose customer data permanently, which is an existential event for a small SaaS, not an afternoon. That’s why a tested restore matters more than the backup itself.