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

Salary plus overhead divided by paid hours, in the currency above. 1,500 is an example, not a market figure: use your own.

Default is the FBIL reference rate of 2026-10-19. Edit it; nothing is fetched live.

h per dev per week
h per dev per week
h per dev per week
h per dev per week

46 allows for leave and holidays. Our assumption; change it.

%

A planning assumption. A code audit replaces it with a measured number.

%

A planning assumption: a rewrite brings its own new debt and bugs.

%

Our planning assumption, not a measured industry figure.

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 vs rewrite: the assumptions and what they give
RefactorRewrite
Effort (team-months)26 + 25% overrun
Cost of that effort₹27,60,000₹1,03,50,000
Lost hours removed50%80%
Saved a month₹1,29,375₹2,07,000
Pays back after21.3 months50 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?

Stripe, The Developer Coefficient, September 2018: a Harris Poll survey, self-reported, global
MeasureHours a weekShare of a 41.1-hour week
Maintenance in total (tech debt plus bad code)17.342%
Addressing technical debt13.533%
Fixing bad code3.89%

How to put a number on your technical debt

  1. 1
    Count 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.
  2. 2
    Enter 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.
  3. 3
    Estimate 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.
  4. 4
    Read 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?
Count the hours developers lose each week to debt (slow builds, flaky tests, rework from fragile code, manual deploys), multiply by team size and hourly cost, and scale by working weeks. That gives a monthly and yearly cost in developer time. It is a floor: it leaves out delayed features, lost customers and outages.
Is this a good estimate for a team of three developers?
The arithmetic is the same at any size, but small teams have noisier numbers. One slow deploy process or one flaky suite can account for most of the loss, so look at the biggest of the four categories first.
When is a rewrite better than a refactor?
When the code cannot be changed safely in pieces, for example the language or framework is end of life, or no one can build it any more, and the savings are large enough to pay back the effort and the overrun. If a refactor pays back sooner on the same assumptions, it usually wins.
What does Stripe's Developer Coefficient say about developer time?
In September 2018 Stripe reported that developers in its survey spent 17.3 hours a week on maintenance, made up of 13.5 on technical debt and 3.8 on bad code, in a 41.1-hour week. It is self-reported and global, so it is context for your own numbers, not a benchmark.
Can the cost of technical debt be zero?
No. Every codebase has some drag, and removing all of it is not worth the effort. The question is whether your lost share is moderate or severe and whether a fix pays back within a period you can plan for.
Why is the rewrite overrun a separate input?
Because a rewrite has to match the old system's behaviour, including behaviour no one remembers, while the business keeps moving. Our 25% default is a planning assumption, not a measured industry figure; set it to what your team has experienced.

Sources

Related tools

See all 135 free tools

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