Outage / Downtime Cost Calculator
Per-minute revenue, productivity and reputation cost — the number to fund reliability work with.
Set your annual online revenue, team size and a realistic churn rate. We compute downtime cost per minute, per hour and per "one bad incident" — the budget you should be allowed to spend on reliability.
Sum of pager, war-room and the postmortem cycle that follows.
Share of impacted users who never return. 0.1–1% is the usual range for a visible outage.
Churn cost is the long-tail bite — many teams under-count it because the user is gone before they ever show up in a churn report.
Runs entirely in your browser — nothing you enter is sent to a server.
Need this for real, on your stack?
These free tools are a taste of how we think. We’re a senior software team across Romania & Pakistan that ships deep technical work — platforms, infra, data and the gnarly bits in between.
Talk to our engineers →What we model
Three components: lost revenue (annual ÷ business-hours-per-year, scaled to the outage window), engineering time (responders + post-incident review hours × fully-loaded cost), and customer churn (a small fraction of impacted users never come back, modelled as their lifetime value).
Pair with SLOs
This is the number to put next to your SLO. "An extra nine costs $X to engineer and saves $Y per year" is the conversation that actually funds reliability.
Built by WeWorkWorldwide — a senior software team in Romania & Pakistan that ships deep technical work. Need this turned into something production-grade for your stack? Talk to our engineers →