Search for the cost of IT downtime and you will find confident numbers. One widely repeated figure puts it at 5,600 dollars per minute. Surveys of small and mid-sized businesses variously report 8,000 dollars per hour, 25,000 dollars per hour, and in some cases 100,000 dollars per hour for companies with twenty to a hundred staff.
These numbers should be treated with suspicion, for three reasons. They are drawn almost entirely from US businesses with US wage structures and US revenue per employee. Many originate from vendors who sell the remedy. And the spread between them, more than a factor of ten for businesses of the same size, tells you the underlying measurement is not precise enough to plan against.
The useful observation buried in that same research is that most businesses have never calculated the figure for themselves. That is the gap worth closing, because your own number is both more accurate and more actionable than any survey average.
Downtime cost for a single incident comes down to four components. Add them.
1. Lost revenue. Take your annual revenue, divide by your actual operating hours per year. For a business open six days a week, nine hours a day, that is roughly 2,800 hours. Then multiply by the share of revenue that genuinely stops during an outage.
That last multiplier matters more than people expect. If you take orders continuously and cannot process them offline, it approaches 100 percent. If you are a project business that invoices monthly, a four-hour outage may delay revenue rather than destroy it, and the honest multiplier is closer to 10 or 20 percent.
2. Idle payroll. Count the staff who genuinely cannot work, not your whole headcount. Multiply their fully loaded hourly cost by the outage duration. Fully loaded means salary plus employer contributions, roughly 1.2 to 1.3 times gross salary for most Indian employers.
3. Recovery labour. The hours your team or your vendor spends restoring service, plus any emergency support charges. This continues after service is restored, because someone has to reconcile what was missed.
4. Recovery drag. After systems come back, people spend time working out where they left off and redoing lost work. A reasonable planning assumption is that this adds a further 20 to 50 percent on top of the idle payroll figure, though this is a rule of thumb rather than a measured constant.
The following uses invented figures for a hypothetical business. Replace every number with your own; the point is the method, not the result.
Suppose a Bengaluru distribution business turns over Rs 12 crore a year, operates 2,800 hours a year, and employs 40 people, of whom 25 cannot work at all when the order system is down. Average fully loaded cost is Rs 500 per hour. During an outage, 60 percent of revenue activity stops. The outage lasts four hours, and two engineers spend six hours between them on recovery.
Total for the incident: approximately Rs 1,72,600, or around Rs 43,000 per hour.
That figure is an order of magnitude below the US survey numbers, and it is far more useful, because it was built from facts the business owner can verify.
Not for alarming yourself. It exists to answer one question: how much is it worth spending to reduce downtime?
If a four-hour outage costs you Rs 1.7 lakh and you experience two per year, your annual exposure is around Rs 3.5 lakh. A disaster recovery arrangement costing Rs 15,000 a month, or Rs 1.8 lakh a year, is then a reasonable proposition if it meaningfully reduces either the frequency or the duration. If it costs Rs 50,000 a month, it is not, and you should be told that plainly rather than sold it.
This is also how you decide between recovery targets. Halving your recovery time from four hours to two saves roughly Rs 84,000 per incident in the example above. If achieving that costs more than the saving, the slower option is the correct one.
The purpose of the calculation is not to justify spending. It is to identify the point where further spending stops being worth it.
Customer loss. Some customers who cannot reach you go elsewhere permanently. This is real and genuinely hard to quantify, and estimates of it in vendor literature are usually guesses dressed as data. Treat it as a reason to be conservative rather than as a line item.
Timing. An outage during your peak season or at month end costs several times one on a quiet Tuesday. If your business is seasonal, run the calculation twice, once for a normal day and once for your worst plausible day, and plan against the second.
If you would like help running these numbers against your actual environment, and an honest view of whether your current exposure justifies spending anything at all, start the conversation on our contact page.
Book a free 30 minute strategy session with our certified experts.
Book a Session