Downtime cost calculator.
A rough, honest estimate of what an hour of downtime actually costs, lost productivity, lost revenue, and what it adds up to over a year if it keeps happening.
What an hour of downtime really costs.
When IT goes down, the obvious cost is the outage itself, but the real cost is almost always bigger than it looks, because it's made of pieces that don't show up on an invoice: employees who are paid but not producing, sales that don't happen while a system is unreachable, and a multiplying effect if the same kind of outage keeps recurring.
This calculator adds those pieces up using your own numbers. It multiplies the number of employees affected by their fully-loaded hourly cost, wages plus benefits and overhead, not just take-home pay, to get lost labor cost, adds any revenue directly at risk per hour if the outage stops sales rather than just slowing an office down, and multiplies by how many hours the incident lasted. If you enter how often incidents like this tend to happen, it also shows a rough annualized cost, what this adds up to over a year if nothing changes.
The number that comes out is a floor, not a ceiling. It doesn't include reputational damage, missed deadlines, compliance exposure, or the cost of recovering data that was never backed up, all real, all harder to put a clean number on than lost labor and lost sales, which is exactly what this tool focuses on.
Include wages plus benefits/overhead, not just take-home pay, this is usually higher than people expect.
Leave at 0 if downtime doesn't directly stop sales (e.g. a back-office outage vs. a storefront POS outage).
The middle number is what this specific incident is estimated to have cost, the annual figure only appears if you entered how often incidents like this occur.
This is a simplified estimate, it doesn't account for reputational damage, missed deadlines, compliance exposure, or the cost of recovering data that wasn't backed up. Those are real, but harder to put a number on than lost labor and lost sales.

