Hire the executive, then work out the job
The search runs on a specification assembled from current pain. The hire arrives, spends a year finding out what was actually needed, and either reshapes the role or leaves.
The comparison
Fractional CIO vs full-time CIO
This is usually framed as a question about budget. The more useful question is whether you yet know what you would be hiring the person to do.
The actual difference
You cannot recruit well for a role you have not defined
The case for fractional is normally made on cost, and cost is the least interesting part of it. A full-time CIO is expensive, at $250,000 and up before equity, benefits and recruitment fees. That is a real number, and it is not the reason most companies get this decision wrong.
They get it wrong because hiring a technology executive is among the most consequential decisions a company makes, and it is routinely made at exactly the moment the company understands its own technology least. The job specification gets written by people who are not technologists, from a list of current frustrations, and it describes a role nobody has scoped. The candidate is then assessed against it by interviewers who cannot evaluate the answers.
What follows is familiar. The hire is competent and the mandate is vague, so they spend their first year discovering what the role actually needed to be, which is the year you were paying them to deliver it. Or the mandate turns out to be smaller than the title, and somebody senior leaves within eighteen months because the job was not the one advertised.
A fractional engagement inverts the sequence. Somebody who has done the job establishes what is true, builds the roadmap, and in doing so produces the thing the recruitment process actually needed: a specification grounded in evidence rather than in frustration. Sometimes the conclusion is that you should hire, and now the job description is real, the first year's plan already exists, and there is somebody who can assess the candidates. That is a better outcome than a retainer, and it is a legitimate way for the engagement to end.
The fork
Two ways this usually goes
Define the job, then decide whether to hire
Establish what is true, build the plan, and see what the role has to be. If a full-time executive is the answer, you are now recruiting against a real specification with a plan already in hand.
Side by side
Fractional CIO and full-time CIO, on the axes that separate them
| Fractional CIO | full-time CIO | |
|---|---|---|
| Commitment | Month to month after the first ninety days | A permanent hire, with the cost of getting it wrong |
| Time you get | A defined cadence, days a month | Full time, including the parts that do not need an executive |
| Time to productive | Weeks, and has done this at your next size | Three to six months, plus the search before it |
| Annual cost | Tens of thousands, scoped to the mandate | $250,000 and up, plus equity, benefits and recruitment |
| Breadth of experience | Many estates, so patterns are recognised early | Deep in yours, over time |
| Where they are stronger | Direction, objectivity, and pace at the start | Presence, team building, and everything that needs to be there daily |
Which one you need
How to tell them apart
Go fractional when
- You know something is wrong but not yet what the role should be
- The need is direction rather than daily presence
- A specific decision is coming that the current setup cannot make well
- You want the option to conclude that a full-time hire is right, with a specification to recruit against
- The scale does not yet support an executive salary, but the decisions have executive consequences
Hire full time when
- Technology is how you make money, and the roadmap is the company's roadmap
- There is a real team to build, lead and retain, which needs somebody present
- The decisions are continuous rather than periodic, and waiting for a cadence costs you
- You already know what the role is, because somebody has done the work of defining it
- The scale genuinely justifies it, and you can attract somebody good at that scale
Questions
What people ask about this choice
Is a fractional CIO just a cheaper CIO?
No, and treating it that way leads to disappointment. It is a different shape of engagement: executive judgement on a defined cadence, rather than a full-time presence at a discount. If what you need is somebody in the building every day leading a team, a fractional arrangement will underdeliver no matter what it costs.
Can a fractional engagement become a full-time hire?
Frequently, and it is a good outcome rather than a failure. The engagement produces the evidence, the roadmap and the job specification, which is exactly what a search needs and rarely has. The adviser can also help assess candidates, which is hard to do well from inside a company that has never had the role.
How many days a month is typical?
Cadence is the single largest factor in what an engagement costs, and it is set by how much of the agenda you are handing over. Advice on decisions you bring is one shape; owning the roadmap, the budget, the vendors and the risk register is another. The models and what drives the number are set out on the cost page.
What happens to continuity when the engagement ends?
It depends entirely on what you own at the end, which is worth settling before you start. The roadmap, the risk register and the documentation should be yours outright and usable whether or not you ever work with the firm again. An engagement that leaves nothing behind has been consultancy rather than leadership.
Not sure which one you need?
That is a reasonable place to be, and it is usually answerable in a conversation rather than a proposal. Start with a thirty-minute call.
The other comparisons