The QBR in an MSP Relationship
A QBR is the one meeting where an MSP talks to a client about their business rather than their tickets. Why it matters, who should attend, and how to run it are covered in depth in what is a QBR, and why does it matter. This entry covers the terms and building blocks you will hear around it.
What Goes Into One
A useful QBR draws on data you already collect and turns it into decisions. Pull the numbers from your PSA and RMM ahead of time so the preparation takes minutes rather than an afternoon, and send the client a short pre-read so the meeting starts with questions instead of slides. A typical agenda:
- Service summary in business terms, using SLA attainment and client satisfaction instead of raw ticket counts.
- Risk review covering items such as patch compliance, MFA coverage and backup success.
- The client's plans: hiring, new offices, new applications, compliance deadlines.
- Roadmap and budget, meaning what should happen next quarter and next year, and what it costs.
- Agreed actions with owners and dates, reviewed at the start of the next QBR.
Who Runs It and How Often
At smaller MSPs the owner or an account manager runs QBRs. As the business grows the role usually moves to a vCIO, whose job is to connect technology recommendations to the client's goals. Despite the name, many MSPs hold them twice a year for smaller clients and quarterly only for the largest, because a meeting with nothing new to discuss trains the client to skip it.
| Term | What It Usually Means |
|---|---|
| QBR | Quarterly business review with the client's decision maker |
| TBR | Technology business review, often the same meeting with a technical focus |
| SBR | Strategic business review, typically held once or twice a year |
| Roadmap | The agreed list of upcoming projects and their budget |
Measuring Whether QBRs Work
A QBR earns its time through what follows it. Track how many roadmap items are approved, how often a QBR produces project work, and whether clients who attend renew at better rates than those who do not. Over time you should see the effect in net revenue retention and in fewer surprise cancellations. If the meeting only produces a slide deck, shorten it and spend more of it listening.
Keep a record of every recommendation made in a QBR and the client's answer, including the ones they declined. That history makes the next conversation easier, shows the client you remember what they told you, and protects you if a declined recommendation later turns into an incident. It also gives whoever takes over the account a clear picture of where the relationship stands.
Common Questions
Should I charge clients for a QBR?
Most MSPs include it in the managed services fee because it protects renewals and generates project work. Detailed strategy work beyond the meeting is often sold separately as vCIO time.
How long should a QBR take?
Long enough to cover decisions, which is often under an hour for a small client. If most of the time goes to reporting, send the report ahead and use the meeting to discuss it.
What if the client keeps canceling QBRs?
Treat it as a renewal risk. Offer a shorter format, bring one specific decision they need to make, or ask directly whether the meeting is useful to them.
Can a QBR be done remotely?
Yes, and many are. In person meetings still help with larger clients and first reviews, where building the relationship is part of the point.