MSP QBR template: a quarterly business review clients will show up for

Most MSP QBRs are a ticket report with a hardware quote attached. Clients learn to skip them. Here's a version built around what the client's business is trying to do, with an agenda, a slide outline and a scorecard you can copy.

Why clients skip MSP QBRs

Here's the usual deck. Tickets opened and closed. Average response time. Patch compliance. Backup success rate. Then a list of machines that are out of warranty, and a quote.

Every number is accurate. And the owner of a 40-person accounting firm doesn't know what to do with any of them. Is 94% patch compliance good? Should they worry? They sit through it, approve nothing, and next quarter something comes up.

The data isn't the problem. The meeting is built around what the MSP measures, and the client came to hear about their business.

An MSP QBR agenda

MinutesBlockWho talks mostDone when
0–5The decisions we need todayYouThey know what they'll be asked to approve
5–15What's changing in your businessThe clientYou've heard about hiring, offices, new software and deadlines
15–25Scorecard, and what isn't working and whyBothYou agree on the cause of the top one or two problems
25–35Risk: security, backups, aging equipmentYouThey understand the top risk in business terms
35–45Next quarter, the 12-month budget, and decisionsBothEach decision is made or has an owner and a date

The second block does the most work. Ten minutes of the client talking about a new hire class in March or a second office in the fall tells you what next quarter's plan should be. It also changes how they hear the rest of the meeting.

The slide outline

#SlideWhat goes on it
1TodayThe agenda, and the two or three decisions you need
2Your businessWhat they told you is changing. Leave room to add to it live.
3ScorecardTheir goals for IT, with a result and an honest status for each
4What isn't working, and whyWhat we see, what we think is causing it, the evidence, our confidence
5RiskThe top three risks, each in terms of what it would cost the business
6Equipment and softwareWhat needs replacing in the next 12 months, and why each item matters
7BudgetThe next four quarters on one line, so nothing arrives as a surprise
8Action planActions, owners on both sides, dates
9DecisionsEach decision with options and your recommendation
—AppendixTicket report, patch and backup detail, asset list

An MSP scorecard

The goals and numbers below are fictional examples. Use the goals your client gave you.

What you told us mattersMeasureTargetResultStatus
Staff aren't stopped by IT problemsHours lost to outages and repeat issuesUnder 10 a quarter23Off track
New hires are productive on day oneNew starters fully set up before they arriveAll5 of 6Watch
We'd survive a ransomware attackLast successful restore testEvery quarterTested in FebruaryOn track

Then the diagnosis. "Hours lost" is off track. Why? Say the ticket data shows 14 of the 23 hours came from one cause: the Wi-Fi in the back office drops during client calls, and it's the same two access points every time. Now the hardware recommendation is a fix for something the owner already feels, with evidence, and the quote that follows doesn't read as an upsell.

Talk about risk in their terms

"Eleven machines are running an unsupported operating system" is a technical fact. The owner hears a sales pitch.

Try the same fact as a consequence. "Eleven machines can no longer get security updates. They're the ones the front desk uses for client records. If one is compromised, you'd be looking at notifying clients." That's a risk a business owner can weigh. Give them the options, your recommendation and the cost, and ask for a decision.

Before the meeting

  • Call the office manager first. Ask what's annoying people and what's coming up. Surprises belong in that call.
  • Write the decisions before the slides. If there's nothing to decide, send a one-page update and give them the hour back.
  • Send the scorecard a week ahead. See the QBR agenda page for a pre-read email you can adapt.

Start from the QBR kit

The kit's 15 slides run in the same order as the outline above: goals, scorecard, what isn't working and why, risks, next quarter, action plan, decisions. Replace the placeholders with your client's numbers. PowerPoint, opens in Google Slides, $39.

MSP QBR questions

What is an MSP QBR?

An MSP QBR is a quarterly business review between a managed service provider and a client. It reviews how IT is supporting the client's business goals, covers risks such as security and aging equipment, and agrees on priorities and budget for the next quarter.

What should an MSP QBR include?

The client's business goals, a scorecard of IT results against them, what isn't working and why, security and risk, the equipment and software that need attention, a budget view for the next 12 months, and the decisions you need.

How long should an MSP QBR be?

Forty-five to sixty minutes for larger clients. For small clients, 30 minutes twice a year is often enough, with a one-page update in the other quarters.

Who should attend an MSP QBR?

The client's owner or the executive who controls the IT budget, and their office or operations manager. On your side, the account manager or vCIO. Leave the ticket detail to a separate conversation with their day-to-day contact.

Should an MSP QBR include ticket statistics?

Only where they explain something the client cares about. Put the full report in the appendix and bring one or two findings to the meeting, such as a repeat issue that points to a cause.

How do you get clients to attend QBRs?

Send an agenda that names the decisions you need from them, keep it short, and make sure the last one was worth their time. Clients skip meetings that are reports. They attend meetings where something of theirs gets decided.