Founders and boards use "fractional CTO", "interim CTO" and "CTO-as-a-service" as if they were the same purchase. They are not. They differ on four things that matter more than the label: how much capacity you get, how much authority the person carries, how long the arrangement is meant to last, and what the exit looks like. Pick the wrong one and you either pay for a leader you cannot use, or you get a vendor when you needed an owner.
I have been on the receiving end of all three requests. After 50+ engagements as a fractional CTO, and a full-time CTO role at Spericorn before that (35+ engineers), I have turned down engagements that were really interim jobs or vendor jobs in disguise. The label on the inquiry rarely tells me what the company actually needs.
The market is moving fast, and the vocabulary has not caught up. According to Revelio Labs data featured in the Financial Times (September 2026), 24 of every 1,000 new executive postings were fractional in 2026, up from 9 five years earlier. In the same data, CFO roles are the largest fractional category at 20% of fractional executive postings, so technology is still catching up and the terms are still loose. If you want to know whether the fractional model itself fits your company, read The Fractional CTO Model: When It Works and When It Doesn't. This post is about choosing between the three models.
Three Models, One Gap
| Model | What it is | Who it usually suits |
|---|---|---|
| Fractional CTO | A senior technologist who embeds part-time, commonly a fixed number of hours or days per week, with an open-ended horizon. Owns strategy, architecture, hiring and board-level technical reporting. | Companies that need ongoing senior judgment but not a full-time seat: seed to Series B, non-technical founders, scale-ups whose VP Engineering runs delivery. |
| Interim CTO | A full-time, time-boxed executive who holds the actual CTO seat while the company is between leaders or inside a defined transition. The job ends on a date or on a handover to a permanent hire. | Post-departure gaps, pre-acquisition periods, turnarounds and replatforming. |
| CTO-as-a-Service | A productised offering from a firm or agency, usually a named lead backed by a bench, sold as a package: architecture reviews, roadmap, vendor management, sometimes delivery. | Very early companies that need a technical function set up quickly, or companies that want a vendor relationship rather than an executive one. |
On duration, the INIMA Europe 2025 survey (reporting 2024 data) put average interim assignments at 11.5 months, and the Stanton House Interim Management Survey 2026, published June 2026, reported average assignment length rising to 10 months. The same Stanton House survey found that almost a quarter of interims' most recent assignments were delivered on a fractional basis, which is exactly why the labels blur in practice.
Here is the opinion I will defend: the difference is not seniority. All three can be excellent operators. The difference is where accountability sits. A fractional CTO is accountable as a person. An interim CTO is accountable as the seat-holder. CTO-as-a-service is accountable as a contract.
The CADE Test: Capacity, Authority, Duration, Exit
I use four questions to separate the models. I call it the CADE test. The table shows how each model answers them; it expands on the choice laid out in my earlier post on the fractional model.
| Dimension | Fractional CTO | Interim CTO | CTO-as-a-Service |
|---|---|---|---|
| Capacity (how much of a person) | Part of one senior person's week, consistent week to week, same person every time | All of one person's week for the term, same person | A contracted bundle of hours or deliverables, possibly spread across several people |
| Authority (who can say no) | Owns technical decisions within an agreed scope, reports to CEO or board, usually no direct line management of the whole team | Holds the full seat: headcount, budget, hiring and firing, vendor sign-off | Advisory or scoped delivery authority; final technical decisions remain with the client unless contracted otherwise |
| Duration (how long it is meant to last) | Open-ended, reviewed quarterly, often runs for years | Fixed term, typically measured in months (surveys put averages at 10 to 11.5 months) | Subscription or project term, renewed or cancelled on notice |
| Exit (what success looks like at the end) | Either continues as the standing technical leader or hires their own replacement when the company outgrows part-time | Hands over to a permanent CTO; the engagement is designed to end | Contract ends or converts into a larger delivery relationship with the same firm |
Ask yourself the four questions in order:
- Capacity: do I need someone present every day, or someone present every week? Daily means interim or full-time. Weekly means fractional.
- Authority: do I need someone who can hire, fire and sign vendor contracts tomorrow? If yes, interim. If I need judgment and ownership of architecture and roadmap but keep line management inside the company, fractional.
- Duration: is there a date or event that ends this, such as a permanent hire, an acquisition closing or a migration finishing? If yes, interim. If the need is standing, fractional.
- Exit: at the end, do I want a person I can keep, a seat I can refill, or a contract I can cancel? That answer usually settles it.
Most companies that ask for "a fractional CTO" because it sounds cheaper actually fail question 1 or 2. If production is down weekly and the team is leaving, you need an interim with full authority, not a part-time advisor. I cover that failure mode in the "when it doesn't work" part of the earlier post.
Matching the Model to the Situation
| Situation | Usual fit | Why |
|---|---|---|
| CTO resigned, team of 15+, roadmap committed to customers | Interim CTO | Needs daily presence and full authority to hold the seat until a permanent hire; time-boxed by design. |
| Non-technical founder, outsourced dev team, pre-Series A | Fractional CTO | Needs a standing owner of architecture, vendor quality and hiring plan; part-time capacity is enough and the need does not end. |
| Pre-seed, no engineers yet, needs an MVP built and a stack chosen | CTO-as-a-Service (or fractional plus a delivery partner) | The need is largely delivery plus setup; a firm with a bench can start faster. Watch the conflict of interest if the same firm also builds. |
| Scale-up with a strong VP Engineering, now adding AI | Fractional CTO | Strategic layer on top of a working delivery machine; the VPE keeps line management. |
| Acquisition or funding diligence in the next two quarters | Interim CTO or a fractional CTO with a diligence mandate | Depends on whether someone must own the seat through close; if the permanent CTO is staying, fractional support on the diligence workstream is enough. |
| Regulated product (healthcare, finance) with compliance deadlines | Fractional or interim, not CTO-as-a-Service alone | Accountability must sit with a named individual the board can question, not with a vendor contract. |
These are defaults, not rules. The CADE test overrides the table.
Red Flags You Picked the Wrong Model
- You hired fractional but are messaging them at 11pm about an outage every week. That is interim capacity being bought at fractional hours; one of the two has to change.
- You hired interim but nine months in there is no search running for a permanent CTO. The interim has become an expensive habit with no exit; the Duration and Exit answers were never written down.
- You hired CTO-as-a-service and every roadmap recommendation ends with the same firm's delivery team doing the work. Advice and delivery from one vendor is a conflict of interest unless you consciously accepted it.
- The named lead keeps changing. Rotating people is fine for a help desk, not for the person who holds your architecture in their head.
- Your board cannot name who is accountable for security and compliance decisions. If the answer is "the vendor", you have no CTO of any kind.
- The engagement started without a written scope of authority. Whatever the label, if nobody wrote down what the person can decide alone, the model will fail on question 2.
What I'd do
- Write the CADE answers before contacting anyone. Four lines. If the answers say "daily, full authority, ends when we hire", stop calling it fractional.
- Hire the model, then the person. Interview for the model you need. An interim candidate should talk about handovers and search timelines. A fractional candidate should talk about standing cadence and what they will not take on. A CTO-as-a-service firm should be asked who exactly turns up and what happens if that person leaves.
- Put the exit in the contract on day one. For interim: the permanent search starts by week four and the interim helps run it. For fractional: a quarterly review with a defined trigger for converting to full-time, for example engineering headcount or a funding event. For CTO-as-a-service: a clause separating advice from delivery, or an explicit decision to accept the bundle.
- Keep accountability on a named person. Whatever the model, the board should be able to name one human who owns architecture, security and vendor decisions. If the model cannot give you that, choose a different model.
- Re-run the test every quarter. Companies change model more often than they think: fractional converts to full-time at scale, interim converts to fractional after the handover, CTO-as-a-service converts to a fractional or full-time hire once there is an internal team to lead. The failure is not switching, it is not noticing you should.
The Takeaway
The label on the invoice matters less than the four answers behind it. Fractional buys a standing owner at part-time capacity. Interim buys the whole seat for a defined period. CTO-as-a-service buys a contract with a firm. Decide on capacity, authority, duration and exit first, and the right model is usually obvious. Decide on the label first and you will spend months finding out it was the wrong one.
Frequently Asked Questions
What is the difference between a fractional CTO and an interim CTO?
A fractional CTO works part-time on an open-ended basis and owns technology strategy, architecture and hiring alongside the existing team, usually without the full seat's line management. An interim CTO works full-time for a fixed term, holds the complete CTO seat including budget and headcount, and is expected to hand over to a permanent hire. Industry surveys put average interim assignments at roughly 10 to 11.5 months (INIMA Europe 2025 survey; Stanton House Interim Management Survey 2026), while fractional engagements are open-ended and reviewed periodically.
Is CTO-as-a-service the same as a fractional CTO?
No. CTO-as-a-service is a productised offering from a firm or agency: you contract for a bundle of hours or deliverables, often backed by a bench of people, and the named lead can change. A fractional CTO is one named senior person who is personally accountable for your technology decisions. CTO-as-a-service can suit a very early company that needs a technical function set up quickly, but accountability sits with a contract rather than an individual, and the firm may have an incentive to sell its own delivery work.
When should a startup hire an interim CTO instead of a fractional CTO?
Hire an interim CTO when the need is full-time and time-boxed: the CTO has left, there is a team that needs a daily leader with hiring and budget authority, and the arrangement should end with a permanent hire or a defined event such as an acquisition. Hire a fractional CTO when the need is standing but part-time: you want ongoing senior ownership of architecture, vendors and the hiring plan without a full-time executive seat. The simplest test is capacity and exit: daily presence with a planned end date points to interim, weekly presence with no end date points to fractional.