Fractional CTO vs Interim CTO: What's the Difference?

Why the two models get confused

The terms "fractional" and "interim" are used interchangeably in the market, sometimes deliberately so (a consultant calling themselves "interim" sounds more committed; "fractional" sounds more flexible). In practice, they refer to meaningfully different things, and choosing the wrong model will cost you time, money, and momentum.

Let me be direct about the distinction, because this question comes up in almost every initial conversation I have with founders.

The fractional model: ongoing, part-time leadership

A fractional CTO works with your company on a recurring, part-time basis. Think of it as a structured retainer: you're typically buying one to three days of their working week, on an ongoing basis, for as long as the engagement serves you. They become a genuine part of your leadership team (attending your leadership meetings, owning your technology strategy, leading your engineering organisation) but they're not there every day, and they may be working with one or two other companies simultaneously.

The fractional model works best when:

• You need strategic technology leadership over an extended period, not just to solve a specific crisis.
• You have an engineering team that needs long-term leadership and cultural investment.
• Your budget doesn't support a full-time CTO salary, but your challenges clearly require C-suite-level thinking.
• You're at Seed to Series A/B and building towards a point where you'll hire a permanent CTO.

The interim model: full-time, fixed-term cover

An interim CTO is a full-time appointment, but a temporary one. They join your company as if they were a permanent CTO (five days a week, fully embedded, accountable to the board) but with a defined end date in mind. The engagement typically runs between three and twelve months.

The classic use cases for an interim CTO are:

• Sudden departure. Your CTO left, unexpectedly or after a difficult period. You need someone in the seat immediately, at full commitment, while you run a proper permanent search.
• Planned leave or incapacity. Your CTO is going on extended leave and needs someone to hold the function while they're away.
• Crisis or transformation. The business is going through a significant change (a pivot, a major acquisition integration, a serious technical incident) and you need a dedicated leader with their full focus on it.
• Pre-exit or due diligence preparation. You're preparing for acquisition and need an experienced CTO fully embedded to run the technical side of the process.

The key differences in practice

Time commitment

A fractional CTO commits a defined portion of their week (typically 1–3 days) on an ongoing basis. An interim CTO is full-time for a fixed term. This sounds straightforward, but it has significant implications for how each engagement operates.

A fractional CTO must operate asynchronously for much of their time. The engineering team needs to be able to function without them being physically present every day. A good fractional engagement builds that capability into the team, which is actually a healthy side effect. An interim CTO is expected to be in every key meeting, respond to every escalation, and carry the full weight of the function.

Cost

Fractional: typically £3,000–£7,000 per month on a retainer, depending on days committed and complexity.
Interim: typically billed at a day rate of £1,000–£1,600, which at five days per week becomes £20,000–£32,000 per month. This is considerably more expensive, and should be, given the full-time commitment and urgency premium.

Focus

A fractional CTO is typically working across strategy, team leadership, architecture decisions, and hiring, across a longer time horizon. An interim CTO is often parachuted in to solve a specific problem and is much more execution-focused in the near term, while also establishing longer-term foundations before they hand over.

Handoff

Fractional engagements often run for one to three years, evolving as the company grows. The relationship ends when the company is genuinely ready to hire a permanent CTO, ideally one the fractional CTO has helped to define and recruit. Interim engagements are designed from the outset to end: the goal is to leave the function in a stable, well-documented state that enables a smooth transition to whoever comes next.

Which one do you actually need?

Ask yourself these questions honestly:

• Is there a specific acute problem (a departure, a crisis, a transformation) that requires someone's full-time focus? → Interim CTO.
• Do you need ongoing strategic leadership, team building, and architectural guidance over a 12–24 month period? → Fractional CTO.
• Is your engineering team small enough to function well with a part-time leader, given the right rhythms and expectations set? → Fractional CTO is likely viable.
• Are there too many time-sensitive decisions or escalations happening daily for a part-time model to handle safely? → Interim CTO, or a full-time hire.

The hybrid approach

A pattern that works well in practice: start with an interim CTO engagement to stabilise a critical situation, then transition to a fractional model once the immediate problem is resolved and the team is functioning well. The same person can do both, which maintains continuity and avoids the costly handoff of institutional knowledge.

I've run exactly this kind of hybrid engagement, starting at full-time intensity for two to three months, then stepping back to a two-day-per-week fractional rhythm once the foundations were solid. It works well when the brief is clear and both parties understand what "done" looks like for each phase.

Questions to ask before you decide

Regardless of which model you're leaning towards, the most important conversation to have first is about the scope and success criteria of the engagement. A clear brief prevents most of the disappointments I've seen companies experience when they bring in external CTO-level support. Some questions worth working through:

• What does success look like at 30 days? At 90 days? At 12 months?
• Who does this person report to, and how are they included in key decisions?
• What authority do they have over the engineering team from day one?
• What's the handoff plan, either to a permanent hire or back to a co-founder?

Getting these questions answered before you engage anyone will save you a significant amount of time and money.