The true cost of downtime (and how to measure it)
A pragmatic approach to understanding business impact beyond the obvious.
Ask what an hour of downtime costs and most companies reach for lost revenue. That is the visible number. It is rarely the largest one.
What the headline number misses
Recovery labour, contractual penalties, regulatory exposure, customer churn and reputational drag often dwarf the revenue line — and they play out over weeks, not hours.
Then there is the cost that appears on no spreadsheet: trust. A customer who cannot complete a payment, a partner who does not receive an order, a user who finds a service down — each quietly recalibrates how far they can rely on you. That loss is not restored by a backup; it is re-earned, and more slowly than it was lost.
A better measure
Model impact by process, not by system. Map the handful of processes that generate value, establish how long each can be interrupted before the cost curve bends, and prioritise resilience there.
Modelling by process also changes the questions you put to the technical team. Not “how reliable is this server?” but “how long can we run without billing, without production, without the sales channel — and what happens at hour eight versus hour two?”. The answers are rarely linear: many impacts stay manageable for a while, then spike as contracts, reporting duties or customer patience run out.
The goal is not to eliminate downtime. It is to know, in advance, exactly what it costs — and to have decided what you will do about it.
