The three titles appear on the same résumés, cost roughly the same per day, and describe people with overlapping skills. Buyers reasonably treat them as variations on one thing.
They are not. They differ on a single axis, and it decides everything else: who holds the decision, and who lives with it.
The consultant produces a recommendation
Analysis, comparison, a conclusion. What they bring is a view your organization cannot have, because they have seen other contexts and because they are not caught in your internal politics.
The deliverable is a document and a conviction. What happens next is not theirs. If the recommendation is sound and the execution poor, they are not implicated. If the recommendation is ambitious and the organization cannot absorb it, they will not carry the consequence.
That is not a criticism. It is the contract, and it is legitimate: there are situations where what is missing is precisely an outside view, informed and uninvolved.
The interim holds the seat
Not an observer position. A function, with a mandate, in the org chart. They decide, they commit, they carry it.
The deliverable is not a document, it is a state of affairs: the migration is done, the team is delivering, the hire is made. And they live with their own decisions for the duration, which changes the nature of those decisions completely.
That is where the difference becomes concrete. Someone who will have to execute their own recommendation does not recommend the same thing. They quietly discard the options that are elegant on paper and undeliverable in this organization, with these people, in this window. That self-censorship is exactly what you are buying.
The fractional CTO holds the seat part-time, without an end date
The arrangement that is genuinely newest, and the most often mis-sold.
A fractional CTO occupies the function on a recurring basis, typically a day or two a week, with no assumption that it stops. It suits companies where the technology decisions are consequential enough to need someone senior and not numerous enough to fill a full-time role.
What it is not is a cheaper full-time CTO. Scheduled time means the work has to be shaped for it: decisions batched, delegation real, documentation non-optional. A company that needs someone reachable continuously does not need a fractional CTO, it needs a hire, and hearing that from the person you are about to engage is a good sign.
The drift to watch for
The most common failure is not buying the wrong category. It is buying an interim mandate and receiving consulting.
The symptom is recognizable: someone senior, present, respected, who runs steering committees, produces excellent status reports and analysis, and has authority over nothing. Decisions keep escalating to a person who has no time to make them. Six months later the situation is better documented and unchanged.
Two checks settle it before you sign.
Is the mandate written? Not the objectives, the mandate: what this person decides alone, what they must escalate, and to whom by name. If it is not written it will be arbitrated case by case, which in practice means never in their favour when it matters.
Do they appear in the org chart, even temporarily? A function that does not exist in the organization has no authority, whatever the seniority of the person holding it. Teams work this out in a week, usually before the executive team does.
Which one your situation needs
A consultant, when the missing thing is a judgement rather than an execution. Migrate or renegotiate, rebuild or consolidate. And it is better coming from someone who will not be paid for whatever comes next. That is what an assessment is for.
An interim, when a seat is empty and decisions cannot wait, or when a specific programme has to be driven by someone who has done it before. The engagement is explicitly about handing over to a permanent hire, and that hire is the deliverable rather than an afterthought.
A fractional CTO, when the decisions are ongoing but do not fill a week. Vendor strategy, architecture calls, roadmap, hiring the first engineers. That is the shape of most of our fractional CTO work.
The question that cuts through all three
It is not about titles. It is this:
Is this person paid according to the conclusion they reach?
A consultant remunerated by the project that follows is not a consultant, they are pre-sales. An interim whose mandate renews for as long as they are indispensable has no reason to stop being indispensable. A fractional arrangement with no exit condition becomes a salary with worse terms for both sides.
In none of those cases has anyone behaved badly. The incentive structure simply ate the independence.
That is why our assessments are priced as a standalone deliverable: if the recommendation is to renegotiate rather than rebuild, we are paid the same. And why our mandates name the exit condition and the internal person who takes over before the work starts.
Measured in July 2026, across roughly thirty engagements since 2019: no client has ever had to call us back on an emergency after handover. That is a first-party figure, so treat it as a claim we are accountable for rather than an audited fact. It is also the only number that tests whether an exit was actually prepared rather than promised.
Further reading
- Fractional CTO: the engagement format and what is written into it
- Fractional CIO: the same logic applied to internal systems rather than product
- Technical due diligence: when a judgement is what is missing
- Case studies: including an interim product ownership handed to an internal hire
- Modernize or renegotiate: price the exit first: a decision that needs a disinterested read
- Build or buy: the calculation almost nobody runs: another one
- What a fractional CTO costs: the three pricing models, and what each rewards
- Measuring what an AI agent actually saves: how to judge a result six months in