What Does an Hour of Downtime Cost Your Business?
Most small business owners can’t say what an hour of downtime costs, which makes it hard to decide how much to spend preventing it. The number does not need to be precise. Add up what you pay people who can’t work, the revenue you can’t take in, and the cost of catching up afterward, and you have a figure you can hold up against the price of backups, redundancy, and support. Here is how to work it out in about 30 minutes, with a worked example.
Start with idle payroll
When systems are down, you still pay the people who can’t use them. Take the loaded hourly cost of each affected employee, meaning wages plus payroll taxes and benefits. If you don’t have that figure handy, a common rule of thumb is wages multiplied by 1.25 to 1.4. Multiply it by the number of people who truly cannot work.
That last part matters. Few outages stop everyone. When Microsoft 365 went down on November 12, many offices lost email and Teams at once; when one line-of-business app fails, it might be a single department. Estimate the share of staff who are stuck, not just inconvenienced.
Add lost and delayed revenue
Next, estimate the revenue that depends on the system being available. Divide the annual revenue that flows through it by your annual business hours. A business open 45 hours a week has roughly 2,300 hours a year. That gives you revenue per hour.
Then be honest about how much of it is truly lost. An online order that goes to a competitor is gone. A client project that slips by an afternoon is delayed, not lost. A walk-in customer who can’t pay by card may come back, or may not. Most businesses lose a fraction of hourly revenue during a short outage, and more the longer it lasts.
Count the cost of recovery
- Catch-up time. Work that stopped still has to get done, often as overtime.
- Outside help. Emergency IT support, data recovery services, or forensic investigators after a security incident.
- Rework. Re-entering data, rebuilding files, and fixing errors made during workarounds.
- Penalties. Missed deadlines, late fees, or service credits you owe your own customers.
Don’t forget the costs you can’t count easily
Missed calls, frustrated customers, and staff who lose trust in the systems all carry a cost that never shows up on a spreadsheet. If an outage involves lost or exposed data, notification, legal, and investigation costs can dwarf everything else. You don’t need to put a number on these, but keep them in mind when the calculated figure looks small.
A worked example
Take a 20-person accounting firm with $2.4 million in annual revenue, where 18 people can’t work when the systems are down:
- Idle payroll: 18 people at a loaded $45 an hour is $810 an hour.
- Lost revenue: $2.4 million divided by 2,300 hours is about $1,040 an hour. If a quarter of that is truly lost, that is $260 an hour.
- Catch-up: if half the lost hours are made up later at time and a half, that is 9 hours at $67.50, about $610.
Total: roughly $1,680 for every hour the firm is down. A four-hour outage costs about $6,700. A ransomware incident that takes two full business days to recover from costs around $27,000 before anyone pays for data recovery or an investigation, and in the middle of tax season the lost-revenue share would be far higher.
Use the number to make decisions
Once you know the hourly cost, technology decisions get easier:
- Redundancy. If a backup internet line costs less per year than one bad afternoon offline, the decision makes itself. See business internet failover.
- Recovery targets. Decide how long each system can be down (your recovery time objective) and how much data you can afford to re-create (your recovery point objective). Our guide to business continuity vs. disaster recovery explains both.
- Priorities. Rank systems by what an hour without each one costs. The top of the list gets the best backups, the fastest support response, and the first spot in your recovery plan.
- Support coverage. If an hour down costs more than a month of proactive support, waiting for things to break is the expensive option.
Know how long recovery really takes
The cost per hour only helps if you know how many hours a failure would last. Most businesses find out during a real outage, when it is too late to fix the plan. Restore a server or a mailbox as a test, time it, and run a tabletop exercise with the people who would be involved. Our guide to disaster recovery testing shows how, and the 3-2-1 backup rule covers the foundation.
Put a number on your risk
Equal Tech Solutions helps businesses across Cleveland, Chattanooga, and the Southeast calculate their downtime costs, set realistic recovery targets, and fund the protections that matter most through our vCIO services and managed IT. Contact us to find out what an hour offline costs you.
