Tech debt service ratio: borrowing the financial vocabulary
CFOs operate fluently in financial-ratio language. Applying financial-ratio framing to engineering metrics produces immediately legible communication that survives the CTO-CFO translation gap. The Debt Service Ratio is the cleanest single example.
The 90-Second Answer
The tech debt service ratio is the percentage of engineering capacity consumed by debt-servicing work over total engineering capacity. Healthy range: 10-20%. Concerning: 20-30%. Above 30%: unsustainable and indicating a need for structural remediation. The metric is internally useful, immediately legible to a CFO, and trackable as a quarterly leading indicator.
The Source Metaphor
Where the Debt Service Coverage Ratio comes from
The Debt Service Coverage Ratio (DSCR) is a standard credit-analysis metric. In its consumer form, it measures the borrower's net operating income against debt-service obligations; ratios above 1.25 are conventionally lendable, ratios below 1.0 indicate insufficient income to service debt. The metric appears in mortgage underwriting, commercial-real-estate loan analysis, leveraged-buyout structuring, and corporate-bond rating methodology. Every CFO has worked with it; many CFOs have one as part of their existing covenant structure.
Ward Cunningham's 1992 WyCash technical-debt metaphor opened the door to using financial vocabulary for engineering decisions. The metaphor has been extended over the decades by Martin Fowler, Steve McConnell (Code Complete), Capers Jones (Software Quality Economics), and the CAST CRASH research programme. The debt-service-ratio specifically is a more recent extension that has gained traction among CFOs who want a familiar financial vocabulary applied to engineering.
The translation is exact in some dimensions and inexact in others. The exact dimension: the metric measures the burden of servicing existing debt against the resources available to service it. The inexact dimension: engineering capacity is not strictly analogous to operating income, and the ratio threshold conventions do not transfer directly from consumer credit. Useful precision exists; mathematical identity does not. CFOs typically accept this asymmetry once it is named.
The Tech Application
How to measure it specifically
The tech debt service ratio is calculated as the percentage of engineering capacity consumed by debt-servicing work, divided by total engineering capacity. The denominator is straightforward (total engineer-hours or engineer-months). The numerator requires definitional choices about what counts as debt-servicing work.
The methodology can be calibrated per company; the important property is consistency over time, not absolute precision against an external standard. A 22% ratio measured the same way every quarter is more useful than a perfect-methodology 23% ratio that cannot be tracked.
The Threshold Bands
What different ratio bands indicate
10-15%: healthy. A team operating at this ratio is in steady-state debt management. Some servicing is necessary (bugs, dependency upgrades, ongoing maintenance) but the capacity is not being consumed by accumulated debt. This band is achievable in well-architected systems with sustained platform investment, and it is the right long-term target for most software organisations.
15-25%: typical. The modal range across mid-stage SaaS companies. The team has accumulated some debt and is paying interest on it, but the burden is sustainable and does not crowd out new development materially. CFOs should expect this band; CTOs should not panic about being in it.
25-35%: concerning. The team is paying significant interest on accumulated debt. New feature velocity is materially impaired. Senior IC retention is at risk. The CFO conversation about funding remediation should be active. This band aligns with the McKinsey 25-42% drag range and is where most companies with significant debt positions sit.
35-50%: unsustainable. The team is consuming most of its capacity on debt servicing with little remaining for forward progress. The codebase is approaching the velocity-to-zero inflection covered on the technical insolvency page. Structural remediation is no longer optional. This band typically requires either a dedicated remediation programme funded out of the operating budget or a strategic decision to deprecate the affected system.
50%+: technical insolvency. The team cannot deliver meaningful forward progress through routine work. The only paths forward are rewrite, replacement, or deprecation. Reaching this band represents a failure of earlier-stage debt-servicing discipline, and the cost of cleanup typically exceeds the cost of the original work that was deferred.
The Related Vocabulary
Other financial metaphors that translate
Debt-to-Velocity Ratio. Analogous to Debt-to-Income. The accumulated debt position (in engineer-months of remediation required) divided by current engineering throughput (in engineer-months per quarter). A ratio above 8 quarters indicates a structural problem that cannot be addressed by current-period allocation; remediation requires either dedicated programme funding or strategic deprecation.
Credit Score. Analogous to FICO. A composite engineering-health score combining DORA-key performance band, debt service ratio, senior IC retention rate, and incident frequency. Some engineering organisations build internal versions of this score and report it quarterly; the metric is most useful as a trend indicator rather than an absolute benchmark.
Term Loan vs Revolving Credit. Analogous to the choice between scheduled refactor sprints and ongoing capacity allocation. A term-loan-style approach concentrates remediation work into a finite period; a revolving-credit-style approach distributes it across ongoing work. The choice has the same trade-offs as the financial version: term loans concentrate impact but require discipline to actually execute; revolving credit is easier to use but harder to track.
Restructuring. Analogous to corporate financial restructuring. The polite word for a major remediation programme, often coinciding with leadership changes. The vocabulary signals to the CFO that the work is structural rather than routine and that the timeline is longer. CFOs typically respond more receptively to a “restructuring” framing than to “refactoring”, despite the underlying work being similar.
Cross-Reference
Debt Service Ratio in the financial-framework stack
The Debt Service Ratio is one of four financial-framework treatments: CapEx vs OpEx (IRC §174), this page (debt service), technical insolvency, and enterprise value at exit. The vocabulary works alongside the existing site pages on the cost formula (the underlying calculation) and the debt quadrant (the prioritisation framework).
For the stakeholder framing that uses financial-vocabulary translations most directly, see the CFO pitch. For the engineering-practitioner view of how to measure these ratios from existing engineering data, see the sister site technicaldebtcost.com, which covers the per-team and per-codebase measurement methodologies.
Field Notes
Frequently asked questions
What is the tech debt service ratio?+
An adapted version of the Debt Service Coverage Ratio from consumer and corporate credit. In the tech-debt application: the percentage of engineering capacity consumed by debt-servicing work (maintenance, rework, on-call response) over total engineering capacity. The healthy range is broadly 10-20%; above 30% indicates a debt position that is consuming capacity at an unsustainable rate.
Where does the metaphor come from?+
Ward Cunningham's 1992 WyCash report originated the technical-debt-as-financial-debt analogy. The metaphor has been extended in the years since by Martin Fowler, Steve McConnell, Capers Jones, and the CAST CRASH research programme. The debt-service-ratio specifically is a more recent extension that has gained traction among CFOs who want a familiar financial vocabulary.
Why does using financial vocabulary help with CFO conversations?+
Because CFOs already operate fluently in financial-ratio language. A debt service ratio is a metric a CFO has worked with for decades in evaluating loan applications, leveraged buyouts, and credit-rating analyses. Applied to engineering, the same metric is immediately legible without translation, which is the rare case in engineering-finance communication.
What other financial vocabulary translates well?+
Debt-to-Velocity Ratio (analogous to Debt-to-Income), Credit Score (analogous to a composite engineering-health score), Term Loan vs Revolving Credit (analogous to scheduled refactor sprints vs ongoing capacity allocation), and Restructuring (the polite word for a major remediation programme). Each has a financial precedent the CFO already understands.
Are these metaphors precise or just rhetorical?+
Both. The metaphors are not mathematically identical to their financial counterparts, but they are precise enough to support quantitative analysis. A tech debt service ratio can be measured the same way every quarter and tracked as a leading indicator of engineering health. The rhetorical value is in legibility; the quantitative value is in measurability.
Should we publish the debt service ratio externally?+
Almost never. The metric is most useful internally as a CFO-CTO shared vocabulary. External publication would invite scrutiny without producing comparable benchmark data, since the methodology is not standardised across companies. Internal use is the productive use.
Adjacent Reading