Fractional CTO, interim CTO, or lead developer: which one you need

These three roles get used as if they mean the same thing, but they solve different problems, and the cost gap between them runs from a few thousand a month to over thirty thousand, so hiring the wrong one is expensive twice: once for the fee, and again for the problem that does not get solved. This article sets out what each role actually does, the real UK day rates and monthly costs in 2026, and a plain decision framework for working out which one your store needs. It finishes with the most common mis-hire and what it costs, and how to structure the engagement so you get delivery instead of a monthly invoice for advice.

The difference that matters is not seniority. All three can be genuinely senior people. It is what they do with their time and how much of that time you actually get. Start there and the titles stop being interchangeable.

The three roles at a glance

Side by side, on the attributes that actually drive the decision and the cost:

What each actually costs, honestly

The reason the choice matters is the spread. Getting it wrong is not a rounding error, it is a multiple. Here is roughly what a growing UK store pays per month for each, at a typical cadence, in 2026.

A fractional CTO in the UK runs roughly £900 to £1,600 a day in 2026 [1][4]. At one day a week that is about £57,000 a year; at two days a week about £115,000 [2]. Experienced operators serving funded startups sit at £8,000 to £16,000 a month [2]. The framing that sells it is real: you get executive-level seniority for roughly 40 to 65 percent less than the all-in cost of the same person full-time [2].

An interim CTO is full-time and temporary, at similar day rates of £1,000 to £1,600, which is £20,000 to £32,000 a month [3]. You pay more per month because you are buying all of someone's time, not a slice of it. That is correct when you genuinely need daily senior presence, and wasteful when you do not.

A permanent CTO at a UK Series A store is £120,000 to £180,000 base, and once you add employer National Insurance, pension, recruitment fees and the rest, year one comfortably tops £170,000 [2]. That is the number the fractional and interim options are quietly measured against, and it is why both exist.

A lead or fractional senior developer is a different budget entirely, a senior contractor rate rather than an executive one, because you are paying for delivery, not governance. If your problem is that you need something built and built properly, this is usually the honest answer, and the cheapest of the four.

A plain decision framework

Forget the titles for a moment and answer honestly. Whichever line describes your situation is your answer.

• A decision with multi-year consequences and no senior technical head. Replatforming, choosing between Shopify Plus and a headless build, planning how to scale before a big season. You need the right call made and owned, not someone every day. That is a fractional CTO. [7]
• Your CTO just left, or you are mid-transition, and need daily senior hands now, for a known window. A merger, a migration, a crisis. That is an interim CTO. [3]
• The gap is delivery, not direction. You know what you want built and need someone senior to build it well and steer a couple of developers. That is a lead or senior developer.
• Your engineering team is past roughly fifteen people and complexity demands daily executive presence. You need a permanent CTO, and a good fractional one will tell you that and help you hire them. [8][2]
• You are not sure which of these you are. That uncertainty is the first thing a fractional CTO earns their fee on: a short, honest scoping engagement to tell you which role you actually need, including if the answer is none yet. [8]

The mis-hire, and what it costs

Three mistakes come up again and again, and all three are avoidable once you have matched the role to the problem rather than the title.

The first is hiring a fractional CTO when the job was delivery. You pay a strategic day rate for someone whose value is decisions, then get frustrated that nothing is shipping, because shipping was never the deal. You wanted a lead developer, and the cost is months of retainer against a codebase that has not moved.

The second is the reverse, and pricier: retaining an interim CTO, at £20,000 to £32,000 a month, for a need that was ongoing and part-time [3]. That is a fractional engagement wearing the wrong label, and you are paying three to four times over for time you are not using. Interim is for a gap with an end date. If there is no end date, you wanted fractional or permanent.

The third is quieter: hiring a capable developer to make architecture decisions. They will build what you ask, well, and it will be the wrong thing at scale, because choosing the platform and the architecture is a different skill from implementing it. That bill arrives later, as a rebuild, and it is usually the most expensive of the three.

How to structure it so you get delivery, not just invoices

Day rate or retainer. A retainer, a fixed number of days a month, suits an ongoing fractional relationship and keeps you both honest about scope. A day rate suits short or spiky interim work [1].

Scope the outcomes, not the hours. Own the replatform decision and the 90-day plan, not be available on Tuesdays [6]. A good operator will push for this framing too, because it protects them as much as you.

Agree the exit up front. The best fractional and interim engagements have a defined end, or a defined graduate-to-permanent trigger, built in from day one. If the person you hire is not talking about the point at which you no longer need them, treat that as a flag.

The bottom line

Match the role to the problem. Strategy and direction, part-time and ongoing, is fractional. A full-time gap with an end date is interim. Building things well is a lead developer. The titles are close enough to blur, but the problems behind them are not, and the cost of blurring them is a multiple, not a margin.

If you are not sure which one your store needs, that is worth a short conversation before it is worth a contract. I offer a scoping call to work out which role fits the problem in front of you, including when the honest answer is that you do not need one yet.