W03Pricing tech debt like a loan: principal, interest, default
Platform TCO+
This is one of the more useful ways to price tech debt I've seen
(borrowed from how the best CFOs I've worked with read engineering budgets)
A few notes on how it works:
Don't ask "how much debt do we have?"
Ask what it costs you every month to keep it.
Debt behaves like a loan:
Principal → Interest → Default
The principal is the rewrite. The interest is the toil, incidents and slow deploys you pay while you wait.
Interest is the number finance understands
If a 40-person team spends a fifth of its hours on debt service, that's about eight engineers' salaries every year. Nobody approves that line on purpose.
Default risk matters more than size
A small module that blocks every release is worse than a large one nobody touches.
Refinance in slices
Pay down the highest-interest piece each quarter and measure the drop in interest, the way you would with any loan.
One practice worth copying:
every item on the debt register gets a named owner and a monthly interest estimate, reviewed alongside cloud spend.
As an engineer, I want to rewrite the whole thing.
As a founder, I know the math says pay off the most expensive interest first.
How do you put tech debt in front of your CFO today: as a backlog, or as a monthly cost?