How Much Does IT Downtime Cost a Small Business?

A two-hour IT outage can cost a small business thousands of dollars before anyone adds lost customers or recovery work.

The IT downtime cost depends on your revenue, staff size, systems, and outage timing. A failed internet connection may stop sales, while a ransomware incident can halt operations for days. Recent 2026 estimates place many small-business outages between $8,000 and $25,000 per hour, but your actual figure requires a closer look.

A simple formula can help you estimate the cost before the next incident occurs.

Key Takeaways

• Many small businesses lose between $1,000 and $25,000 for each hour of serious downtime.
• Your total cost includes lost revenue, idle payroll, recovery expenses, and customer-related losses.
• A high-revenue company with fewer employees can lose more than a larger company with lower sales.
• Recovery time objectives, tested backups, monitoring, and responsive IT support can reduce the final bill.
• Calculate your own hourly cost instead of relying on a broad industry average.

What Determines the Cost of IT Downtime?

Downtime starts costing money when employees cannot work, customers cannot buy, or essential business systems stop responding. The outage might involve your internet service, point-of-sale system, cloud applications, file server, phones, email, or cybersecurity controls.

The first cost is often lost productivity. Employees may sit idle, use personal devices, or spend time trying to fix a technical problem. Payroll continues even when work stops. If ten employees earning a combined loaded rate of $350 per hour lose access for two hours, the business absorbs $700 in unproductive labor.

Lost sales can create a larger loss. A restaurant with a failed payment system may turn customers away. An online retailer can lose orders every minute its website is unavailable. A law firm or accounting office may miss filing deadlines, delay client work, or spend extra hours rebuilding its schedule.

Recovery adds another layer. You may pay an IT provider for emergency service, replace damaged hardware, restore data, bring in overtime staff, or purchase temporary equipment. A cyberattack can also require forensic investigation, legal advice, notification services, and security remediation.

Recent estimates show why the numbers vary so widely:

• Narrow estimates of $1,000 to $5,000 per hour often count direct productivity and technical recovery costs.
• Broader small-business estimates of $8,000 to $25,000 per hour include lost sales, labor, recovery, and customer impact.
• A widely cited ITIC benchmark places some microbusinesses below 25 employees near $100,000 per hour. That figure fits certain high-revenue companies, but it shouldn't become a default number for every small office.

Industry matters, too. A retail outage during a quiet weekday may have a modest effect. The same failure during a holiday promotion can multiply lost sales. Healthcare providers, manufacturers, financial firms, and professional-service companies also face different deadlines, compliance duties, and service expectations.

A Simple IT Downtime Cost Formula

You can estimate your business's hourly downtime cost with four parts:

For a more detailed estimate, use this formula:

Start by calculating average hourly revenue:

Use operating hours rather than all hours in the month. A business open 8 hours a day, 5 days a week operates about 160 hours per month.

The percentage of revenue lost matters because some delayed work may be completed later. If an outage delays a consultation but the client keeps the appointment, that revenue may not be lost. If a customer leaves for a competitor, the full sale may disappear.

Loaded hourly pay includes wages, payroll taxes, benefits, and other employment costs. A worker earning $25 per hour may cost the business closer to $35 per hour after those additions. Use the number that reflects your real payroll expense.

Recovery costs include emergency IT labor, replacement equipment, data restoration, overtime, temporary services, and outside consultants. Other direct costs may include customer credits, missed-delivery fees, late-payment charges, or contractual penalties.

Keep revenue and profit separate. A business may generate $2,500 in sales per operating hour, but that isn't $2,500 in profit. Your estimate should show both the revenue at risk and the actual expenses caused by the outage.

For a quick first estimate, calculate the cost of one hour with full revenue loss and one hour with only productivity loss. Those two figures give you a useful range for planning.

A Realistic Small-Business Downtime Example

Consider a 20-person professional-services firm with $5 million in annual revenue. The company operates 160 hours each month and depends on Microsoft 365, cloud accounting software, client files, email, and VoIP phones.

Its average hourly revenue is:

$416,667 monthly revenue / 160 operating hours = about $2,604 per hour

Now assume an outage lasts two hours. The company estimates that 60% of the affected revenue won't be recovered because clients cannot reach staff and several appointments are canceled.

Lost revenue becomes:

$2,604 x 2 hours x 60% = $3,125

Fourteen employees cannot work during the outage. Their loaded labor cost averages $38 per hour.

Idle labor becomes:

14 employees x $38 x 2 hours = $1,064

The firm then pays $1,200 for emergency IT support, $600 in overtime to clear the backlog, and $500 in client credits. Recovery and other direct expenses total $2,300.

The estimated cost is:

• Lost revenue: $3,125
• Idle labor: $1,064
• Recovery and direct expenses: $2,300
• Total estimated cost: $6,489

If the company recovers every delayed sale, the revenue portion falls to zero. The outage still costs $3,364 in idle labor, emergency support, overtime, and credits. If the incident damages a client relationship or causes a missed deadline, the longer-term cost may exceed this estimate.

This example also shows why employee count alone isn't enough. A small firm with high-value client work can lose more per hour than a larger company with lower sales per employee.

Write down your own figures for monthly revenue, operating hours, affected employees, loaded pay, and recovery expenses. Then calculate costs for a 30-minute outage, a four-hour outage, and a full business day. Those scenarios can guide decisions about backup internet, battery systems, monitoring, and support coverage.

The Hidden Costs Behind an Outage

Lost sales and idle staff are easy to measure. Other losses are less visible but still affect cash flow and customer relationships.

A backlog can keep employees busy long after systems return. If a two-hour outage creates a full day of catch-up work, the payroll impact continues. Managers may also postpone sales calls, employee training, or billable projects while staff repair the backlog.

Customer trust can suffer when people cannot reach your business. Missed calls, delayed invoices, failed payments, and unanswered emails create friction. One incident may not lose a customer, but repeated outages can influence renewal decisions and referrals.

Security incidents create additional expenses. Restoring files from a backup is different from investigating whether an attacker accessed sensitive information. A business may need to reset accounts, replace devices, review logs, notify affected parties, and respond to insurance or legal requirements.

Contract terms can create another cost. A service-level agreement may require credits when systems miss an availability target. Vendors and business partners may also charge fees for missed appointments, delayed shipments, or incomplete work.

Local businesses should account for power and connectivity problems as well. Storms, vehicle accidents, construction damage, and utility failures can interrupt both office systems and internet service. A backup connection may keep cloud applications running, but it won't help if critical devices lack battery power.

How Small Businesses Can Lower Downtime Costs

Reducing downtime starts with identifying which systems keep revenue moving. List your payment systems, internet connection, phones, email, file storage, line-of-business applications, and devices. Then record what happens when each one fails.

Set two recovery targets:

1. Recovery time objective (RTO) : How long can the system remain unavailable?
2. Recovery point objective (RPO) : How much recent data can the business afford to lose?

A payment system may need recovery within minutes. An archived file system may have a longer acceptable recovery time. These targets help you spend money where an outage would cause the greatest harm.

Use monitoring to detect failed services before employees report them. Apply operating system and application updates on a regular schedule. Replace aging hardware before it becomes a single point of failure. Keep contact information for your internet, software, phone, and IT providers in one accessible location.

Backups need testing, not only scheduling. A backup that cannot restore a current file or application won't reduce your losses during an emergency. SJC Technology's data backup and disaster recovery services include backup monitoring and recovery testing for businesses in the Fort Myers, Estero, and Naples area.

Redundancy can also reduce the length of an outage. Options may include a secondary internet connection, battery backup, cloud-hosted systems, spare networking equipment, and alternate work locations. The right combination depends on your systems and cost calculation.

Finally, decide who responds and who communicates with customers. Businesses comparing support requirements can use this managed IT services checklist to review monitoring, backups, storm planning, and response procedures.

Conclusion

The cost of IT downtime is more than the repair invoice. Lost revenue, idle payroll, recovery work, customer credits, and missed deadlines can turn a short outage into a substantial business expense.

Use your own operating hours, revenue, payroll, and recovery costs to calculate a realistic hourly figure. Once you know that number, you can compare it with the cost of monitoring, tested backups, backup connectivity, and responsive IT support.

A two-hour outage may look manageable on paper. Your calculation will show whether it is an acceptable risk or an expensive problem waiting to happen.