Most companies that believe they need to hire a CTO actually need a focused 90-day engagement. Not a permanent executive. Not an expensive search process. Not another seat on the leadership team.
I've seen this pattern across enough boardrooms to know: the instinct to hire a full-time CTO often arrives at exactly the wrong moment, for exactly the wrong reasons. And acting on it prematurely costs companies six to twelve months and a significant chunk of their runway.
Why the Instinct Is Wrong
The trigger is usually one of three things: a critical system breaks, an investor asks "who's your CTO?" during due diligence, or the founding engineer announces they're leaving. All three feel like permanent CTO problems. Almost none of them are.
When a system breaks, you don't need a CTO — you need incident leadership and a credible remediation plan. When an investor asks who runs technology, they want confidence, not a business card. When your founding engineer leaves, you need continuity and a handover, not a full-time executive who won't start for four months.
The real test is simpler: does your company have an ongoing technology leadership need that cannot be served part-time? For the vast majority of companies below 150 engineers, the honest answer is no.
A permanent CTO earns their salary through sustained, full-time presence — managing people, running performance reviews, attending every cross-functional meeting, setting and maintaining engineering culture over years. Before you have the team size to justify that overhead, you're paying for seat-warming.
The Problems That Actually Need Solving
When I run a rapid technology assessment for a new client, I typically find the same cluster of issues underneath the "we need a CTO" headline:
Architectural ambiguity — Nobody has documented what the system does, how it's meant to scale, or what the key dependencies are. Decisions are made by whoever is most available rather than most qualified.
Technical debt tipping point — The codebase has reached the point where every new feature takes 40% longer than it should. Engineers are frustrated. Product is frustrated. Nobody has a remediation plan.
Pre-fundraise readiness — A Series A or Series B process is 3–6 months away and the technology narrative isn't investor-ready. An acquirer or investor's due diligence team will find things the founders haven't named.
Vendor or platform decision — A critical build-vs-buy or architectural choice is stalled because there's nobody with the authority and experience to make the call.
Team leadership vacuum — A senior technical person has left and the engineering team is operating without clear direction.
Each of these has a time-bounded solution. None of them require a permanent hire.
The question I ask every founder
Before we discuss what kind of engagement makes sense, I ask: "If you found the perfect CTO tomorrow and they started Monday, what specifically would they do in the first 90 days?" In my experience, 80% of founders describe a defined problem with a finite scope. That's a 90-day engagement. The other 20% describe an ongoing leadership function. That's a hire — or a long-form fractional relationship.
What a Focused 90-Day Engagement Actually Delivers
A well-structured 90-day fractional CTO engagement is not a placeholder. It's a specific programme designed to resolve a presenting problem, leave the organisation better than it was found, and — critically — reduce its dependency on external technology leadership, not increase it.
Here's what the 90 days typically look like:
Month 1: Diagnosis and Stabilisation
No meaningful engagement starts without an honest assessment. In the first month, the work is to understand the actual state of the technology — not the self-reported state, not the state that feels safe to share with the board, but the real one.
This includes a codebase review, infrastructure audit, security posture scan, team capability assessment, and a structured series of conversations with every engineering lead and key stakeholder. The output is a prioritised findings document: what's breaking, what's brittle, what's just expensive technical debt, and what's actually fine.
This month also handles whatever the immediate stabilisation need is. If a system is actively failing, that gets resolved first. If a critical vendor contract is expiring, that decision gets unblocked. You don't do strategic work in a burning building.
Month 2: Structured Remediation
Armed with a clear picture of the landscape, Month 2 focuses on the highest-impact fixes. The guiding principle: maximum leverage in minimum time.
This is not "fix everything" — that's a multi-year programme that requires a different engagement model. This is surgical: address the issues that are slowing the team the most, creating the most risk, or most likely to surface as problems in the next investor conversation.
Typical Month 2 outputs include: an architecture decision record establishing the baseline design, a technical debt register with remediation owners and timelines, a CI/CD pipeline that actually works, and a documented on-call and incident response process.
Month 3: Capability Transfer and Handover
The most important — and most often skipped — part of a fractional engagement is building the client's capacity to operate without you.
Month 3 is intentionally structured around transfer. The internal team should be running the processes, owning the documentation, and making decisions using frameworks they now understand. The fractional CTO is coaching, not doing. By the end, the client should be able to articulate their architecture, manage their debt backlog, and run their engineering team without an external hand on the wheel.
If a permanent CTO search is in motion, Month 3 is also when the onboarding materials get built. A good handover document is worth more than six months of a new hire's ramp time.
The three months follow a deliberate arc from discovery to independence:
When You Actually Do Need a Full-Time Hire
There are situations where a permanent CTO is the right answer, and I'll name them honestly rather than steer every conversation toward a fractional engagement.
| Situation | What You Need |
|---|---|
| Engineering team of 50+ people with multiple product lines | Full-time CTO — the management load is real |
| Post-acquisition technology integration, 12+ months | Interim or permanent CTO — the problem is sustained |
| Series C+ with board-level technology accountability | Permanent CTO — investor expectations require it |
| Culture-defining moment: platform rebuild, first enterprise sales | Interim CTO to lead the programme |
| Ongoing strategic direction, pre-Series B | Fractional CTO — this is the sweet spot |
| Specific bounded problem (audit, architecture, fundraise prep) | 90-day engagement |
The heuristic I use: if the problem goes away in three months when solved well, you need an engagement. If the problem is structural and grows with the company, you need a hire.
The most expensive mistake
Hiring a permanent CTO to solve a 90-day problem. They spend the first three months on your bounded issue, fix it, and then spend years justifying their continued salary by finding new problems to own. The company ends up with a headcount commitment built on a temporary need. I've watched this happen at three companies in the last two years.
The Economics Are Unambiguous
A fractional CTO engagement for 90 days runs, depending on the scope and seniority required, in the range of €20k–€60k. A first-year full-time CTO — salary, benefits, equity cost, recruiting fees — lands somewhere between €300k and €450k in a European market, closer to $400k–$550k in the United States.
That's a 6–10x cost difference for a problem that, most of the time, has a 90-day solution.
The counter-argument is that the permanent hire keeps delivering value after the 90-day problem is solved. That's true — assuming the problem is continuous and the organisation is at the scale to need full-time technology leadership. For most companies asking this question, neither condition holds.
The more precise framing: spend the fractional engagement cost, solve the bounded problem, and then decide whether a permanent hire is warranted. You'll make a much better hiring decision with 90 days of inside knowledge than you will in month one of a panicked search.
The Diagnostic Question
If you're unsure which applies to you, ask this: what specifically changes in your company if you have a CTO next month that doesn't change if you don't?
If the answer is a concrete list of things — the architectural decision gets made, the technical narrative gets built, the team gets direction — that's a 90-day engagement.
If the answer is "the company has better technology leadership permanently" — that's either a permanent hire, or a long-form fractional relationship. Not a crisis. Not a search process launched on adrenaline.
The 90-day engagement is not a stepping stone to a hire. For most companies at this stage, it is the answer.
If you're staring at this question right now — whether to hire, when to hire, and what you actually need solved — let's talk. A 30-minute discovery call will give you a clearer framework than any job description you'll write.