Most MSPs agree that quarterly business reviews are where client relationships are won or lost. Most also struggle to run them consistently. The reason is preparation: pulling three months of data out of the PSA, RMM and backup tools, every quarter, for every client, takes longer than the meeting.
The fix is to build the QBR from the monthly reports you already send. If each month uses the same measures, the quarter is mostly a matter of putting three of them side by side. This is how Monthly Service Report is designed, and it's covered in What to put in a monthly IT service report.
Before the meeting
- Pull the last three monthly reports and put their headline numbers in one table.
- List recurring issues: ticket categories, users and devices that came up more than once.
- Check last quarter's recommendations: what was done, what's in progress, what was declined.
- Review lifecycle: devices past their replacement age, warranties and licences expiring in the next two quarters.
- Draft the roadmap: three to five items for the next two or three quarters, each with a rough cost and reason.
- Send the agenda a few days ahead, with one question for the client: "What's changing in your business in the next six months?"
The agenda
| Part | Time | What to cover |
|---|---|---|
| 1. Their business | 10 min | Hires, moves, new services, new software, anything that worries them |
| 2. Service trends | 5 min | Tickets, SLA, uptime: three months side by side |
| 3. Recurring issues | 5 min | The patterns behind the tickets, and what fixes them |
| 4. Security | 10 min | MFA, patching, backups and restore tests, training, insurance requirements |
| 5. Lifecycle | 5 min | Devices and licences due for replacement or renewal |
| 6. Roadmap and budget | 15 min | Last quarter's recommendations, then the next two or three quarters |
| 7. Decisions | 5 min | What's approved, who does what, by when |
Start with their business, not your numbers. A client planning to open a second office next spring changes the roadmap more than any ticket trend.
A worked example
Here's the trend table for a fictional client, Larkspur Dental Group, for August to October:
| Measure | Aug | Sep | Oct | Trend |
|---|---|---|---|---|
| Tickets | 51 | 47 | 42 | Down |
| First response within SLA | 92.2% | 95.7% | 95.2% | Steady |
| Backup jobs succeeded | 97.6% | 99.2% | 98.4% | Steady; restore tested Oct 20 |
| Workstations fully patched | 35 of 39 | 36 of 39 | 37 of 39 | Improving |
| Accounts with MFA | 48 of 54 | 50 of 54 | 52 of 54 | Improving; 2 shared accounts left |
The story in one line: things are getting better, and the remaining gaps are the shared front-desk accounts and three old reception PCs. The roadmap follows from that, plus the client's news that they're opening a third clinic in the spring:
| Quarter | Item | Why |
|---|---|---|
| Q1 | Named accounts with MFA for front desk | Closes the last MFA gap; cuts password-reset tickets |
| Q1 | Replace three reception PCs | Over five years old; most hardware tickets |
| Q2 | Network, phones and devices for the new clinic | Opening in the spring |
| Q3 | Security awareness training for all staff | Required by their cyber insurer at renewal |
Each item has a rough cost in the budget section, so the practice manager can take one page to the partners.
After the meeting
- Send a one-page summary within two days: decisions, owners, dates and the agreed budget.
- Turn approved items into projects with start dates, so they don't drift into next quarter.
- Carry declined items forward with the reason. If the risk grows, raise them again.
- Book the next QBR before you leave.
Common mistakes
- A slide deck of charts. Clients remember decisions, not dashboards.
- No business conversation. Without the client's plans, the roadmap is guesswork.
- Selling in disguise. If every recommendation is a product, clients stop coming.
- Different measures each quarter. Trends only work if the numbers are comparable.
- Skipping a quarter. The QBR that doesn't happen is the one before the client leaves.
Frequently asked questions
What is a QBR for a managed service provider?
A quarterly business review is a meeting, usually 30 to 60 minutes, where an MSP and a client review the last three months of service, security and assets, discuss the client's business plans, and agree a technology roadmap and budget for the coming quarters.
What should an MSP QBR include?
The client's business update, service-level trends, recurring issues, security posture, device and licence lifecycle, the status of previous recommendations, a roadmap and budget, and agreed decisions and next steps.
Who should attend a QBR?
On the client side, the person who signs off on IT spending and ideally someone who knows day-to-day operations. On the MSP side, the account manager or vCIO and, for technical clients, a senior engineer. Keep it small enough to make decisions.
How long should a QBR take to prepare?
With consistent monthly reports, an hour or two per client: most of the trend data already exists. Without them, preparation can take a day, which is why many MSPs stop running QBRs.