Skip to main content

Guide

How to explain technical debt to your CFO

A communication playbook for engineering leaders asking for refactoring budget. What lands. What doesn't. What to prepare.

10 min read

Engineering leaders are good at talking to engineers. Most of us are bad at talking to executives. This is a different discipline, and it is rarely taught.

This guide is about one specific conversation: asking your CFO (or CEO, or board) for time to fix technical debt. Everything below is written assuming you have no more than fifteen minutes.

Rule one: translate before you justify

The most common mistake is to open with technical evidence: "our cyclomatic complexity is trending up," or "we have 47 critical code smells." All true. All useless in this room.

The CFO has no mental model in which any of those numbers can be evaluated against other budget priorities. So the meeting stalls. You feel unheard. They feel annoyed.

Translate into their vocabulary first. Justify second.

  • Instead of "cyclomatic complexity is up": "we are spending €14,000 more on bug fixes this quarter than last quarter."
  • Instead of "47 critical code smells": "four files consume 38% of our engineering debugging time."
  • Instead of "unmaintainable code": "onboarding a new engineer on payment processing takes three times longer than any other module."

Same evidence. Different framing. Only the second version leaves the meeting with a decision.

The three-slide rule

Fifteen minutes equals three slides, plus questions. Here is what goes on each.

Slide 1 — the cost of the status quo

One big number. Euros per month. Something like: "Our current technical debt costs us €21,300/month in firefighting and debt servicing — equivalent to 2.4 full-time engineers."

Bullet-point footnote, small font: the assumptions behind the number. Daily rate, working days, how you classified commits. Be ready to defend the methodology if asked.

Slide 2 — the investment required

A second big number. One-time cost. "A focused cleanup investment of €58,000, spread over one quarter, would eliminate roughly 60% of the recurring cost above."

Include the breakdown: how much per hotspot, per silo, per dead file. Not to overwhelm — to prove the number is grounded.

Slide 3 — break-even and projection

A chart. Two curves: current trajectory (with debt compounding), and post-investment trajectory (with debt partially resolved). Where they cross is your break-even month. The area between them afterward is your annual savings.

Add a confidence interval. Never claim precision you can't defend.

The three questions you will get

"How do you know the savings are real?"

This is the right question. The honest answer is: you don't, not precisely. What you can do is model, forecast, and measure.

Frame it as an experiment: "Three months after the investment, we'll re-run the analysis. If firefighting cost hasn't dropped by at least X euros, we've learned something important." Treating the budget as a measurable bet — not as a leap of faith — is what separates credible engineering leaders from unconvincing ones.

"What happens if we don't invest?"

Do not moralise. Give a specific, bounded claim: "Based on the last six months of trend data, firefighting cost is growing at roughly 4% per quarter. At that rate, we would be spending €28,000/month on firefighting alone by the end of next year."

Then add the compounding argument: the cost of cleanup also scales with debt accumulation. "A €58k investment now is likely to be a €120k investment eighteen months from now."

"Why now?"

Best answer: "Because we finally have the data to justify it. Six months ago, I could not have given you these numbers. Now I can."

If you have a concrete trigger — an upcoming release cycle, a hiring ramp, a migration — use it. Triggers make timing defensible.

What not to do

A short list of moves that backfire:

  • Emotional appeals. "The team is frustrated." True. Not actionable.
  • Competitor comparisons. "Google refactors continuously." You are not Google.
  • Open-ended estimates. "It will take as long as it takes." This is not a budget.
  • Abstract quality arguments. "Our code is bad." CFO thinks: is it costing us money or not?

One habit that pays for itself

Keep a running log, for one quarter, of every bug fix, every delayed feature, every incident, every refactoring detour. Note the files involved and the engineering hours consumed.

At the end of the quarter, multiply hours by your loaded daily rate. You now have a quantified, defensible, specific cost for technical debt — derived from your own data, not from any external model.

Bring that to your next budget meeting.

Using DebtLens for the prep work

DebtLens exists to do most of this prep for you. Run the CLI on your repo, activate a hub licence, and the generated PDF is laid out exactly like the three slides above. Forward it to your CFO as an FYI before the meeting. Walk in with the deck already read.

Try DebtLens on your own repo.

Free local analysis, 60 seconds from install to first report.

Download the CLI