Quarterly Business Reviews for MSPs: How an Assistant Prepares Them

For managed service providers, the quarterly business review is where the relationship is renewed. It is the meeting where the client sees what the MSP did, understands the state of their technology, hears recommendations and plans the year ahead. Done well, QBRs strengthen retention and lead to projects. Done poorly, or skipped, they leave clients wondering what they are paying for.

The problem is preparation. Pulling ticket data from the PSA, patch and backup status from the RMM, license counts, hardware age, security findings and project status, then turning it all into a clear presentation, can take hours per client. Many virtual CIOs and account managers simply don't have that time. A dedicated remote assistant can prepare QBRs consistently, schedule them and track recommendations afterward. This guide explains how. For other MSP roles, including tier 1 support, see our IT and MSP role playbook.

What goes into a good QBR

A useful QBR is short, visual and focused on the client's business, not just technical metrics. A typical structure:

1. Service summary: tickets opened and resolved, categories, trends, satisfaction feedback.
2. Health overview: patch compliance, backup success, endpoint protection status, device ages.
3. Security posture: findings from your assessments, phishing training results, MFA coverage, open risks.
4. Licensing and assets: license counts versus users, renewals coming up, hardware due for replacement.
5. Projects: completed, in progress and proposed.
6. Recommendations and roadmap: prioritized items with business rationale.
7. Action items from the last QBR and their status.

The vCIO or account manager owns the recommendations and the conversation. The assistant prepares everything else.

Data sources

Most of the data comes from systems the MSP already runs:

• PSA such as ConnectWise PSA, Autotask or HaloPSA for tickets, agreements and projects.
• RMM such as NinjaOne, Datto RMM, N-able or ConnectWise Automate for patching, device inventory and alerts.
• Backup platforms for job success and restore tests.
• Security tools for endpoint protection, email security and training platforms.
• Documentation platforms such as IT Glue or Hudu for asset details and lifecycle data.
• Vendor portals for license counts and renewal dates.

Many MSPs use QBR or vCIO tools that pull from these systems automatically. Where they don't, the assistant exports reports and builds the pack from a template.

The preparation workflow

For each client QBR, the assistant:

1. Schedules the meeting with the client's decision makers according to the QBR calendar.
2. Pulls data for the quarter from each system using saved reports.
3. Builds the pack in your template, adding charts and short factual summaries.
4. Highlights changes: rising ticket categories, failed backups, devices out of support, licenses unassigned.
5. Lists action items from the last QBR with status from the PSA.
6. Sends the draft to the vCIO or account manager several days ahead for recommendations and narrative.
7. Finalizes and sends the pre-read to the client if that is your practice.

The assistant never makes recommendations to the client. They surface facts so the vCIO can make informed recommendations.

Scheduling the QBR calendar

Reviewing every client quarterly is ambitious for small MSPs. Many segment clients: larger clients quarterly, smaller ones twice a year. The assistant maintains the calendar, sends scheduling requests well ahead, books the meeting with the right attendees and sends reminders. A calendar view showing which clients are due, scheduled or overdue keeps the program on track.

Making packs readable for business leaders

Clients who attend QBRs are often owners, operations directors or finance leads, not IT specialists. A few presentation habits make packs far more useful:

• One idea per slide, with a plain-language headline that states the point, such as "Backups recovered after two failures mid-quarter" rather than "Backup job status."
• Trends over snapshots. Show the last few quarters where you have the data, so the client sees direction.
• Consistent colors for status: the same color always means healthy, attention or action needed.
• Short glossary at the end for any technical terms that remain.
• An appendix for detailed tables, so the main pack stays short.

The assistant applies these habits consistently, and the vCIO's narrative ties the facts to the client's business priorities, such as growth plans, new offices or compliance obligations.

After the meeting

The value of a QBR is in follow-through. The assistant:

• Logs meeting notes the vCIO provides.
• Creates tickets or opportunities in the PSA for agreed actions and proposed projects.
• Sends the follow-up summary the vCIO approves.
• Tracks action items to closure and reports status before the next QBR.

Lifecycle and renewal tracking

Between QBRs, the assistant can maintain a lifecycle calendar for each client: hardware warranty expirations, software end-of-support dates, domain and certificate renewals, and license renewals. Flagging these ahead of time gives the vCIO and client room to plan budgets and projects rather than react.

Boundaries and access

The assistant needs read access to reporting in the PSA, RMM, backup and security tools, plus documentation. They do not need administrative rights to client environments to prepare QBRs, and they should not have them for this role. Keep client credentials in your password management platform with access scoped appropriately; the assistant should not have access to client admin credentials unless their role specifically requires it. Our MSP tier 1 runbook guide covers technical roles separately.

Security findings are sensitive. QBR packs should be shared only with authorized client contacts, through secure channels.

A worked example

An MSP has a mid-size client with an upcoming quarterly review. Three weeks ahead, the assistant sends scheduling options to the client's operations director and books the meeting. Ten days ahead, they pull ticket reports from the PSA and notice a spike in printer-related tickets at one office. They pull patch and backup reports from the RMM and backup platform: patch compliance is strong, but two backup jobs failed repeatedly mid-quarter before a fix. Device inventory shows several laptops past their warranty. License reports show unassigned seats. The assistant builds the pack, highlighting these items, and sends it to the vCIO.

The vCIO adds recommendations: a printer replacement project, a laptop refresh plan and license cleanup. After the meeting, the assistant creates opportunities in the PSA for the projects, a ticket for the license cleanup, and sends the summary. Before the next QBR, the assistant reports that license cleanup is complete and the printer project is approved.

A sample week

What to measure

• QBRs held on schedule by client segment.
• Packs delivered to vCIOs by the agreed lead time.
• Action items closed before the next review.
• Projects proposed from QBRs and their status.
• vCIO prep time per QBR, estimated before and after.

Templates to prepare

• QBR deck template with standard charts.
• Saved reports in each system.
• Scheduling email and reminder.
• Post-QBR summary.
• Lifecycle calendar template.

Common mistakes

Metrics without meaning. Translate technical data into business impact in the vCIO's narrative.

No follow-through. Track every action item.

Admin rights for reporting roles. Read access is enough.

Skipping smaller clients entirely. A simpler pack twice a year is better than nothing.

Onboarding the assistant

In the first week, give the assistant read access to reporting, walk through two recent QBRs and your template, and build saved reports together. In the second week, they prepare packs for two clients with close review. By the end of the month, they run the QBR calendar and preparation for the agreed client set.

Frequently asked questions

Does the assistant need technical skills?

Comfort with IT terminology and reporting tools is important, but they do not need engineering skills for this role. ExecWing screens for familiarity with MSP tools.

Can the assistant present the QBR?

The vCIO or account manager presents. The assistant can join to take notes.

Can one assistant support several vCIOs?

Yes, depending on client count and QBR frequency. Each placement is dedicated, on a customized schedule based on your needs and budget.

Do clients see the assistant?

Only if you choose. Many MSPs introduce the assistant as part of the account team for scheduling and follow-ups.