The Real Cost of Downtime: Calculate It for Your Business

Most conversations about IT investment stall at the same point. Someone proposes better backups, redundant internet or proper monitoring, and someone else asks what it costs. The number is concrete, the benefit is vague, and the proposal quietly dies.

The way out of that loop is to make the other side concrete too. Once you know the cost of downtime for your own business, the conversation stops being about spending money and starts being about comparing two numbers.

Ignore the industry averages

You will find headline figures claiming downtime costs thousands per minute. Those numbers come from surveys dominated by large enterprises, banks and manufacturers with production lines. They are not wrong, they are simply about somebody else.

Your own figure will be lower, and it will be far more persuasive, because you can defend every line of it. Fifteen minutes with a calculator beats any statistic you could quote.

The four components of the cost of downtime

1. People who cannot work

Take the fully loaded hourly cost of an employee, meaning salary plus employer contributions and overhead, not the gross wage. Multiply by the number of people genuinely blocked.

Be honest about who is blocked. During an outage some people find other work to do. Others are completely stuck. Estimating that seventy percent of affected staff lose their time is usually closer to reality than assuming everyone stops, and this lost productivity is the largest single component for most offices.

2. Revenue you do not recover

This is the line people overstate. If your systems are down for two hours and every order arrives anyway that afternoon, you lost time rather than revenue.

Ask instead: what proportion of business simply disappears? A webshop loses sales permanently. A wholesaler with regular customers usually does not. Use your gross margin rather than turnover, because that is what an unmade sale actually costs you.

3. Catching up afterwards

The forgotten one, and often the largest part of the cost of downtime. Work does not vanish, it queues. Every hour offline generates rework, overtime, rescheduled appointments and a support inbox that takes days to clear.

A reasonable rule of thumb is that recovery takes roughly half again the time you were down. If you were offline for four hours, expect around six hours of disrupted work afterwards.

4. The consequences you cannot invoice

Deadlines missed, a delivery that slips, a customer who tells someone else. These resist measurement, so leave them out of the arithmetic and mention them separately. A number you can defend is worth more than a number you inflated.

Working through an example

Take a company of twenty people. Fifteen are affected by an outage, at a loaded cost of forty-five euros an hour. That is roughly six hundred and seventy-five euros per hour in wages, and if seventy percent of that time is truly lost, call it four hundred and seventy euros.

Say the business turns over three million a year with a thirty percent margin. That works out to around four hundred and fifty euros of margin per working hour, of which perhaps a quarter is permanently lost rather than delayed. Add roughly a hundred and ten euros.

Then the catch-up: half again the lost labour, another two hundred and thirty-five or so.

The cost of downtime lands near eight hundred euros per hour. A full working day is around six thousand five hundred. Two days, which is a very ordinary recovery time after a serious incident, is thirteen thousand euros before anyone mentions reputation.

Run those same steps with your own figures. The exercise takes fifteen minutes and the result is yours to defend.

What to do with your cost of downtime figure

Compare it against what you actually spend. If a day offline costs six thousand five hundred euros and better backup and monitoring costs two hundred a month, the payback period is measured in hours of avoided outage, not years.

It also sharpens priorities. Once you can see the cost of downtime per hour, the question shifts from “is this worth it” to “which failure would hurt most, and what does it cost to shorten it”. That is a much better conversation to have with a finance director, and it turns an IT budget line into a risk decision rather than an expense to be trimmed.

Keep the estimate conservative. A defensible eight hundred euros an hour convinces people. An inflated five thousand invites an argument about your assumptions instead of the decision in front of you.

Let us work out what an outage would really do

Most companies have never calculated their cost of downtime, which is precisely why IT spending feels like a cost rather than an investment. Nobody has put the two numbers side by side.

At EvolvingDesk we do this with clients as a matter of course. We work through your figures, look at which systems would actually take you offline and for how long, and then show you what shortening that recovery costs. Sometimes the answer is that your current setup is fine. Sometimes it is that one unmonitored server sits between you and a very expensive week.

Either way you get a decision based on your own numbers rather than on a vendor’s scare story, and a business continuity plan sized to what you actually stand to lose.

Want to know what an hour offline costs you? Plan a call and we will work it out together, with your figures on the table.

Read more

• How much does IT management cost per employee, per month
• The 3-2-1 backup rule explained
• Managed IT services at EvolvingDesk

Background reading on resilience planning: the NCSC material on business continuity and the Ready.gov guidance on continuity planning.