Signs your CTO isn't the right CTO for the next stage.

Founders almost never get this call right. Not because they can't see the signals. Most can, when someone else names them. It is because the CTO in question is usually a co-founder, an early hire, or a friend. The category the brain reaches for is "this needs fixing." The category the situation is actually in: "the person who got us here doesn't want to do the job we now need."

Here's what to watch for.

They're still the best engineer on the team

Not because they're brilliant, though they might be. It is because they never stopped writing code. At 40 engineers, the CTO who is still merging pull requests on the critical path is blocking the org and doesn't know it. If the honest answer to "what did you do last week" is a list of tickets rather than a list of people you talked to, the role has already changed and they haven't.

Their calendar looks like an engineer's

Long focus blocks, sparse 1:1s, no time with sales, no time with the CEO outside the weekly. At a certain point the job is 60 percent conversation. If it is still 60 percent code, they are avoiding the transition. More often, nobody ever told them what the transition was.

Every hard call comes to the founder

Not the strategic ones. The tactical ones. Should we let Marco go? Do we approve the Snowflake spend? Should we sunset the mobile app? A CTO who's grown into the stage owns those. A CTO who hasn't punts them upward and then feels resentful when the founder decides.

The team has stopped growing under them

People stay, but they don't grow. Senior engineers plateau at senior. No one has been promoted to staff. There's no bench of managers. The org chart is flat because the CTO is doing all the management work themselves, and nobody underneath is being developed to replace them at their current level, let alone the next one.

They're guarding their scope

You brought in a strong VP of Product and now there is friction. You floated the idea of a head of platform and it went quiet for a week. Every leadership addition feels like a subtraction from them. That is not insecurity. It is the correct read that the role they signed up for is being carved down, and they don't want the smaller version.

They tell you what they think you want to hear

This one is the last to appear and the most damning. When you can no longer trust that the number in the roadmap review is the real number, the operating relationship is finished. Sometimes this is a character problem. Usually it's exhaustion: the CTO has been managing your feelings for too long and the tank is empty.

What to do about it

Not what most founders do, which is either nothing for another six months or a sudden explosion. The middle path:

1. Say it out loud, to them, first. Not "we might need to change things" but "the role has changed and I don't think it's the role you want." Give them the option to decide before you decide for them. About 1 in 3 times, they have been waiting to have this conversation.
2. Define the next-stage role on paper. 2 pages. What the CTO of this company needs to do in the next 18 months. Share it with them. If they want to grow into it, help them. If they don't, they'll tell you.
3. Run the transition properly. The worst version is the one where the CTO stays "as advisor" and drops in every 3 weeks to second-guess the new hire. Pay them well, thank them publicly, and give them either a real new scope or a real exit.

The best outcomes I've seen are the ones where the outgoing CTO lands in a scope they actually wanted: chief architect, founding fellow, a specific product they own end to end. The new hire runs the org. From the outside those transitions look like promotions. From the inside they are everyone finally admitting what the job had become.

Written from patterns I've seen across engagements. If any of it sounds too specific to be general, that's why.

Bridging that transition is one of the three problems I take on. See CTO replacement on the homepage. If you recognise your situation and want to talk about it in private, that is what the intro call is for.