In this article 6 sections
The same QBR mistakes show up again and again, and the same small changes produce disproportionate commercial results. Here are the patterns that separate the QBRs clients pay more for from the ones they tune out.
Why do most MSP QBRs fail to move pricing?
The majority of QBRs open with a ticket volume summary. How many tickets were raised, how many were closed, how long they took. Clients do not know what to do with this information. Clients hired the MSP to keep their business running securely.
Leading with operational activity instead of business outcomes is the most common mistake we see, and the easiest to fix. The fix is a different first slide.
What is the second most common QBR mistake?
No evidence the client can verify themselves.
- Charts generated from the MSP’s own systems invite scepticism
- Third-party or independently verified evidence removes that friction
- Security posture data the client can cross-reference is worth more than any slide deck
When the only source of truth in the QBR is the MSP’s own ticketing tool, the conversation defaults to a debate about the numbers rather than a conversation about value.
At Labyrinth, a vendor’s policy setting left real patching at 47% while the MSP’s own reporting showed 95%. Assurix’s monitoring flagged it.
What change has the biggest commercial impact?
Separating the operational review from the strategic review.
Operations deals with what happened: tickets, incidents, patch state, backup status. Strategy deals with where the client is going and how the MSP’s service supports it. When these are mixed together, neither gets the attention it deserves and clients leave feeling talked at rather than served.
The QBRs that move pricing put the operational summary on a single page, then spend the rest of the meeting on forward-looking improvements. That alone changes the meeting from a status report into a strategic discussion.
What do the best MSP QBRs share?
The strongest QBRs we see have three things in common:
- They open with client-facing outcome evidence (security posture, business risk, regulatory readiness), not internal activity
- They spend more time on forward-looking improvements than backward-looking activity
- They end with a specific commitment from both sides
Where does evidence the client can verify actually come from?
Three sources work in practice:
- Independent verification (a live trustmark, an external audit, an insurer’s own report)
- Industry-benchmarked data (maturity scores against peer MSPs)
- The client’s own systems (security posture pulled from their tenant, not the MSP’s)
The MSPs winning the pricing conversation lean on the first one. That is what we built Assurix to provide: live evidence pulled from the MSP’s PSA, RMM and security stack, with live-measured controls checked every six hours, the rest on a set cycle, and sign-off by an Assurix assessor. The result sits on a Trust Portal the client can open. Clients see what they pay for, so a cheaper quote has to match the standard, not just the price.
“Someone else validating what we are, what we do, how we do it.” Nick Haley, Little Big Tech
That is the QBR shift: show clients what someone else has checked.
For the full 6-slide QBR template and commercial playbook, see Use QBRs to justify your pricing.
Frequently asked questions
How long should an MSP QBR be?
30 to 45 minutes. 60 minutes if multiple stakeholders are involved. Anything over 90 loses attention.
What is the right cadence for a QBR?
Quarterly for clients above £24k ARR or £2k MRR. Every 6 months below that.
Should you include security in every QBR?
Yes. Security is increasingly the evidence clients need to defend their MSP choice internally. Even when nothing has changed, show them the live posture.
