Two different jobs sharing one market. Buying the wrong one is expensive, and the usual way to find out is nine months of excellent advice nobody acts on.
The market has settled into using these two titles almost interchangeably, which is unhelpful, because they answer different questions and the people who are good at one are frequently not interested in the other.
The distinction is not seniority and it is not hours. It is this: a fractional CTO is accountable for what you build. A vCIO is accountable for what you run.
The clearest test
Does software form part of what you sell?
If yes, and you have engineers, then your hardest technology decisions are engineering decisions. What to build, what to buy, what the architecture should look like in two years, who to hire and in what order, how much technical debt is acceptable before it starts costing you customers. That is a fractional CTO, and they need to be close enough to the code to have an opinion that engineers respect.
If no, and technology is the thing your business runs on rather than the thing it sells, then your hardest decisions are operational and financial. What should this cost. What are we exposed to. What do we replace next year and what can wait. What do we tell the insurer. That is a vCIO.
Where the confusion is expensive
The expensive mistake is hiring a fractional CTO for a vCIO problem, and it happens because the CTO title sounds more substantial and the market prices it accordingly.
A professional services firm with 80 staff, no product, and a messy Microsoft 365 tenant does not have a technology strategy problem in the CTO sense. It has a planning and governance problem: nobody owns the budget, the risk register is a spreadsheet from 2023, three vendors are auto-renewing, and an enterprise client has just sent a 200-question security questionnaire nobody can answer.
Put an excellent fractional CTO into that and you will get an excellent assessment, a sensible target architecture, and very little movement, because the work that actually needs doing is unglamorous and continuous and does not look like the job they signed up for.
The reverse mistake is rarer but worse. A vCIO advising a software business on its product architecture is operating outside their competence, and the failure mode is a recommendation that sounds reasonable to the board and is wrong in ways only the engineers can see.
What you should be able to point at after six months
This is the question worth asking before you sign anything, because it exposes whether either party knows what the engagement is for.
From a vCIO, after six months, you should have a risk register that somebody reviews, a budget for next year with the reasoning visible, a vendor list with renewal dates and owners, and a one-page plan you could put in front of the board. You should also have a shorter list of things that used to worry you.
From a fractional CTO, after six months, you should have architecture decisions written down with their trade-offs, a hiring plan tied to what you are building, a view on the parts of the system that will not survive the next doubling, and engineers who can explain the direction without reading from a slide.
If six months in you have a lot of documents and nothing has changed, the problem is usually not the individual. It is that nobody internal was made accountable for acting on the advice, which brings us to the thing both roles depend on.
Neither works without an internal counterpart
Both of these are advisory roles. Advice goes nowhere unless somebody inside the business owns the decision it leads to.
That person does not need to be technical. In the firms where this works best, it is an operations director or a managing partner who has decided that technology is part of their remit, meets the advisor monthly, and is willing to say no to things. In the ones where it fails, the advisor reports to nobody in particular, their recommendations go into a shared folder, and everyone is mildly disappointed at renewal.
If you cannot name the person internally who will act on the advice, you are not ready to buy the advice yet.
Do you need either?
Often, no. Not yet, or not permanently.
Two situations where the honest answer is "not a retainer".
You need a diagnosis, not a relationship. If what you actually want is to know how bad things are, buy an assessment. Four to six weeks, a fixed fee, a report with a prioritised list. You can decide about ongoing advice once you know what you are dealing with, and you will be a much better buyer at that point.
You already have the person, they just have no time. Sometimes there is an internal person who could own this and is drowning in operational work. Taking the operational work off them is cheaper and better than adding an advisor above them.
Rough shapes
Specific numbers date quickly and vary enormously by market, so treat these as shapes rather than quotes.
A vCIO engagement for a business of 50 to 250 people is typically one to two days a month, structured around a quarterly review, with budget season and audit season taking more. It is a retainer because the value is continuity: the register, the plan and the relationships only compound if somebody keeps them current.
A fractional CTO is usually more time, often one to two days a week, and frequently has a natural end. Many of the good ones are explicitly building towards hiring their replacement, and will tell you so in the first conversation. That is a feature.
If you remember one thing
Ask what you will be able to point at in six months. Then ask who internally is going to act on it. If both answers are clear, the title on the contract barely matters.
