"Fractional" and "interim" get used interchangeably, and that costs companies money — because they solve genuinely different problems. Pick the wrong one and you either overpay for capacity you don't need or under-resource a gap that needed full-time ownership. Here's how to tell them apart, from someone who does both.
The one-sentence difference
A fractional CTO gives you ongoing, part-time technology leadership. An interim CTO gives you full-time leadership for a fixed period. Fractional is about right-sizing seniority to a small company; interim is about covering a gap.
Side by side
| Fractional CTO | Interim CTO | |
|---|---|---|
| Time | 1–3 days/week, ongoing | Full or near-full-time |
| Duration | Open-ended retainer | Fixed term (often 3–9 months) |
| Primary job | Ongoing strategy & oversight | Cover a leadership gap, stabilise, hand over |
| Typical trigger | "We need senior tech leadership but not a full-time hire" | "Our CTO just left / is on leave / we're mid-crisis" |
| Pricing | Monthly retainer (~€3k–8k) | Engagement-based, scoped to the period |
| Ends with | Continues as long as it's useful | A clean handover to a permanent CTO |
When fractional is the right call
Choose a fractional CTO when the company is small enough that a full-time technology executive would be underutilised, but the decisions are big enough that you can't afford to get them wrong. Classic fits:
- A seed or Series A startup that needs architecture, hiring, and a roadmap — a few days a week.
- A founder who can build but is drowning in technical-leadership decisions and wants a sparring partner.
- A profitable SME modernising its stack without the budget (or need) for a permanent CTO.
The defining feature is continuity at low intensity. You want the same senior brain available every week, not a full-time seat.
When interim is the right call
Choose an interim CTO when there's a gap that needs full-time ownership right now:
- Your CTO just resigned and the roadmap, the team, and the deploys suddenly have no owner.
- A parental or medical leave you need covered without losing momentum.
- A fundraise or acquisition where the technology org has to look credible to a buyer fast.
- A delivery crunch or live crisis (a failing migration, a security incident) that needs a steady, senior hand full-time until it's resolved.
The defining feature is full-time ownership for a defined window, ending in a clean handover — documented architecture, a 30/60/90 plan for the incoming leader, and hiring support to find them.
A simple test
Ask yourself two questions:
- Do you need someone full-time, or a few days a week? Full-time points to interim; part-time points to fractional.
- Is there an end date in view? A defined gap (a departure, a leave, a raise) points to interim. An open-ended need for senior guidance points to fractional.
If you answered "part-time" and "no end date," you want fractional. If you answered "full-time" and "yes, there's a gap to fill," you want interim.
They're not mutually exclusive
In practice the two often flow into each other. A common pattern: start fractional for ongoing guidance, then scale up to interim during a crunch (a raise, a launch, a crisis), then settle back to fractional — or hand over to the permanent CTO you helped hire. The engagement bends to the situation; that flexibility is the whole point of not making a permanent hire too early.
If you want the wider view across all four options — advisory, fractional, interim, and full-time — I mapped it out in a decision tree, and there's a plain-English primer in what is a fractional CTO?.
Still not sure?
That's normal — the right answer depends on specifics that are hard to self-diagnose. The fastest way to settle it is a short conversation. Book a no-commitment 30-minute call and we'll figure out which model (if either) actually fits — including the honest answer if you don't need one yet.