Every business above a certain size has someone fixing the technology. Far fewer have anyone steering it — deciding what to buy next year instead of this week, whether the aging server means cloud migration or replacement, what the insurance application’s demands mean for the budget, whether the software vendor’s renewal quote is normal or negotiable. In a large company, that’s the CIO’s job — a Chief Information Officer, at an executive salary no 40-person business can justify. A vCIO (virtual CIO) is the fractional version: senior technology leadership, delivered as part of a service relationship, sized to businesses that need the thinking a few days a quarter rather than a corner office. Here’s what the role actually does, and how to tell the real thing from a rebranded sales meeting.

What a vCIO actually does

The work is judgment, not wrenches — the questions that don’t fit in a support ticket:

  • Planning and roadmapping. Running the annual planning pass: what’s aging out, what the growth plans require, what’s forced by vendor calendars — turned into a sequenced, priced roadmap instead of a series of surprises.
  • Budget ownership. Building and defending the technology budget — run/refresh/projects/reserve — and translating between finance’s questions and technology’s answers, in both directions.
  • Risk decisions, framed for owners. Not “we need EDR” but “here’s what a down-day costs us, here’s our current exposure, here are three options at three price points, and here’s what I’d do.” The vCIO’s product is decisions you can make confidently without becoming technical.
  • Vendor and contract strategy. Evaluating the new platform, sanity-checking renewal pricing, running the licensing reviews — the negotiations where knowing what’s normal is worth real money.
  • The standing rhythm. Quarterly reviews that look forward, not just back; being the named senior person who knows your business well enough that the big questions — the second location, the acquisition, the compliance letter — have a first phone call.

Notice what’s absent: fixing things. The vCIO sits above the help desk and the engineering, which is exactly why the role gets skipped — it’s the layer nobody misses until they price its absence in accumulated drift: shelfware, emergency replacements, security gaps discovered by the insurer, and technology decisions made one urgent Tuesday at a time.

Who needs one

The signals: technology decisions keep landing on an owner who has to research each from scratch · the “IT budget” is whatever got spent · there’s a capable IT person or provider fixing things, but nobody owns the eighteen-month view · compliance, insurance, or big clients have started asking strategic questions (“what’s your security roadmap?”) that have no owner · or growth keeps generating technology surprises that were, in hindsight, entirely foreseeable. Businesses roughly 15–200 seats live in exactly this gap: real stakes, no rational case for a $200k+ executive hire — which is the gap fractional delivery exists to fill.

Real vCIO service vs. the rebranded sales meeting

Here’s the industry’s open secret: “vCIO” appears on many MSP brochures, describing anything from genuine strategic counsel to a quarterly upsell presentation. The tells are straightforward. Real vCIO work produces artifacts: a written roadmap with dates and prices, a budget document, a risk register with owners, meeting notes with decisions — things you could hand a new owner or a bank. Real vCIO advice sometimes costs the provider money: “you’re over-licensed,” “defer that project,” “the cheaper option fits you” — recommendations that trace to your data rather than their catalog. And real vCIOs ask about the business first: revenue model, growth plans, what keeps you up at night — because technology strategy that doesn’t start there is just shopping. Ask a prospective provider to show you (anonymized) a real client roadmap and budget they’ve built. The ones doing the work have them within arm’s reach; ours are the backbone of the account management practice, because the strategy layer is what makes the rest of a managed relationship compound instead of just continue.

The bottom line

A vCIO puts an owner in charge of your technology’s direction — planning, budgeting, risk, and vendors — at a fraction of the executive it replaces. The test for whether you need one is one question: who, by name, owns what our technology should look like in two years? If the answer is “nobody, exactly,” you’ve found the gap. If a provider claims to fill it, ask to see the paperwork that proves the thinking — strategy leaves a trail.