On this page
Start with the deliverables, not the title
Many MSPs announce a "vCIO service" before deciding what a client actually gets. Clients judge the service by what they can hold in their hands afterwards, so write the deliverables down first:
| Deliverable | What the client receives | How often |
|---|---|---|
| Assessment | Findings against a named standard, with evidence | Once at the start, then repeated on a schedule |
| Technology roadmap | Prioritised initiatives with dates, costs and owners | Updated at each review |
| IT budget | Recurring costs, licences, replacements and projects by month | Yearly, tracked during the year |
| Risk view | The open gaps, what each means for the business, and the plan | Updated as work progresses |
| Business review | A meeting with written decisions and next steps | Usually quarterly |
If you are not sure what a vCIO covers, What is a vCIO? explains the role. Keep the first version narrow. A roadmap and a quarterly review done well are worth more to a client than a long list of services delivered inconsistently.
Decide how to package and price it
There are three common models, and none is right for every MSP:
- Included in managed services. Every managed client gets reviews and a roadmap. This raises the value of the core agreement but needs capacity planning, because every client is entitled to it.
- Tiered. Higher service tiers include more frequent reviews, budget tracking or compliance work.
- Separate engagement. The vCIO service is priced on its own, often monthly, sometimes for clients who are not on full managed services.
Whichever you choose, estimate the hours per client per quarter (preparation, the meeting, follow-up) before setting a price. Preparation is usually where the time goes, which is why it pays to standardise the data you bring to each review.
Pick the first clients carefully
Pilot with three to five clients rather than launching to everyone. Good first candidates:
- Clients who already ask about budgets, renewals, insurance questionnaires or growth plans.
- Clients with a decision-maker who will attend a review and act on it.
- A mix of sizes, so you learn how much effort different clients need.
Ask pilot clients what they found useful and what they skipped. Their answers tell you which deliverables to keep.
Build a repeatable process
A vCIO service scales when every client follows the same rhythm:
- Assess each client against one standard. Many MSPs start from a public framework such as the CIS Controls and add their own technology standards on top. See How do MSPs use CIS Benchmarks with clients?
- Recommend. Turn each meaningful gap into a roadmap item with a business reason, a cost and a target quarter.
- Plan the budget from those roadmap items plus recurring costs. See How do MSPs help clients plan an IT budget?
- Review on a fixed cadence with an agenda built from current data. See How do you run a QBR meeting with a client?
- Follow up in writing: what was decided, who owns each next step, and when it will be checked.
Who should be the vCIO?
The vCIO needs enough technical depth to judge a recommendation and enough business sense to explain it to an owner or finance director without jargon. In many MSPs this starts with the owner or a senior engineer. As the service grows, it often moves to a dedicated advisor who uses the help desk's data rather than working tickets.
Whoever takes the role needs protected time. Reviews squeezed between escalations tend to become status updates instead of planning sessions.
Common mistakes when launching
- Selling the meeting instead of the plan. If the client only sees value during the meeting, the service is easy to cancel.
- Recommendations without costs or dates. Clients cannot approve something they cannot budget for.
- Plans the client cannot see. A roadmap that lives in the MSP's spreadsheet is forgotten between reviews.
- No record of decisions. When a client declines a recommendation, record it, so the conversation can be revisited later with context.
How MSPortal helps run a vCIO service
MSPortal puts the vCIO deliverables in the branded client portal clients already use for tickets, so the plan stays visible between reviews. With the vCIO tools:
- Assess with compliance checks against your own standards or imported CIS Benchmark and NIS2 playbooks, scored with weighted A to F grades you configure.
- Recommend by opening a Planner item, risk or ticket from a failed check, keeping the finding linked to the work that fixes it.
- Plan roadmap items with hours and costs, and add them to a budget that keeps a link to each item.
- Review with reports that pull ticket, device, compliance, Microsoft 365 and budget data. AI can draft the QBR narrative with sources cited for your vCIO to review. Drafts stay hidden until you publish them, and scheduled reports can wait for your team's approval before they go out.
- Follow up with meeting wrap-up that turns a transcript into notes, action items and a summary email for the client.
For your own team, Client Health scores, a standards matrix and vCIO workload and pricing calculators help decide which clients need attention and how to price the service. These stay internal. Recurring meeting booking lets clients pick their review times from a link, as described in the recurring meeting booking guide. See the full workflow on MSPortal for vCIOs, check pricing, or book a demo.
Related questions
Should vCIO services be included in managed services or sold separately?
Both work. Including vCIO in managed services raises the value of the core agreement but commits capacity for every client. Selling it separately or in higher tiers lets you price the preparation time, which is where most of the effort goes.
What does a vCIO need to prepare for a quarterly review?
Current service data such as ticket trends, device age and security findings, an updated roadmap and budget, open risks, and decisions from the last review. See How do you build a QBR for an MSP client?
How many clients can one vCIO handle?
It depends on review frequency, client size and how much preparation is automated or standardised. Measure the hours per client during a pilot before committing to a ratio, rather than relying on a rule of thumb.
What is the first deliverable in a new vCIO engagement?
Usually an assessment against a named standard. It gives the roadmap and budget an evidence base and shows the client where they stand before any recommendation is made.