Fractional Chief Technology Officer: What to Look For

A fractional chief technology officer in the UK is priced between £800 and £2,000 a day and works one to three days a week, according to Exec Capital's market summary, and that band includes three kinds of provider that share a job title and agree on almost nothing else. A board that sorts the shortlist by fee meets the wrong candidate first.

Three kinds of provider sit behind one job title

The former operator has held the CTO seat, reported to a board, approved a platform rebuild and lived with a build-versus-buy call for two years or more. Accountability for a technology function is something this person has already held.
The bench fractional CTO arrives through a consultancy, a recruiter or a fractional services firm. The commercial interest of the bench is between the candidate and the client.
The hands-on principal is an architect or lead engineer of real depth. The systems were built at first hand, a repository reads faster than a board pack, and a technology function at executive level has never been owned.

All three can be hired inside the same rate band. What separates them is set out below.

How the three compare on the attributes that separate them

Attribute that separates them	Former operator	Bench fractional CTO	Hands-on principal
Who signed the last architecture decision	That person's own signature, on a system they owned	A client's system, often delivered by someone else	That person's own signature, at code or service level
What the fee is charged against	Board-level accountability	Bench availability	A defined piece of work
What remains when the engagement ends	A technology function with a successor in place	A report and a continuing relationship with the bench	Working systems and a team able to extend them
Who bears the cost of a wrong call	The candidate, personally and in reputation	The bench contract sets a limit	The client's platform absorbs it first
How the first thirty days are spent	Reading the estate and meeting the board	Running the bench's standard diagnostic	In the repository and the delivery record

The five rows above do the sorting work. Each one is taken in turn below, with the question that tests it.

Ownership of the architecture decision

The single question to ask is which architecture decision the candidate signed, what it cost to reverse, and who argued against it at the time.

The former operator can point to a decision, the cost of reversing it, and the colleague who disagreed. The hands-on principal offers a service diagram and a rollback plan. The bench candidate reaches for a case study from the bench's marketing library. On its own that proves little, and it does show where accountability lies. A rebuild decision that nobody outside the team objected to is a decision nobody owned.

What the fee is charged against

A former operator charges for accountability, a bench fractional CTO charges for availability, and a hands-on principal charges for a piece of work.

The difference shows when the engagement goes wrong. A former operator's decision that creates a problem turns into a conversation about the record. A bench associate's error routes through an account manager. A hands-on principal's code fails in front of the client's own engineers. Only one of the three matches the risk carried by a platform rebuild, and the fee is identical across all three.

What remains after the engagement

One of the three leaves the client less dependent on the firm that sent them.

The former operator builds a function and recruits a successor. The hands-on principal writes code and mentors the team that will extend it. The bench fractional CTO leaves a report and a continuing relationship with the bench, which is a commercial outcome for the bench before it is an operational one for the client.

Ten Mile Square sets out its own version of the exit: engagements typically run three to six months, and the plan builds the client team's capability so the role can pass to a permanent hire. Test every candidate against the same question. What did the engagement look like in month seven?

Who bears the cost of a wrong call

A former operator bears it in reputation, the bench limits it by contract, and the hands-on principal leaves it on the platform.

That is no reason to avoid a hands-on principal. It is a reason to pair one with a board-level owner. The strongest technical candidate on a shortlist is often the weakest commercial one, and the fee gives no signal either way. A board that hires the principal alone buys excellent engineering and no executive cover.

How the first thirty days are used

The first month tells the board which of the three it hired.

The former operator spends it reading the estate, conferring with the board and writing a ranked risk register. The bench fractional CTO spends it running the bench's standard diagnostic. The hands-on principal spends it in the repository, the delivery record and the incident log.

TechCXO sets out the signals that push a business towards CTO-level leadership: a CTO lost, projects dragging, development costs out of proportion to progress, and a team that is busy without improving outcomes. A candidate with no answer for how those thirty days would be spent against those signals is selling a template.

The questions that do the sorting

Use these in the interview. A strong candidate responds to each point with a specific engagement.

Which technology decision did you personally sign off last, and what did it cost to reverse?
Which board did you report to, for how long, and what went in front of it?
What happened when engineering velocity and commercial pressure pulled in opposite directions?
Who argued against your last architecture call, and what became of the objection?
What did you leave behind that a successor could run alone?
How do you decide what not to build?
What is the first thing you would read in this estate, and what would you expect to find?
When have you told a board that the technology strategy was wrong?
What does a good handover look like?
Who else on the shortlist would you hire, and why?

If the first five come back vague, without a specific decision, a specific board and a specific consequence, the interview is over. Vention's guide to the search makes the same point from the other side: the need is assessed before candidates are sought, and cultural fit is tested as hard as technical depth.

The fee is not the separator

Day rates cluster because the market prices the title, and evidence is harder to price.

Exec Capital's market summary states UK fractional CTO day rates are £800 to £2,000, and the same document sets a permanent CTO's base salary at £120,000 to £220,000 before employer NI, benefits, equity and bonus. Two days a week of fractional cover comes to well under the full-time equivalent once those costs are counted, according to the same summary.

Full Stack Consulting starts its fractional service at £5,000 a month and sells three fixed-scope tiers above it: an audit at £995, a single-process sprint at £4,995, and a full architecture blueprint at £20,000. All three are assessments with a defined end, and each one is priced against the size of the estate it examines.

Bronson Technical Search sets out the hiring sequence from the same starting point: define the need, take recommendations, weigh experience, interview, take references and settle terms. The first step is the one most boards skip, and it is the step that decides whether the other five matter.

CTO Fraction's account of a fintech startup sets out the exit pattern in detail: a fractional CTO held the technology function through minimum viable product and product-market fit, a vice-president of engineering then took the seat, and the role moved to full time. That is a stage, a handover and a permanent hire, and it is the outcome a board should be able to picture before it signs anything.

Every figure above describes the shape of the market. The five questions at the start of the interview sort the candidates inside it.