Most QBRs are status meetings nobody finds useful. The CS team narrates usage data, the customer half-listens, nothing changes. AI-assisted QBRs look completely different — strategic conversations grounded in real analysis. Here is the workflow.
Most QBRs are status reports the CS team delivers. They contain usage data and "how things are going." The customer attends out of obligation. Nobody decides anything.
The version that works: the CSM brings strategic analysis (what the data means, what to do about it), the customer brings their priorities, and the meeting produces specific next-quarter commitments. AI does most of the analysis prep.
I am preparing a QBR for [CUSTOMER]. Their usage data last quarter: [PASTE] Their original goals when they signed: [PASTE] Key tickets they raised: [PASTE] Product features they have not adopted: [PASTE] Their health score and trend: [PASTE] Business changes they have shared with us: [PASTE] Prepare: 1. Executive summary (3 sentences for the CS lead to open with) 2. Wins this quarter — specific, with numbers 3. Issues that came up and how we resolved them 4. Where they are tracking against their original goals 5. Three specific strategic recommendations for next quarter 6. Specific expansion opportunities (with reasoning, not just upsell language) 7. Risks I should raise carefully (churn signals or escalations) 8. The single question to ask them that would surface most useful info Format: 1-page brief. CSM reads in 5 minutes before the call.
0-5 min: CSM shares the executive summary and asks the customer to confirm their priorities.
5-15 min: Strategic recommendations for next quarter. Customer reacts.
15-25 min: Customer-led discussion of their priorities and constraints.
25-30 min: Specific commitments for next 30/60/90 days from both sides.
Total: 30 minutes. Beats 60-minute status QBRs on every metric.