Preparing for an MSP QBR Meeting<\/h2>\n\n\n\n
Running your first QBR can be intimidating. However, taking time to plan the meeting can make a big difference in its outcome. With the right preparation, you can highlight successes and solicit customer feedback in an open and trusting environment.<\/p>\n\n\n\n
Here are a few things you should do before your QBR meeting starts:<\/p>\n\n\n\n
Gather Relevant Data and Metrics<\/h3>\n\n\n\n
Your organization\u2019s customer relationship management (CRM) solution is the best place to start. You will probably find a great deal of high-level information here, but not too much detail into your customer\u2019s day-to-day routine. That\u2019s okay \u2014 this information will establish a good baseline.<\/p>\n\n\n\n
For more in-depth data, look through monitoring tools and helpdesk software for records that apply to your customer. This is where you might find pain points, friction, and other areas of improvement that you can bring up and address during the meeting.<\/p>\n\n\n\n
Invite the Right Stakeholders<\/h3>\n\n\n\n
Make sure your QBR involves the right people to represent your customer\u2019s organization. Ideally, you should have a C-suite executive or other high-level decision-maker present. You should also consider including a financial representative for your client, and your main point of contact for day-to-day operations there.<\/p>\n\n\n\n
Sometimes, getting everyone in the same room is inconvenient. While it\u2019s ideal to get everyone together, these meetings can still be successful without having every stakeholder present each time. Remember that the next one is only three months away, so it\u2019s okay if a key stakeholder misses them from time to time.<\/p>\n\n\n\n
Set Clear Meeting Agendas<\/h3>\n\n\n\n
The QBR doesn\u2019t have to be a strict and formal affair, but it should have some structure. Use the data you gathered to identify customer successes and pain points, and list all the issues you\u2019d like to bring up beforehand. Make sure you also devote time to listening and learning more about your customer, as well. <\/p>\n\n\n\n
We\u2019ll cover more details on what to include in your meeting agenda in the next section.\u00a0<\/p>\n\n\n\n
![\"JumpCloud\"](\"https:\/\/jumpcloud.com\/wp-content\/uploads\/2022\/08\/202207-Resource-TheMSPsGuideToITCentralization-1200x628-1-aspect-ratio-160-110.jpg\")
\n <\/div>\n \n <\/p>\n
\n JumpCloud for MSPs enables you to securely and efficiently provide your customers with seamless access to resources to make work happen. <\/p>\n <\/div>\n
What to Include in a Quarterly Business Review Meeting<\/h2>\n\n\n\n
Every QBR agenda is unique. It reflects the priorities of the customer involved, as well as your history together. Some QBRs focus on past performance and metrics, while others are forward-looking. Ideally, you should have a balanced perspective that includes both.<\/p>\n\n\n\n
Here are some things that most QBR meetings should cover:<\/p>\n\n\n\n
1. Performance Metrics and KPIs<\/h3>\n\n\n\n
Discussing the latest performance metrics is a good way to start the meeting off productively. Compare this snapshot of your current relationship with past performance and future goals. This should establish a solid understanding of where your two organizations stand and where you should go next.<\/p>\n\n\n\n
Service Level Agreement<\/h4>\n\n\n\n
Take time to review your service level agreements (SLAs) and address any compliance issues that may have come up. Maintaining SLA compliance contributes greatly to the trustworthiness of your organization. Make sure you and your customer communicate clearly about SLA expectations and any adjustments moving forward.<\/p>\n\n\n\n
Operational Metrics<\/h4>\n\n\n\n
Operational metrics can provide insight into how smoothly your working relationship is going. Consider talking about uptime measurements, incident response times, ticket resolution, and overall system performance insights<\/a>. Find out if your customer has unmet operational needs.<\/p>\n\n\n\n Security<\/a> is an important topic for MSPs and customers in every field. Take a moment to review security incidents, detection and response times, and compliance. Bring up supply chain risk and work together to manage that risk effectively.<\/p>\n\n\n\n Make sure to measure the number of tickets raised and closed in the last 90-day period. Look for metrics that tell you how smoothly the ticketing process actually works for end users. Response and solution times are a good place to start. Consider incorporating qualitative data about the user experience, as well.<\/p>\n\n\n\n Your QBR should cover cost savings, your customer\u2019s ROI, and budgeting status. Any discrepancies in budgeted expenditure versus actual spending should be discussed. If you are over or under budget, now is the time to talk about it openly and come up with a plan to calibrate spending more effectively.<\/p>\n\n\n\n You may also want to talk about the status of upcoming software patches<\/a>, warranties, and hardware lifecycles. These technical details can become problems if they are ignored until the last minute. QBRs are an opportunity to be proactive about infrastructure management and the technology roadmap well ahead of time.<\/p>\n\n\n\n It may also be a good idea to identify some trends and benchmarks to measure your success by. Look for the latest data on industry standards for guidance on how well your MSP is performing compared to other alternatives. Consider creating charts, graphs, and other visuals to present this data in a digestible format.<\/p>\n\n\n\n It\u2019s important to collect clear and honest feedback from your customer on the quality and value of your service. Open-ended feedback is valuable, but you should also consider a structured survey that can help identify specific pain points to address in the next 90 days. Consider analyzing this data over time to better understand how well your MSP actually responds to real-world customer needs.<\/p>\n\n\n\n The final result of your QBR should be an actionable set of initiatives you can put into place before the next meeting. This might include replacing hardware, upgrading software, or conducting end-user training<\/a>. It could mean implementing new products and services into your portfolio or reviewing internal tasks to strengthen performance metrics. <\/p>\n\n\n\n \n <\/p>\n \n JumpCloud for MSPs enables you to securely and efficiently provide your customers with seamless access to resources to make work happen. <\/p>\n <\/div>\n The better prepared you are for your QBR meeting, the easier it will be to run. Take some of the following tips into consideration when managing QBR meetings.<\/p>\n\n\n\n Getting multiple stakeholders on board for a meeting can be challenging. Consider scheduling the meetings on regular dates throughout the year. Share these dates and get buy-in well ahead of time so you can ensure the right stakeholders show up.<\/p>\n\n\n\n Treat the QBR as a meeting, not a presentation. Don\u2019t be afraid to reach out to customer stakeholders ahead of time when planning for it. It may take effort to get stakeholders to contribute, but the reward is worth it.<\/p>\n\n\n\n It\u2019s easy to fall into the trap of discussing your MSP services more than your customer\u2019s actual needs. Be aware of this pitfall and try to steer the conversation toward your customer whenever possible. Help them open up about their goals and strategy so you can support them more effectively.<\/p>\n\n\n\n After the meeting is done, take time to list out the action items discussed. Complete any tasks you can conveniently finish immediately and report back on the rest. This helps build accountability and ensure a consistent dialogue between stakeholders.<\/p>\n\n\n\n Even the best-prepared customer success managers can run into issues with QBRs. Look out for these common difficulties you may encounter when planning and executing these meetings.<\/p>\n\n\n\n Don\u2019t make the mistake of assuming you know the customer\u2019s needs before they express them. Consider sharing your agenda with the customer team beforehand and asking if there is anything they want to add to it before the meeting starts. You may be surprised by new concerns or requirements you didn\u2019t think of before.<\/p>\n\n\n\n Focusing too intently on data and metrics can lead to a bit of information overload. If you tend to spend time diving into technical details, you\u2019ll need to resist that urge during your QBR. Using high-quality visualizations will help you make brief, salient points without turning the meeting into a technical presentation.<\/p>\n\n\n\n Simply identifying areas where you can improve isn\u2019t enough. You must also commit time and resources to execution. This may require buy-in from other stakeholders in both organizations. Make sure you communicate these dependencies ahead of time and follow up on them as you complete tasks.<\/p>\n\n\n\n The success of your QBRs relies heavily on the quality of the data you can gather during preparation. Having transparent access to device usage and security data makes planning and conducting these meetings much easier. For MSPs, this can be difficult without cloud-native multi-tenant solutions<\/a> for mobile device management.<\/p>\n\n\n\nSecurity Metrics<\/h4>\n\n\n\n
Ticket Metrics<\/h4>\n\n\n\n
Financial Metrics<\/h4>\n\n\n\n
Other Technical Metrics<\/h4>\n\n\n\n
Data Analysis and Interpretation<\/h4>\n\n\n\n
2. Client Feedback and Satisfaction Surveys<\/h3>\n\n\n\n
3. Strategic Recommendations and Action Plans<\/h3>\n\n\n\n
\n <\/div>\n Best Practices for Conducting QBR Meetings<\/h2>\n\n\n\n
Maintain Regular Meeting Schedules<\/h3>\n\n\n\n
Encourage Stakeholder Participation<\/h3>\n\n\n\n
Focus on Client-Centric Discussions<\/h3>\n\n\n\n
Follow Up on Action Items<\/h3>\n\n\n\n
Common QBR Challenges and Solutions<\/h2>\n\n\n\n
Addressing Client Concerns Effectively<\/h3>\n\n\n\n
Avoiding Data Overload<\/h3>\n\n\n\n
Continuous Improvement and Follow-Up<\/h3>\n\n\n\n
Final Thoughts<\/h2>\n\n\n\n