Fig. 01 · Glossary
Technical Debt
Also known as Tech Debt, Code Debt, Software Debt
Definition
Technical debt is the future cost imposed by present implementation shortcuts: mismatched abstractions, end-of-life dependencies, missing test coverage, manual operational toil. Unmanaged, it compounds until velocity collapses; quantified, it converts to dollar EBITDA drag at roughly 2-8% of ARR depending on stage and stack. Buyers pricing acquisition multiples include a technical-debt haircut that sellers consistently underestimate by ~3x. The Human Renaissance EBITDA-DevOps Bridge maps technical debt categories to dollar drag so the conversation moves from engineering complaint to board-agenda item.
In our Tech-Debt to EBITDA Calculator, the categories that consistently produce the largest unrecognized drag are on-call burden (interruption multiplier × loaded hourly rate × team size) and incident cost (failed deploys × MTTR × team size + per-event fixed cost). Velocity drag and coverage gap are visible in engineering metrics; on-call burden hides in HR attrition reports a quarter later.
For a founder preparing for sale: get the dollar-drag number on file before LOI. Buyers will compute their own; if your number is in the same band as theirs and you have a remediation plan with sequenced ROI, the haircut argument compresses from “1.5 turns of multiple” to “0.4 turns and an offset earnout.”
Methodology: see The EBITDA-DevOps Bridge. Calculator: /tools/tech-debt-ebitda-calculator.
Human Renaissance glossary · operator-grade definitions · Research methodology
