Free tool
What do bugs caught in production actually cost you?
Most teams know their defects are expensive but have never put a number on them. Enter five figures you already know and see the annual bill, where it goes, and how much of it moving detection earlier would recover. No signup, and every assumption is shown.
Your numbers
Rough figures are fine. The order of magnitude is what matters.
Everyone whose week a production defect can interrupt.
Production deploys, not merges to main.
Per month, counting anything users or support noticed.
Just the engineer writing the fix, from report to deploy.
Salary, benefits and overhead, in USD.
Defects caught in production cost you
per year, across 216 defects
That is 4.5 defects escaping to users on every release you ship.
Where it goes
Each production defect consumes 10.0 hours once everything around the fix is counted.
6.0 hours per defect, the figure you entered.
2.5 hours per defect, spent by people who aren't writing the fix.
1.5 hours per defect of planned work displaced and picked back up.
What moving detection earlier recovers
A defect caught before release costs a fraction of the same defect caught by a user. Drag the share you think a disciplined pre-release process would catch.
Recoverable each year
91 defects never reach users, freeing 744 engineering hours.
Want the full breakdown?
We'll email these numbers with every assumption spelled out, so you can put them in front of your team without re-deriving them.
Why late defects cost so much more
A defect found by a developer while the code is still fresh is a small correction. The same defect found by a user is an incident: someone triages it, someone reproduces it, someone writes the fix, someone re-tests it, and someone ships an unplanned release. Each of those steps pulls a person off the work they had planned.
That is why this calculator does not stop at the hours it takes to write the fix. The fix is usually the smallest part of the bill, and it is the only part most teams count when they estimate what a production bug costs them.
The number that tends to land hardest is not the annual total. It is the defects escaping on every release, and the fraction of your team's capacity that unplanned defect work quietly consumes. Both are on the results above.
Questions about the model
How is the cost of a production bug calculated?
Annual cost = defects per month × 12 × (your hotfix hours + 2.5 hours of triage, re-testing and emergency release + 1.5 hours of displaced planned work) × your loaded hourly rate. Every constant is printed on the page, and the only inputs are the five numbers you enter.
Why does a production defect cost more than the time it takes to fix?
The engineer writing the fix is rarely the only cost. A production defect also consumes triage, reproduction, QA re-verification and an unplanned release, and it displaces whatever planned work the team was doing. Counting only the fix typically understates the real bill by two to three times.
What does it cost to catch the same defect before release?
Far less, because there is no incident, no emergency release and no context switch, just a ticket fixed in the sprint it was written in. The calculator models a pre-release defect at 18% of the cost of the same defect in production, and the recoverable figure is the difference between the two, not the whole production cost.
Do you need my email to see the results?
No. The results appear as you type and nothing is gated. If you want the full breakdown with every assumption written out, you can optionally have it emailed to you.