The Real Cost
Most business owners have never calculated this number, and that is understandable. It is not a fun exercise. But it is one of the most useful numbers you can have, because it is the number that makes every conversation about IT investment, backups, and redundancy make sense.
Here is how to think about it, and why the answer usually surprises people.
Start With a Simple Formula
The cost of downtime breaks down into a few categories:
- Lost revenue. If your systems are down, can your business still generate revenue? For many businesses, the honest answer is no, or close to it.
- Idle labor. Your team is still getting paid whether or not they can work. That cost does not pause just because your systems did.
- Recovery costs. Getting back online often costs more than the original problem, especially if it involves emergency vendor support or after-hours rates.
- Intangible costs. Missed deadlines, frustrated customers, and damaged trust do not show up on an invoice, but they are real costs nonetheless.
Add those together for even a single hour, and the number is often larger than people expect.
What This Looks Like for a Real Business
Picture a 25-person company generating a couple million dollars a year in revenue. During business hours, that works out to roughly a thousand dollars an hour in revenue alone. Add payroll for 25 people sitting idle, and you are easily looking at well over a thousand dollars more per hour, before anything else is even factored in.
Now stretch that across a full day. A single day of downtime for a business this size can easily run into the tens of thousands of dollars, and that is before recovery costs or any lasting impact on customers.
Why "A Day" Often Becomes "A Week"
Here is the part that catches people off guard. The initial outage is rarely the whole story. Among businesses with 20 to 100 employees, more than half report downtime costs reaching well into six figures per hour when a serious incident, particularly a cyberattack, takes critical systems offline for an extended stretch.
A ransomware attack, a major hardware failure, or a botched update can turn what felt like "we'll be back by lunch" into days of recovery, backlog, and catch-up work that extends well beyond the original incident.
Why This Number Changes the Conversation
Once you know your actual hourly cost of downtime, IT decisions stop being about price tags and start being about risk. A monthly managed IT investment that once looked like a line item to minimize suddenly looks very different next to even a single bad day.
This is also exactly how Nevtec frames business continuity and disaster recovery investments with clients. Not as overhead, but as insurance against a number you can calculate for your own business right now.
Calculate Your Own Number
You do not need a consultant to get a rough estimate. Take your annual revenue, divide by your working hours per year, and that is your baseline revenue-per-hour. Add your hourly payroll cost. That combined number, multiplied by however many hours an outage might realistically last, is your starting point.
Write that number down. Share it with your leadership team. Then look at what you are currently spending on prevention and ask whether the math lines up.
Want help putting real numbers behind your own risk?
Talk to Nevtec about a downtime cost assessment and see where your business really stands.
Frequently Asked Questions
- How do we calculate our own cost of downtime?
Start with your annual revenue divided by working hours for a baseline hourly figure, then add your hourly payroll cost. Multiply that combined number by a realistic outage length for a rough estimate.
- Is lost revenue really the biggest factor?
Not always. For many businesses, idle payroll and recovery costs add up just as quickly, especially if the outage requires emergency support outside normal hours.
- Why does a "one day" outage sometimes turn into a week of impact?
Serious incidents like ransomware often involve not just restoring systems, but also catching up on backlogged work, communicating with affected customers, and rebuilding processes that broke during the outage.
- Does this number justify spending more on IT?
It depends on the comparison. The point is not to spend more for its own sake, but to compare what prevention costs against what an actual outage would cost, and make an informed decision from there.
- What is the first step if we want to reduce this risk?
A review of your current backup, redundancy, and recovery setup will show where the biggest gaps are relative to what an outage would really cost your business.