A founder called me last month who'd talked to four different fractional CTO outfits in the same week. £1,200 a day. £1,800 a day. £6,000 a month. One "discovery package" at £4,500 just to scope the engagement. Four quotes, four day rates, four flavours of senior-sounding pitch. By the time he got to me he was about to make an expensive mistake — not because any of the four firms were bad, but because he'd never asked the question that comes before "which one?" He hadn't asked whether he needed a fractional CTO at all.
He didn't. He needed a senior developer for six months and a paid audit to scope the build. He hired neither at the time, paid £5,400 to one of the four outfits, ended the engagement at month two, and called me again the following quarter to ask what he should have done the first time. The answer hadn't changed.
Most founders shopping for a fractional CTO ask the wrong first question. The right first question isn't "fractional or full-time?" It's "do I need a technical hire of any kind right now?" Five times out of ten the answer is no. You need a senior developer, a one-off audit, three months of mentorship, or six months of patience. Only one of those five answers is "hire a fractional CTO". The other four cost a lot less and work a lot better in the contexts they fit.
I call the diagnostic the Four Forks. Four sequential questions, each routing you to one of five outcomes. The framework exists because most fractional-CTO advice you'll find online is sales content written by fractional CTOs — every sign points to hire-us. The Four Forks route most readers somewhere else, including most readers I'd lose money on by taking.
The Four Forks — Fork 1: Do you have a customer-facing software product?
The first fork is the cheapest one to get wrong. A fractional CTO is a technology leadership role for a business whose product or core operation depends on software you own and improve. If your product isn't software — if you're a service business with a website and a Stripe checkout, an ecommerce store on Shopify, or a marketing-led business running on a sales CRM — you almost certainly don't need a CTO of any kind.
What that looks like in practice. A tradesman with a website and a Google Business Profile doesn't need a fractional CTO; they need someone who can manage the GBP, optimise the booking flow, and pull data out of the CRM. That's a marketer or an ops person. A small ecommerce business doesn't need a fractional CTO; they need a Shopify specialist, a paid-ads strategist, or a CRO operator. A consultancy doesn't need a fractional CTO; they need a sales-ops person who knows their CRM and a senior contractor for the occasional integration.
The signal is binary. Does the business own a piece of customer-facing software that needs ongoing engineering judgement to keep working and improving? If no, the answer is mentorship if you want to learn to do this yourself, or a senior contractor in the relevant adjacent discipline if you want it done. Either route costs a fraction of any fractional CTO retainer, and both fit the business better than over-hiring.
If yes, continue to fork 2.
The Four Forks — Fork 2: Do you have someone writing code today?
Assume you passed fork 1. You own software; the product depends on it. The second fork is whether anyone is currently writing code for the business. The honest answer here matters because a fractional CTO is a leadership role, not an individual contributor role. They architect, they decide, they unblock, they hire — but in most engagements they don't ship the daily code themselves.
If the answer is "no one is writing code right now", a fractional CTO is the wrong first hire. You don't yet have anything for them to lead. The correct first move is a senior developer — someone who can write the code that proves the business hypothesis. A senior dev in the UK costs £80,000 to £120,000 a year in salary, or £450 to £700 a day on contract. Once they've been building for six months and the codebase is generating revenue, a fractional CTO becomes useful as the strategic layer over their work.
The honest exception. If you're at the audit stage — pre-build, pre-hire, trying to figure out what to build at all — a one-off paid audit (a few hundred to a couple of thousand pounds depending on scope) answers the question better than either a senior dev or a fractional CTO. The audit tells you whether what you're trying to build is the right thing to build, and what to build it with. Most people who think they need a fractional CTO at the pre-build stage need this instead.
If you do have someone writing code today, continue to fork 3.
The Four Forks — Fork 3: Are you making 5+ significant technical decisions per month?
Fork 3 measures decision load. A "significant technical decision" here means: architecture choices (monolith vs services, what database, what auth provider, what queue), hiring decisions (do we hire another engineer or use a contractor), vendor decisions (Vercel vs self-host, OpenAI vs Anthropic vs build), product-engineering trade-offs (ship this feature now vs invest in stability first), commercial-technical trade-offs (custom build vs SaaS integration), and infrastructure choices that affect cost or compliance.
If you're making one or two of these a quarter — a hiring decision once, an architecture review once — a fractional CTO is over-scoped. What you actually need is an advisor on retainer or a quarterly session. £500 to £1,500 for a senior brain on a single decision twice a year is cheap insurance against expensive mistakes, and it's the right shape of engagement for a business whose technical decisions are infrequent.
If you're making five or more of these a month, the senior brain needs to be in the room continuously. That's where a fractional CTO earns the fee. The constraint they relieve isn't "we don't know what to build" (the audit answers that) and it isn't "we don't have anyone to build it" (a senior dev answers that). The constraint is that you have decisions coming faster than you can think them through, and each wrong call costs weeks or months of rework. Fractional CTO is the role designed for that load.
If decision load is high, continue to fork 4.
The Four Forks — Fork 4: Is your revenue £100k–£5m (or VC-funded with >12 months runway)?
Fork 4 is the affordability and fit fork. A fractional CTO at UK rates costs £3,000 to £10,000 per month depending on the engagement size. For that to be a sensible spend you need either revenue or runway that absorbs the cost without burning more than 10–15% of monthly OPEX on the role alone.
Under £100k annual revenue, the maths usually doesn't work. A pre-revenue or sub-£100k business taking on a £5,000/month fractional CTO is spending 60% or more of its annual revenue on technical leadership, before any of the engineering work the CTO is supposed to oversee. The honest answer at this stage is to wait — keep building with whatever you have, validate the business model, and revisit when revenue clears six figures or you raise. If you want to use the time productively, the £149 audit and a senior contractor for specific builds will give you most of the strategic value at a fraction of the cost.
Over £5m annual revenue, or VC-funded with twelve-plus months of runway, you're approaching the point where a full-time CTO is justified. Fractional CTO is a stop-gap, not a destination. At this scale the executive is making decisions every day, the codebase needs sustained ownership, and the leadership team needs a peer who's in the building. Fractional engagement is the wrong shape — the gap between attention and demand grows every month. The right move is to start a full-time search, ideally with the fractional CTO as the hiring lead, then transition the role.
If your revenue sits between £100k and £5m, or you're VC-funded with healthy runway and not yet ready for a full-time technical executive — that's the band where a fractional CTO is genuinely the right call.
Where the Four Forks land you — the five outcomes
Five possible answers. Here's where the framework lands you.
| Your situation | The right hire |
|---|---|
| No customer-facing software (fork 1 = no) | Mentorship or senior contractor in the adjacent discipline. Not a CTO. |
| Software exists, but no one writing code yet (fork 2 = no) | Senior developer first. CTO comes later. |
| Software + code being written, but fewer than 5 technical decisions / month (fork 3 = no) | Quarterly advisor or a one-off paid audit. Fractional is over-scoped. |
| Software + code + 5+ decisions / month + revenue £100k–£5m (all four forks = yes) | Fractional CTO. This is the band the role is designed for. |
| Software + code + 5+ decisions / month + revenue >£5m or VC with long runway | Full-time CTO. Fractional is a stop-gap, not a destination. |
Why most founders get this wrong
The standard advice you'll find on the open web is written by fractional CTOs. Every page is a checklist where every sign — even mild ones — points back to hire-us. The "do you need a fractional CTO?" essays ranking on Google are sales content, not diagnostic content. The result is that founders self-diagnose their way into the wrong hire because they read four pages that all confirmed they need the thing those four pages were selling.
The diagnostic in this essay routes most readers away from us. Of the five outcomes above, only one is "fractional CTO". The other four are work we don't take. That's intentional. The £149 audit applies the Four Forks to your specific business in sixty minutes, and you walk out with the right answer — not necessarily "work with me". Most of the time it isn't.
The other reason founders get this wrong: the wrong hire is more expensive than no hire. A fractional CTO at £5,000 a month who's the wrong fit for a business that should have hired a senior dev costs £30,000 across the six-month minimum, plus the opportunity cost of the build that didn't happen because the leadership-shaped person couldn't ship the code-shaped work. We've seen this play out enough times that the diagnostic exists for it.
Common questions
How much should a fractional CTO cost in the UK in 2026?
UK fractional CTO rates in 2026 sit between £1,000 and £1,600 per day, or £3,000 to £10,000 per month on retainer. The range is wide because the engagement shape varies — a half-day per week advisory on a stable codebase costs less than a three-day-per-week embedded role on a fast-scaling product. London rates run 20–40% above Manchester, Leeds, Bristol or Sheffield rates for like-for-like work. A reasonable budget for a £500k–£3m revenue business is £4,000–£6,500 per month for a one-to-two day per week engagement. Anything substantially cheaper is usually either a junior in fractional's clothing, or a strategy-only role with no real delivery accountability.
How long does a fractional CTO engagement usually last?
Six months minimum is the standard contract. The realistic working range is twelve to eighteen months — long enough for the operator to ship meaningful structural change, short enough that they aren't slowly becoming an unaccountable senior advisor. Beyond eighteen months one of two things should happen: either the company has grown into needing a full-time CTO, or the work has wound down to advisor frequency and the engagement should be re-scoped to a lower-intensity retainer or ended cleanly. The failure mode is fractional CTO engagements that drift to year three or four without either transition — both sides lose.
Can a fractional CTO also write code, or is it strategy-only?
Depends entirely on who you're hiring. Most fractional CTO firms position the role as strategy-only — the partner-and-associates model where the senior name is on the contract and juniors do the build. Operator-led practices put the same person on the strategy and the code, because the strategy you'll execute is the strategy you wrote and the code you'll ship is the code you understand. The difference matters most at the production-incident moment: the operator-led model means the person who shipped the code is the person debugging it at 11pm on a Sunday. The strategy-only model means a queue of escalations. The cheapest way to find out which one you're being pitched is the three-question Operator Test.
When should I transition from a fractional CTO to a full-time one?
Two clean signals. First, revenue or headcount: when the engineering team passes eight people, or annual revenue clears £5m, the role is full-time. The cadence of decisions and the load of people-management outpaces a part-time engagement. Second, fundraising and board pressure: institutional investors past Series A typically want a full-time technical executive in the leadership team. The fractional CTO often becomes the hiring lead for their full-time replacement and stays on for two to three months of overlap. The worst outcome is to let the fractional engagement drag past the point of justification because nobody had the conversation. Build the trigger into the original engagement contract — revisit fractional vs full-time at twelve months or £5m revenue, whichever comes first.
What's the fastest way to figure out which of the Four Forks applies to my business?
The Four Forks are designed to be self-applicable — sit down for thirty minutes with the framework and you'll usually land somewhere clean. If you don't, or if you land on "maybe two outcomes", that's what the £149 audit is for. Sixty-minute paid consultation, written follow-up within 48 hours, the answer is whichever of the five outcomes actually fits your business. The output is the answer, not a sales pitch. If the answer is mentorship, the audit recommends mentorship. If the answer is a senior developer, the audit recommends a senior developer. If the answer is "wait six months and revisit", that's what the written follow-up says.