Quarterly business review
kyoo-bee-AR
A structured meeting between the vendor and customer to review value delivered, align on goals, and plan for the next quarter.
A QBR is a structured meeting where the vendor and customer review the past quarter and plan the next. It is the highest-touch engagement in the customer success playbook.
A good QBR has a clear agenda. Review usage data and results achieved. Celebrate wins. Discuss challenges. Align on goals for next quarter. Introduce new features or capabilities. Identify expansion opportunities. Get feedback.
The most common QBR mistake is turning it into a product demo or a status update. QBRs should be strategic. The customer's executive sponsor should attend and walk away thinking: 'This vendor understands our business and is helping us succeed.' If the executive stops attending, the account is at risk.
Examples
A well-run enterprise QBR.
The CSM presents: 'In Q1, your team deployed 340 services through our platform, up from 210 in Q4. Average deployment time dropped from 45 minutes to 12 minutes. Based on your 50-engineer team, that saved approximately 170 engineering hours this quarter.' The VP of Engineering nods and asks about the AI features roadmap.
A QBR reveals expansion opportunity.
During the QBR, the customer mentions they are opening a European office with 30 engineers. The CSM asks about their infrastructure needs. The conversation turns into a proposal for a second deployment in EU-west. Expansion revenue from a QBR conversation.
An executive stops attending QBRs.
For three consecutive QBRs, only the technical lead attends. No executive. The CSM asks directly: 'Is there a reason Sarah has not been joining?' The lead says: 'She is evaluating budget cuts across all vendors.' Red flag. The CSM escalates internally and requests an executive-to-executive meeting.
In practice
QBR agenda template
QUARTERLY BUSINESS REVIEW - [Customer Name] Date: [DATE] | Attendees: [Names] 1. RECAP (10 min) - Key metrics: adoption, usage, ROI achieved - Milestones completed since last QBR - Open support issues resolved 2. VALUE DELIVERED (15 min) - Business outcomes tied to original goals - Usage data and trends - Success stories from their team 3. ROADMAP AND PRIORITIES (15 min) - Upcoming product features relevant to them - Their priorities for next quarter - Expansion opportunities 4. RISKS AND BLOCKERS (10 min) - Adoption gaps - Technical issues - Stakeholder changes 5. ACTION ITEMS (10 min) - Owner | Action | Due date
Read more on the blog
Frequently asked questions
Who should attend a QBR?
From the vendor: CSM and, for large accounts, a VP or director. From the customer: the executive sponsor and the day-to-day users. If neither an executive nor a power user attends from the customer side, the QBR is not valuable enough to justify their time. Fix the content.
How long should a QBR be?
30 to 60 minutes. Anything longer loses executive attention. Structure: 10 minutes on results, 10 minutes on challenges, 10 minutes on goals, 10 minutes on new capabilities, 10 minutes for discussion. Leave the last 10 minutes unstructured for relationship building.
Related terms
The team and practice of ensuring customers achieve their goals with your product. Owns retention, expansion, and advocacy.
A composite metric that combines usage data, engagement signals, and support patterns to indicate whether a customer account is healthy or at risk.
When an existing customer extends their contract for another term. The foundation of recurring revenue.
Additional revenue from existing customers through upsells, cross-sells, and increased usage. The engine of net-negative churn.
Selling a customer a higher-tier plan or more expensive version of what they already buy. Moving them up, not out.
Want the complete playbook?
Picks and Shovels is the definitive guide to developer marketing. Amazon #1 bestseller with practical strategies from 30 years of marketing to developers.