K7 Insights

vCIO QBRs: Get Out of the Review and Into the Board Meeting

By Kyle Christensen · July 7, 2026

Part of Grow Your MSP

A working MSP QBR (quarterly business review) is the client’s meeting. You hold a seat in their planning, you bring an agenda, and the thing on the table is their business: where it’s going, what technology has to be true for it to get there, what that costs, and when they’ll spend it. Getting there takes three moves: split the service review from the strategy meeting, set the cadence per client, and get inside their budget cycle. Most QBRs do the opposite of all three, and clients can tell. This piece is the operating manual for the real motion, one piece of how you grow your MSP.

What should an MSP QBR actually cover?

Less than yours probably does, and different things. A real quarterly review covers the client’s plan. Service stats get a few minutes, for the audience that cares about them, and the rest of the time belongs to the roadmap, the budget, and the decisions ahead.

It helps to know where the QBR came from, because the origin explains the smell. The story the industry tells on itself goes like this: once remote tools got good enough that almost everything got fixed without a visit, clients stopped seeing their IT provider. The QBR got invented to put a face back in the room, a stopgap for lost on-site presence. And for a while it did that job.

Then it curdled into the meeting most MSPs run today, which I’d call the self-congratulation QBR. Ninety minutes of here’s how great we did, you bought most of my stuff, would you like to buy more of my stuff. Run that meeting enough quarters in a row and you teach the client that the whole relationship is a pitch with a dashboard on it. You are, very politely, training your customer to cancel.

Here’s my actual position, and it’s the spine of this whole article. If you’re truly a fractional c-suite, there is no QBR. There’s a seat at the client’s own table. Nobody at your client runs a quarterly review meeting about their CFO. The CFO sits in the company’s quarterly leadership meeting with a budget and an opinion. That’s the standard for the seat: you show up to the client’s planning meeting, on their calendar, with your own agenda items. If you’re still deciding whether to build the seat at all, start with what a vCIO is and come back. The rest of this piece is how you get from the first kind of meeting to the second.

Why run the service review and the strategy meeting separately?

Because they have different jobs and different audiences, and mixing them ruins both.

The service review is about the machine: tickets, response times, recurring problems, the patching backlog. Your account manager can run it, and the right audience is the office manager or internal IT contact who lives in that detail. The strategy meeting is about the business: the roadmap, the budget, the risk trend, the decisions only an owner can make. When I coach MSP owners through this, the question I keep putting in front of them is some version of: what’s your vision for this account? The quarterly ticket numbers are just the maintenance.

Split them and something useful happens to the room. The owner stops getting dragged through ticket counts they don’t care about, so they show up. And the strategy conversation stops competing with a complaint about the printer, so it happens at all. If your only recurring meeting is a maintenance meeting, you’ve told the client that maintenance is what you do.

How often should a vCIO meet with clients?

As often as their business changes, which means you set the cadence per client. Quarterly is a default, and defaults are for clients you haven’t thought about yet.

I learned this at an MSP I ran as its operator (the one I took from $2M to $20M in under four years), and I learned it by getting it wrong first: we started with one review rhythm for everybody, because that’s what the template said. We had a FINRA-regulated client where quarterly would have been negligent. Regulation moved monthly, audits stacked, and ninety days of drift was real exposure, so that client got a strategy review every month. And we had a CPA firm where quarterly was comical. Their technology needs barely moved between tax seasons, and if I’d shown up every ninety days I could already see the partner’s face: why are you here again? I just went to lunch with you two months ago.

So build tiers. Monthly for regulated or fast-moving clients. Quarterly for clients in active growth with real project flow. Semi-annual or annual for small, stable accounts whose honest strategy needs fit in one good afternoon a year. Not every client has earned a quarterly rhythm, and pretending otherwise burns your most expensive billable person’s hours on meetings nobody asked for.

One cadence rule has no tiers, though: the first technology-alignment review gets scheduled the day the contract is signed. Ink dries, meeting goes on the calendar. It tells the client strategy is part of the deal from day one, and the roadmap starts while the relationship is still warm. Wait until the first renewal scare to book it and you’ve taught them the meeting is a retention play.

How do you get into the client’s budget cycle?

You ask for a seat in it, in the fall, before the client builds next year’s budget. This is the move the rest of the motion exists to set up.

Most businesses set next year’s numbers in the last few months of this year. So around October, the vCIO walks into the strategy meeting with a three-year view of the client’s technology spend and puts it on the table: between the workstation refresh, the firewall replacement, and the server that’s aging out, we probably have $300 grand of IT to spend over the next three years. Let’s decide together when each piece lands.

Watch what that one meeting does. The client stops experiencing IT spend as a stream of surprise quotes and starts experiencing it as their own plan. Every proposal that shows up next year was approved months ago, in their budget, by them. Which is why the strange-sounding result is real: clients with a budget never say no to the quote. There’s nothing to say no to. They said yes in October.

The seat pays you in the other direction too. Inside their planning cycle, you hear a no coming a mile away. The budget’s getting trimmed, a merger’s in the wind, the owner’s thinking about selling: you know a quarter before it hits your MRR, while there’s still time to act on it. The vendor who shows up four times a year with a quote finds out when the cancellation letter does.

And this runs as a system, past any one hero. One MSP I coach turned it into straight operations: every strategy client has a budget spreadsheet broken out by category (recurring services, project recommendations, end-of-life devices) and laid out by quarter, and the last count I saw had the team at roughly 222 meetings against a 300-meeting quarterly target. That’s a document standard, a scoreboard, and a team running the motion, and it holds up whether or not anyone on staff is having a heroic month.

Building that motion into an existing client base is the part owners usually don’t want to do alone. If that’s you, book a call and we’ll rough out the three-year numbers for your two biggest accounts on the spot.

How does the roadmap sell without a pitch?

By advising. In this motion the sale happens before anything gets pitched, because the investment becomes obvious inside the client’s own planning.

Here’s the shape of it. You sit in the client’s planning meeting. You ask the question that surfaces the real problem: what happens to order flow if that ERP finally dies during your busy season? You tie the problem to a number and a timeline. Then you mostly stop talking, because the client is now looking at a risk with a price tag on their own whiteboard. I’ve watched that sequence turn a genuine problem into a serious project with nobody ever delivering a pitch. High close rates in this seat are normal. That’s what the advisory motion buys you. The funnel that lands new logos is a different machine, with a quota on it, and that machine is covered in how to sell managed services.

For the advisory motion to stay honest, the vCIO has to be protected from your own sales engine. The structure I teach is a gatekeeper model. Your account manager still hunts for expansion, but they pitch it internally, to your vCIO, who judges it against the client’s roadmap and budget. If it belongs, it goes on the roadmap, and the client hears it from their advisor: something’s come up that wasn’t on the roadmap, we need to talk. If it doesn’t belong, the client never hears it at all. The client only ever hears roadmap. That’s exactly why they believe the roadmap.

The quarterly meeting is also where the growth ask gets a home and a built-in gate. The sequence comes out of my book. End the review with one honest question: would you give us an 8 or better out of 10? An 8 or better earns the ask, whether that’s an expansion conversation or an introduction. A low score kills the ask and starts the save, because you just caught a problem while the account can still be rescued. A high score with a no tells you something’s unsaid, so you ask about that instead.

I ran that sequence for years, and it earned its keep in a way I didn’t expect: a CPA firm I coached liked it enough to lift it whole and run it on their own customers. When an accounting firm steals your meeting agenda, the agenda works.

Common QBR mistakes MSPs make

The pattern behind all of them: the meeting serves the MSP. The specific versions are worth naming.

• One template for every client. Quarterly-for-all bores your stable accounts and shortchanges your regulated ones. Fix: cadence tiers, set per client.
• The owner in the ticket review. Wrong audience kills attendance, and then the strategy dies with it. Fix: send the account manager to the service review and save the owner for the strategy table.
• Quotes from nowhere. A proposal the client never saw coming gets shopped or stalled. Fix: every quote lands on a budget line the client approved in the fall.
• Sales pitching around the roadmap. One off-roadmap upsell that reaches the client directly costs you the credibility the whole seat runs on. Fix: expansion goes through the vCIO’s gate, every time.

Take the seat

The whole motion compresses to one sentence: get into the client’s own planning cycle and make their budget the place where technology decisions get made. Everything else here (the split meetings, the cadence tiers, the gatekeeper) exists to earn that seat and protect it.

Do the first pass yourself this week. Pull your ten biggest strategy accounts, write each one’s honest cadence next to its name, and find out which of them builds next year’s budget this fall. That list is your October calendar. Then comes the harder question, because this motion only runs if the right person holds the seat: who belongs in the vCIO seat, and what to pay them is the next piece. Both feed the same growth system.