The difference between a virtual CIO and an IT consultant is not a difference of skill, seniority or subject knowledge. The same individual can credibly do both jobs, often in the same week. The difference is the engagement model — whether you are buying an ongoing relationship that is still there when the consequences of its own advice arrive, or a bounded piece of expertise that produces a defined deliverable and then leaves. Almost every disappointing outcome in this area traces back to a business buying one and expecting the behaviour of the other.
This guide separates them properly. It covers what each engagement model actually commits to and what it does not, when a UK business genuinely needs ongoing strategic governance rather than project expertise, how the pricing differs and why comparing day rates is misleading, what accountability means in practice given that neither party is contractually liable for your business outcomes, the structural conflict that exists whenever the organisation advising you on what to buy is also the organisation selling it, and the specific questions worth asking before signing either kind of contract. The comparison against employing a CIO outright is a separate question, covered in our guide to virtual CIO against an in-house CIO.
The distinction is the engagement model, not the expertise
Start with what each one is actually selling. An IT consultant sells a deliverable: a cloud migration design, a vendor selection recommendation, a security architecture review, a technology due diligence report for an acquisition. The scope is defined in advance, there is an acceptance point, and the engagement has a natural end. The consultant is accountable for the quality of the deliverable against the brief.
A virtual CIO — sometimes called a fractional CIO — sells continuity of judgement. There is no single deliverable; there is a standing role, typically one to four days a month, in which someone senior holds the technology strategy, maintains the risk register, owns the three-year roadmap and the budget that supports it, governs the supplier relationships, and translates between the technical estate and whoever is accountable at board level. They are accountable for the trajectory of the estate over time.
That distinction produces three consequences that matter more than anything on a capability matrix.
The first is accumulated context. A consultant arrives without history and spends part of the engagement acquiring it, which you pay for. A vCIO who has been in place two years knows why the odd decision was made in 2024, which supplier relationship is strained, which department will resist a change and why, and which previous initiative failed and what killed it. That context is not recoverable by briefing and it is the largest part of what a mature vCIO relationship is worth.
The second is who is present when the recommendation lands. A consultant’s advice is delivered and the consultant departs; the consequences arrive six, twelve or twenty-four months later, by which time nobody involved in the recommendation is in the room. A vCIO who recommends a platform is the person sitting in the review meeting when it is underperforming. This is not a moral point about diligence — good consultants are diligent — it is a structural point about whose problem the outcome becomes.
The third is what the engagement optimises for. A consultant is rewarded for a defensible, well-argued deliverable. A vCIO is rewarded for an estate that keeps working and a board that keeps being unsurprised. Those are different objectives, and they produce different advice in genuinely difficult cases — particularly on whether to do something at all, where a consultant engaged to design a migration has little incentive to conclude that the migration is unnecessary.
Before approaching anyone, write down whether the thing you need has an end. “We need to decide whether to move our ERP to the cloud” has an end and wants a consultant. “We do not know what we should be spending on IT or whether our risks are covered” has no end and wants a vCIO. If you cannot tell, the honest answer is usually that you have an ongoing governance gap that has surfaced as a specific question — in which case answering the question alone will leave the gap, and the same question will recur in a different form next year.
Where buyers get this wrong
The grid below groups the recurring confusions we encounter when UK businesses procure strategic IT help. The badges reflect how much each error costs, in money or in wasted time, rather than how common it is.
The first row of the first card is the most expensive error in the set, and it is the one that repeats. An organisation with no ongoing IT leadership experiences the absence as a series of specific questions — should we move to the cloud, is our security adequate, why has our spend gone up. Each is answerable by a consultant, each gets answered, and the underlying condition is untouched. Three consultancy engagements over four years frequently cost more than the retainer that would have prevented the need for any of them, and leave no accumulated context behind.
The day-rate comparison deserves explanation because it looks like diligence. A consultant at £1,200 a day appears expensive next to a vCIO retainer of £1,800 a month. But the retainer buys perhaps two days of senior time plus continuity, while the consultant day buys a day. Comparing them requires converting both to an annual cost for the outcome you actually want, and organisations that compare unit prices rather than annual outcomes systematically over-buy consultancy.
The third card’s first row is worth stating plainly: if the contract names a firm rather than a person, you do not know who you are getting, and in a role whose value is accumulated judgement that is the whole product. Ask for the individual by name, ask what happens if they leave, and treat a refusal to name them as the answer to a different question.
Strategic IT advice in UK businesses — the numbers
The figures below reflect what we observe across UK organisations of 25 to 500 staff buying strategic technology advice in some form. They describe the market as buyers encounter it rather than as it is marketed.
Setting the first and last figures next to each other frames the whole market. A vCIO retainer at roughly £21,600 a year against a loaded full-time IT director at around £125,000 is not primarily a saving — it is a different quantity of leadership. Two days a month is enough to hold a strategy, govern suppliers and keep a board informed. It is not enough to run a transformation programme, manage a team, or be available for every operational decision. Organisations that outgrow the fractional model usually do so because the volume of decisions has risen, not because the advice stopped being good.
The third figure is the one buyers most need to know, and it is discussed less than it should be. A substantial majority of what is sold under the virtual CIO label in the UK SME market is a quarterly review meeting included within a managed service contract. Those meetings can be genuinely useful. They are not an independent strategic function, because the person running them works for the organisation whose products and services form most of the agenda, and they are typically a fraction of the time a retained vCIO commits. Buyers comparing a £1,800 monthly retainer against something described as included should understand they are comparing different things.
The day rate figure carries a caveat worth stating: median hides an enormous range. General IT consulting sits around the figure shown; specialist security architecture, regulatory or transaction work routinely runs from £1,400 to well over £2,000 a day, and for genuinely scarce expertise that is often correct pricing rather than a premium. Detailed pricing for the fractional model sits in our guide to virtual CIO cost in the UK.
The two models side by side
The comparison below highlights the ongoing model, and it is worth being explicit about why: most UK SMEs already know how to buy project consulting and already do it, while comparatively few have any continuing governance function at all. The highlight marks the more commonly unmet need, not a judgement that one is better. For a bounded decision, the consultant column is the correct answer and retaining a vCIO to make it would be poor value.
IT consultant
Project-scoped expertise with an end date
Virtual CIO
Ongoing strategic governance on retainer
The row on accountability repays close reading, because it is where marketing language does the most damage. Neither engagement carries contractual liability for your business outcomes; a professional services contract with a competent firm will limit liability to fees paid, and no advisor of either kind underwrites your commercial results. What differs is not legal exposure but presence. The vCIO is still in the room a year later, which changes the advice given today in ways that no contract clause reproduces. Anyone claiming an advisory engagement makes them accountable for your outcomes in a stronger sense than that is overstating what they are selling.
The pricing rows are deliberately shown in different units because that is how the market quotes them, and converting between the two is the single most useful thing a buyer can do before comparing proposals. Two consultant days a month at £950 is £22,800 a year for two days of attention with no continuity. A £1,800 monthly retainer is £21,600 for roughly the same time with continuity included. Those are close on price and very different on what they produce, and neither is universally correct.
What a virtual CIO actually spends time on
The chart below shows how retained vCIO time is typically distributed across a year in UK SME engagements. It is worth reviewing before buying, because several of these activities are ones organisations assume they are getting from an IT support contract and generally are not.
Supplier governance at nearly a fifth is the line that surprises people and frequently pays for the engagement on its own. Somebody reading contracts, tracking renewal dates, benchmarking pricing, holding suppliers to what they committed to and being willing to have an uncomfortable conversation on the client’s behalf is a function most SMEs simply do not have. It is also a function that cannot credibly be performed by one of the suppliers. The mechanics of doing it well sit in our guide to IT governance, vendor management and procurement.
Note how little of the distribution is technical work. A vCIO who is spending significant time configuring systems has been mis-deployed — that is an engineering need, and buying senior strategic time to meet it is expensive. If your candidate’s proposed plan is heavy on implementation, either the scope is wrong or what you actually need is delivery capacity rather than governance.
Board reporting at fourteen per cent is the component that justifies the role to directors, who carry duties that increasingly touch technology risk whether or not they understand it. The NCSC publishes a board toolkit precisely because this translation problem is widespread, and a vCIO whose reporting cannot be understood by a non-technical director is not doing the part of the job that only they can do.
The number buyers should check first
Before comparing proposals, it is worth knowing how much of what is marketed as virtual CIO in the UK SME market is an independent strategic function and how much is a supplier relationship meeting with a senior-sounding label.
Sixty-one per cent is not an accusation of bad faith. A quarterly business review run by a good managed service provider is a legitimate and valuable thing: it surfaces incident trends, flags equipment approaching end of support, and keeps a client informed. The problem is only that it is sold under a label implying something structurally different, and buyers price it against retained independent advice as though the two were substitutes.
The practical test is not what the meeting is called but what it can conclude. A genuine strategic function can conclude that you should reduce spend with your incumbent provider, change provider, bring something in-house, or do nothing at all this year. If the person chairing your strategy review cannot comfortably reach any of those conclusions, what you have is account management, and it should be valued as account management — which is to say, as something worth having and not worth paying a separate strategic fee for.
There is a related figure worth having in mind: the proportion of roadmaps that are, on inspection, mostly a schedule of purchases. A roadmap that contains no organisational change, no process work, no decommissioning and no decisions to defer spending is a procurement plan. Real roadmaps contain a meaningful share of items that cost nobody anything except attention, and several that involve switching things off.
The conflict when your advisor is also your supplier
This section is uncomfortable to write as a firm that provides both managed IT services and virtual CIO engagements, and leaving it out would make the guide less useful. The structural issue is real and it applies to us as much as to anyone.
When the organisation advising you on what to buy is also the organisation selling it, the advice carries an incentive it would not otherwise carry. This does not mean the advice is wrong — most providers most of the time recommend sensible things, and a supplier who knows your estate intimately often gives better advice than an outsider who does not. It means the incentive exists, that you cannot verify from the outside whether it influenced a given recommendation, and that the burden of managing it sits with you as the buyer rather than with the provider.
Three ways to handle it
The first is separation: retain an independent vCIO with no supply relationship, and let them govern whoever supplies you. This is the cleanest arrangement and it is the most expensive, because you are paying for a function that a bundled arrangement appears to give you free. It works best where IT spend is large enough that a few per cent of governance-driven savings covers the fee.
The second is disclosure and structure: keep the combined arrangement but require that margins on resold products are visible, that any recommendation above an agreed value is accompanied by at least one alternative the advisor does not supply, and that the roadmap is reviewed annually by someone with no commercial interest — a board member, a finance director, occasionally a one-off independent consultant engaged precisely for that review. This is the pragmatic option for most SMEs and it works provided the requirements are contractual rather than assumed.
The third is to accept it with clear eyes for a defined period. A young organisation without the scale to fund independent governance is often better served by a capable supplier giving advice with a known bias than by no strategic function at all. The failure is not accepting the arrangement; it is forgetting that you accepted it, and treating the resulting roadmap as though it had been produced independently.
Whichever route you take, the question to ask any prospective advisor is simple and revealing: what do you sell, what do you earn margin on, and what would you do if the right answer for us were to spend less with you? The answer matters less than the ease with which it is given.
The first twelve months of a virtual CIO engagement
A retained engagement that is working has a recognisable shape. The sequence below is what to expect, and equally what to hold a provider to — if month nine looks like month one, the relationship is not compounding and something is wrong.
The single most informative checkpoint is month four. A supplier and contract review conducted properly will surface something uncomfortable — an auto-renewed circuit, a licence count that drifted, a service being paid for that nobody uses, a provider not meeting a commitment. If the review surfaces nothing at all in a year-one engagement, the more likely explanation is that it was not conducted rigorously than that the estate was already immaculate.
By contrast, a consultancy engagement has no equivalent of months five through twelve. That is not a criticism; it is the model working as designed. It is simply the thing to be clear about when deciding which you are buying, because the value of a retained relationship is concentrated in exactly the period a project engagement does not have.
Governance readiness — where most UK SMEs sit
Combining the assessment areas gives an indication of how much strategic technology governance an organisation currently has, independent of how good its IT support is. The gauge reflects a first review of a UK business of 25 to 500 staff with no in-house IT leadership.
A score in the low thirties is usually not a reflection of poor IT. Operational delivery frequently scores well: the helpdesk works, patches get applied, backups run. What is absent is everything above the operational layer — a costed multi-year plan, a risk register expressed in business terms, supplier governance with somebody holding the contracts, and reporting that lets directors ask informed questions.
The distinctive feature of this particular gap is that it is invisible while things go well. An organisation with excellent support and no governance looks identical to one with both, right up until a renewal is missed, a supplier underdelivers unchallenged, an acquirer asks a question nobody can answer, or a risk that was known to one engineer materialises into an incident the board had never heard of. That is why the gap tends to be closed reactively, and why closing it reactively is more expensive.
The usual caveat applies and applies strongly here. A 30-person business with straightforward IT, a capable office manager coordinating a good support provider and a director who takes an interest may score in the thirties and be entirely well served. Governance should be proportionate to the consequences of getting technology decisions wrong, which scales with spend, regulatory exposure and how much of the business stops when systems do. Buying a retained CIO function below that threshold is over-governance, and it is a real way to waste money.
When each is the right fit
The choice is usually clearer than the marketing makes it look, and it resolves on two questions: does the need have an end, and is the gap judgement or capacity.
Buy a consultant when
There is a specific decision with a deadline and a defined scope — selecting an ERP, designing a cloud migration, reviewing security architecture against a framework, conducting technology due diligence for an acquisition. Also when you need depth you will not need again: a specialist who has done the thing forty times is worth a high day rate for a fortnight and would be poor value on a permanent retainer. And when you need an independent second opinion on advice you have already received, which is a genuinely underused and inexpensive form of assurance.
Buy a vCIO when
There is no in-house technology leadership and IT spend or risk is material enough that somebody senior should be holding it continuously. Also when the same category of question keeps recurring, when suppliers are going ungoverned, when the board is receiving technology information it cannot act on, or when the business is changing fast enough that a plan written once will be wrong within months. The threshold test in our experience is whether a poor technology decision would materially hurt the business — if yes, somebody should own the decisions between projects.
Buy both
This is common and sensible. A retained vCIO holds the direction and governs the estate; consultants are engaged for specific depth as the roadmap requires, with the vCIO scoping the brief, selecting the firm and assuring the output. That last part is the significant benefit: a consultancy engagement scoped by somebody who knows your estate and reviewed by somebody who will live with the result is substantially more likely to produce something usable than one scoped by a buyer who cannot evaluate the deliverable.
Buy neither
If the gap is delivery capacity rather than judgement, neither model addresses it. An organisation that knows exactly what it needs to do and lacks the hands to do it should buy project delivery or additional engineering capacity, and buying advice instead produces a better-articulated version of a plan it already had. Equally, if IT is genuinely simple and the consequences of getting it wrong are contained, proportionate governance may be an interested director and an annual review. The decision framework for when the threshold is crossed sits in our guide to when a UK SME needs a virtual CIO.
What each model costs in the UK
The table below gives indicative 2026 UK figures excluding VAT. The final column is the one to compare on, because the market quotes these in incompatible units and unit-price comparison systematically misleads.
| Model | Typical commitment | Indicative rate | Annualised cost |
|---|---|---|---|
| Bundled review within a support contract | Quarterly meeting, 2–3 hours | Presented as included | Embedded in the support fee |
| Virtual CIO, light retainer | 1 day per month | £900–1,400 per month | £10,800–16,800 |
| Virtual CIO, standard retainer | 2 days per month | £1,600–2,600 per month | £19,200–31,200 |
| Fractional CIO, heavier engagement | 3–4 days per month | £2,800–6,000 per month | £33,600–72,000 |
| Project-based IT consulting | Scoped engagement | £700–1,600 per day | Varies entirely with scope |
The first row is included deliberately, because it is what most buyers are implicitly comparing against and it rarely appears in a comparison table. Treating it as a zero-cost strategic function is the error; it is a component of a support fee, it is worth something, and it is not equivalent to any of the rows below it.
The step from the standard retainer to the heavier fractional engagement is where organisations should pause. At three to four days a month and £33,600 to £72,000 annualised, the comparison is no longer against consultancy — it is against a part-time or full-time employed IT leader, at an indicative loaded cost of around £125,000 for a full-time IT director. Fractional still frequently wins on access to seniority a business could not otherwise recruit, and on flexibility, but the argument has to be made rather than assumed.
On consultancy, resist judging a proposal by day rate. A specialist at £1,500 a day who completes the work in four days is cheaper and better than a generalist at £800 who takes twelve and produces something you cannot act on. Ask what the deliverable is, who specifically will produce it, and what acceptance looks like — then compare total cost for a defined outcome.
Benchmarks — governance artefacts against what we find
The figures below show how often each governance artefact exists in a current and usable form across UK organisations of 25 to 500 staff without an in-house CIO. These are the outputs a retained engagement should produce, which makes them a reasonable way to assess what you have and what you would be buying.
Presence of technology governance artefacts in UK SMEs
Seventy-two per cent against nine per cent describes the gap precisely. Nearly three-quarters have a budget, because finance requires one. Fewer than one in ten ever step back and ask whether the whole arrangement — the support model, the supplier set, the in-house split — still suits the business. That annual question is close to being the defining activity of the role, and its near-total absence is why organisations run the same IT model for a decade through several changes of size and strategy.
Use this list as a procurement instrument. Ask a prospective vCIO which of these artefacts they will produce, on what cadence, and to show you an anonymised example of each. A provider who can show a real risk register written in business language and a roadmap containing deferrals and decommissioning is demonstrating the job. One who offers a slide template is demonstrating something else.
What the board actually needs, and which model supplies it
Part of the reason this decision gets muddled is that the people making it are often not technologists, and the thing they are trying to buy is, at root, the ability to discharge a duty they hold whether or not they understand the subject.
Directors of UK companies carry duties that increasingly touch technology whether or not technology appears in the job description — the duty to promote the success of the company requires having regard to risk, and a material technology risk is not exempt because it is technical. Data protection obligations impose an accountability principle: an organisation must not merely be compliant but be able to demonstrate it. Where a business is regulated, operational resilience expectations add a further layer. None of these require a CIO, and all of them require somebody to be able to answer questions in front of people who cannot evaluate a technical answer.
The NCSC publishes a board toolkit precisely because this translation problem is so common, and it is a reasonable free benchmark for what a UK board should be able to ask and expect answers to: what are our most important assets, what is our biggest technology risk, how would we know if we were attacked, what would we do, and are we getting value from what we spend. Any organisation can test its current arrangement against those questions this afternoon, and the result usually clarifies which engagement model is needed without any supplier conversation at all.
Which model answers which question
A consultant can answer any one of those questions extremely well, once. If the board needs to know whether its security posture is adequate against a framework, a scoped review answers it authoritatively and the report can be tabled. What a consultant cannot do is answer them continuously, or notice when the answer changes, or be the person the chair looks at when the question is asked again next quarter.
A vCIO is the standing answer. The reporting is the product: a pack that a non-technical director can act on, a risk register in business language that sits alongside the other corporate risks rather than in a separate technical document nobody reads, and a named person present at the meeting who can be questioned. Where a board is receiving technology information it cannot act on, that is nearly always a governance gap rather than an information gap, and producing more detailed technical reporting makes it worse rather than better.
The test worth applying
Ask whoever currently holds technology in your business to answer the five questions above in front of the board, in business language, in ten minutes, without preparation time. The exercise is not a trap and it is not about the individual — most finance directors holding IT as a fifth portfolio will struggle, and that is the finding rather than a criticism. If the answers are not available, the gap is ongoing and a project will not close it.
Making a consultancy engagement survive its own ending
If the honest answer for your business is a consultant rather than a retainer, there is still a structural problem worth planning for: the recommendation outlives the engagement, and by the time it matters nobody involved in making it is present. A few provisions make the difference between a report that changes something and one that is referenced twice and filed.
Name the internal owner before the engagement starts, not at the end. Somebody in the business has to hold the recommendations afterwards, and identifying them at the outset means they attend the working sessions, understand the reasoning rather than just the conclusion, and can defend it later. Engagements where the owner is nominated on delivery day reliably underperform, because the reasoning was never transferred — only the output.
Ask for the decision record, not only the recommendation. What options were considered, what was rejected and why, and what assumptions the recommendation depends on. This is the part that ages usefully: in two years the recommendation may no longer fit, and knowing which assumption broke is what tells you whether to adjust or start again. A recommendation without its reasoning is unmaintainable in exactly the way undocumented infrastructure is.
Agree what happens if circumstances change within a defined window. Not a warranty on outcomes, which no reputable firm will give, but a modest provision — a half-day revisit at three or six months, priced in at the start — that creates a natural checkpoint. It is inexpensive, it substantially raises the chance the recommendation is actually implemented, and a firm confident in its work will not object.
Finally, be clear that a well-run consultancy engagement can legitimately conclude that you need ongoing governance, and that this is not an upsell when it comes from a firm that does not provide it. If two or three separate consultants have each independently observed that the underlying issue is the absence of continuous ownership, that is data rather than a sales pattern, and it is worth acting on before the fourth engagement.
Common mistakes when buying strategic IT help
The errors below are the ones that most reliably produce a disappointing engagement. Most are procurement errors rather than judgements about suppliers, which means they are entirely within the buyer’s control.
- Solving an ongoing governance gap with a series of projects. Three consultancy engagements over four years often cost more than the retainer that would have prevented the need for any of them, and leave no accumulated context behind.
- Comparing a day rate with a monthly retainer. They are different units buying different things. Convert both to an annual cost for the outcome you want before comparing anything.
- Treating a bundled quarterly review as an independent strategic function. It may be genuinely useful and it cannot conclude that you should spend less with the firm running it. Value it accordingly.
- Accepting a roadmap that is a purchase schedule. A real roadmap contains process work, decommissioning, deferrals and items that cost nothing but attention. One that is entirely acquisitions is a procurement plan wearing a strategy label.
- Contracting with a firm rather than a named person. In a role whose value is accumulated judgement, who specifically does the work is the product. Ask for the name and what happens if they leave.
- Buying advice when the gap is delivery capacity. If you already know what to do and lack the hands to do it, an advisor produces a better-written version of the plan you had. Buy delivery.
- Never asking about margins and supply relationships. The answer matters less than the ease with which it is given. An advisor who is uncomfortable with the question has told you something useful.
- Defining no artefacts, so nothing is inspectable. Without agreed outputs on an agreed cadence, a retainer becomes a monthly meeting whose value nobody can assess at renewal.
Be cautious about the engagement that quietly converts from strategy into implementation. It starts as a retained advisory relationship, the advisor identifies work, the advisor is well placed to do the work, and within a year most of the fee is delivery and nobody is governing it — including, now, nobody governing the advisor. This is a gradual drift rather than a decision, which is why it goes unnoticed. The defence is to keep the retained governance line separate in the contract and in the budget, so that if delivery work grows it is visibly a second engagement that the first one is supposed to be assuring.
The 12 questions to ask before signing
Questions one to five apply to a retained virtual CIO engagement. Questions six to nine apply to a project consultancy engagement. Questions ten to twelve apply to both and are the ones most often skipped.
- Who specifically will do this work, and what happens if they leave? A name, their background, how much of their time you get, and what continuity provision exists. A firm name is not an answer.
- Exactly how many days a month, and how are they evidenced? Notional time is not time. Ask how days are recorded and what happens to unused ones.
- Which artefacts will you produce, on what cadence? Roadmap, risk register, budget, supplier register, board pack, decision log. Ask to see an anonymised example of each before signing.
- What do you sell, and what would you do if the right answer were for us to spend less with you? Ask even where you expect the arrangement to be bundled. The comfort of the answer is the signal.
- How will we review whether this engagement was worth it in twelve months? Agree the review at the start. A provider who treats the annual review as a renewal pitch will not give you an honest one.
- What precisely is the deliverable, and what does acceptance look like? Written down, with a definition of done. Ambiguity here is where consultancy disputes originate.
- Who will actually produce it — the person in this meeting? Sold by a principal and delivered by a junior is common and is not necessarily wrong, but you should know before you sign.
- What vendor relationships and accreditations do you hold in this area? Not disqualifying, but you need to know before weighing a recommendation. Certifications are competence, not independence.
- Who owns the outputs, the data and the documentation afterwards? IP and documentation ownership stated in the contract, in a portable format, not as a goodwill assumption at the end.
- What is the notice period, and what does handover include? For a retainer especially, the exit terms tell you how confident the provider is that you will want to stay.
- What will you not do? A straight answer here separates advisors who understand their scope from those who will agree to anything and disappoint you later.
- Can you point to a comparable UK client and what changed for them? Not a logo wall — a specific situation, a specific intervention and a specific outcome, including one that did not go to plan.
If only three of these are ever asked, make them questions one, three and four. Who does the work determines the quality of everything else. Which artefacts are produced is the only way to make a retainer inspectable rather than a monthly conversation. And the question about supply and margin is the one that establishes whether you are receiving advice or a well-informed sales process — which you may reasonably choose to accept, provided you have chosen it rather than assumed otherwise.
What this looks like in practice
A 140-person UK manufacturer of specialist components had no internal IT leadership. Support came from a competent regional managed service provider on a contract that had rolled for six years, and which included a quarterly review described in the contract as a virtual CIO service. The finance director, who held IT alongside four other portfolios, regarded the arrangement as working.
The trigger was an acquisition approach. The acquirer’s technology due diligence asked four questions: what is the estate, what is out of vendor support, what are the top technology risks, and what is committed spend over the next three years. The business could answer the first partially, from an inventory the provider maintained, and could not answer the other three at all. The quarterly review packs, six years of them, contained ticket volumes, uptime figures and equipment approaching end of warranty. They contained no roadmap, no risk register and no forward spend view, because that had never been what the meeting was for.
The business engaged a consultant for the due diligence response, which was the correct model for that need — a bounded deliverable with a deadline. It cost about £11,000 over three weeks and produced what the acquirer needed. The approach ultimately did not proceed for commercial reasons unrelated to technology.
What followed was the more interesting decision. Having seen what it could not answer, the board retained an independent vCIO at two days a month on roughly a £2,000 monthly retainer, explicitly separate from the support provider. The first-year supplier and contract review found three things: a disaster recovery service being paid for at £940 a month that had never been configured after an aborted project in 2023, a licence count twenty-two seats above headcount, and a support contract whose pricing had not been benchmarked in six years and which, on renegotiation with the incumbent, reduced by about eleven per cent.
Those three items came to roughly £26,000 annualised against a £24,000 retainer. The board found that persuasive, though the vCIO was careful in the year-one review to note that first-year supplier findings are one-off by nature and that year two would have to justify itself differently — on roadmap execution and risk reduction rather than on recovered spend.
We had been told for years that we had a virtual CIO. We did have a quarterly meeting, and it was a good meeting, and the people running it were straight with us. It simply was never going to tell us to stop paying them for something, because that is not what the meeting was. Once we understood that, we stopped being annoyed about it and just bought the thing we were actually missing.
Two points generalise. The first is that both models were correct in turn: a consultant for the bounded due diligence response, a retainer for the continuing gap it exposed. Using one for the other would have failed in both directions. The second is the year-two caveat the vCIO raised unprompted, which is the behaviour to look for — an advisor who tells you the easy savings are finite before you discover it yourself is an advisor planning to still be there.
At a glance — virtual CIO against IT consultant
| Question | Short answer |
|---|---|
| What is the actual difference? | The engagement model, not the skill set. One is continuity of judgement on retainer; the other is bounded expertise producing a deliverable. |
| The simplest test | Does the need have an end? If yes, a consultant. If no, a vCIO. |
| What a consultant is accountable for | The quality of the deliverable against the brief |
| What a vCIO is accountable for | The trajectory of the estate over time — and being present when the advice lands |
| Does either carry liability for outcomes? | No. Professional services liability is typically limited to fees. The difference is presence, not legal exposure. |
| Typical UK consultant pricing | £700–1,600 per day, specialists higher |
| Typical UK vCIO pricing | £900–1,400 monthly for one day; £1,600–2,600 for two; £2,800–6,000 for three to four |
| Full-time comparison point | Around £125,000 loaded for a UK IT director — the relevant comparison once you reach three to four days a month |
| The pricing trap | Comparing a day rate with a monthly retainer. Convert both to annualised cost for a defined outcome. |
| What a vCIO spends time on | Roadmap and budget, supplier governance, risk and compliance, board reporting, project assurance — very little hands-on technical work |
| The label to be careful with | Around 61 per cent of UK engagements sold as vCIO are quarterly account reviews bundled into a support contract |
| How to test independence | Can the review conclude you should spend less with the firm running it? If not, it is account management. |
| Managing the advisor-supplier conflict | Separate the functions, or require margin disclosure plus an alternative option and an independent annual review, or accept it deliberately for a defined period |
| When to buy both | Commonly. The vCIO holds direction and scopes, selects and assures the consultants the roadmap requires. |
| When to buy neither | When the gap is delivery capacity, or when IT is simple enough that proportionate governance is an interested director and an annual review |
How Cloudswitched approaches this
Cloudswitched provides virtual CIO engagements for UK organisations, and also provides managed IT support — which means the conflict described earlier in this guide is one we sit inside rather than above. We think the honest position is to name it and structure around it: retained governance quoted and contracted separately from supply so the fee is visible rather than embedded, a named individual you meet before signing, defined artefacts on a defined cadence, and an annual review of the engagement that is a review rather than a renewal conversation. Where a client wants governance genuinely independent of their supplier, the right answer is sometimes an advisor with no supply relationship, and we would rather say so than win the work by not mentioning it. For bounded questions we also deliver scoped consultancy, which is a different product and priced as one.
Work out which one you actually need
A short conversation usually settles whether your gap has an end date. We will tell you if it is a project, a retainer, delivery capacity, or nothing at all this year.
Talk to a Virtual CIO SpecialistFrequently Asked Questions
What is the difference between a virtual CIO and an IT consultant?
The engagement model rather than the skill set — the same person can credibly do both. An IT consultant sells a defined deliverable against a scoped brief with an end date: a migration design, a vendor selection, a security review, a due diligence report. A virtual CIO sells continuity of senior judgement on a rolling retainer, typically one to four days a month, holding the roadmap, the risk register, the budget and supplier governance. The three practical consequences are accumulated context, presence when the consequences of advice arrive, and what the engagement optimises for. A consultant is rewarded for a defensible deliverable; a vCIO is rewarded for an estate that keeps working.
How do I know which one my business needs?
Ask whether the need has an end. “Should we move our ERP to the cloud” has an end and wants a consultant. “We do not know what we should be spending or whether our risks are covered” has no end and wants a vCIO. If you cannot tell, the usual reality is an ongoing governance gap that has surfaced as one specific question — and answering the question alone leaves the gap, so the same issue recurs in a different form next year. Also check whether the gap is judgement or capacity: if you already know what to do and lack the hands, buy delivery rather than advice.
What does a virtual CIO cost in the UK?
Indicatively in 2026, excluding VAT: roughly £900 to £1,400 a month for one day, £1,600 to £2,600 for two days, and £2,800 to £6,000 a month for a heavier three-to-four-day fractional engagement. Annualised that is about £10,800 to £72,000 depending on commitment. The comparison point worth holding is a full-time UK IT director at an indicative loaded cost around £125,000. Once you are buying three or four days a month, the honest comparison is against employment rather than against consultancy, and the case for fractional then rests on access to seniority you could not otherwise recruit and on flexibility.
Why can I not just compare day rates?
Because the two models are quoted in incompatible units and buy different things. A consultant at £1,200 a day looks expensive beside a £1,800 monthly retainer, but the retainer buys roughly two days of senior time plus continuity while the consultant day buys a day. Two consultant days a month at £950 is £22,800 a year with no continuity; a £1,800 retainer is £21,600 with continuity included. Convert both to an annualised cost for the outcome you actually want. Organisations that compare unit prices rather than annual outcomes systematically over-buy consultancy.
Is the free vCIO included with my IT support contract a real vCIO?
Usually it is a quarterly account review, which is a legitimate and useful thing sold under a label that implies something structurally different. Around 61 per cent of UK engagements presented as virtual CIO fall into this category. The test is not what the meeting is called but what it can conclude: a genuine strategic function can recommend that you reduce spend with your incumbent provider, change provider, bring something in-house, or do nothing this year. If the person chairing your review cannot comfortably reach those conclusions, value it as account management — worth having, and not a substitute for retained independent governance.
Is it a problem if my advisor also supplies my IT?
It is a structural conflict rather than a character flaw, and it is worth naming rather than ignoring. The advice may well be good — a supplier who knows your estate intimately often advises better than an outsider who does not — but the incentive exists and you cannot verify from outside whether it influenced a given recommendation. Three workable responses: separate the functions entirely and pay for independent governance; keep the combined arrangement but contractually require margin visibility, an alternative option the advisor does not supply on significant recommendations, and an annual review by someone without a commercial interest; or accept it deliberately for a defined period. The failure is forgetting you accepted it.
What should a virtual CIO actually produce?
Inspectable artefacts on a stated cadence: a costed one-to-three-year roadmap mapped to business objectives, a risk register written in business rather than technical language, an IT budget and forecast, a supplier register with contract end dates and benchmarked pricing, an asset lifecycle and refresh plan, regular reporting a non-technical director can act on, and a decision log. Ask to see anonymised examples of each before signing. A provider who can show a real roadmap containing deferrals and decommissioning is demonstrating the job; one offering a slide template is demonstrating something else.
How much of a vCIO engagement is technical work?
Very little, and that is correct. Typical distribution across a year is roughly a quarter on roadmap, budget and planning, a fifth on supplier governance and contract review, a little under a fifth on risk and compliance, around an eighth on board and leadership reporting, and the remainder on project assurance, ad hoc decision support and incident post-mortems. A vCIO spending significant time configuring systems has been mis-deployed — that is an engineering need being met with expensive senior strategic time, and it usually means either the scope is wrong or what you needed was delivery capacity.
Can I use both a virtual CIO and consultants?
Yes, and it is a common and sensible arrangement. The retained vCIO holds direction and governs the estate, while consultants are engaged for specific depth as the roadmap requires. The significant benefit is that the vCIO scopes the brief, helps select the firm and assures the output — a consultancy engagement scoped by someone who knows your estate and reviewed by someone who will live with the result is far more likely to produce something usable than one scoped by a buyer who cannot evaluate the deliverable.
Is a virtual CIO accountable for business outcomes?
Not contractually, and be sceptical of anyone implying otherwise. A professional services agreement with a competent firm will limit liability to fees paid, and no advisor of either kind underwrites your commercial results. What differs between the models is presence rather than legal exposure: the vCIO is still in the room when the consequences of their advice arrive, which changes the advice given today in ways no contract clause reproduces. That is a real and valuable difference, and it is not the same as accountability in the liability sense.
What are the warning signs in a proposal?
A firm name with no named individual. Days per month described as notional or unlimited. No defined artefacts, so nothing is inspectable at renewal. A roadmap sample that is entirely a schedule of purchases with no process work, decommissioning or deferrals. Vendor certifications presented as evidence of independence. Discomfort when asked what the firm sells and earns margin on. And an annual review framed as a renewal conversation rather than an honest assessment of what the retainer produced.
When should we hire a full-time IT leader instead?
When the volume of decisions rather than their difficulty exceeds what a few days a month can hold. Practical indicators: an internal IT team that needs day-to-day management, a transformation programme running for more than a couple of quarters, technology becoming central to the product rather than supporting it, regulatory obligations requiring a continuously available accountable person, or a fractional engagement that has crept to four-plus days a month. At that point the annualised fractional cost is approaching employment cost anyway, and the fractional case has to rest on seniority you could not otherwise recruit rather than on price.
Related reading
More guidance on technology leadership, governance and buying IT services in the UK:
An ongoing relationship, or a bounded piece of work
Cloudswitched provides retained virtual CIO engagements and scoped IT consultancy as separate, separately priced products — with a named advisor, defined artefacts and an annual review that is allowed to conclude you need less than you are buying.
Talk to a Virtual CIO Specialist
CloudSwitched
London-based managed IT services provider offering support, cloud solutions and cybersecurity for SMEs.
