QBR Builder

Goal

Convert messy account notes and usage data into a structured Quarterly Business Review covering wins, value delivered, risks, and a specific customer ask.

Trigger

When a CSM or AE needs to prepare a QBR and has raw account notes or usage data ready to process.

Steps

1. 1

   Analyze the raw account notes and usage data below. Identify the account name, contract period, key stakeholders, product areas used, adoption metrics, and any notable events from the quarter. $account_notes

   • □Account name and review period are identified
   • □Key stakeholders and product areas are noted
   • □Adoption or usage metrics are extracted

   Analyze the raw account notes and usage data below. Identify the account name, contract period, key stakeholders, product areas used, adoption metrics, and any notable events from the quarter.
   
   $account_notes

2. 2

   Compile the Wins section. Surface 3–5 specific, measurable achievements from the quarter — feature launches, adoption milestones, support resolutions, or business outcomes the customer can claim credit for. Lead with the customer's success, not vendor activity.

   • □Each win is specific and attributable to the quarter
   • □At least one win ties to a business outcome, not just a product event
3. 3

   Draft the Value Delivered section. Quantify ROI where possible — time saved, revenue influenced, cost avoided, or efficiency gains. If hard numbers aren't available, describe qualitative value using the customer's own language and goals from the notes.

   • □Value is framed in the customer's business terms
   • □At least one metric or concrete example is included
4. 4

   Identify Risks and open issues. Flag low adoption areas, unresolved support tickets, stakeholder changes, upcoming renewals, or any signals of dissatisfaction. Rate each risk as High / Medium / Low and suggest a one-line mitigation action.

   • □Every risk has a severity rating
   • □A mitigation action is paired with each risk
5. 5

   Write The Ask section. Based on account health, usage gaps, and upcoming opportunities, craft one primary ask for the customer — this could be an expansion conversation, an exec sponsor introduction, a case study commitment, or a renewal close. Make it specific, time-bound, and tied to their goals.

   • □The ask is singular and focused
   • □It connects back to a customer goal or pain point from the notes
6. 6

   Assemble the full QBR outline in presentation-ready format. Add a one-paragraph executive summary at the top that a VP could read in 30 seconds. Include a suggested agenda slide order and flag any data gaps where the CSM should verify numbers before the live meeting.

   • □Executive summary is under 75 words
   • □Agenda order flows logically from context to value to ask
   • □Data gaps are explicitly called out

Output format

Return the QBR as clearly labeled sections: Executive Summary, Suggested Agenda, Wins, Value Delivered, Risks (table with severity and mitigation), and The Ask. Use bullet points within sections. End with a 'Data Gaps to Verify' list. Tone should be confident and customer-centric, suitable for a VP-level audience.