Quarterly Business Review Process

Purpose: relationship and roadmap, not ticket review

A QBR is a business meeting with a business owner about where their technology is going – not a recap of last quarter's tickets. Done right, it is the single best churn defense and project-revenue source an MSP has: it is where standardization work gets sold as risk reduction, where price increases get justified with evidence, and where the client hears – on a predictable cadence – that someone is thinking about their business, not just their inbox. Clients rarely leave the provider who owns their technology roadmap.

The role running this meeting is the vCIO function (or a technical account manager in larger shops). In a small MSP that person is you, the founder – and even a solo founder should run lightweight QBRs with top clients. The process below scales down to a 45-minute version.

Who attends

• Client side: the business owner or executive sponsor – the person who owns budget and risk. An office manager alone is a warning sign; if decision-makers stop attending, the relationship is drifting. Their internal IT lead attends in co-managed arrangements.
• MSP side: the vCIO/account owner leads. Optionally the lead tech for that client for credibility on findings – but the meeting is run in business language, not by engineers to engineers.
• Not the whole service desk, and not a parade of five people that outnumbers the client.

Cadence by client size

Typical practice as of 2026:

Don't promise quarterly reviews to thirty clients and deliver four. Commit to a cadence you can sustain; a reliable semi-annual review beats a fictional quarterly one. Start with systems you already pay for: Acronis Cyber Protect Cloud can generate and schedule customizable executive reports, while Acronis PSA provides KPI, profitability, SLA, and NPS reporting. Purpose-built QBR tools such as myITprocess, ScalePad Lifecycle Manager, and vCIOToolbox can help when client volume makes manual preparation expensive. A spreadsheet and editable slide template are enough at the start.

Preparation checklist

Preparation is most of the value. For each review, roughly a week out:

• Pull the quarter's service scorecard from the PSA: ticket volume and trend, SLA attainment (response times with waiting-clock pauses honored), CSAT results, endpoint counts. See MSP KPIs and benchmarks for which numbers belong here.
• Run the standards audit: compare the client's environment against your written standards library; every deviation becomes a finding with a risk rating. (This is the TruMethods-style standardization practice – their data suggests keeping clients on standard can cut reactive tickets by roughly two-thirds.)
• Update the risk register: open findings, aging hardware, unsupported OS versions, backup test results, security posture gaps, compliance progress where relevant – see compliance as a service.
• Refresh the 12–36 month roadmap and the budget forecast: what's planned, what it costs, what quarter it lands in.
• Note business context: anything you've learned about the client's growth, hiring, moves, or plans.
• Send the agenda ahead, and confirm the decision-maker is attending.

Agenda structure

A 60–90 minute meeting (45 minutes for the lightweight version):

1. Business review (client talks first). What's changing in their business – headcount, locations, applications, plans. This is where roadmap items are born, and it signals the meeting is about them.
2. Service scorecard (brief). Tickets, SLA attainment, CSAT – trends, not ticket-by-ticket detail. Five minutes unless something needs explaining.
3. Standards audit results. Findings from the standards review and any network assessment, framed as business risk: "these machines leave support in March; here's the exposure," not CVE numbers.
4. Roadmap and budget forecast. The 12–36 month plan: what you recommend, when, and what it costs – so IT spend becomes a planned budget line instead of surprise invoices.
5. Risk register and compliance progress. What's open, what was closed since last time, what needs a decision today.
6. Decisions and next steps. Leave with explicit outcomes: projects approved, deferred (with the risk documented as accepted), and the next review booked.

Follow up within a week: summary, decisions, and quotes for approved projects.

Turning QBRs into project revenue

The QBR is where the findings-to-projects engine runs: standards audit → findings → roadmap items → funded projects. Sell them as risk reduction, not upsell – "your firewall exits support in Q3; here is the replacement plan" lands very differently from a cold quote. A healthy practice sees a meaningful share of project revenue originate in reviews. When the client defers, document the accepted risk in the register and revisit next cycle; a written, dated "declined" protects you and often converts later. QBRs are also where price adjustments get grounded in evidence – the scorecard and delivered roadmap make the conversation factual instead of awkward.

Common mistakes

• Rehashing tickets. The fastest way to teach executives to skip the meeting. Scorecard in five minutes, then forward-looking.
• Tech jargon. Speak in risk, cost, and downtime. If a slide needs an acronym glossary, rewrite it.
• No decisions requested. A review that ends with "any questions?" produced nothing. Every QBR should ask for at least one decision.
• Skipping quiet clients. "No news" clients skip reviews, drift, and churn without warning – the review is the touch-point that would have caught it; see churn rate.
• Presenting without preparation. An unprepared QBR is worse than none; it demonstrates that the strategic relationship is theater.
• Waiting until the client is big enough. The first review belongs at day ~90 of client onboarding, setting the rhythm from the start.

Exit criteria

A QBR is done when: the decision-maker attended; the scorecard, standards findings, risk register, and roadmap were reviewed; at least one decision was made or a deferral documented; the summary went out within a week; and the next review is on the calendar. Miss those and you held a status call, not a business review.

Bottom line

Run QBRs quarterly for your top clients and semi-annually below that, prepare with the checklist, keep the agenda pointed at the client's business and the next 12–36 months, and always leave with a decision. It is the highest-return recurring meeting in the MSP business model – the place where retention, project revenue, and pricing power are all earned in the same hour.