Key Takeaway: The QBR that starts with a question about the client’s business is a service. The QBR that starts with a slide deck about the MSP’s activity is a report. Start with: what has changed in your business since we last met? That question changes the entire dynamic of the meeting.
Most MSP quarterly business reviews are presentations. The best ones are conversations. The difference is not the slide deck. It is whether the meeting starts with a question about the client’s business or a summary of the MSP’s activity. One of those openings builds the relationship. The other one is a report that could have been an email.
The QBR is the most underutilized retention tool in managed services. Done well, it is the meeting where clients remember why they pay what they pay, where problems surface before they become churn, and where the vCIO relationship earns its keep. Done poorly, it is the meeting clients cancel because they do not see the value in attending.
Why Most QBRs Fail
The typical MSP QBR follows a predictable structure: the MSP presents a summary of tickets closed, uptime statistics, and security alerts handled. The client nods. The MSP mentions a few upcoming projects or renewals. The client nods again. The meeting ends in 30 minutes and nobody is sure what was accomplished.
That meeting fails because it is designed around what the MSP wants to report, not around what the client needs to discuss. The client does not care how many tickets were closed. They care whether their technology is working, whether their business is protected, and whether their IT investment is aligned with where their business is going. Those are different questions, and they require a different kind of meeting.
The other common failure is the QBR that becomes a sales call. The MSP arrives with a list of recommended upgrades, new services, and contract expansions. The client feels sold to rather than advised. The trust that the advisory relationship requires is eroded, and the client starts treating the QBR as a meeting to avoid rather than a meeting to prepare for.
The Opening Question That Changes Everything
The single most effective change you can make to your QBR structure is to start with a question rather than a slide deck. The question is: what has changed in your business since we last met?
New hires, new locations, new compliance requirements, new competitive pressures, a planned acquisition, a key employee departure, a change in the business model. Any of these can change the technology priorities. An MSP that shows up with a prepared agenda and no curiosity about what has changed is delivering a presentation, not a service.
The opening question does several things simultaneously. It signals that you are there to serve the client’s interests, not to deliver a report. It surfaces information that changes the conversation. It gives the client a reason to prepare for the meeting rather than treat it as an obligation. And it establishes the tone of the relationship: this is a partnership, not a vendor relationship.
The Four-Part QBR Structure
A well-structured QBR covers four areas. The order matters. Start with the client’s business, not the MSP’s activity.
Part 1: Business changes and priorities (15 minutes). What has changed since the last meeting? What are the business priorities for the next quarter? Are there any planned changes, projects, or events that will affect the technology environment? This section is a conversation, not a presentation. The MSP listens more than they talk.
Part 2: Technology roadmap progress (15 minutes). What was on the roadmap from the last meeting? What was completed? What is still in progress? What has changed in the roadmap based on the business priorities discussed in Part 1? This section demonstrates that the MSP is executing against a plan, not just responding to incidents. It also creates accountability: the client can see whether the MSP is delivering on what was committed.
Part 3: Risk posture and security update (10 minutes). What is the current security posture? Are there any new risks or vulnerabilities that require attention? What is the status of the client’s cyber insurance requirements? This section should be factual and specific, not a sales pitch for additional security services. If there are genuine risks that require investment, they should be presented as risks, not as products.
Part 4: Service delivery feedback (10 minutes). How is the MSP performing? Are there any recurring issues that have not been resolved? Are there any technicians or processes that are working particularly well or particularly poorly? This is the section most MSPs skip, and it is the section that surfaces the problems before they become churn. The client who has a complaint they have not raised will raise it here, or they will raise it when they send the termination notice. The QBR is the better venue.
The Technology Roadmap: The QBR’s Most Important Artifact
The technology roadmap is what separates a QBR from a status meeting. A status meeting reports on what happened. A QBR reviews progress against a plan and updates the plan based on new information. Without a roadmap, there is no plan to review, and the meeting defaults to a status report.
The roadmap does not need to be elaborate. It needs to answer three questions: where is the client’s technology environment today, where does it need to be in 12 to 36 months, and what specific investments in what order will close that gap? A one-page document that answers those three questions is a roadmap. A 40-slide deck that describes every possible technology upgrade is a sales catalog.
The roadmap should be updated at every QBR. Business priorities change. Technology changes. The roadmap that was right six months ago may not be right today. The MSP that updates the roadmap at every meeting is demonstrating that they are paying attention. The MSP that presents the same roadmap quarter after quarter is demonstrating that they are not.
How to Handle the Client Who Cancels Every QBR
The client who consistently cancels or reschedules the QBR is telling you something. Either the meeting is not valuable enough to protect time for, or the client is avoiding a conversation they do not want to have.
The first problem is a QBR design problem. If the meeting is a status report, clients will deprioritize it. If it is a conversation about their business and their technology strategy, they will protect time for it. The fix is to change the meeting, not to chase the client.
The second problem is a relationship problem. A client who is avoiding the QBR may be avoiding a difficult conversation about service quality, pricing, or the relationship itself. The fix is to have that conversation directly, outside the QBR context. Ask the client what would make the meeting more valuable. Ask whether there is something about the relationship that is not working. The answer, whatever it is, is more useful than another rescheduled meeting.
The QBR as a Retention Tool
The clients who stay with an MSP for a decade are not the ones who never had a problem. They are the ones who had problems that were handled well, who felt that their MSP understood their business, and who believed that leaving would be a mistake. The QBR is the primary mechanism for building that belief.
A client who attends four QBRs per year and leaves each one feeling that their MSP is paying attention, executing against a plan, and genuinely interested in their business success is a client who does not shop around. A client who attends four QBRs per year and leaves each one feeling like they sat through a vendor presentation is a client who is already evaluating alternatives.
The QBR completion rate, the percentage of clients who actually attend their scheduled QBRs, is a leading indicator of retention. MSPs with high QBR completion rates retain clients longer. The correlation is not coincidental.
Frequently Asked Questions
How long should a QBR be?
60 minutes is the right target for most clients. 90 minutes for clients with complex environments or significant roadmap items. Less than 45 minutes is usually a sign that the meeting is not covering what it should. More than 90 minutes is usually a sign that the meeting is not well-structured. The four-part structure described above fits comfortably in 60 minutes when both parties are prepared.
Who should attend the QBR?
From the client side: the decision-maker who approves the IT budget and the person who manages the day-to-day relationship with the MSP. From the MSP side: the account manager or vCIO who owns the relationship and, for larger clients, the technical lead who knows the environment. The QBR is not a meeting for the entire team. It is a meeting for the people who make decisions.
What if the client does not have a technology roadmap?
Build one. The first QBR with a new client should include a technology assessment that produces the first version of the roadmap. It does not need to be comprehensive. It needs to identify the three to five most important technology priorities for the next 12 months and the investments required to address them. That is enough to make the next QBR a meaningful conversation rather than a status report.
How do I handle a QBR where the client is unhappy?
Listen first. Understand specifically what is not working before you respond. Acknowledge the problem without being defensive. Commit to a specific resolution with a specific timeline. Follow up on that commitment before the next QBR. The client who raises a problem in a QBR and sees it resolved is more loyal than the client who never had a problem. The client who raises a problem and sees it ignored is the one who sends the termination notice.
About Brent Lacy: Brent Lacy is a technology advisor and the voice behind Rewired MSP. He helps MSPs operate with greater maturity and helps business owners make IT choices that make them more secure and more efficient. He is the author of Rewired MSP: Mastery, Scalability & Performance, vCIO Rewired: Virtually Conquering IT Obstacles, and Near Miss: Preventable IT Failures Threatening Your Business Security.
Related Reading
- vCIO Services: The Fiduciary Standard, the Roadmap, and the Advisory Practice That Clients Trust
- Building a Technology Roadmap: The vCIO’s Most Powerful Tool
- Why vCIO Strategy Should Never Feel Like a Sales Pitch
- vCIO Deliverables That Prove Value (Without Selling)
- The Client Churn Problem No MSP Wants to Talk About
