What a fractional CIO actually does for a 20-person company
Most people hear "CIO" and picture someone running a department of forty. In a twenty-person company the role is almost entirely about a handful of decisions a year, and about who is in the room when they get made.
What does a fractional CIO actually do?
A fractional CIO owns the technology decisions a business cannot afford to get wrong, on a set number of days each month. In practice that is four things: the roadmap, the budget, the vendors, and the hiring.
The roadmap is the artefact everything else hangs off. It says what gets fixed, what gets replaced, what gets left alone and roughly what each costs, over the next twelve months. Without one, technology spending is a series of individually reasonable decisions that add up to something nobody chose.
The budget work is mostly saying no in a structured way, and being able to explain why to a finance director. The vendor work is reading contracts before they are signed, challenging renewals rather than waving them through, and cancelling licences nobody has used since someone left. The hiring work is knowing which two roles matter and which three can wait.
What a fractional CIO does not do is fix laptops. That is a different job, and conflating them is the most common reason small businesses end up with neither done well.
When does a business actually need one?
The trigger is rarely headcount. It is the moment when someone is making technology decisions as a side effect of another job, and it is starting to show.
Common shapes: an operations manager who has become the de facto IT lead and is now negotiating a five-year contract they have no basis to evaluate. A finance director who cannot explain the technology line to the board. A founder who has bought four systems that do not talk to each other, each for a good reason at the time.
The other trigger is a decision that is expensive to reverse. A major renewal, an office move, an acquisition, a system replacement. Those are worth bringing experience to even if nothing else changes.
How is that different from an MSP's vCIO?
The difference is who pays them and what they are selling. A managed service provider's "virtual CIO" is usually a senior account manager for the support contract you already have, and their recommendations tend to route through their employer's product catalogue.
That is not necessarily dishonest, and a good vCIO can be genuinely useful. But the incentive is structural: nobody recommends replacing a service they are paid to deliver.
An independent fractional CIO has no commission riding on the answer, which matters most in exactly the situations where the advice is worth the most — whether to renew, whether to replace, whether to bring something in house. It also means they can hold your MSP to account, which is a service your MSP cannot perform on itself.
The two are not substitutes. Most businesses want both: someone keeping things running, and someone independent deciding what should be running.
What do the first ninety days look like?
Almost entirely listening, then one document.
The first weeks are spent finding out what the business actually runs, what it spends, and which work the team repeats. That last one is the most revealing and the most often skipped: the gap between how a system is meant to work and how people actually use it is usually where the cost is hiding.
Then the roadmap gets written, and it should be short enough to read. Ranked, costed, and specific enough to act on. If the honest answer is that two of the four items can be done in house without help, it should say that too.
After that the rhythm is quarterly. Review what changed, re-rank what is left, and be reachable in between for the decisions that cannot wait.
What does it cost, and how is it structured?
Fractional CIO work is normally billed monthly against an agreed number of days, rather than hourly. That matters more than the figure: a day-based arrangement makes the cost predictable and makes it obvious when the engagement should shrink.
The thing to look for is what happens when you want to stop. A month-to-month arrangement with a short notice period tells you the supplier expects to keep earning it. A long minimum term is a signal about their confidence, not yours.
Ask, too, what you keep. The roadmap, the documentation and anything built should be yours and should be legible to another supplier. A plan only one consultancy can read is a plan that has locked you in.
What should you expect to change?
Within a quarter, the main change is usually that decisions stop being made in a hurry. There is a document to check them against, and someone accountable for keeping it current.
Within a year, the visible changes tend to be cost and clarity: fewer overlapping tools, contracts that were negotiated rather than accepted, and a technology line in the budget that someone can explain.
What should not change is your team's day-to-day tooling, at least not immediately. A fractional CIO who starts by replacing everything is not doing the job; they are doing a project and calling it leadership.
Want this applied to your business?
It starts with a 15-minute call: what you run, what is slowing you down, and whether we are any use to you. A short written summary afterwards either way.