How to run an MSP QBR (with an agenda)

A good quarterly business review does one thing for your MSP: it turns a monthly invoice into a relationship. Done well, a QBR is where a partner stops seeing you as "the IT bill" and starts seeing you as the team that keeps their business running and helps them plan what's next. Done badly, it's a ticket-count slideshow nobody remembers by Friday. This guide gives you a repeatable structure — a timed agenda, the data pack to bring, a realistic cadence, and the follow-up that actually moves the needle — so any account manager on your team can run a QBR that lands.

QBR vs SBR: know which meeting you're running

People use these terms interchangeably, but they answer different questions and the mix-up is why so many reviews feel unfocused. A QBR (quarterly business review) is largely operational and looks backward: how did service delivery go this quarter, are we hitting SLAs, what broke, what did we ship, and what needs attention in the next 90 days. An SBR (strategic business review) is forward-looking and usually less frequent: the multi-year technology roadmap, budget planning, security and risk posture, and how IT maps to where the business is trying to go. Most partners need frequent, lightweight QBRs and one or two heavier strategic reviews a year.

The practical rule: don't try to do both in one 45-minute call. If you bury a three-year roadmap conversation inside a quarterly ops review, you'll rush the strategy and skip the follow-up. Keep the QBR tight and operational, flag strategic items as they surface, and schedule the deeper SBR separately when the stakes justify it.

How often to run them (cadence)

Not every partner needs a formal QBR every quarter, and pretending they do just burns your account managers out. Tier your book and match the cadence to the relationship:

• Top-tier / high-MRR / strategically important partners: full QBR every quarter, plus one annual SBR.
• Mid-tier partners: a lighter QBR twice a year, with a written scorecard sent the other two quarters.
• Smaller or transactional partners: an annual review, often async — a one-page scorecard and a short call only if something needs a decision.
• Any partner mid-project, mid-migration, or post-incident: review on the project's rhythm regardless of tier, because that's when trust is won or lost.

The goal is consistency, not heroics. A predictable, well-prepared review every six months beats an ambitious quarterly cadence you abandon by Q3.

What to bring to the QBR

Walk in with a data pack you assembled in advance, not numbers you pull up live. The best QBR materials fit on one page the partner can skim, backed by talking points for anything that needs context. At minimum bring:

• A service scorecard: ticket volume and trend, average response and resolution time, SLA attainment, and top recurring issues.
• Wins and delivered work: projects completed, upgrades shipped, incidents prevented — the value that doesn't show up on an invoice.
• Risk and security posture: patch and backup status, endpoint coverage gaps, warranty/end-of-life hardware, and anything flagged from your RMM and security tooling.
• Roadmap and renewals: what's coming up for renewal, contracts or licenses expiring, and the recommended next projects with rough budget ranges.
• One or two decisions you actually need the partner to make — a QBR without an ask is a status update, not a business review.

Anonymize and double-check every figure before you present it. Nothing erodes trust faster than a scorecard number the partner knows is wrong.

A timed agenda that keeps you on schedule

Time-box the meeting so it stays a conversation, not a monologue. A 45-to-60-minute QBR usually breaks down like this:

• 0–5 min — Reconnect: restate the partner's business goals and what "good" looks like for them this year.
• 5–15 min — Service review: walk the scorecard, own any misses honestly, and highlight the wins.
• 15–30 min — Risks and roadmap: surface what needs attention, then the recommended next steps and rough budget.
• 30–45 min — Decisions and priorities: agree what happens next quarter and who owns it.
• 45–50 min — Recap: read back the action items, owners, and dates out loud before anyone leaves.

Leaving the room with three agreed, owned actions is worth more than covering every slide. If a topic needs more time than the box allows, park it and book a separate session rather than blowing the schedule.

The follow-up is the meeting

Most of a QBR's value is realized after everyone hangs up. Send a written recap within 48 hours — the agreed actions, the owner and due date for each, and any decisions made. Turn the next-quarter items into real projects or tickets in your delivery system so they don't evaporate, and put a reminder on your own calendar to check progress before the next review. When you open the following QBR by reporting on last quarter's commitments, you prove the review is a working system and not theater. That follow-through, repeated over a few cycles, is what turns a review into retention.

If you're running reviews at any scale, pull the evidence from the tools you already run rather than rebuilding decks by hand. Current's SBR/QBR module assembles service, project, security, and roadmap data — including view-only evidence feeds from your RMM, backup, and security stack — into an AI-assisted strategic review, so your account managers spend their prep time on the story and the recommendations instead of copy-pasting metrics.

Step by step

1. Step 1
   Set the objective and confirm the right people

   Decide what this specific QBR needs to accomplish and who has to be in the room to make decisions. Get a business decision-maker on the partner side, not just an IT contact, and confirm the date early so it doesn't slip.

2. Step 2
   Build the data pack in advance

   Assemble a one-page scorecard plus talking points: ticket and SLA trends, wins delivered, risk and security posture, renewals, and the recommended next projects with rough budgets. Verify every number before you present it.

3. Step 3
   Open by reconnecting to their goals

   Spend the first few minutes restating the partner's business objectives and what success looks like for them. This frames everything that follows as being about their outcomes, not your metrics.

4. Step 4
   Review last quarter's delivery honestly

   Walk the scorecard. Celebrate the wins, but own any SLA misses or recurring issues directly and say what you're doing about them. Honesty here is what buys credibility for your recommendations.

5. Step 5
   Surface risks and the roadmap

   Lay out what needs attention — aging hardware, coverage gaps, expiring contracts, security exposure — then present the recommended next steps and rough budget so the partner can plan, not just react.

6. Step 6
   Align on next quarter's priorities

   Agree together what actually happens next and in what order. Aim to leave with a short, realistic list the partner has signed off on, rather than a long wish list nobody committed to.

7. Step 7
   Confirm owners, dates, and the recap

   Before anyone leaves, read the action items back out loud with an owner and a due date for each, so there's no ambiguity about who does what and when.

8. Step 8
   Send the recap and turn actions into work

   Within 48 hours, send a written summary of decisions, actions, owners, and dates. Convert the next-quarter items into real projects or tickets, and set your own reminder to check progress before the following review.