Search for either term and you will find the same firms offering both, often on the same page, frequently as synonyms. That is convenient for the firms and unhelpful if you are the one buying, because the two roles answer different problems and the wrong one is expensive in a way that is hard to see until several months in.
The distinction is not the number of days. It is what is missing.
The actual difference
An interim CIO fills a seat that exists and is currently empty. There was a CIO, or there was going to be one, and right now there is not. The role has a shape already — a team reports into it, a budget sits under it, decisions are queued behind it. The interim's job is to hold that shape until somebody permanent arrives.
A fractional CIO supplies a capability the organization never had a seat for. Nobody left. There is no vacancy, because there was never a post. What there is instead is a set of decisions being made by default — by whoever shouted, by whichever vendor called, by the person who happened to have budget that quarter — and a growing sense that this is not a sustainable way to decide.
Four things follow from that, and they are what actually differ:
- Commitment. Interim work tends toward full-time or close to it, because the seat is full-time-shaped. Fractional is a slice, deliberately, because the decisions being made do not require somebody present every day — they require somebody senior present at the right moments.
- Mandate. An interim inherits a mandate, including its limits. A fractional usually has to establish one, which is slower at the start and is often the more useful half of the work.
- What success looks like. An interim succeeds if the handover is clean and nothing broke. A fractional succeeds if decisions get made, get made on evidence, and the organization can still explain why six months later.
- The exit. An interim's engagement ends on an event — the permanent hire starts. A fractional engagement ends when the capability is no longer needed at that level, which is a judgement rather than a date, and should be reviewable rather than locked.
Signals you need an interim
These are situational and mostly obvious once named. If several are true, you are looking for an interim and a fractional arrangement will underserve you.
- A CIO or equivalent has left, or is leaving, and a search is running.
- There is a team that reports into the empty seat and is currently unmanaged.
- Something is in flight with a hard date — a migration, an audit, an integration after an acquisition — and it needs daily ownership.
- The organization is mid-crisis and the work is triage, which does not schedule well into a slice of a week.
The common thread is that the work is continuous and someone has to be reachable. Buying a slice of a week for that produces a bottleneck with a senior job title.
Signals you need a fractional
- There has never been a CIO, and the technology decisions currently belong to a founder, a finance lead, or an MSP.
- Spend is rising and nobody can explain the shape of it, because each individual decision was defensible and nobody owns the total.
- There is a strategy question with real money attached — what to build, what to buy, what to stop — and the honest answer is that it is being decided by whoever is loudest.
- Vendors are setting the roadmap. This one is worth its own sentence: if the technology plan for next year is largely a list of things suppliers have proposed, that is not a plan, and it is the most common reason this role gets created.
- A permanent hire is not warranted, or not yet, and pretending otherwise would mean recruiting for a job the company cannot yet describe.
The two expensive mistakes
Buying interim when the problem is that the role was never defined. A seat falls empty, an interim is hired to fill it, and the interim spends the engagement doing the job as the previous occupant did it — because that is what filling a seat means. Nobody asks whether the seat is the right shape. Then a permanent hire is recruited against the same description, and the organization has paid twice to preserve a structure it never examined. The tell is a search that keeps failing: candidates decline, or the offers do not land. That usually means the role as written does not make sense, and no amount of interim cover fixes it.
Buying fractional when you actually need somebody in the building. A slice of senior attention is genuinely good value for decisions. It is poor value for a burning platform. If the work is continuous, has a hard date, and involves managing people day to day, fractional arrangements strain in a predictable way — things queue behind the days that person is available, and the queue is where the damage happens.
The question that separates them: if this person were unavailable for a fortnight, what would happen? If the answer is that decisions wait — fractional is the right shape. If the answer is that operations degrade, you need an interim, and probably a permanent hire behind them.
The one thing to insist on either way
Ask what survives the engagement.
Both roles are temporary by design, which means both can leave nothing behind. An interim who held everything together personally and wrote none of it down has handed the next person the same problem with a shorter runway. A fractional who made good decisions and documented none of the reasoning has produced a set of conclusions nobody can revisit when a premise changes — and premises change constantly in this particular area.
So the deliverable worth naming in the agreement is not a report. It is the written reasoning behind each material decision, in a place your own people can find it, in a form that says what would have to change for the decision to change. That artifact is the difference between having bought a capability and having rented a person.
Where we sit, and where we do not
We do fractional. That is a real limit rather than a positioning statement: if what you need is somebody holding a vacant seat full-time for six months while a search runs, we are the wrong call and would rather say so early than three meetings in. The same goes for day-to-day IT operations, a helpdesk, or device management — that is an MSP, and it is a different purchase.
What fractional CIO work is here: senior technology judgement bought by the engagement, aimed at the decisions rather than the operations, on platforms you hold in your own name. Nothing is resold, nothing is licensed through us, and the reasoning stays with you when the engagement ends.
Related reading: What a useful IT assessment contains — usually the first month of either engagement, and the four verdicts it should be able to reach. And technology due diligence: what actually moves the number, where key-person concentration stops being an inconvenience and starts being a valuation issue.