The Real Cost of Downtime: A Business Case for Your Board

The Real Cost of Downtime: A Business Case for Your Board

You're in a board meeting. There's been a 2-hour outage.

Finance director asks: "How much did that cost us?"

You don't have a good answer. You know it was bad, but you can't quantify it.

This is a problem. Because when you ask for CHF 500K to invest in redundancy, disaster recovery, and reliability infrastructure, your board asks the same question: "What's the ROI?"

If you can't calculate the cost of downtime, you can't make a financial case for preventing it.

This article walks through the calculation. By the end, you'll have a number you can present to your board: "Every hour of downtime costs us CHF X. Therefore, investing CHF Y in reliability infrastructure has a payback period of Z months."

The Obvious Costs

Most companies only count the most obvious cost: Lost sales during the outage.

For an e-commerce company:

• Annual revenue: CHF 50 million
• Daily revenue: CHF 137,000
• Hourly revenue: CHF 5,700
• 2-hour outage: CHF 11,400 in lost revenue

This is real, but it's not the whole story.

The Hidden Costs (Usually Larger)

1. Lost Productivity of Affected Users

If your application is a business tool (Salesforce, ERP, accounting software), users can't work during downtime.

Example: SaaS CRM used by 100 sales reps

• Average sales rep salary: CHF 80,000/year
• Hourly cost: CHF 40/hour
• 2-hour outage: 100 reps × CHF 40/hour × 2 hours = CHF 8,000
• Plus they need to catch up (additional 4 hours of cleanup): CHF 16,000 more
• Total productivity cost: CHF 24,000

2. Customer Churn and Reputation Damage

Downtime damages customer relationships.

Typical customer behavior after a major outage:

• High-touch customers (50% of revenue): Don't churn immediately, but increase risk of future churn
• Commodity customers (25% of revenue): Evaluate alternatives, 5-10% churn within 30 days
• Enterprise customers (25% of revenue): File complaints, expect service credits, increase scrutiny

Calculating churn cost:

• Assume 5% of customers churn within 30 days
• Average customer lifetime value: CHF 15,000
• Churn cost: 50,000 customers × 5% × CHF 15,000 = CHF 37.5 million

That's catastrophic. But if we assume a 2-hour outage causes only 0.5% churn:

• Churn cost: 50,000 × 0.5% × CHF 15,000 = CHF 3.75 million

3. Customer Support Escalation

Support volume spikes during outages.

During a 2-hour outage:

• Normal support volume: 20 tickets/hour = 40 tickets over 2 hours
• Outage support volume: 200 tickets/hour = 400 tickets over 2 hours
• Plus 6 hours of overflow after outage as backlog clears

Cost calculation:

• Support staff: 5 agents at CHF 50/hour
• Normal 2-hour cost: CHF 500
• Outage 2-hour cost: CHF 5,000
• Cleanup overflow (6 hours): CHF 1,500
• Escalation (customers angry, longer calls): $2,000
• Total support cost: CHF 8,500

4. Incident Response Costs

Your team spends time responding to the outage.

During the incident:

• 5 engineers on-call: 2 hours
• 2 manager/leads coordinating: 2 hours
• CTO/VP involved: 0.5 hours
• Total engineer hours: 11.5 hours

Cost:

• 11.5 hours × (average cost per engineer hour): CHF 75/hour = CHF 863

5. Post-Incident Investigation

After the outage, you investigate root cause.

Typical post-incident work:

• Root cause analysis: 4-6 hours
• Documentation: 2-3 hours
• Engineering improvements: 20-40 hours
• Total: 30-50 hours

Cost:

• 40 hours × CHF 75/hour = CHF 3,000

6. Compliance and SLA Penalties

If you have SLA commitments, you owe credits.

Example SLA:

• 99.5% uptime commitment
• CHF 10K penalty per 0.1% below SLA
• 2-hour outage on system running 99.95% SLA baseline
• Drops to 99.93% SLA
• Penalty: CHF 20,000

7. Lost Business Opportunities

During downtime, you can't sign new customers or close deals in progress.

Example:

• Sales team is in middle of 5 deal closures
• Total deal value: CHF 2 million
• 2-hour delay could result in 1 deal lost (20% probability)
• Expected loss: CHF 400,000

This is harder to quantify but real.

Building Your Downtime Cost Model

Here's a framework to calculate your specific downtime cost:

For each of your critical systems, estimate:

Example company numbers:

• Lost revenue: CHF 5,700/hour
• Productivity loss: CHF 8,000/hour
• Support escalation: CHF 1,500/hour
• Customer churn risk: CHF 5,000/hour (conservative)
• Incident response: CHF 500/hour
• Post-incident (amortized): CHF 1,500/hour
• SLA penalties: CHF 2,000/hour
• Total: CHF 24,200/hour

A 2-hour outage costs this company CHF 48,400.

A 4-hour outage costs CHF 96,800.

The Financial Case for Reliability Investment

Once you know your downtime cost, you can justify reliability investments.

Example: Disaster Recovery Infrastructure

Your team proposes: CHF 500K infrastructure + CHF 50K/year ops

Reliability improvement:

• Current system: 99.5% uptime (3.7 hours downtime/year)
• With DR infrastructure: 99.99% uptime (0.36 hours downtime/year)
• Improvement: 3.34 fewer hours of downtime/year

Financial benefit:

• 3.34 hours × CHF 24,200 = CHF 80,828/year in downtime cost avoided

ROI calculation:

• Year 1: CHF 80,828 benefit - CHF 550K cost = -CHF 469K net (investment year)
• Year 2: CHF 80,828 benefit - CHF 50K cost = +CHF 30,828 net
• Year 3: CHF 80,828 benefit - CHF 50K cost = +CHF 30,828 net
• Payback period: 6 years
• 10-year NPV: CHF 65,228

This is a weak case financially (6-year payback), so you need another angle:

• Reputation value (retention, future revenue)
• Competitive advantage (market cap impact)
• Compliance requirements

The Board Presentation

Here's how to present this to your board:

1. Lead with the number: "A single outage costs us CHF 24,200/hour in lost revenue, support costs, and customer churn risk."

2. Show historical impact: "In the last year, we experienced 8 hours of downtime. That's CHF 193,600 in direct cost, not including reputation damage and customer churn."

3. Show industry benchmarks: "Amazon reported that a 1-hour outage costs them USD 5-7 million. Our hourly cost of CHF 24K puts us in line with businesses our size."

4. Present the investment case: "Investing CHF 500K in disaster recovery infrastructure would reduce downtime from 3.7 hours/year to 0.36 hours/year. That's a CHF 80,828/year benefit, with payback in 6 years."

5. Add strategic value: "Beyond financials, reliable infrastructure is a competitive advantage. It improves customer retention, enables us to win deals against less-reliable competitors, and gives us confidence to scale."

Avoiding Common Mistakes in This Calculation

Mistake 1: Only Counting Lost Revenue

The most common mistake: Only counting the transactions you lose during downtime.

Problem: For businesses with thin margins (like SaaS), lost revenue understates actual cost.

Solution: Include all costs: productivity, support, reputation, churn risk.

Mistake 2: Being Too Conservative

Some teams assume "nobody will churn over a 2-hour outage."

Problem: This leads to undervaluing reliability.

Solution: Base churn assumptions on actual data (survey customers, analyze historical churn).

Mistake 3: Ignoring Indirect Costs

The most expensive cost is often reputation damage and customer churn.

Solution: Model this explicitly, even if you have to estimate.

Mistake 4: Underestimating Investigation Time

Post-incident investigation and engineering often takes 40+ hours.

Solution: Track actual post-incident time, include in calculations.

Using This Number Operationally

Once you know your downtime cost, use it:

1. For investment decisions:

• "This reliability project costs CHF 100K and prevents 1 hour of downtime/year"
• "That's CHF 24K of value, so ROI is 24%, payback is 4 years"
• Reject projects with poor ROI

2. For on-call rotation decisions:

• If on-call engineer burn-out causes missed incident response (adding 30 min to MTTR)
• That's CHF 12,100 in additional downtime cost
• Worth investing CHF 50K/year in better on-call tooling/processes

3. For customer communication:

• If customer complains about reliability, show them the improvement plan
• "We experienced 2 hours of downtime costing us CHF 48K. We're investing in redundancy to prevent this."

4. For hiring and staffing:

• "A 2-hour incident requires 3 engineers for 4 hours each (12 hours total)"
• "The cost of that incident is CHF 48K, cost of engineering is CHF 900"
• "Investing in better monitoring and automation would be 20:1 ROI"

The Bottom Line

Downtime has a real, calculable financial cost.

For most companies, that cost is much larger than they assume.

Once you quantify it, you can make rational financial decisions about reliability investment.

Your board won't approve a CHF 500K infrastructure project based on "we need better reliability."

But they will approve a "CHF 500K project prevents CHF 80K/year in downtime cost (6-year payback, plus strategic benefits)."

Calculate your number. Use it.

It transforms reliability from a cost center to an investment with measurable ROI.

Related reading:

• SLA vs. Managed Services: Understanding Reliability Commitments
• Disaster Recovery and Kubernetes: Building Resilient Systems

Ready to build reliable infrastructure? Hidora helps enterprises design resilient systems: Infrastructure Consulting · Managed Services · Disaster Recovery Solutions