CTO replacement
The CTO who got you here is not the CTO for what's next.
To replace a CTO without losing the team, put an interim CTO in the seat the week the decision is made, give the outgoing CTO an exit with dignity or a role that fits, run the permanent search alongside, and overlap the successor for 6 weeks before the interim leaves. What usually goes wrong is not the decision but the execution: a rushed exit, a 6-month vacancy, and the best engineers gone before the new leader starts.
This page is for the founder, CEO or board who is about to replace a CTO, or whose CTO is leaving anyway. It covers who the bridge is for, the situations that lead to it, what to do in the first two weeks if your CTO just resigned, how the transition runs month by month, what it costs, and the alternatives. I do this work across Belgium and the Netherlands, in Dutch and English.
Who this is for
- Scale-ups with 15 to 120 engineers where the CTO is leaving, has been asked to leave, or has lost the board.
- Founders whose co-founder CTO built the first version brilliantly and is now the bottleneck, and who want to keep them in the company.
- Owner-led SMEs where the person who held the software together is leaving and nobody else knows where the keys are.
- Boards that need the transition run by someone who is neutral: not the founder's friend, not the CTO's rival.
Who it is not for
- You want someone to push the CTO out while you stay out of the room. The decision is yours, and you will be in that conversation.
- You have not looked at whether the seat is the problem. If delivery is slipping for reasons a new CTO would inherit, replacing them fixes nothing. The diagnosis checks that first.
- You want an interim who quietly becomes the permanent CTO. I don't take the permanent job. That is part of why the team can trust the search.
- You need a hands-on engineer to replace a CTO who mostly wrote code. That is a hiring problem, not a bridge.
The situations that lead to the call
- The founding CTO past 25 engineers. No structure survives contact with them, every decision routes through one calendar, and the team leads are quietly leaving. Everyone is being polite about it.
- The CTO resigned. Sometimes for a better offer, sometimes from exhaustion, sometimes because they saw the conversation coming. Either way the notice period is shorter than a search.
- The board lost confidence. 2 quarters of missed roadmap, a failed launch, or a due diligence that went badly, and the board wants a change before the next round.
- The stage changed under them. A CTO who was right for 10 engineers and a prototype is not automatically right for 60 engineers and enterprise customers. That is not a failure. It is arithmetic.
Not sure yet it is the seat? The signs your CTO isn't the right CTO lists what I look for.
If your CTO just resigned: the first two weeks
A CTO leaving a startup is survivable. A CTO leaving and nobody saying anything for a month is not. The order matters.
- Tell the senior engineers yourself, in person, before the rumour does. Say who holds which decisions from tomorrow.
- List what only the CTO has: the production access, the cloud and domain accounts, the supplier contacts, the architecture nobody wrote down. Get it transferred during the notice period, not after.
- Do not make a counteroffer by reflex, and do not promote the strongest engineer in a panic. Both decisions are hard to undo.
- Decide who holds the seat while you search. If the answer is the founder on top of the CEO job, the search will take twice as long.
How the transition runs
| When | What happens |
|---|---|
| Weeks 1 to 3 | The fixed-price diagnosis: what engineering actually ships, what the org needs next, and whether the current CTO can carry it. By week 2, the one conversation nobody has dared to have: what role the outgoing CTO actually wants. |
| Month 1 | I take the seat, so there is no vacancy and no drift. Team leads get real mandates, so the incoming CTO inherits a structure rather than a queue of decisions. The outgoing CTO's exit or new role is agreed and announced. |
| Months 2 to 5 | The search. A written profile that you and the board both sign, then the search itself, through a recruiter or your own network. I run the technical interviews and sit on the final panel. The team keeps shipping while it happens. |
| Months 5 to 6 | The hire signs and starts. Belgian and Dutch notice periods for senior people are long, so the start date is usually a month or more after the signature. Plan for it. |
| Handover | I stay 6 weeks past the successor's start date. The new CTO runs the org from day one; my days step down to 1 a week and then to zero. No standing retainer afterwards. |
A typical bridge runs 6 to 9 months at 3 days a week. Sometimes the diagnosis concludes the current CTO can carry the next stage with a changed scope. That is a cheaper answer than a replacement, and it ends there.
What happens to the outgoing CTO
This is where most transitions are won or lost. The team watches how the person who built the company is treated, and decides from that whether to stay. A founder CTO often wants the architecture, not the org: a chief architect role with a written scope and no direct reports keeps the knowledge and removes the bottleneck. When there is no fitting role, the exit is negotiated early, done with respect, and explained to the team in one honest sentence. In Belgium many CTOs work through a management company, so the exit is often a contract question as much as an employment one; your lawyer should see it early.
What it costs
Day rates in the normal Western European band of EUR 1 000 to EUR 1 600, invoiced monthly. The diagnosis is EUR 9 500, fixed. No equity, no success fee, and no fee tied to the hire: I am not a recruiter and earn nothing from which candidate you pick. Recruiter fees, if you use one, are separate and between you and them.
The comparison that matters is the cost of a 6-month vacancy. An empty CTO seat leaks senior engineers within a quarter, and each one takes months and a recruiter fee to replace. What a fractional CTO costs has the bands.
What it looked like in practice
- A founding CTO replaced, nobody lost. Series A, 28 engineers, a founder in the wrong seat. An 8-month bridge, the search run alongside: 14 candidates, 5 to the panel, 1 hire. Zero regretted attrition, and the founder still in the building as chief architect.
- 45 engineers to 22. Series B SaaS, releases slipping, cut to the shape the roadmap needed. Weekly releases again after 4 months, one regretted departure in the six months after.
- The portal shipped in 11 weeks. Owner-led SME, where the answer was not a new CTO at all but the lead developer promoted into the job. EUR 180 000 a year off the agency bill.
The fourth case, cloud bill down 42 percent, was a cost engagement rather than a leadership change, and is on the homepage with the others.
The options when a CTO leaves
| Option | Works when | Usually goes wrong because |
|---|---|---|
| Leave the seat empty and search | The team is small, senior and self-directed | The search takes 4 to 6 months and senior engineers leave in the second |
| Founder covers while searching | The founder is technical and has time | The founder has neither, and both jobs suffer |
| Promote the strongest engineer now | That person has already been leading, informally | It is done in a panic, without a mandate or support, and you lose a good engineer |
| Interim bridge plus search | The org is 15 engineers or more and the next CTO matters | The interim has no planned exit, or wants the permanent job |
Hiring an interim CTO covers what to check before you sign one, me included.
Frequently asked
How do you replace a CTO without losing the team?
Put an interim CTO in the seat the week the decision is made, so there is no vacancy. Give the outgoing CTO an exit with dignity or a role that fits, run the search alongside, and overlap the successor for 6 weeks. The team stays when it can see the structure holding and the search moving.
How does a CTO replacement bridge work?
An interim CTO steps in the week the decision is made, so there is no vacancy and no drift. The outgoing leader gets an exit with dignity, sometimes a new seat that fits, like chief architect. The search runs alongside, with the interim CTO on the technical interviews. When the new CTO starts, the interim CTO stays 6 weeks past their start date, then leaves.
What should a startup do when its CTO leaves?
Tell the senior engineers yourself before the rumour does, and say who holds which decisions. Get access, accounts and undocumented knowledge transferred during the notice period. Then decide who holds the seat during the search; if it is the founder on top of the CEO job, the search will take twice as long.
Where does a CTO replacement start?
Often with doubt rather than a decision. A 3-week diagnosis settles it with data: what engineering actually ships, what the org needs next, and whether the current CTO can carry it. Sometimes the answer is that they can, with a changed scope, which is a cheaper answer than a replacement.
How long does it take to replace a CTO?
Usually 6 to 9 months from decision to handover. The search itself takes 4 to 6 months, and senior notice periods in Belgium and the Netherlands add a month or more before the new CTO starts. The interim bridge covers that whole stretch.
Can the interim CTO become the permanent CTO?
Not with me. I don't take the permanent job, which is part of why the team and the candidates can trust the search. The deliverable is a permanent leader who isn't me.
Related
- CTO replacement among the four problems I take on, on the homepage.
- Interim CTO: the form the bridge takes, and how it differs from fractional.
- The diagnosis: what the 3 weeks cover and what you get at the end.
- Fractional, interim, or part-time CTO: which one you need.