Technical debt calculator
This calculator turns the hours your developers lose each week to slow builds, flaky tests, bug rework and manual deploys into a monthly and yearly cost. It then compares the payback of a refactor and a rewrite with the assumptions shown, and puts your lost share beside Stripe's 2018 Developer Coefficient survey.
Updated
Technical debt costs you
₹2,58,750 a month
₹31,05,000 a year, about $32,764 in dollars. 1.1 developers' worth of time.
- Hours lost a week, whole team
- 45 h7.5 h per developer
- Your lost share of a paid week
- 18.8%Stripe's 2018 survey: 42% on maintenance, bad code and debt (self-reported, global)
- Refactor or rewrite, on these assumptions
- RefactorRefactor comes out ahead on these assumptions: it pays back sooner and nets more over 36 months.
| Refactor | Rewrite | |
|---|---|---|
| Effort (team-months) | 2 | 6 + 25% overrun |
| Cost of that effort | ₹27,60,000 | ₹1,03,50,000 |
| Lost hours removed | 50% | 80% |
| Saved a month | ₹1,29,375 | ₹2,07,000 |
| Pays back after | 21.3 months | 50 months |
| Net over 36 months | ₹18,97,500 | -₹28,98,000 |
- The four hour fields, the effort in team-months and the percentages are your inputs. Our defaults are example values and planning assumptions, not measurements.
- This counts only developer time. Delayed features, churn from bugs and the risk of a stalled rewrite are real costs it does not price.
- A refactor and a rewrite are not exclusive: most teams refactor the parts that hurt and keep the rest.
Code Audit: from ₹90,000 / $950
The refactor and rewrite numbers above are guesses until someone reads the code. A code audit returns findings with file and line, a fix, refactor or rebuild verdict per area, with the effort for each, and a fixed-price quote.
How does the calculator price technical debt?
Technical debt shows up as time: builds you wait for, tests you rerun, bugs you fix twice and releases someone has to watch. You enter the hours each developer loses to each of the four in an average week. The calculator multiplies by team size, working weeks and your hourly cost, and gives a monthly and a yearly figure.
The refactor-versus-rewrite block puts effort next to payback. Effort is in team-months, the whole team's time for a month, priced from your hourly cost. Each option removes a share of the lost hours, so each saves a share of the monthly cost. Payback is effort cost divided by the monthly saving. The rewrite is increased by the overrun you choose, because a rewrite carries more schedule risk than a targeted refactor.
Every percentage there is an assumption you can change, and the page says so. The calculator does not measure your code, so use the verdict to decide what to measure next, not as a decision.
monthly cost = hours lost per dev per week × developers × working weeks ÷ 12 × hourly cost payback = effort cost ÷ (monthly cost × share removed)
How big is the problem, compared with a survey?
| Measure | Hours a week | Share of a 41.1-hour week |
|---|---|---|
| Maintenance in total (tech debt plus bad code) | 17.3 | 42% |
| Addressing technical debt | 13.5 | 33% |
| Fixing bad code | 3.8 | 9% |
How to put a number on your technical debt
- 1Count hours honestlyAsk three developers how many hours a week they lose to each of the four categories and use the average. Round up rather than down; people forget the small waits.
- 2Enter team size and hourly costUse fully loaded cost: salary plus overheads, divided by the paid hours. Choose rupees or dollars and check the exchange rate.
- 3Estimate the two fixesAsk your team how many team-months a refactor and a rewrite would take and what share of the pain each would remove. Treat the defaults as a prompt.
- 4Read payback, not just the totalA large monthly cost with a three-year payback is a different decision from a smaller one that pays back in four months.
Frequently asked questions
How do you calculate the cost of technical debt?
Is this a good estimate for a team of three developers?
When is a rewrite better than a refactor?
What does Stripe's Developer Coefficient say about developer time?
Can the cost of technical debt be zero?
Why is the rewrite overrun a separate input?
Sources
- Stripe, The Developer Coefficient (September 2018) (checked 11 Nov 2026)
- FBIL reference rates, as shown by the RBI (checked 11 Nov 2026)
Need a custom dev tool for your team?
We build internal tools, dashboards, APIs, and SaaS platforms. If you can describe it, we can ship it.
Built by CountryDevs · No signup · No ads · We count visits, never what you enter