Scaleup Debt Economics

A CTO wanted a full platform rewrite before the next raise. 8 weeks of tickets pointed at two components.

The pitch for the rewrite was reasonable. Pipelines broke most weeks and due diligence was close. The team was tired enough that a clean start sounded like the safe story for investors.

Before agreeing, we priced the debt. For every part of the platform we pulled 8 weeks of incidents, reruns and “quick fix” tickets and put hours next to each one.

The spread was lopsided. Ingestion from two old sources and one tangled revenue model ate most of the unplanned hours. The rest of the platform was dull and mostly fine, which nobody had said out loud, because dullness is simply not attractive.

So the plan shrank. Refactor those two areas first, with owners and tests, and document the rest honestly for the data room. The rewrite went back in the drawer. It might come out again, on a timeline the company picks.

I expected the rewrite case to survive that exercise. It didn’t.

If a raise is coming and nobody can put a number on your platform debt, that’s worth 30 minutes: https://app.cal.eu/thomasnys/30min?utm_source=linkedin&utm_content=2026-09-14-scaleup-debt-economics