A vCIO scorecard is a short list of measures that tells an MSP owner whether the vCIO team is doing its job. It should be small enough to review in ten minutes, honest enough to show problems early, and free of measures that push advisors toward selling. Most MSPs either track nothing or track revenue, and both approaches miss the point of the role.
This article is written for MSP owners and service leaders. If you want the client-facing view of the same subject, see Measuring What Matters: The vCIO KPIs Business Owners Actually Understand.
Why You Need a vCIO Scorecard
A vCIO’s work is hard to see from the outside. Meetings happen, documents get written, and recommendations get made, but the results arrive slowly. Without a scorecard, you find out a vCIO is struggling when a client leaves or a review is missed for two quarters running. A scorecard moves that discovery earlier, so you can coach instead of react.
It also gives the vCIOs themselves a clear picture of what good looks like. People do better work when they know how it is judged.
Start With the Purpose of the Role
Before choosing a single measure, write one sentence describing what a vCIO is for in your company. For example: a vCIO keeps each client’s technology plan current, honest, and connected to what the client is trying to achieve. Every measure on the scorecard should trace back to that sentence. If a number does not, drop it.
The Measures Worth Tracking
Roadmap Currency
Track how many clients have a written technology roadmap that was reviewed within the last twelve months. A stale roadmap is the most common failure in vCIO practices and the easiest to measure. Report it as a simple count: clients with a current roadmap out of total clients. Guidance on what belongs in one is in Building a Technology Roadmap.
Review Cadence
Count the strategic reviews scheduled and completed each quarter. Missed reviews are an early warning. One skipped meeting is normal. A pattern of skipped meetings with the same client means the relationship is drifting. The standards for a good review are covered in What a Good MSP QBR Actually Looks Like.
Client Sentiment
Use whatever feedback system you already have, such as an NPS survey or a satisfaction score, and look at it by vCIO and by client. Watch trends more than single scores. A client who drops from strong to lukewarm deserves a conversation even if the number is still acceptable.
Agreement Health
Review the financial health of each client agreement on a regular schedule. A vCIO who ignores profitability will slowly build unprofitable relationships, and one who ignores client experience will build fragile ones. Pair the financial view with the sentiment view so neither dominates. Look at the causes behind a weak agreement, such as scope creep, underpriced services, or a recurring problem nobody has fixed.
Budget Accuracy
Ask each vCIO to forecast the client’s technology spend for the coming year, then compare the forecast with actual spend. Large misses point to gaps in planning, such as forgotten renewals or unplanned hardware failures. Over time, this measure builds trust because clients can rely on the number they were given.
Recommendations Delivered
Track how many roadmap items were completed on the planned timeline. This is different from sales. A recommendation that saves the client money or removes a risk counts, even if it generates no revenue for you. Measuring delivery instead of sales keeps advisors honest, and it keeps the client’s interest ahead of yours. That principle is central to the fiduciary standard for vCIOs.
Escalation and Ticket Health
Look at open and aging tickets for each vCIO’s clients. Languishing tickets often signal a problem the vCIO should be raising with the service team. This is not a measure of the vCIO’s own tickets. It is a check on whether they are watching the client’s overall experience.
Documentation Quality
Spot-check the documentation for each client, including network diagrams, contact lists, and key process records. A vCIO who cannot find current documentation cannot plan reliably. Spot checks work better than full audits, because they are fast and still reveal the pattern.
Measures to Avoid
- Revenue generated by recommendations. It rewards selling and undermines trust. If clients sense a quota behind the advice, the role loses its value.
- Hours logged with the client alone. Time matters, but a high number can mean an advisor who talks a lot and produces little.
- Number of meetings held without a quality check. A meeting with no preparation and no follow-up counts the same as a good one.
- Anything the vCIO cannot influence. Holding someone accountable for outcomes they do not control breeds resentment.
Build the vCIO Scorecard
Pick five to seven measures from the list above. Assign each a target and a color rule, such as green, yellow, or red, so the state is visible at a glance. Put the measures in a single view for each vCIO and one rolled-up view for the whole team.
Keep the scorecard on one page. If it needs a legend and a manual, it will not be used. Update it monthly, and review it in person with each vCIO at least quarterly.
Use It as a Coaching Tool
A scorecard should start conversations. When a number is red, ask what is getting in the way before asking who is responsible. Sometimes the cause is workload, such as too many clients per vCIO. Sometimes it is a process gap, such as no template for the roadmap. Sometimes it is a skill gap that needs training, which is where developing vCIOs within your MSP becomes practical.
If you see the same red measure across the whole team, the problem is probably not the people. Look at capacity, tools, and expectations first.
What a One-Page Layout Looks Like
Put the vCIO’s name and client count at the top. Below that, list each measure in its own row with three columns: the current value, the target, and the direction of travel compared with last quarter. Add one line at the bottom for the vCIO to write a short note about the biggest risk they see across their clients. That single sentence is often the most useful thing on the page, because it shows whether the advisor is thinking ahead or only reporting numbers.
Share the scorecard with the vCIO before you discuss it with anyone else. Nobody should learn about a red measure in a group meeting. A private review builds the trust that makes honest reporting possible.
Pitfalls
The most common mistake is measuring too much. Ten or fifteen measures dilute attention and invite gaming. The second is treating the scorecard as a grade. When advisors feel judged instead of supported, they hide problems, and hidden problems cost more than visible ones. The third is setting targets without checking whether the team has the time to hit them. If each vCIO carries a client load that leaves no room for preparation, the scorecard will only document the shortfall.
Related Reading
See the vCIO services hub for the full library, and MSP KPIs: The Metrics That Actually Tell You Whether Your Business Is Healthy for the company-wide view.
Frequently Asked Questions
What should be on a vCIO scorecard?
Roadmap currency, review cadence, client sentiment, agreement health, budget accuracy, recommendations delivered, and ticket health cover most of what matters. Choose five to seven and keep the scorecard to one page.
Should vCIOs have sales targets?
Sales targets pull advisors toward selling and away from honest guidance. Measure whether recommendations were delivered and whether clients are better off, and keep revenue as a company outcome instead of an individual quota.
How often should I review the scorecard?
Update it monthly and review it with each vCIO at least quarterly. Look at the team view every month so patterns show up early.
How many clients should one vCIO support?
There is no universal number. It depends on client size, the depth of each engagement, and the vCIO’s other duties. Use the scorecard to see whether the current load allows the work to get done, and adjust when measures start to slip across several clients.
About Brent Lacy: Brent Lacy is a technology advisor and the voice behind Rewired MSP. He helps MSPs operate with greater maturity and helps business owners make IT choices that make them more secure and more efficient. He is the author of Out of Cycle: A Field Guide to Strategic IT Continuity, vCIO Rewired: Virtually Conquering IT Obstacles, and Near Miss: Preventable IT Failures Threatening Your Business Security.
