The 60-minute running order
Timings are a working default. The proportions matter more than the exact minutes: roughly a third on what happened, a third on what is next, and a third on decisions.
- 0 to 5, where we left off: last quarter's recommendations with their status, approved, declined, done or still open. Starting here rather than ending here is the single highest-value change most MSPs can make to this meeting.
- 5 to 12, the executive summary: three to five sentences in the client's language on how the quarter went and what needs deciding. No metrics on this slide.
- 12 to 22, service performance: ticket volume with its trend, response and resolution times against SLA, and the one or two categories that drove volume. Two slides at most.
- 22 to 30, the environment scorecard: a red, amber and green grade per domain, such as endpoints, backup, security posture, licensing and network. The client should be able to read this in ten seconds.
- 30 to 40, risks and what changed: open risks with an owner and a date, plus anything material that changed in the environment this quarter.
- 40 to 50, roadmap and budget: the next 12 months of planned work, costed and phased, with the hardware refresh line called out separately because it is the one finance always asks about.
- 50 to 58, decisions: each recommendation stated as a specific ask with a number and a date. Approved, declined, or deferred with a review date. Nothing leaves this block undecided.
- 58 to 60, close: confirm the next review date in the calendar before anyone leaves the call.
What to cut when you lose time
You will lose fifteen minutes at some point. Cut in this order, and never improvise the order in the moment.
- Cut first: the detail behind service performance. Show the headline numbers and the trend, and offer the breakdown as a follow-up document.
- Cut second: what changed in the environment. It is useful context and it is not a decision.
- Cut third: the risk detail, keeping only risks that need a decision this quarter.
- Never cut: last quarter's status, the decisions block, and booking the next date. A review that skips the decisions block is a status update, and status updates do not renew retainers.
The slide behind each block
One idea per slide, and the total should sit between eight and twelve slides. A twenty-slide deck is a sign the meeting has become a report reading.
- Commitment status: a table of last quarter's recommendations with a status column. Four columns, no chart.
- Executive summary: text only, three to five sentences, in the client's vocabulary rather than yours.
- Service performance: one chart of ticket volume over four quarters, one table of response and resolution against target.
- Scorecard: one grid, one colour per domain, no numbers.
- Risk register extract: open risks only, with owner and date.
- Roadmap: a timeline across the next 12 months with cost against each item.
- Budget: opex and capex phased by quarter, with the refresh line visible.
- Decisions: one slide listing each ask with its cost and the date it needs answering by.
The three mistakes that ruin the meeting
These are the failure modes we see most often, and each one has a cheap fix.
- Leading with tickets: opening on ticket volume tells the client the meeting is about your workload. Open on what they decided last quarter and what happened to it.
- Presenting metrics without a decision attached: every number in the deck should either support a recommendation or be cut. A metric with no consequence is a slide the client will not remember.
- Ending without dated commitments: if the meeting ends on general agreement, the next review starts by reconstructing what was agreed from memory, and the client learns that these meetings do not lead anywhere.
Cadence, and being honest about it
Quarterly for every client is a target almost nobody hits, and pretending otherwise is why practices collapse. Tier it. Strategic accounts get four reviews a year with a full roadmap. Mid-tier accounts get two. The long tail gets one annual review and a monthly service report that does not require a meeting. A client who gets two well-prepared reviews a year is better served than one who was promised four and received one rushed deck.
Preparing the agenda without spending a day on it
Every block above except the executive summary and the decisions is computable from data you already hold. Ticket volume, response and resolution times, SLA attainment, asset age, warranty expiry and the refresh budget are arithmetic on your PSA. The commitment status is a lookup against what you recorded last quarter, if you recorded it. That leaves the executive summary and the recommendations, which are the two things the client is actually paying you to think about. If your preparation time is going anywhere else, that is the thing to fix before the agenda is.
Keep recommendations reviewed and evidence explicit
QBR Studio computes service metrics and drafts client-facing summaries from connected data. Your MSP reviews the evidence, chooses every recommendation, and approves the final report before a client sees it.
What MSP teams usually ask
How long should an MSP QBR be?
Sixty minutes is the working default and it is enough if the preparation is done. Ninety minutes is a sign that the meeting is being used to present data the client could have read beforehand. Thirty minutes works for smaller accounts if you keep the commitment status and the decisions block and drop the detail.
What should be on an MSP QBR agenda?
Eight blocks: last quarter's commitment status, an executive summary, service performance against SLA, an environment scorecard, risks and changes, the roadmap and budget, the decisions being asked for, and booking the next date. The first and second to last are the ones that make it a business review rather than a service report.
Should the QBR start with metrics?
No. Starting with metrics frames the meeting around your workload. Start with what the client decided last quarter and what happened to it, which frames the meeting around their decisions and immediately demonstrates follow-through.
How is an MSP QBR different from a customer-success QBR?
Different audience and different currency. A customer-success QBR is usually about product adoption and usage with a programme owner. An MSP review is about service delivery, risk and capital spending with someone who controls a budget. Most QBR agenda templates online are written for the first meeting and will lead you astray in the second.
What do I do when the client cancels the review?
Send the artifact anyway, with the decisions listed and a date by which you need answers. A published review that gets read is worth more than a meeting that keeps getting moved, and it keeps the commitment record intact for the next quarter.