When systems go down, most businesses argue about whose fault it is instead of asking the only question that matters: how much did this actually cost us? For most SMEs, the answer is far higher than the IT invoice that follows.
Multiple industry studies put small business downtime losses at €125 to €400 per minute once you factor in idle staff, lost revenue, and recovery work. For critical systems, even modest firms can see €100,000 per hour in impact. Yet most Malta business owners cannot show that figure in a board pack or bank meeting.
This guide gives you a straightforward way to calculate the real cost of IT downtime for a small business, using formulas you can plug into a spreadsheet today.
#What counts as IT downtime for a small business?
In practice, for a Malta SME, IT downtime usually means:
- Internet outage blocking access to cloud systems
- Accounting or ERP system unavailable (Sage, Xero, custom apps)
- Email or Microsoft 365 down
- Payment terminals or e-commerce website offline
- Ransomware locking systems
There are two forms. Full outages stop you operating entirely. Micro-outages — systems working slowly or unreliably — are often more costly over time because they go untracked. Ten minutes here, twenty minutes there, multiplied across a year, adds up fast.
#Core formula: how to calculate the real cost of IT downtime
You do not need complex analytics. You need a consistent, defensible way to estimate.
Total downtime cost = Idle staff cost + Lost revenue + Recovery cost + Risk and reputation impact
Here is how to put numbers on each part.
#1. Idle staff cost
Idle staff cost = Average hourly staff cost × Affected staff × Hours of impact
Use the total cost to the company — not just basic pay. Include employer contributions and any bonuses.
Example — small Malta office
- Average loaded staff cost: €18/hour
- 12 staff cannot work properly for 3 hours during an internet outage
Idle staff cost = €18 × 12 × 3 = €648
#2. Lost revenue
Lost revenue = Average hourly revenue × Hours systems were unable to generate income
Average hourly revenue = Annual revenue ÷ Business hours per year
Example — service business with €1.5M annual revenue
- 2,000 business hours per year (8 hours/day, 5 days/week, 50 weeks)
- Average hourly revenue = €1,500,000 ÷ 2,000 = €750/hour
- 4-hour outage on billing and quoting system → Lost revenue = €750 × 4 = €3,000
If some revenue can be recovered later, use half this figure and document the assumption.
#3. Recovery cost
Recovery cost = IT labour + Staff overtime + Third-party tools or services
Example — ransomware cleanup on a small network
- External IT support: 10 hours at €90/hour = €900
- Staff overtime re-entering one day of orders: 4 staff × 3 hours × €18 = €216
Total recovery cost ≈ €1,116
#4. Risk and reputation impact
For regulated sectors in Malta and the EU, this becomes very real: customer loss after a bad outage, refunds, SLA penalties, data protection fines, or extra security audits following an incident.
A practical way to estimate it: if this exact outage happened every quarter, what annual revenue would you expect to lose because clients stop trusting you? Divide that by four.
The cost you can quantify is almost always smaller than the cost you cannot. Reputation damage compounds quietly — one missed deadline, one payment failure, one client who tells five others.
#A full example: 3-hour outage for a 20-person SME
| Cost component | Calculation | Amount |
|---|---|---|
| Idle staff (20 staff × €20/hr × 3 hrs) | Productivity lost during outage | €1,200 |
| Lost revenue (€1,000/hr × 3 hrs) | Based on €2M annual revenue / 2,000 hrs | €3,000 |
| Recovery (IT + staff overtime) | 3 hrs IT at €90 + 20 staff × 2 hrs catch-up | €1,070 |
| Reputation and risk (conservative) | One lost contract estimated over the year | €2,000 |
| Total | €7,270 |
Three or four incidents like this per year means you are quietly burning €20,000 to €30,000 on downtime with no line item in the budget.
#Downtime cost vs managed IT cost
| IT setup | Typical annual cost | Estimated annual downtime cost | Risk level |
|---|---|---|---|
| Break-fix only | €0–€6,000 | €15,000–€60,000 | High |
| Basic managed IT | €12,000–€24,000 | €5,000–€20,000 | Medium |
| Managed IT + backup and continuity | €24,000–€40,000 | €1,000–€10,000 | Lower |
One or two serious outages typically cost more than a full year of proper IT management.
#How to calculate your own downtime cost
- List your critical systems. Identify the 5–10 systems where downtime stops revenue: accounting, POS, email, ERP, booking platform.
- Get your basic numbers. Annual revenue, business hours per year, average fully loaded hourly staff cost, and your IT provider's emergency call-out rate.
- Build a simple spreadsheet. Columns for: outage duration, affected staff, hourly revenue, idle staff cost, lost revenue, recovery hours. Add formulas based on the ones above.
- Model three scenarios. A 1-hour internet outage, a 4-hour system outage, and a 2-day cyber incident. Use conservative assumptions.
- Compare to your IT budget. If a single realistic incident costs more than your annual prevention spend, that is a strong case for tightening things up.
If you want to stop worrying about IT downtime, get in touch — we work with Malta businesses to make IT one less thing on your list.