When we ask clients what an hour of downtime costs them, most give a number that's either a guess or a figure from an old board deck. That's a problem, because it's the number that should be justifying every dollar spent on redundancy, monitoring, and incident response - and a guessed number leads to underinvestment.
A real model has three components: direct revenue loss (transactions that don't happen during the outage), recovery cost (engineering hours spent firefighting and doing post-incident cleanup), and trust cost - the harder-to-quantify but very real effect on churn and deal velocity after a visible outage.
For a mid-market SaaS company doing ₹40 crore in annual revenue, we typically see direct revenue loss alone land between ₹1.5-4 lakh per hour of full outage, before factoring in recovery labor or churn. That number changes the ROI math on a multi-region deployment or a proper on-call rotation completely - investments that looked optional at a guessed cost look obviously worthwhile at the real one.
If you don't have this number, it's worth the half-day exercise to build it. It's the single most useful input for deciding how much redundancy your infrastructure actually needs.
