What is a technical debt calculator?

A technical debt calculator estimates how much accumulated technical debt an organization carries and what it would cost to remediate. This one rates six debt dimensions — legacy code, dependency debt, security debt, documentation debt, architecture debt, and test debt — and returns a 0–100 debt health grade plus an estimated remediation range in engineer-months and dollars.

How is the technical debt cost estimated?

For each dimension you pick a severity band (None to Severe), which maps to a 0–100 health value. The shortfall below a 'healthy' bar (75/100) is converted into engineer-months using a dampened points-per-engineer-month factor and weighted by dimension, then multiplied by your fully-loaded cost per engineer-month. The result is an explicit low/base/high range — never a single false-precision number — and confidence rises with how many dimensions you rate.

Is the calculator anonymous?

Yes. It runs entirely in your browser and requires no signup. Nothing is sent anywhere unless you choose to enter your email to receive a detailed breakdown.

What are the dimensions of technical debt?

Legacy Code (old, unowned, risky-to-change code); Dependency Debt (outdated or end-of-life libraries and runtimes); Security Debt (unremediated vulnerabilities); Documentation Debt (missing or stale docs for critical systems); Architecture Debt (coupling, drift, and fragility); and Test Debt (low automated coverage on critical paths).

How accurate is the dollar estimate?

It is a directional estimate, not a quote. It deliberately reports a range and surfaces its assumptions (cost per engineer-month, team size, the healthy bar). Treat it as a starting point for prioritization and budgeting — for a measured figure, ShipReady computes technical debt from your real repositories and clouds.

How do I reduce technical debt?

Start with the highest-severity drivers. Common high-leverage moves: strangler-fig refactors on high-churn legacy modules, automated dependency updates, severity-based SLAs to burn down the security backlog, documenting critical systems, defining target architecture seams, and adding tests where defects concentrate.

3 min · no signup · anonymous

Technical Debt Calculator

Rate six debt dimensions and get a debt health grade plus an estimated remediation cost — engineer-months and a low/base/high dollar range — instantly, in your browser.

What is technical debt?

Technical debt is the implied future cost of rework from expedient choices made earlier — accumulated across code, dependencies, architecture, security, documentation, and tests. Left unmanaged it slows delivery, raises change-failure risk, and becomes a red flag in investor and acquisition diligence. This calculator turns a quick severity rating across the six dimensions below into a health grade and an estimated remediation range.

Legacy Code:Old, poorly understood, or unowned code that is risky to change.
Dependency Debt:Outdated or end-of-life libraries, frameworks, and runtimes.
Security Debt:Unremediated vulnerabilities and security findings piling up.
Documentation Debt:Missing or stale docs for critical systems and runbooks.
Architecture Debt:Coupling, drift, and fragility that make change risky.
Test Debt:Low automated coverage on critical paths.

How much of your codebase is legacy, poorly understood, or unowned?

Old, poorly understood, or unowned code that is risky to change.

How outdated or end-of-life are your dependencies and runtimes?

Outdated or end-of-life libraries, frameworks, and runtimes.

How large is your backlog of unremediated security vulnerabilities?

Unremediated vulnerabilities and security findings piling up.

How out-of-date or missing is documentation for your critical systems?

Missing or stale docs for critical systems and runbooks.

How much architectural coupling, drift, or fragility do you carry?

Coupling, drift, and fragility that make change risky.

How much of your critical code lacks automated test coverage?

Low automated coverage on critical paths.

Cost assumptions

These tune the dollar estimate. Sensible defaults are used if you leave them.

Loaded cost / engineer-month (USD)

Engineering team size (optional)

0 of 6 rated

How the estimate is calculated

Each dimension’s severity maps to a 0–100 health value. The shortfall below a healthy bar (75/100) is converted into engineer-months using a dampened points-per-engineer-month factor, weighted by dimension (security and the structural dimensions weigh most), and optionally scaled by team size. Multiplying by your loaded cost per engineer-month yields a low/base/high dollar range. Unrated dimensions are omitted rather than guessed, and the output is always a range — never false precision — mirroring the ShipReady principle of never fabricating data.

Frequently asked questions

What is a technical debt calculator?: A technical debt calculator estimates how much accumulated technical debt an organization carries and what it would cost to remediate. This one rates six debt dimensions — legacy code, dependency debt, security debt, documentation debt, architecture debt, and test debt — and returns a 0–100 debt health grade plus an estimated remediation range in engineer-months and dollars.
How is the technical debt cost estimated?: For each dimension you pick a severity band (None to Severe), which maps to a 0–100 health value. The shortfall below a 'healthy' bar (75/100) is converted into engineer-months using a dampened points-per-engineer-month factor and weighted by dimension, then multiplied by your fully-loaded cost per engineer-month. The result is an explicit low/base/high range — never a single false-precision number — and confidence rises with how many dimensions you rate.
Is the calculator anonymous?: Yes. It runs entirely in your browser and requires no signup. Nothing is sent anywhere unless you choose to enter your email to receive a detailed breakdown.
What are the dimensions of technical debt?: Legacy Code (old, unowned, risky-to-change code); Dependency Debt (outdated or end-of-life libraries and runtimes); Security Debt (unremediated vulnerabilities); Documentation Debt (missing or stale docs for critical systems); Architecture Debt (coupling, drift, and fragility); and Test Debt (low automated coverage on critical paths).
How accurate is the dollar estimate?: It is a directional estimate, not a quote. It deliberately reports a range and surfaces its assumptions (cost per engineer-month, team size, the healthy bar). Treat it as a starting point for prioritization and budgeting — for a measured figure, ShipReady computes technical debt from your real repositories and clouds.
How do I reduce technical debt?: Start with the highest-severity drivers. Common high-leverage moves: strangler-fig refactors on high-churn legacy modules, automated dependency updates, severity-based SLAs to burn down the security backlog, documenting critical systems, defining target architecture seams, and adding tests where defects concentrate.

Glossary

Technical debt: The implied future cost of rework caused by choosing an expedient solution now instead of a more robust one — accumulated across code, dependencies, architecture, security, docs, and tests.
Remediation exposure: An estimated range of effort (engineer-months) and cost (dollars) to bring technical debt back to a healthy bar — expressed as low/base/high, not a single number.
Engineer-month: One engineer working for one month — the unit this calculator uses to size remediation effort before converting it to a dollar range via your loaded cost.
Loaded cost: The fully-loaded monthly cost of an engineer (salary plus benefits, overhead, and tooling), used to translate remediation effort into dollars.

Want technical debt measured from real data?

This estimate is self-reported. ShipReady Metrics computes Technical Debt — and eight other domain scores — from the repositories and clouds you already use, so your board sees evidence, not opinion.

Get your trial report See the methodology