salescustomer success

Customer Success QBR Template

Creates a customer QBR presentation with usage data, ROI analysis, expansion opportunities, and renewal preparation.

Prompt
You are a customer success manager in the [industry] sector. Create a Quarterly Business Review (QBR) template for presenting to [customer name], a [company type] who has been using [your product] for [duration]. The goal is to demonstrate value and identify expansion opportunities. Format the output as structured presentation sections with clear headings and, where applicable, tables and bullet lists: (1) Relationship summary: key contacts, contract details, renewal date, current plan, (2) Usage & Adoption metrics: a table with 6-8 metrics showing current quarter vs previous quarter vs target (e.g. DAU, feature adoption rate, tickets raised), with trend arrows, (3) ROI Analysis: calculate the customer's return based on [value metric, e.g. 'time saved' or 'revenue generated'] with before/after comparison, (4) Wins This Quarter: 3 specific outcomes achieved, (5) Roadmap Preview: 2-3 upcoming features relevant to this customer's use case, (6) Health Check: NPS score, support satisfaction, open issues count, risk assessment (Green/Yellow/Red), (7) Expansion Opportunity: a tasteful upsell recommendation tied to their growth or a pain point, with ROI projection, (8) Action Items: commitments from both sides for next quarter. You must ensure the tone is partner-like, not vendor-like. Avoid making it a product pitch. Only focus on their goals and outcomes.

Why this prompt works

The 'partner-like, not vendor-like' constraint shapes the entire output. Most QBR templates produce documents that read like a sales pitch dressed as a review, which is exactly why customers stop showing up to QBRs. This prompt avoids that with the 'avoid making it a product pitch' rule and the 'focus on their goals and outcomes' framing throughout. The expansion opportunity section specifically calls for 'tasteful upsell tied to growth or pain', not just an upsell; this is the difference between a QBR that strengthens the relationship and one that erodes trust. The ROI analysis with before/after comparison gives the customer something they can show their own boss, which is what makes QBRs renewable.

When to reach for it

  • You're a CSM preparing your first QBR for a customer and want a structured template that's customer-centric.
  • You're standardising QBRs across a CS team and want consistent quality and structure.
  • You're prepping for a renewal conversation and want the QBR to surface expansion opportunities without being heavy-handed.
  • You're a head of CS auditing how the team runs reviews and want a benchmark to compare against.

How to customise it

The duration field (how long they've been a customer) shapes the tone. A 6-month customer needs a QBR focused on adoption; a 3-year customer needs one focused on expansion and roadmap alignment. The value metric is the central anchor: 'time saved' produces different ROI math than 'revenue generated' or 'tickets reduced'. Be honest. For accounts where you don't have rich usage data, ask the model to compress the metrics section and expand the qualitative wins section instead; padding with placeholder numbers undermines credibility.

What good output looks like

Eight presentation sections: relationship summary, usage and adoption metrics table, ROI analysis with before/after, wins this quarter, roadmap preview, health check with NPS and risk assessment, expansion opportunity, action items. Total length 1,000 to 1,500 words plus tables. The expansion opportunity section is the most-customised section; the model's first pass is structurally sound but needs your specific knowledge of the account's roadmap.

QBRcustomer successretentionupsellcustomer reviewChatGPT / Claude

Build a prompt like this for your task

Use the free guided prompt builder on the homepage: pick what you need, answer three quick questions, and get a high-scoring prompt of your own.

Open the prompt builder →
100
out of 100
Role definition100
Task clarity100
Specificity100
Context100
Output format100
Constraints100
Examples100