When should a founder hire a CTO?

The question gets asked too late and phrased wrong. It arrives as “we need a CTO” when what has happened is that a series of technical decisions started costing real money and nobody senior was making them.

A CTO is one answer to that. It isn’t the only one, and it’s the most expensive.

Five signals worth watching for.

1. You’re making architecture decisions by accident

The clearest early warning is a decision nobody recognises as one. It doesn’t have to be a bad decision.

Someone picks a database because it was on the last project. A queue goes in because a tutorial used one. An integration is wired direct instead of through an abstraction because that was quicker on the day. Each is defensible on its own and none of them was ever discussed.

Six months later you have an architecture nobody chose, and changing it takes a project where it should have taken an afternoon.

The test: can anyone in your business name the three technical decisions that would be most expensive to reverse? If not, they have already been made.

2. Your engineers ask commercial questions and get no answer

Good engineers hit forks where the right choice depends on business context they don’t have. Build this properly or ship it in a week? Handle a thousand or a hundred thousand? Is it worse to be slow or to be wrong?

If nobody answers, engineers answer for themselves, and they answer as engineers. That means building for a scale you don’t have and a robustness you never asked for. I don’t blame the engineers for that. It’s a leadership vacuum, and it costs you in both directions: over-engineering wastes months, under-engineering wastes the rewrite.

3. The estimates stopped being useful

Early on, estimates are wrong and it barely matters. There’s a point where it starts to matter, and it’s the point where you make commercial promises against them: a customer date, an investor milestone, a hiring plan.

When estimates and reality diverge again and again, the cause is seldom that the engineers estimate badly. It’s that the work is specified at the wrong altitude. Too vague to size, or so detailed that writing the specification becomes the bottleneck. Fixing that’s a leadership job. Engineering can’t fix it.

4. You can’t answer a technical question from a customer, an auditor or an investor

This one arrives suddenly. A large customer sends a security questionnaire. An investor asks about technical risk in diligence. A regulator asks where the data lives.

If the honest answer is “I’d have to ask”, you’ve found out that nobody owns the technical narrative. That’s a problem well before it becomes a compliance problem, because the same gap means nobody is managing the risk either.

5. You’re the bottleneck and you aren’t technical

The most common version, and the hardest to see from inside. Every technical decision routes through the founder, who lacks the background to make it quickly, so it either queues or gets made on instinct.

The tell is a calendar full of meetings where you’re the least qualified person in the room to decide the thing being decided, and the meeting is happening anyway because it’s your money.

What to do about it

Noticing you need technical leadership doesn’t mean hiring a CTO. Three options, in ascending order of commitment.

Buy a decision, not a person. If you have one large open question, which platform, build or buy, whether this architecture survives contact with growth, then buy an answer to that question. Scoped, paid, finite. It’s by far the cheapest thing on this list, and it frequently shows that the other two are unnecessary for another year.

Buy ownership at a cadence. If the decisions are continuous instead of singular, a fractional arrangement gets you someone accountable for technical direction without a permanent hire. £3,000 to £8,000 a month is what I see quoted and paid, which is a working benchmark rather than a measurement of the market. What a fractional CTO costs in the UK has the named sources and the dates they were checked. This is the right answer for most businesses asking the question, and it stays right for longer than people expect.

Hire permanently. When the technology function is large enough that leading the people becomes a full-time job, hiring, developing, retaining, running a team of real size, you need someone in the building every day. That’s when £150,000-plus (the median in my pricing article is £160,500) and a three-to-six-month search becomes a reasonable plan and not premature.

The order matters. Every business I’ve seen regret this got it backwards: they hired a permanent CTO to answer a question, then found they had bought a leader with nobody to lead.

What is really being bought

At every level the product is the same. Someone whose job is to be right about the expensive decisions, and who carries it when they’re not.

Not someone who knows the most technologies. Not someone who writes code fastest. Someone who can look at a commercial problem, work out what should be built, say plainly what shouldn’t be, and stay accountable either way.

It’s why I’ve kept doing both sides. I’m CEO at the education business I co-founded and I manage its technical team, so I’m the person who decides what gets built and the person who has to explain why a conversion rate moved. Those two jobs teach each other constantly, and the decisions get noticeably worse when they’re split between people who don’t talk.

If you take one thing from this: hire for judgement about consequences. The list of technologies on a CV changes every few years, and the judgement doesn’t.