What is a fractional CTO, and when does a business need one?

A fractional CTO is an experienced technology leader who runs your engineering function part-time - typically one to three days a week, on a rolling arrangement - instead of as a permanent hire. The remit is the same as a full-time CTO: technology strategy, architecture, delivery, team leadership and hiring. The difference is that you buy the seniority you need and none of the seniority you do not. A scale-up needs one when technology decisions have started queuing behind someone who does not have the time or the experience to make them, but the work does not yet fill five days a week.

The phrase has been stretched a long way in the last couple of years. It gets used for advisers who join a monthly call, for contractors writing code, and for genuine executives running a function two days a week. Those are three different products at three different prices, so it is worth being precise about which one you are buying.

What does a fractional CTO actually do?

The job is leadership, not extra hands. In practice the remit covers four things:

• Technology strategy. What you build, what you buy, what you deliberately leave alone, and how that maps to the next two funding milestones rather than the next two sprints.
• Architecture and technical debt. Deciding which parts of your technology estate are load-bearing, what has to be fixed before it breaks under growth, and - just as important - what can safely be left ugly.
• Delivery and the team. Running one-to-ones, planning your roadmap, improving the delivery process, defining the roles, team structure and making honest calls about who is in the right seat.
• Assurance. Security, compliance, and being the person who can hold their own in a technical due diligence when an investor or an enterprise customer starts asking.

That last cluster is the tell. A fractional CTO who only advises and never leads the team is an adviser with a better title. If nobody reports to them, even informally, and they are not accountable for whether things ship, you have bought consultancy rather than leadership. Both are legitimate; they are not interchangeable, and the adviser version costs a fraction of the price for a fraction of the effect.

How is it different from an interim CTO, a consultant or an adviser?

These four get conflated constantly, usually by people selling one of them.

The distinction that matters commercially is between fractional and interim. Interim is cover: someone fills a full-time seat until a permanent person starts, and the company already knows it needs that seat filled. Fractional is a bet that the seat should not be full-time yet. If you find yourself asking a fractional CTO to be available five days a week, the market has answered your question and you should be recruiting.

When does a scale-up actually need one?

Rarely at the moment people first think about it, and usually a few months after the symptoms appear. The signals that reliably mean "you need CTO-level cover" are:

• Technical decisions are queuing. Architecture calls, vendor choices and security questions are all waiting on one already-overloaded person - often the founder, sometimes the best engineer, who is now doing neither job well.
• Delivery has slowed and nobody can explain why. Velocity is down, estimates have stopped meaning anything, and every diagnosis you get is from someone inside the system.
• Due diligence is coming. A funding round, an acquisition, or an enterprise customer's security review. These surface every deferred decision at once, on someone else's timetable.
• You have promoted a strong engineer into a leadership gap. They are capable and struggling, because nobody has led a team in front of them and the company cannot give them the coaching the role needs.
• The AI agenda has an owner in name only. Everyone agrees it matters, several experiments exist, and nothing is in production. That specific gap is often better filled by fractional AI leadership than by a general technology remit.

Team size is a weaker signal, but a useful sanity check: roughly three to twenty engineers is the band where fractional fits best. Below that, a strong lead developer and a handful of advisory days usually does the job. Above it, the role tends to need someone in the building every day.

When do you not need one?

Three cases, and I turn work away for all of them.

• The founder is technical, available and current. If the CEO can still make the architecture calls and has the time to make them, adding a second opinion at executive level creates ambiguity rather than capacity. What you may need is a senior engineer.
• The real problem is hands, not judgement. If the direction is clear and the constraint is delivery capacity, hire or contract engineers. A part-time leader will not make the backlog smaller, and paying leadership rates for execution is the most common way to waste this budget.
• The work is genuinely, permanently full. Once you can describe twelve months of full-time senior technology work and you are ready to carry the cost, hire. Fractional at that point is a slower, more expensive way of reaching the same place.

What does it cost, and how does that compare to hiring?

The comparison people run in their heads is day rate against salary, which understates the permanent option considerably.

The median UK Chief Technology Officer salary was £100,000 in the six months to 1 September 2026 (IT Jobs Watch), and London scale-ups in fintech and SaaS run well above that. On top of base salary sit employer National Insurance at 15% on earnings above the secondary threshold (GOV.UK), pension contributions, benefits, and usually a recruitment fee of 20-25% of first-year salary. A full-time CTO is comfortably a £150K+ commitment in year one, before equity.

Then there is the timing cost, which is larger and less visible. Recruiting a senior technology leader takes three to six months from opening the role to a productive start, and most notice periods extend that. A fractional arrangement starts within days and is charged on a day rate or retainer, usually billed monthly - so cost scales with the cadence you pick, not with headcount, and it scales back down when the need shrinks. There is no equity, no employer NI, no recruitment fee and no long notice period on the way out.

The genuine downsides deserve equal billing. A part-time leader has less context than someone in the building daily, cannot be in every conversation, and has other clients. Deep institutional knowledge accumulates more slowly. Anyone who presents fractional leadership as strictly cheaper and better is selling. The trade is: you accept less presence in exchange for more seniority, sooner, with far less commitment - and for most scale-ups at this stage, that is the right side of the trade.

How long should it last, and how does it end?

A good fractional engagement is designed to end. Typical shape is three to six months to stabilise - fix the delivery process, make the deferred decisions, get the architecture onto a defensible path - then a lighter cadence while the team runs it.

The ending should be planned from the start, and there are only two decent versions of it. Either the workload never becomes permanent and the engagement winds down when the agenda is delivered, or it does become permanent and the fractional CTO helps write the role, sits on the interview panel and hands over to the person who takes it. What should not happen is a retainer quietly renewing for two years because nobody wrote down what "done" looked like. If you are considering a fractional arrangement, ask on the first call what the exit looks like; the answer tells you a lot about who you are dealing with.

How do you tell a good one from an expensive one?

Four questions, on the first call, before any proposal exists:

1. What have you shipped, and when did you last do this job? Technology leadership goes stale quickly. Someone whose last hands-on delivery was in 2019 is an adviser now, whatever the title says.
2. Who reports to you in an engagement, and what are you accountable for? If the answer is nobody and nothing, you are buying advice.
3. What does your exit look like? A specific answer - the conditions, the handover, the artefacts - separates a practitioner from a retainer.
4. How many clients do you have? There is a real number beyond which "one to three days a week" stops being true for anybody. Ask it directly.

The bottom line

A fractional CTO is a part-time technology executive with a full CTO's remit: strategy, architecture, delivery, team and assurance, at one to three days a week on a rolling basis. A company needs one when technology decisions have started queuing behind someone who cannot get to them, when due diligence is coming, or when a capable engineer has been promoted into a gap nobody in the company can coach them through - and does not need one when the constraint is hands rather than judgement, or when the work has clearly become full-time. The cost comparison is not day rate against salary; it is a rolling monthly commitment against £150K+ all-in plus three to six months of waiting.

If you want to see how it stacks up against a permanent hire or a larger consultancy, I have written that comparison here. And if you would rather just get a straight answer on which shape fits your situation - including "you do not need this yet" - that is a thirty-minute discovery call. See fractional CTO and fractional AI leadership for how I run each.