The fractional-versus-permanent CTO decision is one of the most consequential technology hiring choices a mid-market business makes. It is also one of the most misunderstood. The right answer depends less on cost and more on the nature of the technology work the business needs done, the maturity of the existing team, and the speed at which capability is required. This guide explains how to choose.

The short answer

If you need senior technology leadership immediately, on a defined scope, with a clear exit, and the business cannot justify or attract a permanent CTO at the right level - fractional is the right model.

If you need a long-term technology owner who is embedded in culture, builds an internal team over years, and is accountable for the technology function as a whole - permanent is the right model.

Most mid-market businesses get this decision wrong in one direction: they hire permanent when they need fractional, because permanent feels safer. The result is a sub-scale permanent CTO who cannot operate at the level the business actually requires, or a strong permanent CTO who is underutilised because the business does not yet have the scale to keep them busy on strategic work.

The diagnostic question: if you knew exactly what the technology agenda was, with named deliverables and dates, would the work require a CTO for two days a week or for five? If the honest answer is two days, fractional is the right model - and trying to staff that with a permanent hire produces either a frustrated CTO doing too little senior work or a junior hire dressed up with the CTO title.

What each model actually is

The terms are used loosely, which compounds the confusion. Concrete definitions matter.

Fractional CTO

A senior technology executive engaged on a part-time basis - typically one to three days per week - for a defined scope and timeline. They are accountable for strategic technology decisions, governance, vendor management, board reporting, and developing the internal team. They are not consultants; they are accountable leaders who hold the technology brief for the business during their engagement. They sit in your leadership meetings, present to your board, and own technology outcomes. See What is a fractional CTO? for the full definition.

Permanent CTO

A full-time technology executive employed directly by the business. They have a long-term mandate - typically three to seven years - to build and lead the technology function, hire and develop a team, set the technology strategy, and be accountable for technology outcomes across the business lifecycle. They are an employee, with the rights, obligations, and total cost of employment that implies.

The boundary between the two is sharper than people assume. A fractional CTO who works five days a week for an indefinite period is not fractional; they are a contractor. A permanent CTO who only works on strategic matters and delegates everything else is not really running the function. The choice is between two distinct operating models, not two pricing models.

When a fractional CTO fits

Six situations where fractional is consistently the right answer:

1. You need senior capability faster than you can hire it

A good permanent CTO search takes four to six months. Mobilising a fractional CTO takes one to two weeks. For situations where the business cannot wait - a programme in trouble, an investor asking hard questions, a technology leader who has just left - fractional fills the gap immediately. Many engagements then transition to a permanent hire once the immediate situation is stabilised.

2. The scope is genuinely part-time

If the strategic technology agenda is two days a week of senior work plus delegation to a capable internal team, a fractional CTO is the right shape. Hiring permanent for this scope produces an executive who is bored, expensive, or invents projects to stay busy.

3. The business needs specific expertise for a defined period

Major technology programmes - ERP selection, platform migration, M&A integration, regulatory remediation - require senior leadership for the duration of the work but rarely afterwards. Fractional gives you the seniority for the engagement without committing to permanent overhead once the work is done.

4. You cannot attract a permanent CTO at the level you need

Mid-market businesses competing for senior technology talent against larger companies with bigger budgets, recognised brands, or more interesting technology often struggle to attract permanent CTOs at the level they actually need. Fractional engagements with senior practitioners are accessible to mid-market businesses in ways that permanent hires at the same seniority typically are not.

5. You are testing whether the role is needed at all

Some mid-market businesses are not sure whether they need a CTO or whether they need a head of IT. A fractional engagement of three to six months reveals which one the business actually requires, with no permanent commitment if the answer is the latter.

6. The business is between life stages

A business approaching a transaction, a regulatory change, or a strategic pivot may need senior technology leadership specifically for that period, with no clarity yet on what the post-event organisation looks like. Fractional gives you the capability now and the flexibility to redesign the technology function once the situation settles.

When a permanent CTO fits

Equally, five situations where permanent is the right answer:

1. Technology is the product

If your business is a software business, a technology platform, or an organisation where technology IS the proposition rather than the enabler, you need a permanent CTO who is embedded in product strategy, builds a deep internal team, and is accountable across the multi-year technology arc.

2. The technology agenda is genuinely full-time

If senior technology work fills five days a week, every week, with a multi-year horizon, the operating model needs a permanent CTO. Fractional at full-time hours is more expensive than permanent and produces less continuity.

3. You are building deep technical capability internally

If the strategy is to grow a strong internal technology team that competes on capability with the best in the market, that takes years and requires a permanent leader who is recruiting, developing, and retaining people on an open-ended basis.

4. Continuity and cultural fit are critical

Some businesses need a technology leader who is genuinely of the business - immersed in its culture, recognised by customers, trusted by the board over years. Fractional engagements rarely provide that depth of continuity.

5. The business has scaled past the fractional threshold

At a certain size - typically £50m+ turnover with a substantial internal technology team - the technology function becomes too large and too interconnected for part-time leadership to be optimal. The transition from fractional to permanent at this scale is a natural progression, not a failure of the fractional model.

Side-by-side comparison

Dimension Fractional CTO Permanent CTO
Time to mobilise 1-2 weeks (often less) 4-6 months
Typical commitment 1-3 days/week, 3-18 months Full-time, 3-7 years
Seniority accessible Genuine C-suite, often previously held permanent CTO roles at larger orgs Depends on what the business can attract and pay
Exit Defined upfront, typically with handover to internal lead or permanent hire Resignation, retirement, or termination - typically 3-6 months notice
Risk profile Capability risk transferred to provider; commercial risk capped by scope Hire risk borne by business; mis-hire is expensive to unwind
Culture fit Less deep; designed for time-boxed engagement Deep; the CTO becomes part of the culture
Team building Develops existing team; rarely hires permanent staff Builds long-term technology team and capability
Board reporting Direct - sits in SLT meetings and board sessions during engagement Direct, ongoing
Vendor management Active - often the trigger for the engagement Active across the multi-year arc
Best fit business size £10m-£50m turnover; technology is enabler not product £50m+ or any size where technology is the product

The true cost comparison

The cost comparison is the section that gets most misunderstood. Headline day rates and salary figures do not represent the true cost of either model. Total cost of ownership across the engagement is what matters.

Permanent CTO total cost of ownership

A senior CTO base salary in the UK mid-market is one component. On top of that, factor in:

  • Pension, NI, benefits, employer obligations - typically 25-35% of base
  • Bonus (often 20-30% of base in mid-market technology roles)
  • Equity or long-term incentive (varies dramatically by business)
  • Recruitment costs (typically 25-30% of first-year base via search firms)
  • Onboarding time - the first 3-6 months are typically not full productivity
  • Retention costs over a multi-year tenure
  • Exit costs (notice period, garden leave, transition handover)

The fully-loaded first-year cost of a permanent senior CTO typically runs to 1.5-2x the base salary once everything is accounted for. The multi-year commitment compounds this.

Fractional CTO total cost of ownership

Fractional pricing is typically structured as a day rate or monthly retained fee, multiplied by the engagement duration. The cost components are:

  • Day rate or monthly fee - higher per-day than salary cost, lower per-week than a full-time permanent equivalent
  • No employer NI, pension, benefits, recruitment, or onboarding cost
  • No multi-year commitment - engagement ends when the scope is delivered
  • No exit cost beyond the agreed handover

The fully-loaded cost of a 12-month fractional engagement at 2 days a week is usually materially lower than the fully-loaded cost of a permanent CTO at the same level of seniority for the same period.

The break-even point

The cost crossover happens at approximately 3 to 3.5 days a week. Below that, fractional is reliably cheaper than permanent for equivalent seniority. Above it, the economics tilt toward permanent. This is one reason why fractional engagements that consistently run at 4-5 days a week tend to convert to permanent hires - the business is implicitly paying for permanent already.

The most important point about cost: cost should not be the deciding factor. The deciding factor is the shape of the technology agenda. Choosing the wrong model to save money usually costs more than choosing the right model at any price.

Capability differences

Capability is where the two models genuinely diverge, and where the decision should be made.

Fractional CTO capability profile

Fractional CTOs are typically senior practitioners who have previously held permanent CTO roles at larger or comparably-complex organisations. They bring:

  • Pattern recognition from many businesses, including the specific situation you are in
  • Strong technology-strategy and architectural capability
  • Vendor and supplier governance experience
  • Board-level credibility
  • Ability to mobilise and operate immediately
  • Network of practitioners who can be brought in for specific gaps

What they typically do not bring: deep institutional knowledge of your business (this takes time), long-term team-building capability (they will develop your team but rarely hire permanent staff into it), or the cultural continuity that comes from being present every day.

Permanent CTO capability profile

A strong permanent CTO at the level your business actually needs brings:

  • Deep institutional knowledge built up over years
  • Multi-year team building - hiring, developing, retaining
  • Cultural integration that allows them to influence beyond the technology function
  • Continuity across business life stages
  • Long-term ownership of technology strategy and roadmap

What they may not bring: the depth of pattern recognition that comes from operating in many businesses, immediate mobilisation, or the flexibility to flex hours up and down as the business needs.

The honest comparison: a strong fractional CTO and a strong permanent CTO are different capabilities, not the same capability at different intensities.

Risk profile of each

The risk profiles are asymmetric and worth understanding explicitly.

Risks of choosing fractional

  • Continuity risk: when the engagement ends, the senior capability leaves. If the internal team has not been developed during the engagement, the business is back where it started.
  • Depth risk: a fractional CTO may not be present enough to spot subtle cultural or political dynamics that a permanent hire would.
  • Provider dependency: if the fractional CTO is the only senior technology voice, the business depends on the provider relationship continuing well.

Risks of choosing permanent

  • Mis-hire risk: a senior technology hire that does not work out is expensive to unwind - typically 12-18 months of cost plus the opportunity cost of the wrong direction.
  • Scale mismatch: a permanent CTO hired at a level the business cannot sustain is either expensive overhead or under-utilised talent who will leave.
  • Time-to-impact: 4-6 months to hire, plus 3-6 months to be effective. The first nine months can pass before meaningful work happens.
  • Lock-in: once permanent, exiting the relationship is a significant event - notice period, replacement search, handover, knowledge transfer. The business is less optionable.

Mid-market businesses systematically underestimate mis-hire risk and overestimate continuity risk. The actual mid-market data on permanent CTO tenure suggests that the average first-time mid-market CTO hire lasts under three years, often less - which is shorter than many fractional engagements.

When to transition between them

The two models are not permanently separated - many fractional engagements are explicitly designed as the bridge to a permanent hire. Three transition patterns are common.

Fractional to permanent

The pattern: a fractional CTO stabilises the situation, designs the future-state technology function, helps recruit the permanent CTO, and supports the handover. This is often the cleanest way to fill a senior technology gap because the fractional CTO can credibly assess the permanent candidates and design the role specification.

Typical timeline: 6-12 months of fractional engagement with a 30-60 day overlap into the permanent hire.

Permanent to fractional

Less common but real. When a business that has outgrown its permanent CTO recognises that the next phase needs different capability, transitioning to a senior fractional CTO can be cleaner than another permanent search. Also relevant when a business is winding down or being prepared for sale - fractional gives the leanest senior technology presence for the remaining period.

Hybrid steady state

Some businesses settle into a steady state of internal head of technology plus fractional CTO as the strategic overlay. The permanent role runs the technology function day-to-day; the fractional role provides board-facing strategy, vendor governance, and senior-pattern-recognition without the cost of a permanent CTO. This works particularly well for businesses in the £20m-£50m band.

Common mistakes when choosing

Five mistakes that account for most fractional-versus-permanent mis-hires in mid-market businesses.

1. Choosing on cost alone

Treating the decision as primarily commercial. The biggest cost of either model is the cost of getting the choice wrong - which is invariably greater than the cost difference between the two.

2. Hiring permanent because it feels safer

Permanent feels like the more committed, professional choice. In practice, for many mid-market situations, it is the higher-risk choice because the business is committing to a multi-year, multi-hundred-thousand-pound investment in a role whose shape it does not yet understand.

3. Hiring fractional and treating them as a consultant

A fractional CTO is a leader, not a consultant. Treating them as a vendor - excluded from SLT, not invited to board, asked to produce slide decks - wastes the capability and produces frustration on both sides.

4. Mis-sizing the seniority

Hiring a "fractional CTO" who is actually a senior contractor with no genuine C-suite experience. Or hiring a permanent CTO who is a strong head of IT promoted into a role they are not yet ready for. Both produce the same outcome: a title without the capability to match.

5. Not planning the transition

Engaging fractional with no view on what comes next, or hiring permanent with no plan for how to support them in their first 90 days. Both decisions need a clear forward view, not just a hiring decision.

The decision framework

Five questions, in order. The answers point to the right model.

Question 1

Is technology the product, or the enabler?

If technology is the product, default to permanent. If technology is an enabler of a non-technology business, both models are viable - continue to question 2.

Question 2

What is the shape of the technology agenda?

If you can describe a defined scope of work with a credible end-point, fractional is viable. If the agenda is open-ended, multi-year, and embedded in the daily operation, permanent fits better.

Question 3

How urgent is the need?

If the business needs senior technology capability within four weeks, fractional is the only realistic path. If the business has six months to find the right person, permanent is feasible.

Question 4

Can the business attract the calibre of permanent CTO it needs?

Be honest about this. If the answer is no - the brand, scale, technology, or location does not pull the senior talent you need - fractional gives access to that calibre that permanent does not.

Question 5

What does the technology team look like in three years?

If the answer is a larger, deeper internal function led by someone embedded in the business, permanent is the right destination - though fractional may be the right starting point if you cannot fill the role today. If the answer is a lean function with senior strategic overlay, hybrid or fractional steady-state is right.

The decision rarely produces an absolute answer in either direction. What it produces is clarity about what the business needs - which is the necessary precondition to either hiring well or engaging well.

One last test: if the business made the wrong choice and had to reverse it, which model would be more recoverable? In most mid-market situations, the answer is fractional - exiting a fractional engagement is cleaner than unwinding a permanent hire. This is the reason many advisors recommend defaulting to fractional when the decision is genuinely uncertain.

Conclusion

The fractional-versus-permanent CTO decision is fundamentally about matching the model to the shape of the technology work the business needs done. Cost matters; speed matters; capability matters - but none of them is the deciding factor. The deciding factor is whether the agenda is defined and time-boxed (fractional) or open-ended and embedded (permanent).

Mid-market businesses that get this decision right tend to do one of two things: they default to fractional when the agenda is unclear and the urgency is high, transitioning to permanent once the shape stabilises; or they go permanent from the start when technology is the product and the multi-year arc is clear. Both routes work. The middle path - mis-sized permanent or under-utilised fractional - is where most of the mis-hires happen.

If you are mid-decision, the lowest-cost first step is an Executive Discovery Scan: 5 days, scoped to surface whether the operating model needs permanent leadership, fractional leadership, or something else entirely. It removes the risk of making the choice on incomplete information.

Not sure which model fits?

Independent diagnostic that surfaces what the business actually needs - permanent, fractional, or a hybrid. Fixed scope, senior-led, no obligation.