When your CTO walks out mid-quarter, the first 72 hours decide whether it is a wobble or a crisis. I've been the person called in the immediate aftermath of that exit enough times to know that the gap between "we got through it" and "it unravelled" comes down to what happens in the first three days — not the following three months.
This is not a career-planning post. It's an operator's guide to the moment after the door closes.
Why the First 72 Hours Are Decisive
A CTO departure creates an information vacuum. Into that vacuum rushes speculation — from engineers, from investors, from customers who hear things through industry networks. The stories people tell themselves in that vacuum are almost always worse than the reality. Your job in the first 72 hours is not to have all the answers. It is to prevent the vacuum from filling with panic.
Three things typically go wrong in those 72 hours when leadership waits too long to act:
The engineering team starts choosing sides. Senior engineers who were close to the departing CTO begin making quiet assessments of whether to stay. This is not disloyalty — it's rational risk management. They're asking: is this company still a good bet? If nobody credible answers that question quickly, the answer they arrive at is often "probably not."
Investors and board members start calling. Some will be supportive. Some will be probing. Some will be actively considering whether to exercise protective provisions or slow the next tranche. A founder who cannot articulate a clear short-term plan in that first investor call is signalling that they don't have one.
Operational continuity becomes uncertain. Who approves architectural decisions? Who handles vendor escalations? Who signs off on a production deployment that was already in flight? If those questions don't have answers, they become incidents.
The silence problem
The most damaging thing you can do in the immediate aftermath is go quiet. A short, honest all-hands within 24 hours — even if you don't have a full plan — is worth more than a polished communication three days later. People can tolerate uncertainty. They cannot tolerate the feeling that leadership is hiding something.
What an Interim CTO Actually Does (Differently From a Permanent Hire)
This is where the model is often misunderstood. An Interim CTO is not a permanent CTO who hasn't been given a permanent title yet. The job is structurally different, and companies that treat it as a temporary placeholder miss most of the value.
An effective Interim CTO in a post-departure situation is doing three things simultaneously:
Stabilise. Hold the existing team, protect operational continuity, make the decisions that need to be made today. This requires genuine presence — not remote advisory — and a credibility that the team can feel within the first week.
Assess. Develop a clear and honest picture of the technology estate, team capability, technical debt posture, and delivery commitments. This is the raw material for both the board and the permanent search. A permanent CTO who inherits a situation assessed by a competent interim has a far easier first 90 days.
Prepare the permanent landing. Structure the role, scope the first 90-day plan, help define what "good" looks like for the permanent hire so you're not guessing in interviews. This is where I find most value is left on the table — companies hire the interim to cover the gap, not to set up the permanent CTO for success. The two goals are not in conflict.
| Function | Interim CTO | Permanent CTO | Fractional CTO |
|---|---|---|---|
| Time horizon | 3–9 months | Multi-year | Ongoing / part-time |
| Operational depth | Full; in-seat | Full; in-seat | Part-time; advisory |
| Primary mode | Stabilise + assess | Build + scale | Advisory + augment |
| Speed to deploy | 1–2 weeks | 3–6 months | 1–2 weeks |
| Cost structure | Day rate or monthly | Full-time package | Monthly retainer |
| Best fit | Sudden departure, transition, M&A | Steady-state growth | No CTO or augmenting weak CTO |
The First Week Playbook
I follow a consistent structure in the first seven days. It is not subtle. Subtlety is a luxury of stable situations.
Day 1–2: Presence and containment.
Show up. Physically if possible, visibly if remote. Meet the engineering leads individually, not as a group. The group meeting can wait — individual conversations surface the actual concerns before they get managed for the room. Listen more than you talk. Your goal is to understand what each person is worried about, not to reassure them with things you don't yet know to be true.
Identify the two or three decisions that are genuinely urgent — things that will cause a production problem or miss a hard deadline in the next 72 hours — and make them. Everything else can wait a week. The act of making decisions clearly and quickly establishes more credibility than any speech.
Day 3–4: Operational map.
Understand what is running, who owns it, and what is fragile. This is not a full technical audit — that comes later. It's a rapid map of: what are the systems the company cannot afford to have fail, who are the people those systems depend on, and are any of those people also considering leaving?
The last question is the uncomfortable one. Ask it directly, in the individual conversations. "Are you thinking about your options right now?" People will tell you the truth if you give them room to. And knowing the answer is always better than not knowing.
Day 5–7: Communication architecture.
By the end of the first week, you need three things in place: a regular engineering team update cadence (I use a short written update every Monday and a team call every two weeks), a clear decision-making framework so people know who to escalate what to, and an honest update to the board or CEO about what you've found and what the plan is for the next 30 days.
The 30-day plan does not need to be complete. It needs to be credible — rooted in what you've actually seen, not optimistic projection.
The Three Failure Modes I See Repeatedly
After doing this enough times, the same failure modes appear in different clothes.
Failure Mode 1: Promoting the Senior Engineer
The senior engineer steps up, the founder leans on them, and six weeks later you have an under-resourced engineer trying to do two jobs, burning out, and becoming an attrition risk themselves. This is well-intentioned and almost always damaging. Acting-up without the support structure, authority, and experience of a true interim is not fair to the engineer and not adequate for the company.
Failure Mode 2: The Invisible Consultant
A consulting firm is engaged to "provide interim CTO support." A different consultant shows up every two weeks. The engineering team doesn't know who to call. The board gets reports that nobody on the ground recognises. This is not interim CTO work — it is interim CTO cover, and it costs significantly more while delivering significantly less.
Failure Mode 3: Skipping the Assessment
The company is eager to move quickly on the permanent hire. The interim is told to "just keep things running" while the search happens. The permanent CTO is hired into a situation that was not honestly assessed, inherits hidden problems, and — in the worst cases — exits within 12 months. Now you've had three CTOs in 18 months, and the credibility damage to the company is the actual crisis.
The assessment is not optional
The technical and organisational assessment conducted during the interim period is the most valuable output of the engagement. It's the thing that makes the permanent hire viable. Companies that skip it to save time almost always lose more time on the back end. I've seen this pattern enough times that I now make the assessment non-negotiable in any interim engagement I take.
What to Tell the Board
Boards respond better than founders expect when they receive honest, early information. The conversation that goes badly is the one where the founder waits three weeks to call and then has to explain why they waited.
What the board needs to hear, as early as possible:
- What happened (briefly, factually — no spin)
- Who is covering the function right now and in what capacity
- What the known risks are in the next 30–60 days
- What the plan is to address those risks
- What the timeline is for a permanent solution
That's it. You don't need all the answers. You need to demonstrate that you're operating with clear eyes and a real plan.
| Board Concern | What They're Actually Asking | What Helps |
|---|---|---|
| Team stability | Will key engineers leave? | Interim CTO visible, early assessment |
| Delivery risk | Will the roadmap slip? | Honest dependency map; adjusted timelines |
| Investor confidence | Should we still trust this team? | Clear plan, consistent communication |
| M&A / funding impact | Does this change our valuation story? | Strong interim narrative, permanent search timeline |
| Governance | Who has authority over technology decisions? | Named accountable person from day one |
Choosing the Right Interim CTO
Not every interim CTO is right for every situation. The profile that works in a 30-person SaaS startup is different from the profile that works in a 200-person regulated financial services business.
The things I'd look for, regardless of context:
Has operated in-seat, not just as an advisor. Advisory experience does not prepare you for the operational reality of being the person the team calls when a deployment goes wrong at 2am. Check whether the candidate has actually held the role in an executive capacity.
Has genuine sector or scale overlap. A CTO who has only operated in pre-revenue startups may struggle in a complex multi-stakeholder environment. The reverse is also true. The interim doesn't need to be identical to what you need permanently — but the gap should be narrow.
Can be deployed quickly. The value of an interim is speed. If it takes four weeks of onboarding and contracting, the acute phase of the crisis has already resolved itself — one way or another. Experienced interim CTOs should be able to start meaningfully within a week of agreement.
Will actively support the permanent hire, not resist it. Some interims (consciously or not) make themselves indispensable in ways that slow the permanent search. The right interim is actively building toward their own exit — documenting, assessing, preparing — because they understand that's the job.
The moment your CTO walks out, the clock starts. The companies that come through that period strongest are not the ones with the best technology — they're the ones with the clearest leadership response in the immediate aftermath.
If you're in that situation right now, or preparing for the possibility, let's talk. Book a 30-minute call and we can walk through what the first 30 days should look like for your specific context.