Ask an engineer about technical debt and you'll get a list of shortcuts, ageing frameworks, and "we'll fix it later" compromises. Ask a CFO and you'll get a blank look — because the conversation is almost always framed as a cost with no corresponding line for value. That framing is why so many modernisation budgets die in the boardroom. If technology only ever shows up as a liability, of course it loses to everything that promises revenue.
The fix isn't a better pitch. It's a better model. Treat your technology estate the way you'd treat a balance sheet — with debts you service and equity you build — and the whole conversation changes from "cost centre" to "capital allocation."
Two entries, not one
Technical debt is the accumulated cost of past decisions that now slow you down: the brittle integration everyone's scared to touch, the manual month-end close, the platform one retiring contractor understands. Like financial debt, some of it is perfectly rational — you took a shortcut to hit a market window — and some of it is quietly compounding interest in the form of slower releases, higher incident rates, and key-person risk.
Technical equity is the opposite entry: investments that make the business worth more and move faster — a clean data platform others can build on, automation that removes recurring cost, documented systems that reduce reliance on any one person. Equity compounds too, but in your favour. Every capability you build on top of it is cheaper than the last.
The mistake most organisations make is booking only the first entry. They track "we have too much legacy" but never credit the equity a modernisation programme creates. You can't make a capital-allocation decision with only the liabilities side filled in.
The interest-rate test
Not all debt is worth repaying, and cash spent clearing low-interest debt is cash you didn't invest in growth. Before you approve a single "let's rebuild it" project, score each item on two axes:
- Interest rate — what is this costing you now? Engineering time lost to workarounds, incidents and downtime, compliance exposure, deals slowed by "the system can't do that," and the salary premium of scarce skills for obsolete tech. High-interest debt bleeds every month whether or not you touch it.
- Principal — what would it cost to clear? The real effort to fix or replace, including the risk and disruption of the change itself.
That gives you four quadrants. High interest, low principal is your portfolio's free money — pay it down immediately. High interest, high principal is a genuine strategic decision that belongs at board level, sequenced deliberately. Low interest, high principal is debt you service, not repay — leave it be. And low interest, low principal simply isn't worth the context-switch. Most teams burn their best engineers on that last quadrant because it's satisfying, while the high-interest items keep compounding untouched.
Translating it into money the board recognises
The framework only works if you attach numbers a CFO can act on. Three translations do most of the work:
- Debt → recurring cost. "The manual reconciliation is £X of finance time a month" is a number. "The code is messy" is not. Put debt in the language of run-rate.
- Equity → EBITDA. Modernisation that removes recurring cost or unlocks capacity flows straight to margin — and a business that runs on documented, automated systems rather than heroics is worth a higher multiple. That's the same logic behind an AI ROI audit: tie the work to a P&L line or don't prioritise it.
- Risk → probability × cost. Key-person and security exposure aren't free just because nothing has broken yet. Price them as expected loss so they compete fairly for budget.
A pragmatic starting point
You don't need a six-month audit to begin. You need one honest afternoon:
- List your ten biggest debts — the systems and processes people complain about most.
- Score each on interest and principal, using rough numbers, not precision. Directionally right beats perfectly wrong.
- Pay down the top-right free money now, schedule the big strategic items, and consciously choose to service the rest. Writing "we are deliberately not fixing this" is a decision, not neglect.
- Book the equity. For every programme you approve, state the asset it creates and the margin or capacity it returns — then measure it afterwards.
The bottom line
Technology stops being an argument you lose the moment you model it like capital. Some debt is cheap and can wait; some is compounding and has to go; and the best modernisation spend isn't repayment at all — it's equity that makes every future move faster and the business itself worth more. That balance-sheet thinking is exactly what our Executive Advisory work brings to a leadership team: tech decisions tied to EBITDA, not slideware.
Want a one-page read on your own tech debt-versus-equity position? Let's talk.