qbr-generator

QBR Generator: Full Methodology

What a QBR Is (and What It Isn't)

A QBR is a strategic conversation with your customer about their business outcomes and your role in achieving them. It is NOT:

• A product usage report (boring, customer doesn't care about your DAU metrics)
• A feature roadmap presentation (self-serving, makes you look like you're pitching)
• A support ticket review (reactive, should be handled in regular check-ins)
• A renewal negotiation (too early for that; mixing agendas destroys trust)

The litmus test for every slide: If you removed your company name and product name, would the content still be valuable to the customer? If yes, it's a good QBR slide. If no, it's a product pitch disguised as a QBR.

---

The "So What?" Test

Every metric, chart, graph, or statement in your QBR must answer one question from the customer's perspective: "So what?"

Weak (fails the test)	Strong (passes the test)
"You processed 15,000 transactions through our platform"	"Your team processed 15,000 transactions — 3x more than last quarter — which eliminated 240 hours of manual reconciliation work"
"You have 45 active users"	"45 of your 50 licensed users are active weekly, making your team one of our highest-adoption accounts in your industry"
"Uptime was 99.9% this quarter"	"Zero unplanned downtime during your peak audit season, which your team cited as their top concern last quarter"
"We released 12 new features"	"Of the 3 feature requests your team raised in Q2, 2 have been shipped and 1 is in beta — here's how each addresses the workflow gap you identified"

The formula: [Data point] + [So what for THEIR business] + [Connection to THEIR stated goals]

---

QBR Structure: The 7-Section Framework

Section 1: Executive Summary (1 slide)

Purpose: Set the tone. Give the executive sponsor the headlines so they can disengage from the details if needed but still walk away informed.

Contains:

• 3 headline metrics (the numbers that matter most to their stated goals)
• Overall health assessment (green/yellow/red with a one-line explanation)
• 1-2 sentence summary of the quarter
• Preview of recommendations

Tips:

• This is the most important slide. Some executives only read this one.
• Write it last (after you've built everything else) but present it first.
• Avoid jargon. The executive may not be close to the day-to-day product usage.

Section 2: Value Delivered (2-3 slides)

Purpose: Prove ROI. Show the customer what they got for their money this quarter.

Contains:

• KPIs tied to the business case they bought on (not vanity metrics)
• Before/after comparisons (vs. pre-implementation baseline)
• Quarter-over-quarter trends (are things getting better?)
• Specific outcomes: time saved, errors reduced, revenue protected, compliance achieved

How to frame value when metrics are hard to quantify:

If you lack...	Use this proxy...
Hard ROI numbers	Time saved (hours/week x loaded labor cost)
Direct revenue impact	Risk avoided (cost of errors, compliance penalties)
Financial metrics	Operational efficiency (throughput, speed, accuracy rates)
Any quantitative data	Qualitative feedback from their team (quotes, survey results)

Critical: Always tie metrics back to the original business case. If they bought to "reduce audit cycle time by 40%," show exactly where they are on that journey. If you're behind, acknowledge it and show the plan to catch up.

Section 3: Usage & Adoption Metrics (1-2 slides)

Purpose: Show how deeply the product is embedded and where there's room for more adoption.

Contains:

• Active users vs. licensed users
• Feature adoption (which capabilities are being used, which aren't)
• Usage trends over time
• Power users vs. light users
• Comparison to similar customers (anonymized benchmarks)

Why this section matters for expansion: Low adoption of certain features is either (a) a training opportunity that deepens engagement, or (b) a signal that those features aren't relevant — both are valuable information. High adoption across the board is your setup for the expansion conversation.

Section 4: ROI Analysis (1-2 slides)

Purpose: Put a dollar figure on the value delivered.

The ROI Formula:

ROI = (Value Delivered - Cost of Solution) / Cost of Solution x 100

Where:
- Value Delivered = Time saved (hours x loaded cost) + Errors avoided (cost per error x errors prevented) + Revenue impact (if measurable)
- Cost of Solution = Annual contract value + Implementation cost (amortized) + Internal resource cost

Worked Example:

Customer pays: $120K/year
Time saved: 500 hours/quarter x $75/hour loaded cost = $150K/year
Errors avoided: 25 errors/quarter x $2,000/error = $200K/year
Total value: $350K/year
ROI: ($350K - $120K) / $120K = 192%
Payback period: $120K / $350K x 12 months = 4.1 months

If ROI is negative or unclear:

• Don't hide it. Address it directly.
• Show the trajectory: "We're at 0.8x ROI today, but based on the adoption curve, we project 2.1x by end of year."
• Identify what needs to change: "To reach your target ROI, we need to increase adoption from 60% to 85% across the team."

Section 5: Roadmap Alignment (1 slide)

Purpose: Show the customer that your product direction aligns with their future needs.

Contains:

• 2-3 upcoming features/capabilities that are relevant to THIS customer (not your full roadmap)
• Connection to requests they've made or challenges they've raised
• Rough timing (this quarter, next quarter, H2) — don't over-commit on dates
• How these features will impact their specific workflows

Rules:

• Only show roadmap items relevant to this customer. Generic feature lists are a waste of their time.
• Never use the roadmap slide to sell features that don't exist yet. This is about alignment, not vaporware.
• If a feature they requested is NOT on the roadmap, say so honestly and explain why. Don't omit it and hope they forget.

Section 6: Expansion Opportunities (1 slide)

Purpose: The natural bridge from "here's the value we delivered" to "here's how you could get even more value."

Contains:

• 1-2 specific expansion recommendations (not a product catalog)
• Each recommendation tied to a challenge or goal the customer mentioned
• Estimated additional value (in their terms — hours saved, risk reduced, outcomes improved)
• Clear next step (not "let me know if you're interested" but "I'd recommend a 30-minute deep dive with your [specific person] — can we schedule that?")

How to transition naturally: "Based on the usage patterns we're seeing and what [champion's name] mentioned about [their upcoming initiative], I think there are two areas where we could help you get significantly more value from the platform. I don't want to turn this into a sales pitch, but I'd be doing you a disservice if I didn't flag these."

This is the expansion bridge. It works because:

1. It's grounded in data (usage patterns), not speculation
2. It references their own words (what the champion said)
3. It's framed as advice, not a pitch
4. It explicitly acknowledges the concern about "turning into a sales pitch" — which disarms the reaction

Section 7: Risk Review & Action Items (1 slide)

Purpose: End on transparency. Show risks, open issues, and clear next steps.

Contains:

• Any open issues or concerns (don't hide them — the customer knows)
• Risks to the partnership (champion leaving? budget pressure? underperforming area?)
• Mutual action items with owners and deadlines
• Date for next QBR

---

Data Gathering: What to Pull Before Building the QBR

Use references/data-checklist.md for the complete checklist. Summary of sources:

Data Type	Source	Lead Time
Product usage metrics	Product analytics / BI tool	1-2 days to pull and clean
Support tickets & CSAT	Support platform (Zendesk, Intercom)	1 day
NPS/survey data	Survey tool or CS platform	Check if survey needs to be sent 2+ weeks before QBR
Contract & billing details	CRM + billing system	1 day
Previous QBR action items	Previous QBR deck + meeting notes	Already have this
Customer's strategic context	Champion conversation, earnings calls, press releases	1-2 days of research
Benchmark data	Internal analytics (similar customers)	1 day
Feature requests & feedback	Product feedback tool or CRM notes	1 day

Start data gathering 2-3 weeks before the QBR. You need time to analyze, build the deck, review internally, and rehearse.

---

Pre-QBR Champion Conversation

Always have a 15-20 minute call with your champion before the QBR. This conversation:

1. Validates your data. "We're seeing 45 active users and a 30% reduction in processing time. Does that match what your team experiences?"
2. Surfaces hidden concerns. "Is there anything your leadership is concerned about that I should be prepared to address?"
3. Aligns on the expansion bridge. "I'd like to mention the opportunity for [expansion]. Do you think your leadership would be receptive? Should I position it differently?"
4. Avoids surprises. The worst thing that can happen in a QBR is a surprise — for you or the customer. The pre-call eliminates this.

Questions to ask your champion:

• "What's top of mind for your leadership right now?"
• "Are there any sensitive topics I should avoid or address carefully?"
• "Who's attending, and what does each person care about?"
• "Is there anything that's changed since our last QBR that I should know about?"
• "What would make this QBR a success from your perspective?"

---

Meeting Facilitation: Running the QBR

Before the Meeting

• Send the deck 24-48 hours in advance (for executives who want to pre-read)
• Confirm attendees and their roles
• Prepare a printed or shared agenda
• Test any technology (screen sharing, video conferencing)
• Rehearse internally — especially the expansion bridge and any difficult topics

During the Meeting

Opening (5 minutes):

• Thank everyone for their time
• State the purpose: "Today we're going to review the value we've delivered this quarter, discuss what's ahead, and make sure we're aligned on priorities."
• Set expectations for the format and timing
• Ask if there's anything they want to add to the agenda

Presenting (30-40 minutes):

• Spend 60% of time on sections 1-4 (value delivered and ROI)
• Spend 20% on sections 5-6 (roadmap and expansion)
• Spend 20% on section 7 (risks and action items)
• Do NOT read the slides. The deck is a conversation guide, not a script.
• Pause after each section and ask: "Does this match what you're seeing? Anything to add?"

Key facilitation techniques:

• Name the elephant. If metrics are bad, address them directly. "I know our response times weren't where they should have been in January. Here's what happened and here's what we've done about it."
• Ask, don't tell. Instead of "we delivered great value," ask "how has this impacted your team's workflow?" Let them articulate the value — it's more persuasive.
• Read the room. If the executive is checking their phone, your content isn't landing. Pivot to what matters to them. Ask directly: "I want to make sure we're covering what's most important to you — what questions do you have?"
• Capture everything. Assign someone on your team to take notes. Every concern, every request, every action item.

Closing (5-10 minutes)

• Summarize key takeaways (3 bullets max)
• Confirm all action items (read them back with owners and dates)
• Confirm the next QBR date
• Thank them genuinely

---

Handling Difficult QBRs

See references/difficult-qbr-playbook.md for full scripts. Summary of scenarios:

Scenario 1: Underperforming Metrics

The data doesn't look good. Usage is down, outcomes aren't being met, or there's a clear problem.

Approach:

1. Acknowledge it immediately. Do not bury bad metrics in a sea of good ones. The customer knows the truth.
2. Show you understand the root cause. "Usage declined 20% in February. We investigated and identified that the workflow change your team made in January created friction at [specific step]."
3. Present a concrete remediation plan with timeline. "Here's what we recommend to get back on track by next quarter."
4. Ask for their input. "What are we missing? What would you need to see to feel confident we're headed in the right direction?"

Scenario 2: Champion Has Departed

Your primary contact and advocate has left the organization.

Approach:

1. Use the QBR as your opportunity to build a relationship with the new stakeholder.
2. Start with a "reset" framing: "Since [champion's name] has moved on, I want to make sure we're aligned on your priorities and how we can best support your team."
3. Don't assume the new stakeholder has the same relationship or opinion. Earn trust from scratch.
4. Ask about their background and priorities before presenting. Tailor the QBR to what they care about.

Scenario 3: At-Risk Renewal

You know the renewal is at risk. The customer has hinted at evaluating alternatives or reducing scope.

Approach:

1. Do not avoid the topic. Address it directly but constructively. "I understand there are questions about whether to continue at the current level. I want to make sure today's conversation gives you the information you need to make the best decision for your team."
2. Focus the entire QBR on value delivered and outcomes achieved. Make the cost of switching visible (retraining, migration, lost institutional knowledge, implementation timeline).
3. If there are legitimate concerns, acknowledge them and present a plan to address them. "If you give us 90 days to [specific improvement], and we don't deliver, I'll personally support your transition."
4. Do not discount preemptively. Earn the renewal on value first. Discounting signals that you agree the product isn't worth the price.

Scenario 4: Hostile Attendee

Someone in the meeting is openly critical, skeptical, or antagonistic.

Approach:

1. Listen fully without getting defensive. "I appreciate you raising that. Can you tell me more about what you've experienced?"
2. Validate their frustration. "That's a fair criticism, and I understand why that's frustrating."
3. Separate the issue from the person. Address the problem, not the tone.
4. If the issue is legitimate, acknowledge it and commit to resolution. If it's based on misinformation, correct it gently with data.
5. Don't let one hostile attendee derail the entire meeting. "I want to make sure we address your concern fully. Can we schedule a follow-up call to dig into this specifically, so we can also cover the other topics on today's agenda?"

---

Post-QBR Follow-Up

Within 24 Hours

• Send a thank-you email with:
  • Summary of key discussion points (3-5 bullets)
  • All action items with owners and deadlines
  • The QBR deck as an attachment
  • Date of next QBR

Within 1 Week

• Internal debrief with your team:
  • What went well? What didn't?
  • What signals did we pick up about account health?
  • Any expansion opportunities to pursue?
  • Any risks to escalate?
• Update CRM with QBR outcomes, health score changes, and expansion signals

Ongoing

• Track action items to completion. Nothing destroys credibility faster than promising something in a QBR and not delivering.
• Reference QBR commitments in regular check-ins: "In our QBR, we committed to [X]. Here's where we are on that."

---

Reference Files

File	Purpose
references/qbr-template.md	Complete slide-by-slide template with guidance
references/data-checklist.md	Pre-QBR data gathering checklist
references/difficult-qbr-playbook.md	Scripts for handling tough QBR situations