Skip to content

How I Help Scaleup CTOs Fix the Build That’s Now Holding Growth Back

At the scaleup stage, the thing that got you here is usually the thing now slowing you down. The early build — the one that was exactly right when you were proving the business — has become the bottleneck: every new feature takes longer, the team spends more time firefighting than shipping, and nobody can confidently say which parts are load-bearing and which are technical debt waiting to bite. I help scaleups decide, with a clear head, what to fix now, what to leave alone, and what genuinely needs rebuilding. The hard part isn’t the engineering. It’s the judgement about where to spend.

The mistake: treating “rewrite it all” and “patch forever” as the only options

The recurring scaleup error is a binary that doesn’t exist. One camp wants to throw the early system away and rebuild it “properly” now that there’s money and a team — the big rewrite that eats a year, ships nothing new while it runs, and usually recreates the same problems with newer tools. The other camp keeps patching, terrified to touch the core, until the codebase is a minefield only two people understand and one of them is leaving.

Both are failures of judgement under pressure. The rewrite camp is solving the impressive problem — “our architecture is embarrassing” — instead of the real one, which is “specific things cost us specific growth.” The patch-forever camp is avoiding the diagnosis because it’s frightening. The truth is almost always surgical: most of your early build is fine, a small part of it is genuinely throttling you, and the entire game is identifying which part with enough confidence to act. A scaleup that rewrites everything usually didn’t need to; a scaleup that rebuilds the one strangling component buys itself another two years.

What actually moves the needle: an honest diagnosis before any rebuild

What matters here is the read on your actual system — not a vibe, an evidence-based view of where the real constraints are. That’s an architecture review: I go through what you’ve built and tell you plainly what will hold, what won’t, and what to do about the parts that won’t. The output is a prioritised, honest map — this is the bottleneck, rebuild it; this looks ugly but works, leave it; this is a time bomb, defer it but watch it. That map is worth more than any amount of building, because it’s the difference between spending your engineering budget on the throttle and spending it on something that felt urgent but wasn’t.

The own-your-data principle changes shape at this stage. Early on it’s about not renting your foundations. Now it’s about whether your growth is being capped by data and systems you don’t fully control — a critical workflow living in a SaaS tool you’ve outgrown, a third-party platform you’re now fighting to extend, data trapped in a shape that made sense at ten customers and fights you at ten thousand. Scaleup-specific judgement is knowing which of those to bring in-house and own, and which to leave rented because owning them isn’t worth the disruption yet. That’s not a generic call; it depends entirely on where your growth is actually constrained.

I’m useful here because I’m not attached to your codebase and I’m not trying to justify a year-long project. I’ve seen enough scaled systems to tell the load-bearing from the cosmetic, and I’ll give you the call your own team can’t, because they’re too close to it and the rewrite is more exciting than the truth.

How I work with scaleups

Often it starts as a one-off review when something specific has broken the camel’s back — a release that took three months, a near-miss outage, a CTO who needs an independent second opinion before committing the team to a big rebuild. Sometimes it becomes a standing fractional CTO rhythm or interim cover through a transition, where I’m the senior judgement in the room while your team executes. The shape depends on whether you need one hard call made well or ongoing pressure-testing of the calls as they come.

Who this isn’t for

If your honest diagnosis is that you need a sustained team to rebuild and run a major part of the platform over the next year or two, that’s beyond what one advisor delivers — that’s Digital Royalty, the agency, with the team and process to deliver and operate at scale. The most common right answer is both: I make the diagnosis and set the direction, the team executes. Because I run both, I can tell you honestly which you actually need.

Tell me where it’s slowing down

If your build has gone from your advantage to your bottleneck and you need someone to tell you what to fix and what to leave, tell me where it’s hurting and I’ll give you the surgical version, not the rewrite-everything pitch. If you’re earlier than this — still proving the business — the startup read fits better, and if you’re a SaaS company specifically, the SaaS page goes deeper on the product-core version of this problem. The full set of sectors I work in is there if neither quite fits.