Skip to content
AI Native CTO
AI-Native CTODecision guide7 min read

Fractional CTO versus Interim CTO

Two different answers to two different problems. Choosing the wrong one costs months you probably do not have.

The two titles get used as though they were the same arrangement at different intensities. They are not. They answer different problems, they run on different rhythms, and they end in different places.

Choosing between them is usually straightforward once you know which question you are actually asking. Getting it wrong is expensive, because both arrangements take a month or two to become useful and you rarely have that month twice.

The difference is accountability

Everything else follows from this one distinction.

A fractional CTO adds senior technology leadership to a company that does not have it, alongside whoever is currently making the decisions. I sit in the leadership rhythm of the business, set direction, challenge decisions, coach the people doing the work, and stay close enough to delivery to see whether the plan is working. The company remains accountable for its own technology function. I make it better at running it.

An interim CTO holds the role. Not advises it. Holds it. I take clear accountability for the technology function during the transition, and I carry that accountability to the board in the same way a permanent CTO would. When something breaks at two in the morning, it is my problem.

If you find yourself asking whether the person needs to be accountable or merely influential, you have already answered the question.

What each one is actually for

A fractional engagement is a response to a capability gap. The business is fine. It is growing, and growth is exposing something.

Usually one of these:

  • The founder is still acting as the default CTO, and it is costing them the work only they can do.
  • A strong engineering team has no executive technology leadership above it.
  • Growth is exposing gaps in architecture, delivery or organisation design.
  • The board needs a fuller view of technology performance and risk than it currently gets.
  • Fundraising, expansion or a major platform change is coming.

An interim engagement is a response to a discontinuity. Something has broken, or is about to.

Usually one of these:

  • The CTO has left, or has to be replaced.
  • Product delivery has become unreliable and nobody can say why with confidence.
  • Technology risk has reached the board agenda.
  • A turnaround or a major change needs experienced leadership immediately.
  • The organisation needs a safe bridge to its next permanent CTO.

The tell is the verb. Fractional work is about building. Interim work usually begins with repairing, and building only becomes possible once the repair is done.

How the engagement feels

Fractional is part-time, continuing and indefinite. A predictable presence in the leadership rhythm: the same meetings, the same board pack, the same people, month after month. The value compounds precisely because it is continuous. Six weeks in, I know which of your engineers to believe about estimates.

Interim is full attention and deliberately finite. The first weeks are not gentle. The first job is to establish the truth, which means reading the code, the incidents, the roadmap and the contracts, and talking to people who have usually given up expecting anyone to ask. The goal is not to confirm the prevailing story. It is to understand what is actually happening.

That difference shows up in your calendar. A fractional CTO is a fixed rhythm you plan around. An interim CTO is, for the first month, quite disruptive to the organisation, on purpose.

How each one ends

This is the part people skip, and it is the most useful test of all.

A fractional engagement has no natural end. It runs while the company still benefits. Many of them continue for years, changing shape as the business grows. Some end when the company finally hires a full-time CTO, which is a good outcome and one I will usually be the first to raise. The measure of success is that the technology function keeps improving while I am there.

An interim engagement is built to end, and the ending is the point. Success is a stable technology function, a credible plan, a team that knows where it stands, and a structured handover to a permanent leader who can take it from there. If I am still indispensable after the handover, the engagement failed regardless of how much improved along the way.

So: do you want someone who keeps making the company better, or someone who makes themselves unnecessary? Both are legitimate. They are not the same purchase.

The two expensive mistakes

Hiring fractional for an interim problem. This is the common one, and it usually comes from budget. The CTO has gone, delivery is slipping, the board is uneasy, and the company buys two days a month of senior advice. Two days a month cannot hold accountability, cannot be in the room when the incident happens, and cannot make the decisions that a crisis generates daily. The advice will be good. The situation will keep deteriorating.

Hiring interim for a fractional problem. Rarer, and usually driven by anxiety rather than evidence. A company that is growing well brings in a full-attention interim CTO, who arrives, establishes the truth, finds no crisis, and then either invents urgency or spends expensive months doing work a fractional arrangement would have done more cheaply over a longer horizon. You pay a premium for speed you did not need.

When the answer is neither

Sometimes the honest answer is that you should hire a permanent CTO and run the search properly.

If the technology function is central to the company's promise to its customers, if the roadmap is years long rather than quarters, and if the business can attract and afford the right person, then a permanent hire is the right answer and anything else is a delay dressed as a decision.

Where I can help there is in the search itself: designing the role, assessing candidates, and holding the function steady while it runs. That is interim work with a specific ending, and it is often the most valuable version of it.

The wider question underneath all of this is what the technology leadership role is even becoming, now that intelligence is part of the stack and the workforce. That changes what you should be hiring for, whichever arrangement you choose.

Read the full definitionWhat is an AI-Native CTO?
Explore the category

The AI-Native Briefing

A considered note on AI, technology leadership and the agentic enterprise. Written for people making real decisions, not watching from the sidelines.

Useful ideas only. Unsubscribe whenever you like.