Industry Research
Accumulated software technical debt in the United States
Consortium for Information and Software Quality (CISQ), 2022
The Cost of Technical Debt in 2026
What is technical debt costing your organization? This site aggregates every credible data point from CISQ, McKinsey, Stripe, DORA, and Deloitte into one research hub for engineering leaders.
Updated 14 June 2026
What is your team actually paying for tech debt?
CISQ's $1.52T figure is the macro. Your number is the time your engineers lose to debt × your loaded salary × your team size. Set yours, see the paydown-sprint ROI.
How we get to these numbers ↓
- $1.52T national figure: CISQ "The Cost of Poor Software Quality in the US" 2022 report puts accumulated US software technical debt at $1.52T, part of $2.41T in total poor-software-quality cost that year.
- Loaded salary: US software engineer median (~$130k) + 30% benefits + 12% overhead = ~$185k loaded. Adjust for your geography and seniority mix. Sources: Bureau of Labor Statistics Occupational Employment Statistics, Stripe pay benchmarks.
- % time on debt: Stripe Developer Coefficient 2018 found engineers spend ~33% of time on tech debt and bad code. Stack Overflow Developer Surveys 2022-2025 show 20-30% consistent. Set your team's honest number — most are within 15-35%.
- Paydown reclaim assumptions: Empirical observations from Refactoring (Fowler 2nd ed) + Accelerate (Forsgren et al). Heuristic, not a model.
- Risk-adjusted catastrophic cost: rough $25k/engineer/year heuristic for medium-severity. Real number depends on incident history; use this as a placeholder, not a forecast.
The Four Cost Pillars
Productivity Cost
Engineers spend roughly a third of their week on technical debt, about 13.5 hours per engineer, rising to 17.3 hours once all maintenance is counted, lost to workarounds and rework rather than building features.
Read the research →Source: Stripe Developer Coefficient
Hidden Costs
Every engineer who leaves costs $80K-$200K in recruiting, onboarding, and lost productivity. Technical debt is one of the top reasons senior engineers quit.
See the full breakdown →Source: SHRM, Stack Overflow Developer Survey
Security Cost
Defect density rises 31% per standard-deviation increase in the debt-to-code ratio. Outdated dependencies are the leading supply chain attack vector.
Explore the security data →Source: American Impact Review, 2026
Organizational Cost
McKinsey estimates 20-40% of IT budgets are consumed by technical debt maintenance. For large enterprises, this represents hundreds of millions annually.
View all statistics →Source: McKinsey Technology Trends
Key Findings
Total cost of poor software quality in the US, with technical debt as the largest contributor.
CISQ, 2022
Average time each engineer spends on maintenance and technical debt rather than new development.
Stripe Developer Coefficient
Velocity reduction in high-debt codebases, compounding delivery delays across every sprint.
Industry benchmarks
Annual growth rate of unaddressed technical debt, creating a compound interest effect on engineering costs.
CAST Software
Typical break-even on sustained debt remediation, driven by velocity recovery within the first 8-16 weeks.
Stripe Developer Coefficient + DORA Accelerate
How Technical Debt Compounds
Technical debt behaves like financial debt with compound interest. Research from CAST Software shows that unaddressed debt grows at 15-25% annually. A codebase with $500K in technical debt today will carry $800K-$1M in debt within three years if left unmanaged. The compounding effect accelerates as new code is built on unstable foundations, and each workaround becomes a foundation for the next.
| Year | At 15% Growth | At 20% Growth | At 25% Growth |
|---|---|---|---|
| Year 1 | $500,000 | $500,000 | $500,000 |
| Year 3 | $661,000 | $720,000 | $781,000 |
| Year 5 | $874,000 | $1,037,000 | $1,221,000 |
Based on CAST Software compound growth research. See Hidden Costs for the full breakdown of compounding mechanisms.
Engineering Practitioner Library
Tactical, code-aware pages an engineering manager or staff engineer can hand to a manager when quantifying a specific tech-debt category. By debt type, language stack, measurement framework, and refactor strategy.
By Debt Type
By Language / Stack
By Measurement Framework
Frequently Asked Questions
How much does technical debt cost on average?
The Consortium for Information and Software Quality (CISQ) estimates accumulated US software technical debt at $1.52 trillion, a major component of the $2.41 trillion annual cost of poor software quality (2022). At the organizational level, McKinsey research shows 20-40% of IT budgets are consumed by debt-related work. For individual teams, the cost typically ranges from $150K-$500K per engineer per year depending on codebase maturity and debt severity.
What percentage of developer time is spent on technical debt?
The Stripe Developer Coefficient study found that engineers spend an average of 17.3 hours per week on maintenance and technical debt, about 42% of the 41.1-hour work week the report measured, of which roughly 13.5 hours (a third of all engineering time) is technical debt specifically. In high-debt codebases, this figure can reach 40-60% of total engineering capacity. The DORA research program confirms that teams with high technical debt show significantly lower deployment frequency and higher lead times.
How do you calculate the cost of technical debt?
The most practical approach combines three inputs: the percentage of engineering time spent on debt-related work (measurable via cycle time analysis), the fully-loaded cost per engineer ($140K-$200K in the US), and the opportunity cost of delayed features. Multiply the debt time percentage by team cost to get the direct spend, then add estimated revenue impact from slower delivery. Our companion site techdebtcalculator.com provides interactive calculators for this.
What is the ROI of fixing technical debt?
Returns on debt remediation are real but vary widely with the kind of debt and the team's velocity recovery profile. Sustained refactoring efforts typically pay back within 4 to 12 months through restored feature delivery speed; teams that reduce technical debt often report 30-50% improvement in feature delivery within 8-16 weeks of sustained investment (Stripe Developer Coefficient and DORA Accelerate State of DevOps research describe this pattern). Architectural debt usually compounds faster than other categories, so its remediation tends to show the strongest velocity recovery.
Does technical debt affect security?
Technical debt is a significant security vulnerability multiplier. Outdated dependencies with known CVEs are the most common supply chain attack vector, and high-debt codebases take 2-3x longer to apply security patches. The IBM Cost of a Data Breach 2025 report shows the global average breach costs $4.44 million, and organizations with high technical debt face both higher breach probability and longer detection and containment times.
How does technical debt impact recruiting and retention?
Stack Overflow Developer Surveys consistently rank code quality as a top-5 factor in job satisfaction. Senior engineers evaluate codebases during interviews and reject offers when they identify high debt levels. Replacing a mid-senior engineer costs 50-150% of annual salary (SHRM data), and high-debt organizations report 40-60% longer time-to-fill for engineering roles. The best engineers leave first, creating a talent quality spiral.