What an Hour of Downtime Really Costs a 20-Person Company (With the Math)
Most business owners underestimate the cost of IT downtime because they only count lost revenue. Here's the actual arithmetic — payroll burn, lost revenue, recovery costs — and why it changes the break-fix vs. managed services calculation.
The Real Cost of Downtime Is Bigger Than You Think
When business owners think about IT downtime, they usually count one cost: lost revenue. If your business is closed for an hour, you lose an hour of sales. That's the number that comes to mind.
But the actual cost of downtime is significantly higher. It includes payroll for employees who can't work, recovery costs, reputational damage, and the cascading effects of delayed work that piles up after systems come back online. When you add all of these together, the real cost of a single hour of downtime for a 20-person company can be two to three times what you'd estimate.
This guide walks through the actual arithmetic so you can plug in your own numbers. It also addresses the question that this math ultimately informs: is break-fix IT support actually cheaper than managed services, or does the downtime math tell a different story?
The Three Cost Categories
Every downtime event hits you in three ways simultaneously. Understanding each one is the first step to calculating your true cost.
1. Payroll Burn
This is the cost most owners forget. When your systems are down, your employees can't work — but you're still paying them. For a 20-person company with an average loaded salary of $60,000 per employee, that's $30 per hour per person. If everyone is idle during an outage, you're burning $600 per hour in payroll alone — and getting nothing for it.
2. Lost Revenue
This varies by business type. A professional services firm that bills hourly loses billable time that may never be recovered. A retail business loses sales. A medical practice loses appointments that can't be rescheduled. The key is calculating your revenue per productive employee hour.
3. Recovery Costs
When systems come back online, the work doesn't resume at normal speed. There's a recovery period — catching up on delayed tasks, re-entering data, dealing with the backlog of customer inquiries. Studies consistently show that recovery takes 1.5 to 3 times longer than the outage itself.
The Downtime Cost Calculator
Here's a table you can use to plug in your own numbers. The example column uses a hypothetical 20-person professional services firm with $2 million in annual revenue.
| Cost factor | How to calculate | Your number |
|---|---|---|
| Number of employees affected | Count staff who can't work during downtime | 20 |
| Average loaded hourly cost per employee | Annual salary + benefits, divided by 2,080 hours | $30 |
| Payroll cost per hour of downtime | Employees × hourly cost | $600 |
| Annual revenue | Your total revenue | $2,000,000 |
| Productive hours per year | Employees × 2,080 × ~70% productivity | 29,120 |
| Revenue per productive hour | Annual revenue / productive hours | $69 |
| Lost revenue per hour of downtime | Revenue per productive hour × employees affected | $1,380 |
| Recovery multiplier | Time to catch up vs. outage time (typically 1.5x-3x) | 2x |
| Recovery cost per outage hour | Payroll cost × (recovery multiplier - 1) | $600 |
| Total cost per hour of downtime | Payroll + lost revenue + recovery | $2,580 |
For this 20-person firm, one hour of downtime costs $2,580. A full-day outage — which is not uncommon for a serious server failure or ransomware incident with a break-fix provider — costs over $20,000.
How Business Type Changes the Math
The biggest variable in the calculation is revenue per productive hour, and that shifts dramatically by industry.
- Professional services (law, accounting, consulting): High revenue per hour, but also high payroll. Downtime is expensive on both sides. A 10-attorney firm billing $300/hour loses $3,000 per hour in billable time alone.
- Medical/dental practices: Lost appointments are hard to recapture. Patients who can't be seen often reschedule weeks out or go elsewhere. The revenue loss is compounded by potential patient attrition.
- Retail/e-commerce: Direct revenue loss is immediate and measurable. An e-commerce site down for an hour during peak shopping loses that hour's sales permanently — no recovery possible.
- Construction/trades: Lower direct revenue impact per hour, but project delays can trigger contract penalties and cascade into schedule disruptions that cost far more than the outage itself.
Break-Fix vs. Managed Services: The Real Comparison
The reason the downtime math matters is that it changes how you evaluate IT support costs. Here's the comparison most owners do:
Break-fix approach:
- You pay nothing when things are working.
- You pay hourly when something breaks — typically $150-$200/hour, plus parts.
- A server failure that takes 6 hours to fix at $175/hour costs $1,050 in IT labor.
- But the downtime during those 6 hours costs $15,480 (using our 20-person example).
Managed services approach:
- You pay a flat monthly rate — typically $1,500-$3,000/month for a 20-person company.
- That includes 24/7 monitoring, patching, and proactive maintenance.
- The goal is preventing the failures that cause downtime, not fixing them after the fact.
- When issues do occur, response is typically faster because the provider is already monitoring your systems and often catches problems before you notice them.
The question isn't whether managed services cost more than break-fix. The question is whether the downtime you avoid with proactive monitoring costs less than the monthly fee. For most businesses, a single avoided full-day outage pays for 6-12 months of managed services.
Why Response Time Is the Hidden Cost
With break-fix support, the clock doesn't start when the problem begins. It starts when you notice the problem, call the provider, and they arrive. That process typically takes 2-4 hours before any work begins — and during that entire window, you're paying full downtime costs.
With managed services, monitoring often detects the issue before you're aware of it. A hard drive filling up, a server running hot, a service that's stopped responding — these are all conditions that monitoring catches in the early stages, not after they've taken down your systems. The difference between a 15-minute remote fix and a 4-hour on-site visit is the difference between $645 and $10,320 in downtime costs for our example firm.
The Honest Math
If your business can tolerate a full day of downtime once a year without serious financial impact, break-fix may be adequate. If a single day of downtime would cost you more than a year of managed services fees — which is true for most businesses with 10 or more employees — the math points clearly toward proactive management.
The cost of downtime isn't theoretical. It's a number you can calculate, and it's almost always higher than you expect. Dytech Group provides flat-rate managed IT services that include 24/7 monitoring and proactive maintenance to prevent the failures that cause downtime. If you're currently on a break-fix model and want to understand what managed services would look like for your business, our business IT support team can walk you through the options.
More articles