Fractional, interim, or full-time CTO: which one do you actually need?

A company deciding whether it needs a CTO should start with the work: how much senior technical leadership is needed, for how long and with what authority. Fractional, interim and full-time CTOs solve different problems. I have worked in interim and advisory settings, but I am now primarily looking for a full-time leadership role.

Here is the short version, then the reasoning.

	Fractional CTO	Interim CTO	Full-time CTO
Commitment	1 to 3 days a week, ongoing	Full-time, fixed term	Full-time, permanent
Cost model	Monthly retainer or day rate	Day rate or fixed-term salary	Salary plus meaningful equity
When it fits	Real leadership need, not a full-time load	A gap to bridge or a mess to fix	Tech is the core of the business, long-term
Main risk	Too little presence for a deep problem	Leaves before the fix takes root	Expensive mistake if the fit is wrong

What does a fractional CTO actually do?

A fractional CTO gives you senior engineering leadership for a fraction of the week, on an ongoing basis, without the cost or commitment of a full-time executive.

In practice that means the things a founder or CEO should not be improvising: setting technical direction, making the build-versus-buy calls, shaping the engineering organisation, owning security and cost, and speaking credibly to investors and engineers. A strong fractional CTO can contribute to executive decisions and still review a Terraform plan or pull request. Staying close to implementation is one way to test whether the strategy is sound.

Fractional fits when the need is real but not full-time. You may have engineers who need direction more than another manager, or a cloud, e-commerce or AI change that needs someone who has led a similar programme before.

When is a fractional CTO the wrong call?

When the work is genuinely full-time, or when the value is mostly in being physically present and reactive all day.

If your team is in daily firefighting mode, if incidents need someone owning them hour by hour, or if the culture is fragile enough that only a constant, in-the-room leader will hold it together, one to three days a week will not cut it. You will feel the gaps on the days I am not there. In that situation a fractional CTO is a false economy, and I will tell you so rather than take the retainer.

What is the difference between fractional and interim?

Fractional is part-time and open-ended. Interim is full-time and time-boxed.

They get confused because both are “not a permanent CTO,” but they solve different problems. Interim is a bridge or a rescue: your CTO left, you are mid-transformation, you have a due diligence deadline, or something is on fire and needs a full-time senior owner right now. You want someone in the seat five days a week, with a clear mandate and an end date. Fractional is the steady state for a company that needs the judgment of a CTO without the workload of one.

The failure mode of interim is specific and worth naming: the interim leader fixes the visible problem and leaves before the fix has taken root in the team. Good interim work includes handing over deliberately, writing things down, and ideally hiring or grooming the person who takes the seat next.

When do you need a full-time CTO instead?

When technology is the core of the business and the CTO role is a permanent, load-bearing part of how you compete.

If you are a software company whose product is the engineering, if you are scaling past the point where one part-time leader can hold the context, or if the role needs someone accountable to the board every single day with real equity on the line, hire full-time. Do not use fractional or interim to dodge a decision you have already made. The honest use of fractional here is as a bridge: run the search properly, and have a seasoned CTO steering in the meantime so you do not rush the hire or drift for six months.

The trap in the other direction is just as expensive. A full-time CTO you cannot keep occupied is a costly way to feel reassured. A permanent executive hire is poor value when the role does not contain enough sustained work, and a hiring mistake is far harder to reverse than ending a retainer.

How do I actually decide?

Start from the work, not the title. Write down what genuinely needs a CTO over the next six to twelve months and be ruthless about how much of it is real. If it is a full week of high-stakes ownership, hire full-time or bring in interim to bridge. If it is a heavy but temporary lift, interim. If it is real leadership at a couple of days a week, fractional.

Then be honest about the risk you are most exposed to: too little presence, a leader who leaves too soon, or an expensive permanent mistake. That is usually the fastest way to the answer.

The decision becomes clearer once the company writes down the work, authority and time commitment it actually needs.