What a QBR Is
A QBR is a planned meeting between your MSP and a client's decision-makers that happens away from the ticket queue. It looks back briefly at how the service performed, then spends most of its time on the client's business: what is changing, what worries them, and what technology work should follow. The output is a short list of agreed actions and, over time, a roadmap and a budget.
The name says quarterly, but the label matters less than the rhythm. Some clients need the meeting every three months, others twice a year. What makes it a business review rather than a status call is who attends and what gets decided.
Why It Matters to Your MSP
It is the only routine occasion where you are in front of a decision-maker discussing next year rather than last week's outage. Budget gets shaped in these conversations before it is allocated elsewhere, and risk gets heard while there is still time to act on it rather than during an incident.
It is also where you prove value. In Kaseya's 2026 State of the MSP Report, based on more than 1,000 MSPs, 19% reported difficulty quickly demonstrating value to prospective customers, and a client who renews without ever seeing that value is a prospect you are still selling to. On the buyer side, Barracuda's MSP Customer Insight Report 2025 found that 45% of surveyed organizations would switch MSPs if they could not see evidence of skills, expertise and the ability to support them with 24/7 security. A client who has never been shown what you do for them is a client who compares you on price.
The commercial effect shows up in retention and expansion. Projects agreed in a review become revenue you did not have to find through new logos, which lifts net revenue retention, and problems raised early are the ones that do not turn into logo churn at renewal.
Who Should Be in the Room
The most common reason a QBR fails is the wrong attendees. If the only person on the client's side is the office manager who logs tickets, you will get a service review, not a business one.
| Attendee | Side | Why They Are There |
|---|---|---|
| Owner, CEO or managing partner | Client | Makes budget and priority decisions; the reason the meeting exists |
| Finance or operations lead | Client | Connects technology spend to plans and cash flow |
| Day-to-day IT contact | Client | Knows where the friction is and will carry out actions |
| vCIO or account manager | MSP | Runs the meeting, owns the roadmap and the follow-up |
| Service lead or senior engineer (as needed) | MSP | Answers technical questions and owns technical actions |
Who runs the meeting on your side is a staffing decision. Many MSPs start with the owner doing every review and move the work to an account manager or a vCIO as the client base grows. When should I hire a vCIO covers the timing, and the account manager and vCIO resource pages collect material for whoever takes it on.
An Agenda That Works
Keep the service part short and the business part long. Send the agenda and a one-page summary beforehand so the meeting is spent discussing, not reading.
Preparation is where most of the value is created. About a week before the meeting, pull the service numbers from your PSA and RMM, review open recommendations from the last review, and ask the service team what they have noticed about the client: recurring complaints, users who struggle, systems that are getting fragile. Decide on the two or three things you most want the client to act on, and build the summary around them.
- Their business: what has changed since the last review, and what is planned for the next few quarters (hiring, new sites, new software, regulatory changes).
- Service summary: a handful of numbers that matter to an owner, with a sentence on what they mean.
- Risk and security: gaps you found, what they could cost, and what closing them involves.
- Lifecycle: hardware and licenses reaching end of support or renewal, with rough costs.
- Recommendations: a short, prioritized list with a budget range for each.
- Agreed actions: who does what by when, confirmed in writing after the meeting.
What to Measure and Show
Choose metrics that answer an owner's question: are we safe, is the service good, and are we spending sensibly. Reciting closed ticket counts tells an owner nothing they can act on, and quietly frames your value as the volume of problems they had.
- Satisfaction: client satisfaction (CSAT) from ticket surveys, and client NPS if you run it.
- Service levels: SLA attainment against what the agreement promises.
- Security posture: MFA coverage and patch compliance rate, shown as trends rather than single readings.
- Resilience: whether backups succeeded and whether a test restore worked, not only that backups exist.
- Recurring issues: the few problems that keep coming back, with a proposal to remove them.
Before the meeting, check your own side too. Run the client through the client margin calculator so you know whether the relationship is profitable before you propose new work or discuss renewal terms.
Over several reviews, the agreed actions should add up to a technology roadmap: a dated list of projects and replacements for the next year or two, with a budget range for each. Share it with the client's finance lead before they set their annual budget. A roadmap the client has seen and agreed to turns your recommendations into planned spend rather than surprise quotes, and it gives every later review a clear starting point.
Which Clients Get One and How Often
Reviews cost preparation and meeting time, so match the cadence to the relationship rather than giving every client the same schedule.
| Client Profile | Suggested Cadence | Format |
|---|---|---|
| Large or strategic clients, regulated clients | Quarterly | In person or video, with owner and finance present |
| Mid-size clients on a full managed agreement | Quarterly or twice a year | Video, with a written summary |
| Small clients on a basic tier | Once or twice a year | Short call plus a written report |
| Clients approaching renewal | A review well before the renewal date | Includes renewal terms and pricing |
The pre-renewal review deserves its own preparation. If seat prices are rising, the renewal cost worksheet and the article on renegotiating a renewal when seat prices rise help you show the change before the invoice does.
Common Mistakes
It is the meeting that most often gets canceled, because it is never urgent. That is the problem: the work that is never urgent is the work that decides whether you are a supplier or an advisor. Put the next review in the calendar at the end of each one.
A useful test after each review: could the client's owner explain to a partner, in a sentence or two, what their MSP recommended and why? If not, the meeting covered too much or decided too little. Trim the next agenda, lead with the one decision you need, and send a written summary that makes the recommendation and its reason plain.
- Turning it into a ticket report. If you cannot fill the meeting without ticket counts, the meeting is telling you something about the relationship.
- Making it a sales pitch. Recommendations tied to problems the client raised land; product demos do not.
- No follow-up. Actions that are not written down and sent within a day or two are forgotten by both sides.
- Too many slides. A short summary the owner can forward to a partner is worth more than a long deck.
- Presenting only good news. Showing a gap and a plan to close it builds more trust than a page of green metrics.
Common Questions
Should I charge for QBRs?
Many MSPs include them in managed agreements because they drive retention and project work. If a client wants frequent, deep strategic sessions beyond the standard review, that is advisory work you can price separately.
What if the client keeps canceling?
Shorten the meeting, move it to a time that suits the owner, and send the written summary anyway. Repeated cancellations are a relationship signal worth raising directly with the decision-maker.
Can a QBR be done by email or as a report only?
A report is better than nothing for small clients, but it cannot replace the conversation about the client's plans. The business discussion is the part that creates value, and it rarely happens in writing.
How long should a QBR last?
Long enough to cover the client's plans and agree actions, which for most small and mid-size clients means a focused session rather than a half day. Prepared materials sent in advance keep it short.
What tools help prepare QBR reports?
Your PSA and RMM hold most of the data, and many have reporting modules or integrations built for reviews. The tool matters less than choosing a few meaningful metrics and explaining them.
Should technicians attend client QBRs?
Not usually. Bring a senior engineer when a technical decision is on the agenda, and brief the service team afterwards on anything that affects their work.