A vCIO quarterly business review is a decision meeting, not a status report. The client should leave with clear answers on what is at risk, what the next twelve months will cost, and what they are being asked to approve. If the meeting could have been an email, the review failed.
Most MSPs run these reviews badly. The vCIO opens a slide deck, walks through ticket counts, reads out patch compliance, and asks whether there are any questions. The client nods, checks the clock, and cancels the next one. This post lays out how to run a quarterly review that clients protect on their calendars.
What a vCIO Quarterly Business Review Is For
A review exists to connect technology to the business. It answers three questions the client cannot answer alone: Are we protected? Are we spending well? Are we ready for what is coming? Everything on the agenda should serve one of those three. Anything else belongs in a report the client can read on their own time.
It also protects the relationship. Clients who meet with a strategic contact every quarter are far less likely to shop the agreement at renewal, because they can see the work. Clients who only hear from you during outages see a cost, not a partner. If you are building the role itself, our post on developing vCIOs within your MSP covers the skills behind these conversations.
Who Should Be in the Room
The person who can say yes to spending must attend. For a small business that is usually the owner or the general manager. For a larger company it may be the operations lead or the finance lead alongside the executive sponsor. If the only person who attends cannot approve anything, you are having a status meeting, and you will need a second conversation to get decisions.
On your side, bring the vCIO and, when the topic calls for it, a technical lead. Do not bring five people. A crowded room turns a strategy conversation into a technical debate.
How to Prepare: The Two-Week Rule
Start preparing two weeks ahead. That gives you time to gather the data, spot problems, and talk to your own team before you stand in front of the client. A useful prep list looks like this:
- Review every ticket from the last quarter for patterns, not counts. Five tickets about the same printer are one problem, not five.
- Check the state of backups, patching, endpoint protection, and identity controls, and note anything that slipped.
- Look at license usage and renewals coming in the next six months.
- Pull the agreement financials so you know whether the account is healthy for both sides.
- Ask the client contact one week ahead what is changing in their business.
That last item is the most valuable. Hiring plans, new locations, a pending acquisition, a new compliance requirement from a big customer: these shape the technology roadmap more than any tool decision.
The Agenda That Works
Keep the meeting to sixty minutes and send the agenda in advance. A structure that has held up well runs in five parts.
- Business first (10 minutes). Ask what changed and what is coming. Let the client talk.
- Risk and security posture (15 minutes). Show three to five items in plain language, ranked by business impact. Skip the tool names.
- Performance (10 minutes). Summarize service quality with a few numbers and the story behind them, including what you fixed at the root.
- Roadmap and budget (15 minutes). Show what is planned, what it costs, and when. Tie each item to a business reason.
- Decisions and next steps (10 minutes). State what you need approved and who owns each action.
Notice that the client speaks first and the meeting ends with commitments. Those two choices do more for the quality of the review than any slide design.
Translate Risk Into Business Language
Executives fund what they understand. Instead of saying that multi-factor authentication is missing on service accounts, say that one stolen password could give an attacker access to payroll. Instead of reporting that a server is past end of support, say that if it fails, invoicing stops until a replacement is built, and the estimate for that is several days. Name the consequence, then the fix, then the cost.
Give the client a small number of items. If you show twenty risks, they will remember none. Choose the top few, explain why they matter, and put the rest in the written follow-up.
Put Numbers on the Roadmap
A roadmap without dollars is a wish list. For each item, show the expected cost, the year or quarter it lands, and what happens if it is postponed. Group items into what must happen this year, what should happen next year, and what is worth watching. Clients can make decisions from that view, and it removes the surprise from budget season.
Be honest about uncertainty. If a project cost could land in a range, say so and explain what will narrow it. A range you defend is more credible than a precise number you later revise.
Common Mistakes That Kill a Review
- Reading the report aloud instead of discussing it.
- Leading with the good news and burying the one item that needs a decision.
- Selling products during the meeting, which turns advice into a pitch and lowers trust.
- Skipping the review when things are quiet. Quiet quarters are when roadmap conversations go best.
- Letting the meeting slide to a phone call with a technician.
Follow Up Within 48 Hours
Send a short summary within two days: what was discussed, what was decided, who owns each action, and the dates. Put approved work into your normal quoting or project process right away. Then start the next review by checking that list first. Clients notice when you follow through, and it is the simplest way to earn a longer relationship.
How Often Should You Meet?
Quarterly is the standard for a fully managed client. Smaller accounts may do two full reviews and two shorter check-ins per year, but the meeting should never disappear entirely. If a client refuses to meet at all, document that and treat it as a risk to the account, because you cannot guide a business you never hear from.
Adapting the Review for Different Clients
Not every client needs the same meeting. A ten-person office with a single location wants a shorter conversation focused on cost and continuity. A regulated business with multiple sites needs more time on compliance evidence and vendor risk. Keep the five-part structure but shift the minutes. Ask each client in the first meeting what they want to get out of the review, and write it down. Over time you will build a simple profile for each account that tells you where to spend the hour.
Also adjust for the audience. An owner who thinks in cash flow needs the roadmap expressed as an annual budget. An operations leader may care more about downtime and how long recovery would take. Use their language, not yours.
How to Know the Reviews Are Working
Watch for signs that the meeting is producing value. Clients bring you questions between reviews. Budget requests arrive earlier and with fewer objections. Renewals stop being negotiations. If none of that happens after several quarters, revisit the agenda and ask the client directly what they would change.
Related Reading
New to the role? Start with what a vCIO is and why the role matters, then see how the vCIO services hub ties the pieces together.
Frequently Asked Questions
How long should a vCIO quarterly business review last?
Sixty minutes is enough for most clients. Shorter meetings rarely leave room for the roadmap and budget discussion, and longer ones lose the executive’s attention.
What should be in a vCIO QBR?
Cover business changes, top risks in plain language, service performance, the roadmap with costs, and decisions with owners. Everything else can go in a written summary.
Who should attend from the client side?
The person who approves technology spending, plus anyone who owns a major business process the roadmap affects. If nobody with authority attends, decisions will stall.
What if the client keeps cancelling the review?
Ask what would make the meeting worth their time, shorten it, and tie it to something they care about such as budget planning. If cancellations continue, document them and flag the account for leadership.
Should the vCIO sell during a QBR?
The vCIO should recommend what the client needs and explain why. Recommendations tied to a business reason feel like advice. Product pitches feel like sales and cost you trust.
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.
