When QBR season arrives, /qbr-facilitator builds executive presentations and ROI stories, so you can deepen strategic alignment. — Claude Skill

title: Section Organization

1. QBR Program Design (program)

Impact: CRITICAL Description: QBR program architecture, cadence strategy, segmentation approach, governance frameworks, and executive review structures for different customer tiers.

2. Executive Preparation (preparation)

Impact: CRITICAL Description: Stakeholder research, executive briefing preparation, pre-QBR alignment, customer context gathering, and presentation development.

3. Value Demonstration (value)

Impact: CRITICAL Description: ROI calculation, value storytelling, outcome documentation, business impact quantification, and success narrative construction.

4. Success Metrics Presentation (metrics)

Impact: HIGH Description: Metrics selection, benchmarking, dashboard design, data visualization, and performance trend analysis for executive audiences.

5. Strategic Account Planning (planning)

Impact: HIGH Description: Success plan development, goal alignment, customer strategy mapping, growth planning, and long-term partnership development.

6. Roadmap Alignment (roadmap)

Impact: HIGH Description: Product roadmap discussions, feature advocacy, customer influence programs, beta participation, and innovation partnership.

7. Risk & Opportunity Identification (risk)

Impact: HIGH Description: Risk assessment, opportunity discovery, expansion identification, churn signal detection, and proactive intervention strategies.

8. Meeting Facilitation (facilitation)

Impact: MEDIUM-HIGH Description: Executive engagement techniques, discussion facilitation, handling difficult conversations, time management, and driving productive dialogue.

9. Follow-up & Action Tracking (followup)

Impact: MEDIUM-HIGH Description: Action item management, accountability frameworks, follow-up cadence, progress tracking, and commitment fulfillment.

10. QBR Automation & Templates (automation)

Impact: MEDIUM Description: Template development, automated reporting, scaled QBR programs, digital-first reviews, and process optimization.

title: QBR Automation & Templates impact: MEDIUM tags: automation, templates, scalability, digital, efficiency

QBR Automation & Templates

Impact: MEDIUM

Automation enables scale without sacrificing quality. The best QBR programs combine standardized templates with smart automation to deliver consistent, personalized reviews across hundreds of accounts. Automate the repeatable, personalize the meaningful.

Automation Opportunity Matrix

              HIGH VALUE
                   ↑
    ┌──────────────┼──────────────┐
    │   AUTOMATE   │   ENHANCE    │
    │   FULLY      │   WITH AUTO  │
    │              │              │
    │ Data pull,   │ Insights,    │
    │ scheduling,  │ prep alerts, │
    │ reminders    │ templates    │
LOW ←──────────────┼──────────────→ HIGH
PERSONALIZATION    │              PERSONALIZATION
NEEDED             │              NEEDED
    │   AUTOMATE   │   KEEP       │
    │   AS DEFAULT │   MANUAL     │
    │              │              │
    │ Tech-touch   │ Exec prep,   │
    │ QBRs, basic  │ strategic    │
    │ reports      │ discussions  │
    └──────────────┼──────────────┘
                   ↓
              LOW VALUE

What to Automate

What NOT to Automate

QBR Template Library

## Template Hierarchy

MASTER TEMPLATE
├── Strategic EBR ($500K+)
│   └── Full executive package
│   └── 90-120 min format
│   └── C-level content
│
├── Enterprise QBR ($100K-$500K)
│   └── Comprehensive review
│   └── 60-90 min format
│   └── VP/Director content
│
├── Mid-Market QBR ($25K-$100K)
│   └── Streamlined review
│   └── 45-60 min format
│   └── Manager content
│
├── SMB QBR ($5K-$25K)
│   └── Efficient review
│   └── 30-45 min format
│   └── Primary contact content
│
└── Digital QBR (<$5K)
    └── Self-service review
    └── Async/video format
    └── Automated content

Enterprise QBR Slide Template

## Enterprise QBR Deck Structure (15-20 slides)

SLIDE 1: Title
- Customer logo + Vendor logo
- "Q[X] Business Review"
- Date

SLIDE 2: Agenda
- Today's topics
- Time allocation
- Outcomes sought

SLIDE 3: Executive Summary
- Overall health status
- Key metrics snapshot
- Value delivered headline

SLIDE 4-5: Customer Business Context
- Recent company news
- Strategic priorities
- How we align

SLIDE 6-7: Value Delivered
- ROI summary
- Key achievements
- Business impact

SLIDE 8-9: Adoption & Engagement
- Usage trends
- Feature adoption
- User coverage

SLIDE 10: Health Indicators
- Health score components
- Trend analysis
- Areas of focus

SLIDE 11-12: Strategic Discussion
- Goals review
- Success plan status
- Planning framework

SLIDE 13: Product Roadmap
- Relevant upcoming features
- Customer feedback status

SLIDE 14: Risks & Opportunities
- Risk mitigation update
- Expansion opportunities

SLIDE 15: Action Items & Next Steps
- Commitments
- Timeline
- Next QBR date

APPENDIX (as needed)
- Detailed metrics
- Technical data
- Supporting documentation

Digital QBR Framework

## Tech-Touch/Digital QBR Components

1. AUTOMATED EMAIL SUMMARY
   - Personalized with customer data
   - Key metrics and trends
   - Value delivered
   - Product updates relevant to them
   - Self-service resources

2. INTERACTIVE DASHBOARD
   - Real-time metrics access
   - Benchmark comparisons
   - Goal tracking
   - Trend visualization

3. VIDEO SUMMARY (Optional)
   - Pre-recorded 5-10 min overview
   - Personalized with customer name
   - Key highlights and recommendations

4. FEEDBACK MECHANISM
   - Survey link
   - Office hours invitation
   - Escalation path if needed

5. SELF-SERVICE PLANNING
   - Goal-setting wizard
   - Resource recommendations
   - Training suggestions

Digital QBR Email Template

Subject: Your Q[X] Business Review - [Company Name]

Hi [First Name],

Here's your quarterly review of how [Company] is using [Product].

## Your Impact This Quarter
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

📊 TIME SAVED: [X] hours
💰 VALUE DELIVERED: $[X]
📈 ROI: [X]%

## Your Usage at a Glance
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

Active Users: [X] / [X] licensed
Features Used: [X] / [X] available
Engagement Score: [X]/100

[VIEW FULL DASHBOARD →]

## What's Working Well
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

✓ [Positive metric 1]
✓ [Positive metric 2]

## Opportunities to Explore
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

→ [Recommendation 1]
→ [Recommendation 2]

[SEE ALL RECOMMENDATIONS →]

## What's New
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

🆕 [New feature relevant to them]
📚 [Resource recommendation]

## Your Goals for Next Quarter
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

[SET YOUR GOALS →]

---

Questions? Reply to this email or [book office hours].

Your Customer Success Team

Automation Workflow: Pre-QBR

## Automated Pre-QBR Workflow

TRIGGER: QBR scheduled (T-14 days)

T-14: DATA PULL
├── Automatically pull usage metrics
├── Pull support ticket data
├── Pull health score history
├── Pull NPS/CSAT data
└── Stage data in prep document

T-10: CUSTOMER INPUT REQUEST
├── Send automated survey
├── Request agenda input
├── Confirm attendees
└── Track response

T-7: PREP REMINDER (CSM)
├── Alert CSM to begin prep
├── Provide data summary
├── Link to templates
└── Checklist of tasks

T-3: SLIDE DRAFT
├── Auto-populate data slides
├── Pull in charts and graphs
├── Leave narrative sections for CSM
└── Flag missing data

T-2: CUSTOMER REMINDER
├── Send meeting reminder
├── Attach agenda
├── Confirm logistics
└── Final attendee check

T-1: FINAL PREP CHECKLIST
├── Remind CSM to finalize
├── Ensure materials ready
├── Confirm tech setup
└── Last chance to add notes

Automation Workflow: Post-QBR

## Automated Post-QBR Workflow

TRIGGER: QBR completed (marked in system)

T+0 (Same Day): TASK CREATION
├── Create action items in project system
├── Assign owners
├── Set due dates
├── Link to QBR record

T+1: SUMMARY REMINDER
├── If summary not sent, remind CSM
├── Provide template
├── Escalate if needed

T+2: SATISFACTION SURVEY
├── Send post-QBR survey
├── Track response
├── Alert on low scores

T+7: FIRST CHECK-IN REMINDER
├── Remind CSM to check on actions
├── Status update request
└── Flag overdue items

T+14: PROGRESS UPDATE
├── Automated action status report
├── Highlight blockers
├── Escalate overdue items

T-14 (Before Next QBR): PRE-QBR CYCLE BEGINS
└── Start automation for next QBR

QBR Preparation Checklist (Automated)

## Auto-Generated QBR Prep Checklist

□ Data Gathering (Auto-populated)
  □ Usage metrics pulled ✓ [Link]
  □ Health score data ✓ [Link]
  □ Support history ✓ [Link]
  □ NPS/CSAT scores ✓ [Link]
  □ Financial data ✓ [Link]

□ Customer Input (Auto-tracked)
  □ Pre-QBR survey sent ✓ [Date]
  □ Survey completed: [Yes/No]
  □ Agenda confirmed: [Yes/No]
  □ Attendees confirmed: [List]

□ Presentation (Auto-generated)
  □ Deck template created ✓ [Link]
  □ Data slides populated ✓
  □ Manual sections needed: [List]

□ CSM Tasks (Manual required)
  □ Executive research completed
  □ Value narrative drafted
  □ Pre-QBR call scheduled
  □ Internal review completed

□ Logistics (Auto-confirmed)
  □ Meeting scheduled ✓ [Date/Time]
  □ Calendar invites sent ✓
  □ Video link included ✓
  □ Reminder scheduled ✓

Template Customization Guide

Efficiency Metrics

Automation Tools by Category

Anti-Patterns

• Over-automation — Automating relationship-critical elements
• Template rigidity — No customization for unique situations
• Data-without-insight — Auto-populating numbers without narrative
• Impersonal digital QBRs — Generic emails, no personalization
• Automation-as-excuse — "The system sent it" mentality
• No quality check — Auto-generated content sent without review
• Tool overload — Too many tools, no integration
• Segment mismatch — Using tech-touch for strategic accounts

title: Meeting Facilitation Techniques impact: MEDIUM-HIGH tags: facilitation, executive, engagement, conversation, presentation

Meeting Facilitation Techniques

Impact: MEDIUM-HIGH

A QBR is a conversation, not a presentation. The best CSMs facilitate strategic dialogue that leaves executives feeling heard, informed, and confident. Facilitation skills separate good QBRs from great ones — and often determine whether you get the next one.

QBR Facilitation Principles

┌─────────────────────────────────────────────────────────────────┐
│                   FACILITATION PRINCIPLES                        │
├─────────────────────────────────────────────────────────────────┤
│  1. LISTEN MORE THAN TALK                                        │
│     Target: Customer speaks 40-50% of time                       │
├─────────────────────────────────────────────────────────────────┤
│  2. QUESTIONS OVER STATEMENTS                                    │
│     Lead with inquiry, follow with information                   │
├─────────────────────────────────────────────────────────────────┤
│  3. FLEXIBLE WITHIN STRUCTURE                                    │
│     Have an agenda, but follow the conversation                  │
├─────────────────────────────────────────────────────────────────┤
│  4. EVERY MINUTE MUST EARN ITS PLACE                            │
│     Executive time is precious — make it count                   │
├─────────────────────────────────────────────────────────────────┤
│  5. END WITH ACTION, NOT INFORMATION                            │
│     Close with commitments, not just insights                    │
└─────────────────────────────────────────────────────────────────┘

Time Allocation Guide

Good Facilitation Practices

✓ Open with alignment
  → "Before we dive in, I want to make sure we cover
     what's most important to you..."
  → Confirm agenda matches their needs
  → Be willing to adjust on the fly

✓ Ask, then tell
  → "How are you feeling about X?"
  → Listen to their perspective
  → THEN share your data/insights

✓ Create space for honesty
  → "I'd really value your candid feedback..."
  → Don't interrupt or get defensive
  → Thank them for directness

✓ Summarize and confirm
  → "What I'm hearing is..."
  → Ensure understanding
  → Give them chance to correct

✓ Manage time actively
  → "We have 10 minutes on this topic..."
  → Keep energy high, move efficiently
  → Don't let one topic consume all time

✓ End with clear commitments
  → "So our next steps are..."
  → Named owners, specific dates
  → Mutual accountability

Bad Facilitation Practices

✗ Monologue mode
  → CSM talks for 50 straight minutes
  → Customer barely speaks
  → Not a conversation, a lecture

✗ Rigid agenda adherence
  → "We need to stay on agenda"
  → Customer wants to discuss something else
  → Misses what matters to them

✗ Death by PowerPoint
  → Click through 50 slides
  → Reading slides aloud
  → No discussion, no engagement

✗ Question dodging
  → Deflecting difficult questions
  → "Let me get back to you on that"
  → Erodes confidence

✗ Time blindness
  → Running over scheduled time
  → Executive leaves early
  → Rushing key topics at end

✗ Weak closing
  → "Any questions?"
  → No clear next steps
  → Meeting ends without commitments

Opening Techniques

## Strong QBR Openings

ALIGNMENT OPENER
"Thanks for making time for our quarterly review. Before we
dive in, I want to make sure we focus on what matters most
to you. Looking at our agenda, is there anything you'd like
to prioritize or add?"

HEADLINE OPENER
"I have three key things I want you to take away from today:
[one], [two], and [three]. Does that align with what you're
hoping to discuss?"

CUSTOMER-FIRST OPENER
"Before I share anything, I'd love to hear what's top of
mind for you. What's been happening since we last met?"

CELEBRATION OPENER
"I want to start by celebrating — [specific achievement].
Congratulations to you and your team."

AVOID
✗ "Let me just share my screen and we'll get started..."
✗ Starting without confirming attendees/agenda
✗ Jumping into slides without context

Asking Powerful Questions

Handling Difficult Conversations

## When Customer Raises a Problem

1. ACKNOWLEDGE
   "I hear you, and that's a valid concern..."
   Don't minimize or dismiss

2. UNDERSTAND
   "Help me understand more about the impact..."
   Get full picture before responding

3. OWN (if appropriate)
   "We could have done better on that..."
   Take accountability where warranted

4. SOLVE
   "Here's what I propose we do..."
   Move to action quickly

5. CONFIRM
   "Does that address your concern?"
   Ensure resolution

## Example
Customer: "The last release broke our workflow and cost us two days."

CSM: "I'm really sorry that happened — that's not the experience
we want you to have. Can you tell me more about what broke and
the impact on your team?

[Listen fully]

Thank you for sharing that. You're right to be frustrated.
Here's what I want to do: I'll escalate this to our product
team today and get you a detailed response by Friday. I also
want to understand if there's anything we can do to prevent
this in the future. Would a pre-release preview help?

Does that work for you?"

Managing Different Personalities

Time Management Techniques

## Keeping QBR On Track

BEFORE
- Set clear agenda with time allocations
- Share agenda in advance
- Plan for 10% buffer time

DURING
- Announce time checks: "We have 10 minutes on this..."
- Watch for tangents: "That's important — let's note it
  and circle back if we have time..."
- Use parking lot: "Let's capture that for follow-up..."

IF RUNNING OVER
- Acknowledge: "We're running a bit behind..."
- Prioritize: "The most important thing to cover is..."
- Offer follow-up: "Can we schedule 20 minutes to finish
  this discussion?"

IF RUNNING SHORT
- Use time wisely: "We have extra time — anything else
  you'd like to discuss?"
- Don't fill with slides
- End early if appropriate (executives love this)

Engagement Techniques

Closing Techniques

## Strong QBR Closings

ACTION SUMMARY
"Let me recap what we've committed to:
- [You/Customer] will [action] by [date]
- [I/CSM] will [action] by [date]
- Our next check-in is [date]
Does that capture everything?"

VALUE REINFORCEMENT
"Thank you for your time today. To summarize the value
we discussed: [key achievement]. Looking ahead, we're
focused on [next goal]. Any final questions?"

APPRECIATION + PREVIEW
"I really appreciate the open dialogue today. You'll
receive a summary within 24 hours. Our next QBR is
tentatively [date] — does that work?"

AVOID
✗ "Well, I guess that's it..."
✗ Trailing off without clear close
✗ Ending without action items
✗ Rushing the close due to time

Virtual QBR Best Practices

Anti-Patterns

• Monologue delivery — Talking at, not with customer
• Slide dependency — Reading from slides
• Question avoidance — Not asking, just telling
• Time blindness — Running over without awareness
• Weak close — No commitments, just "any questions?"
• Single-voice meeting — Not engaging all attendees
• Defensive posture — Arguing instead of understanding
• Virtual disengagement — Camera off, no interaction

title: Follow-up & Action Tracking impact: MEDIUM-HIGH tags: followup, actions, accountability, tracking, execution

Follow-up & Action Tracking

Impact: MEDIUM-HIGH

The QBR isn't over when the meeting ends — it's over when the actions are complete. Follow-up is where QBRs succeed or fail. 80% of QBR value is lost through poor follow-through. The best CSMs close the loop relentlessly.

Follow-up Timeline

┌─────────────────────────────────────────────────────────────────────────┐
│                      QBR FOLLOW-UP TIMELINE                              │
├─────────────────────────────────────────────────────────────────────────┤
│  DAY 0      QBR complete                                                 │
│  DAY 1      Summary email sent (within 24 hours)                        │
│  DAY 3      Internal debrief completed                                   │
│  WEEK 1     Quick actions completed, complex actions in progress        │
│  WEEK 2     Progress check-in with champion                             │
│  WEEK 4     Mid-quarter review of action items                          │
│  WEEK 8     Pre-QBR check on completion status                          │
│  WEEK 12    Next QBR — all actions should be complete or explained      │
└─────────────────────────────────────────────────────────────────────────┘

QBR Summary Email Template

Subject: [Company Name] Q[X] Business Review - Summary & Next Steps

Hi [Champion] and team,

Thank you for a productive quarterly review today. Here's a summary
of our discussion and the commitments we made.

## Key Takeaways
- [Main insight/outcome 1]
- [Main insight/outcome 2]
- [Main insight/outcome 3]

## Value Delivered This Quarter
- [Achievement 1]: [Impact/metric]
- [Achievement 2]: [Impact/metric]
- Total quarterly ROI: [XXX%]

## Agreed Action Items

### [Customer] Commitments
| # | Action | Owner | Due Date |
|---|--------|-------|----------|
| 1 | [Action] | [Name] | [Date] |
| 2 | [Action] | [Name] | [Date] |

### [Vendor] Commitments
| # | Action | Owner | Due Date |
|---|--------|-------|----------|
| 1 | [Action] | [Name] | [Date] |
| 2 | [Action] | [Name] | [Date] |

## Goals for Next Quarter
1. [Goal 1] — Success criteria: [Metric]
2. [Goal 2] — Success criteria: [Metric]

## Next Steps
- [Immediate next step]
- Our next check-in: [Date]
- Next QBR: [Tentative date]

## Resources
- [Link to presentation]
- [Link to success plan]
- [Other relevant resources]

Please let me know if I've missed anything or if you have questions.

Best,
[CSM Name]

Good Follow-up Practices

✓ Same-day summary
  → Send within 24 hours (ideally same day)
  → While details are fresh
  → Shows professionalism and commitment

✓ Clear action ownership
  → Named owner for every item
  → Both sides have commitments
  → Specific due dates, not "soon"

✓ Regular progress tracking
  → Weekly internal tracking
  → Bi-weekly customer check-ins
  → Visible progress updates

✓ Proactive communication
  → Don't wait for customer to ask
  → Provide updates before due dates
  → Flag blockers early

✓ Complete before next QBR
  → All actions resolved or explained
  → Demonstrate reliability
  → Build trust through execution

Bad Follow-up Practices

✗ Delayed or missing summary
  → Week later: "Sorry, been busy..."
  → Customer loses confidence
  → Details become fuzzy

✗ Vague action items
  → "Improve adoption"
  → "Follow up on that thing"
  → No clarity on what done looks like

✗ Unilateral commitments
  → All actions on vendor, none on customer
  → Or vice versa
  → Need mutual accountability

✗ Set and forget
  → Capture actions, never track
  → Arrive at next QBR with nothing done
  → Trust destroyed

✗ Silent failures
  → Miss deadlines without communication
  → Customer surprised by non-delivery
  → Always communicate early

Action Item Framework

## SMART Action Item Template

S - SPECIFIC
    What exactly will be done?
    "Schedule advanced training for analytics team"
    Not: "Provide training"

M - MEASURABLE
    How will we know it's done?
    "10 team members complete certification"
    Not: "Team is trained"

A - ASSIGNED
    Who is responsible?
    "[Name], with support from [Name]"
    Not: "The team"

R - RELEVANT
    Why does this matter?
    "To unlock Q4 adoption goals"
    Connected to outcomes

T - TIME-BOUND
    When is it due?
    "By [Specific Date]"
    Not: "ASAP" or "Q4"

Action Tracking System

Status Definitions

Progress Check-in Template

Subject: [Company] QBR Action Items - Progress Update

Hi [Champion],

Quick update on our action items from the Q[X] QBR:

## Completed ✓
- [Action 1]: Done on [date]. [Brief result]
- [Action 2]: Done on [date]. [Brief result]

## In Progress
- [Action 3]: On track for [date]. [Brief update]
- [Action 4]: [Update]. Need [any support from customer]

## Your Items
Just wanted to check in on:
- [Customer action 1]: Any update?
- [Customer action 2]: Is there anything you need from us?

Let me know if you have any questions or if anything has changed.

Talk soon,
[CSM Name]

Accountability Meeting Structure

## Monthly Action Review Call (15 minutes)

1. VENDOR UPDATES (5 min)
   - Status of our commitments
   - Any blockers or changes
   - Support needed from customer

2. CUSTOMER UPDATES (5 min)
   - Status of their commitments
   - Any challenges or blockers
   - Support needed from us

3. ADJUSTMENTS (3 min)
   - Reprioritize if needed
   - Adjust timelines if necessary
   - Add new items

4. NEXT CHECK-IN (2 min)
   - Confirm next meeting
   - Immediate next steps

Handling Incomplete Actions

## When Actions Aren't Done

VENDOR ACTIONS NOT COMPLETE

1. Communicate Early
   "I wanted to let you know we're behind on [action].
   Here's why and here's our new plan..."

2. Own the Miss
   Don't make excuses
   Acknowledge impact on customer

3. Provide New Commitment
   Specific new date
   Additional resources if needed

4. Document for QBR
   Be transparent about what happened
   Show corrective actions

CUSTOMER ACTIONS NOT COMPLETE

1. Inquire, Don't Accuse
   "How's [action] progressing?"
   "Is there anything blocking you?"

2. Understand the Barrier
   Resource constraints?
   Priority shift?
   Need help?

3. Offer Support
   "Would it help if we...?"
   "Can I provide anything to make this easier?"

4. Adjust if Needed
   Maybe the action wasn't realistic
   Revise and recommit

QBR Action Tracking Dashboard

## [Customer Name] - QBR Action Status

### Q[X] QBR Actions (Total: X)
| Status | Count | % |
|--------|-------|---|
| Complete | X | XX% |
| In Progress | X | XX% |
| Blocked | X | XX% |
| Overdue | X | XX% |
| Not Started | X | XX% |

### Overdue Items (Needs Attention)
| Action | Owner | Original Due | Days Overdue |
|--------|-------|--------------|--------------|
| [Action] | [Name] | [Date] | X |

### At Risk Items
| Action | Owner | Due | Risk Reason |
|--------|-------|-----|-------------|
| [Action] | [Name] | [Date] | [Reason] |

### Completed Since Last Review
| Action | Owner | Completed | Outcome |
|--------|-------|-----------|---------|
| [Action] | [Name] | [Date] | [Result] |

Pre-Next-QBR Review

## Pre-QBR Action Review Checklist

□ All Actions Reviewed
  □ Status updated for all items
  □ Completed items documented
  □ Incomplete items have explanations

□ Outstanding Items
  □ Path to completion clear
  □ New realistic due dates set
  □ Blockers identified and addressed

□ Ready for QBR Discussion
  □ Summary of completions ready
  □ Explanation for misses ready
  □ Learning/improvements identified

□ New Actions Prepared
  □ Carried forward items listed
  □ New proposed actions drafted
  □ Resource requirements clear

Follow-up Metrics

Anti-Patterns

• Summary delay — Sending summary a week later
• Vague actions — "Follow up on things"
• No tracking system — Actions captured but not managed
• One-sided accountability — Only vendor or customer has actions
• Silent failures — Missing deadlines without communication
• Same actions every QBR — Never complete, always carry forward
• No check-ins — Wait until next QBR to review progress
• Blame shifting — Customer didn't do their part (as excuse)

title: Success Metrics Presentation impact: HIGH tags: metrics, benchmarking, dashboard, visualization, performance

Success Metrics Presentation

Impact: HIGH

Metrics tell your story, but only if you tell them right. Executives are drowning in data — your job is to surface the metrics that matter and present them in a way that drives understanding and action. 10 meaningful metrics beats 100 data points.

The Metrics Hierarchy for QBRs

┌─────────────────────────────────────────────────────────────────┐
│  LEVEL 1: BUSINESS OUTCOMES (Show first)                        │
│  Revenue impact, cost savings, strategic goals achieved         │
├─────────────────────────────────────────────────────────────────┤
│  LEVEL 2: LEADING INDICATORS (Show second)                      │
│  Health score, adoption trends, engagement patterns             │
├─────────────────────────────────────────────────────────────────┤
│  LEVEL 3: OPERATIONAL METRICS (Reference/appendix)              │
│  Usage data, support tickets, feature adoption                  │
├─────────────────────────────────────────────────────────────────┤
│  LEVEL 4: TECHNICAL METRICS (Only if asked)                     │
│  Uptime, performance, API calls                                 │
└─────────────────────────────────────────────────────────────────┘

Metrics Selection by Executive Level

Good Metrics Presentation

✓ Context before numbers
  → "Your goal was to reduce churn by 20%..."
  → "Here's how you're tracking..."

✓ Trend over snapshot
  → Show 4 quarters, not just this quarter
  → Progress and trajectory matter

✓ Benchmark when relevant
  → "You're in the top 20% of similar companies"
  → Peer comparison adds context

✓ Story, not spreadsheet
  → Lead with insight: "Here's what the data tells us..."
  → Numbers support the narrative

✓ Visual hierarchy
  → Most important metrics largest/first
  → Supporting data smaller/secondary
  → Technical data in appendix

✓ Call out the "so what"
  → "This 15% improvement means $200K in savings"
  → Always translate to impact

Bad Metrics Presentation

✗ Data dump approach
  → 50 slides of usage charts
  → No hierarchy or prioritization
  → Executive eyes glaze over

✗ Vanity metrics first
  → "You had 14,523 logins!"
  → "278 API calls this month!"
  → Impressive numbers, zero insight

✗ Snapshot without trend
  → "Your adoption is 67%"
  → Is that up? Down? Good? Bad?
  → No context = no meaning

✗ Technical audience assumption
  → Deep performance metrics for business execs
  → API response times for the CEO
  → Know your audience

✗ Numbers without narrative
  → Slide after slide of charts
  → No interpretation or insight
  → Customer left to figure it out

Metrics Dashboard Structure

## QBR Metrics Dashboard Layout

┌────────────────────────────────────────────────────────────────┐
│                      EXECUTIVE SUMMARY                          │
│  Overall Health: 🟢 85/100    Trend: ↑ +7 vs last quarter      │
├────────────────────────────────────────────────────────────────┤
│  VALUE DELIVERED                                                │
│  ┌──────────────┐ ┌──────────────┐ ┌──────────────┐            │
│  │ ROI: 340%    │ │ Savings:     │ │ Revenue:     │            │
│  │ ↑ from 280%  │ │ $125,000     │ │ $450,000     │            │
│  └──────────────┘ └──────────────┘ └──────────────┘            │
├────────────────────────────────────────────────────────────────┤
│  ADOPTION & ENGAGEMENT                                          │
│  ┌──────────────────────────────┐  ┌────────────────────────┐  │
│  │ User Adoption Trend          │  │ Feature Adoption       │  │
│  │ [Line chart: 4 quarters]     │  │ [Bar chart: top 5]     │  │
│  └──────────────────────────────┘  └────────────────────────┘  │
├────────────────────────────────────────────────────────────────┤
│  CUSTOMER HEALTH INDICATORS                                     │
│  ┌────────┐ ┌────────┐ ┌────────┐ ┌────────┐ ┌────────┐       │
│  │Adoption│ │Engage- │ │Support │ │Senti-  │ │Growth  │       │
│  │  85%   │ │ment 72 │ │Health  │ │ment    │ │Pot.    │       │
│  │   ↑    │ │   ↑    │ │  🟢    │ │  🟢    │ │ High   │       │
│  └────────┘ └────────┘ └────────┘ └────────┘ └────────┘       │
└────────────────────────────────────────────────────────────────┘

Key QBR Metrics Reference

Benchmarking Framework

Benchmark Presentation Examples

## Effective Benchmark Framing

✓ Positive framing with aspiration:
  "Your adoption rate of 78% puts you in the top quartile.
   Our most successful customers typically hit 85%+,
   which is within reach with these three actions..."

✓ Honest with path forward:
  "Your current engagement score of 62 is below the
   benchmark of 70. However, I've seen similar customers
   improve 15+ points in one quarter by focusing on..."

✗ Negative comparison without help:
  "You're below benchmark."
  (No context, no path forward, just bad news)

✗ Manipulative benchmarking:
  "You're in the top 5%!" (of a cherry-picked metric)
  (Loses credibility when customer investigates)

Data Visualization Best Practices

Executive Summary Metrics Slide

## [Customer Name] Q[X] Performance Summary

### Overall Health: 🟢 85/100 (↑7 from Q[X-1])

### Key Metrics at a Glance
| Metric | Current | Trend | Target | Status |
|--------|---------|-------|--------|--------|
| User Adoption | 78% | ↑ +8% | 80% | 🟢 |
| Feature Adoption | 72% | ↑ +5% | 75% | 🟡 |
| Time Savings | 450 hrs | ↑ +22% | 400 hrs | 🟢 |
| NPS | 52 | ↑ +8 | 50 | 🟢 |
| Support Health | Good | ↑ | Good | 🟢 |

### Value Snapshot
- **Quarterly Value Delivered:** $187,000
- **Quarterly ROI:** 374%
- **Year-to-Date Value:** $543,000

### Key Insight
"Adoption accelerated significantly this quarter following
the advanced workflow training. You're now positioned to
capture an additional $75K in value by expanding to the
Analytics team in Q[X+1]."

Metrics Storytelling Sequence

## Presenting Metrics Effectively

1. SET CONTEXT
   "Your goal this quarter was to improve team efficiency..."

2. PRESENT THE HEADLINE
   "You exceeded that goal — here's the summary..."
   [Show executive summary metrics]

3. TELL THE STORY
   "Here's what drove this improvement..."
   [Walk through supporting metrics]

4. HIGHLIGHT BRIGHT SPOTS
   "Particularly impressive was..."
   [Celebrate specific achievements]

5. ADDRESS GAPS
   "We're not quite where we want to be on..."
   [Acknowledge areas for improvement]

6. CONNECT TO NEXT STEPS
   "To build on this momentum..."
   [Bridge to action planning]

Metrics Appendix Structure

## Appendix: Detailed Metrics

### A. Adoption Deep Dive
[Detailed adoption charts and breakdowns]

### B. Usage Analytics
[Feature-by-feature usage data]

### C. Support Metrics
[Ticket analysis, resolution times]

### D. Technical Performance
[Uptime, response times, API metrics]

### E. Historical Comparison
[Multi-quarter trend data]

### F. Methodology Notes
[How metrics are calculated]

Common Metrics Mistakes

Anti-Patterns

• Metric overload — Drowning executives in data
• Vanity metric focus — Logins over outcomes
• Snapshot syndrome — No trends or context
• Cherry-picking — Showing only good news
• Technical metrics for executives — API calls for the CEO
• No benchmarks — Numbers without reference points
• Missing the "so what" — Data without insight
• Inconsistent presentation — Different format each QBR

title: Strategic Account Planning impact: HIGH tags: planning, strategy, success-plan, goals, growth

Strategic Account Planning

Impact: HIGH

The QBR is the premier moment for strategic account planning. It's where you align on goals, co-create the path forward, and secure commitment to mutual success. A QBR without a forward-looking plan is just a history lesson.

Strategic Planning Framework

┌─────────────────────────────────────────────────────────────────────────┐
│                  STRATEGIC ACCOUNT PLANNING LAYERS                       │
├─────────────────────────────────────────────────────────────────────────┤
│  VISION        Where does customer want to be in 1-3 years?             │
│                ↓                                                         │
│  OBJECTIVES    What must they achieve this year to reach vision?        │
│                ↓                                                         │
│  STRATEGIES    How will they pursue those objectives?                    │
│                ↓                                                         │
│  INITIATIVES   What specific projects will they execute?                 │
│                ↓                                                         │
│  OUR ROLE      How do we enable each initiative?                        │
└─────────────────────────────────────────────────────────────────────────┘

Success Plan Structure

## [Customer Name] Success Plan

### Account Summary
| Attribute | Value |
|-----------|-------|
| ARR | $XXX,XXX |
| Contract Term | [Start] - [End] |
| Primary Contact | [Name], [Title] |
| Executive Sponsor | [Name], [Title] |
| CSM | [Name] |
| Health Score | XX/100 |

### Customer Vision
"[Customer's aspirational statement about where they want to be]"

### Annual Objectives
| # | Objective | Metric | Target | Status |
|---|-----------|--------|--------|--------|
| 1 | [Objective] | [Metric] | [Target] | 🟢/🟡/🔴 |
| 2 | [Objective] | [Metric] | [Target] | 🟢/🟡/🔴 |
| 3 | [Objective] | [Metric] | [Target] | 🟢/🟡/🔴 |

### Quarterly Goals (Current Quarter)
| Goal | Success Criteria | Owner | Due | Progress |
|------|------------------|-------|-----|----------|
| [Goal 1] | [Criteria] | [Owner] | [Date] | XX% |
| [Goal 2] | [Criteria] | [Owner] | [Date] | XX% |
| [Goal 3] | [Criteria] | [Owner] | [Date] | XX% |

### Value Realization Targets
| Value Area | Baseline | Target | Current | Gap |
|------------|----------|--------|---------|-----|
| [Area 1] | [X] | [Y] | [Z] | [±] |
| [Area 2] | [X] | [Y] | [Z] | [±] |

### Expansion Roadmap
| Phase | Use Case | Teams/Users | Timeline | ARR Potential |
|-------|----------|-------------|----------|---------------|
| Current | [Use case] | [Teams] | Live | $XXX,XXX |
| Phase 2 | [Use case] | [Teams] | Q[X] | $XX,XXX |
| Phase 3 | [Use case] | [Teams] | Q[X] | $XX,XXX |

### Risk Factors
| Risk | Probability | Impact | Mitigation |
|------|-------------|--------|------------|
| [Risk 1] | H/M/L | H/M/L | [Action] |
| [Risk 2] | H/M/L | H/M/L | [Action] |

### Key Milestones (Next 12 Months)
| Milestone | Target Date | Dependencies | Owner |
|-----------|-------------|--------------|-------|
| [Milestone 1] | [Date] | [Deps] | [Owner] |
| [Milestone 2] | [Date] | [Deps] | [Owner] |

Good Strategic Planning

✓ Customer-driven objectives
  → "What are YOUR goals for next quarter?"
  → Their strategy, not your quota
  → Aligned to their business priorities

✓ Measurable success criteria
  → "We'll know we've succeeded when..."
  → Specific, quantifiable targets
  → Agreed upon jointly

✓ Mutual accountability
  → Customer actions + Vendor actions
  → Named owners on both sides
  → Regular progress checkpoints

✓ Multi-horizon view
  → This quarter's goals
  → This year's objectives
  → Long-term vision alignment

✓ Documented and shared
  → Written success plan
  → Accessible to all stakeholders
  → Updated each QBR

✓ Connected to value
  → Goals tied to outcomes
  → Success = business impact
  → Not just feature adoption

Bad Strategic Planning

✗ Vendor-driven agenda
  → "Here's what WE want you to do next quarter"
  → Pushing features they don't need
  → Sales quota disguised as planning

✗ Vague objectives
  → "Improve adoption"
  → "Increase usage"
  → No measurable criteria

✗ One-sided planning
  → All customer actions, no vendor commitments
  → Or all vendor promises, no customer investment

✗ Absent documentation
  → Plans discussed but not written
  → Lost by next QBR
  → No accountability

✗ Disconnected from business
  → Feature goals, not business outcomes
  → "Use X feature" vs "Achieve Y result"

✗ Static plans
  → Same plan quarter after quarter
  → No adaptation to changing needs

Goal-Setting Framework for QBRs

Strategic Conversation Questions

## Discovery Questions for Planning

VISION & DIRECTION
- "What's your team's/company's vision for the next 12-24 months?"
- "What major initiatives are on the roadmap?"
- "How does our solution fit into that vision?"

PRIORITIES
- "What are your top 3 priorities for next quarter?"
- "What would make this quarter a success for you?"
- "What's keeping you up at night?"

CHALLENGES
- "What obstacles do you see to achieving these goals?"
- "Where are the current gaps we should address?"
- "What's been harder than expected?"

EXPANSION
- "Are there other teams that could benefit from similar outcomes?"
- "What adjacent problems are you trying to solve?"
- "How do you see our partnership evolving?"

VALUE
- "How do you measure success for this investment?"
- "What would make the ROI undeniable?"
- "What would justify expanding our partnership?"

Quarterly Planning Session Structure

## QBR Planning Section (20 minutes)

1. REFLECT (5 min)
   - Review last quarter's goals
   - Assess completion and blockers
   - Celebrate achievements

2. DISCOVER (5 min)
   - Customer shares upcoming priorities
   - New initiatives or challenges
   - Changing business context

3. ALIGN (5 min)
   - Connect priorities to capabilities
   - Identify mutual opportunities
   - Propose focus areas

4. COMMIT (5 min)
   - Define 2-3 specific goals
   - Assign owners (both sides)
   - Set check-in cadence

Account Growth Planning

## Account Growth Assessment

### Current State
| Dimension | Status | Notes |
|-----------|--------|-------|
| Users Licensed | XXX | |
| Users Active | XXX (XX%) | |
| Use Cases Live | X of Y | |
| Products/Modules | X of Y | |
| Departments | X of Y | |

### Whitespace Analysis
| Opportunity | Description | Potential | Timeline |
|-------------|-------------|-----------|----------|
| User expansion | Add XXX users in [Dept] | $XX,XXX | Q[X] |
| Use case expansion | Add [Use Case] | $XX,XXX | Q[X] |
| Product upsell | Add [Module] | $XX,XXX | Q[X] |
| Geographic expansion | Expand to [Region] | $XX,XXX | Q[X] |

### Growth Blockers
| Blocker | Description | Resolution Path |
|---------|-------------|-----------------|
| [Blocker 1] | [Description] | [Path] |
| [Blocker 2] | [Description] | [Path] |

### Growth Plan
| Phase | Action | Owner | Date | ARR Impact |
|-------|--------|-------|------|------------|
| Phase 1 | [Action] | [Owner] | [Date] | $XX,XXX |
| Phase 2 | [Action] | [Owner] | [Date] | $XX,XXX |

Success Plan Review Checklist

□ Success Plan Elements
  □ Customer vision documented
  □ Annual objectives defined
  □ Quarterly goals established
  □ Success criteria measurable
  □ Owners assigned (both sides)
  □ Timeline clear
  □ Risks identified
  □ Value targets set

□ Plan Quality Check
  □ Goals are customer-driven
  □ Objectives are SMART
  □ Plan connects to business outcomes
  □ Mutual accountability exists
  □ Review cadence established

□ Stakeholder Alignment
  □ Champion reviewed and approved
  □ Executive sponsor aware
  □ Key stakeholders informed
  □ Internal team aligned

Connecting Plan to Renewal

Anti-Patterns

• Vendor-centric planning — Your goals, not theirs
• Vague objectives — "Improve" without measurement
• Undocumented plans — Verbal agreements that vanish
• Static planning — Same plan every quarter
• Feature-focused goals — Adoption over outcomes
• One-sided accountability — Only customer has actions
• Disconnected from business — Technical goals, not business impact
• Absent expansion vision — No growth roadmap

title: Executive Preparation impact: CRITICAL tags: preparation, executive, research, briefing, pre-meeting

Executive Preparation

Impact: CRITICAL

Preparation is 80% of QBR success. Walking into an executive meeting without thorough preparation is disrespectful of their time and destructive to your credibility. The best CSMs spend 4-6 hours preparing for a strategic QBR.

QBR Preparation Timeline

┌─────────────────────────────────────────────────────────────────────────┐
│                   QBR PREPARATION TIMELINE                              │
├─────────────────────────────────────────────────────────────────────────┤
│  T-14 DAYS    Schedule confirmed, preparation begins                    │
│  T-10 DAYS    Customer input request sent                               │
│  T-7 DAYS     Data gathering, stakeholder research                      │
│  T-5 DAYS     Draft presentation created                                │
│  T-3 DAYS     Internal review completed                                 │
│  T-2 DAYS     Pre-QBR call with customer champion                       │
│  T-1 DAY      Final materials sent, logistics confirmed                 │
│  DAY 0        QBR execution                                             │
│  T+1 DAY      Follow-up summary sent                                    │
│  T+7 DAYS     Action tracking begins                                    │
└─────────────────────────────────────────────────────────────────────────┘

Executive Research Checklist

## Pre-QBR Executive Research

□ Company Intelligence
  □ Recent earnings calls/reports
  □ Press releases (last 90 days)
  □ Executive changes
  □ M&A activity
  □ Strategic initiatives announced
  □ Competitor landscape changes

□ Stakeholder Research
  □ LinkedIn profiles reviewed
  □ Recent posts/articles
  □ Speaking engagements
  □ Background/career history
  □ Communication preferences known

□ Account Intelligence
  □ Health score trends
  □ Support ticket themes
  □ Usage analytics
  □ NPS/CSAT scores
  □ Champion sentiment
  □ Open opportunities/risks

□ Relationship Intelligence
  □ Last QBR outcomes/actions
  □ Recent interactions logged
  □ Stakeholder changes
  □ Org chart current
  □ Decision-maker mapping

Good QBR Preparation

✓ Deep customer research
  → Know their recent news, earnings, strategy
  → Understand market pressures they face
  → Connect your value to their priorities
  → Reference specific business context

✓ Stakeholder-specific preparation
  → Research each attendee's background
  → Understand their role and interests
  → Prepare relevant talking points per person
  → Anticipate their questions

✓ Data-driven content
  → Pull usage and adoption metrics
  → Calculate ROI with their numbers
  → Benchmark against peers/industry
  → Trend analysis over time

✓ Pre-alignment with champion
  → Validate agenda and content
  → Understand current priorities
  → Identify sensitive topics
  → Confirm attendee dynamics

✓ Rehearsal and review
  → Practice presentation flow
  → Internal review for quality
  → Anticipate tough questions
  → Prepare contingency content

Bad QBR Preparation

✗ Minimal research
  → "I'll just wing the customer context"
  → Generic industry talking points
  → No awareness of recent news

✗ Stale data
  → Using data from last quarter
  → No current usage metrics
  → Outdated success metrics

✗ No pre-alignment
  → Surprising champion with content
  → Missing political landmines
  → Misaligned priorities

✗ Last-minute scramble
  → Building deck morning of QBR
  → No internal review
  → Rushing data gathering

✗ One-size-fits-all content
  → Same slides regardless of attendees
  → No role-specific preparation
  → Ignoring audience composition

Executive Briefing Document Template

## Executive Briefing: [Customer Name] QBR
**Date:** [Date]
**Prepared by:** [CSM Name]
**Internal Review:** [Manager Name]

### Account Overview
| Attribute | Value |
|-----------|-------|
| ARR | $XXX |
| Contract End | [Date] |
| Health Score | XX/100 |
| NPS | XX |
| Segment | Enterprise/Strategic |
| CSM Tenure | X months |

### Executive Attendees
| Name | Title | Background | Key Interests | Prep Notes |
|------|-------|------------|---------------|------------|
| [Name] | [Title] | [Brief bio] | [Priorities] | [Talking points] |

### Business Context
**Recent Company News:**
- [Key development 1]
- [Key development 2]

**Strategic Priorities (from research):**
- [Priority 1]
- [Priority 2]

**Market/Competitive Pressures:**
- [Pressure 1]
- [Pressure 2]

### Account Health Summary
| Dimension | Status | Trend | Notes |
|-----------|--------|-------|-------|
| Adoption | 🟢/🟡/🔴 | ↑/→/↓ | [Notes] |
| Engagement | 🟢/🟡/🔴 | ↑/→/↓ | [Notes] |
| Sentiment | 🟢/🟡/🔴 | ↑/→/↓ | [Notes] |
| Support | 🟢/🟡/🔴 | ↑/→/↓ | [Notes] |
| Renewal Risk | Low/Med/High | — | [Notes] |

### Value Delivered
| Metric | Baseline | Current | Impact |
|--------|----------|---------|--------|
| [Metric 1] | [X] | [Y] | [Z improvement] |
| [Metric 2] | [X] | [Y] | [Z improvement] |

### Risks & Opportunities
**Risks to Address:**
- [Risk 1]: Mitigation plan
- [Risk 2]: Mitigation plan

**Opportunities to Explore:**
- [Opportunity 1]: Approach
- [Opportunity 2]: Approach

### QBR Objectives
1. [Primary objective]
2. [Secondary objective]
3. [Tertiary objective]

### Anticipated Questions/Concerns
| Question | Prepared Response |
|----------|-------------------|
| [Expected question 1] | [Response strategy] |
| [Expected question 2] | [Response strategy] |

### Talking Points by Stakeholder
**For [Executive Sponsor]:**
- Point 1 (connects to their priority)
- Point 2

**For [Champion]:**
- Point 1
- Point 2

Pre-QBR Customer Input Request

## Pre-QBR Input Request Email

Subject: Preparing for Our [Q#] Business Review - Your Input Requested

Hi [Champion],

I'm preparing for our upcoming Quarterly Business Review on [Date]
and want to ensure we cover what matters most to you and your team.

Could you take 5 minutes to share:

1. **Top priorities for next quarter**
   What are the 2-3 most important initiatives for your team?

2. **Successes to highlight**
   What wins would you like to showcase to leadership?

3. **Challenges to address**
   Any obstacles or concerns we should discuss?

4. **Questions for us**
   Topics you'd like us to cover or questions for our team?

5. **Attendee updates**
   Any changes to who should attend?

Your input helps us create a more valuable discussion focused on
your priorities, not just our metrics.

I'll also schedule a 15-minute pre-QBR call next week to align on
the agenda. Please suggest a few times that work.

Thanks,
[CSM Name]

Data Gathering Checklist

Pre-QBR Champion Alignment Call

## Pre-QBR Alignment Call Agenda (15-20 minutes)

1. QBR Objectives (3 min)
   - What do you want to accomplish?
   - What would make this a success?

2. Agenda Review (5 min)
   - Walk through proposed agenda
   - Adjust based on feedback
   - Confirm time allocation

3. Content Preview (5 min)
   - Key data points to present
   - Value story highlights
   - Any concerns about content?

4. Attendee Dynamics (3 min)
   - Who's attending and their mood?
   - Any sensitive topics to avoid?
   - Decision-making dynamics?

5. Logistics Confirmation (2 min)
   - Time, location, tech setup
   - Materials distribution plan

Preparation Time Guidelines

Anti-Patterns

• Winging it — "I know this customer well enough"
• Stale intelligence — Using last quarter's research
• Champion bypass — No pre-alignment call
• Data dump — Gathering data without analysis
• Last-minute prep — Morning-of preparation
• Generic content — No customization for audience
• Question avoidance — Not preparing for tough questions
• Solo preparation — No internal review or input

title: QBR Program Design impact: CRITICAL tags: program, cadence, governance, segmentation, executive-review

QBR Program Design

Impact: CRITICAL

A well-designed QBR program transforms routine customer check-ins into strategic partnership moments. The best QBR programs are segmented, scalable, and systematically drive business outcomes. 65% of customer executives say their vendor QBRs waste their time — be in the 35%.

QBR Program Architecture

┌────────────────────────────────────────────────────────────────────────┐
│                      QBR PROGRAM LAYERS                                 │
├────────────────────────────────────────────────────────────────────────┤
│  STRATEGIC    Executive alignment, business outcomes, partnership       │
├────────────────────────────────────────────────────────────────────────┤
│  GOVERNANCE   Cadence, escalation, review process, standards           │
├────────────────────────────────────────────────────────────────────────┤
│  OPERATIONAL  Preparation, execution, follow-up, tracking              │
├────────────────────────────────────────────────────────────────────────┤
│  TACTICAL     Templates, automation, content, scheduling               │
└────────────────────────────────────────────────────────────────────────┘

QBR Cadence by Segment

QBR vs EBR: When to Elevate

Good QBR Program Design

✓ Segmented approach
  → Different programs for different tiers
  → Strategic accounts get executive investment
  → SMB gets efficient, digital-first reviews
  → Resource allocation matches account value

✓ Clear governance
  → Defined cadence by segment
  → Escalation paths established
  → Quality standards documented
  → Executive sponsor program

✓ Systematic preparation
  → Standard timeline (2 weeks prep minimum)
  → Checklist-driven preparation
  → Data gathering automated where possible
  → Pre-QBR alignment call scheduled

✓ Customer-centric scheduling
  → Aligned to customer fiscal calendar
  → Avoids customer busy periods
  → Renewal timing considered
  → Multi-meeting approach for complex reviews

✓ Measured outcomes
  → QBR effectiveness tracked
  → Action completion rates monitored
  → Customer satisfaction surveyed
  → Continuous improvement applied

Bad QBR Program Design

✗ One-size-fits-all approach
  → Same 60-slide deck for $20K and $500K accounts
  → Identical cadence regardless of value
  → No executive involvement differentiation

✗ Internal-centric scheduling
  → "Let's schedule all QBRs in the last week of quarter"
  → Vendor convenience over customer needs
  → Rush through back-to-back reviews

✗ Reactive, not programmatic
  → QBRs only when customer complains
  → No established cadence
  → Ad hoc preparation

✗ No governance or standards
  → Every CSM does it differently
  → No quality baseline
  → No executive oversight

✗ Presentation over conversation
  → 90 minutes of vendor talking
  → No customer input designed in
  → PowerPoint theater

QBR Program Governance Framework

QBR Calendar Planning

## Annual QBR Calendar Template

Q1 (Jan-Mar)
├── Strategic Accounts: Jan-Feb (avoid fiscal year-end)
├── Enterprise: Feb-Mar (post-holiday)
├── Mid-Market: Feb (semi-annual cohort A)
└── SMB: Mar (annual reviews begin)

Q2 (Apr-Jun)
├── Strategic Accounts: Apr-May
├── Enterprise: Apr-May
├── Mid-Market: N/A (semi-annual)
└── SMB: Apr-May (annual cohort B)

Q3 (Jul-Sep)
├── Strategic Accounts: Jul-Aug (avoid summer vacations)
├── Enterprise: Aug-Sep
├── Mid-Market: Aug (semi-annual cohort A)
└── SMB: Sep (annual cohort C)

Q4 (Oct-Dec)
├── Strategic Accounts: Oct-Nov (pre-planning season)
├── Enterprise: Oct-Nov
├── Mid-Market: Nov (semi-annual cohort B)
└── SMB: Nov (annual cohort D)
└── Note: Avoid Dec for all segments

QBR Timing Considerations

QBR Program Metrics

QBR Program Maturity Assessment

## QBR Program Maturity Checklist

□ Level 1: Basic
  □ QBRs conducted for top accounts
  □ Basic template exists
  □ Ad hoc scheduling

□ Level 2: Standardized
  □ Defined cadence by segment
  □ Standard templates and process
  □ Preparation checklist used
  □ Follow-up tracking

□ Level 3: Optimized
  □ Automated preparation workflows
  □ Executive engagement program
  □ Quality assurance process
  □ Customer satisfaction measurement

□ Level 4: Strategic
  □ Predictive QBR prioritization
  □ Value realization integration
  □ Expansion correlation tracked
  □ Continuous optimization

Program Design Checklist

□ Segmentation
  □ Tiers defined with ARR thresholds
  □ Cadence established per tier
  □ Duration standards set
  □ Executive expectations defined

□ Governance
  □ Quality standards documented
  □ Review process established
  □ Escalation paths clear
  □ Training program in place

□ Operations
  □ Preparation timeline defined
  □ Templates created per segment
  □ Automation configured
  □ Follow-up process documented

□ Measurement
  □ Success metrics identified
  □ Tracking mechanisms in place
  □ Feedback collection enabled
  □ Improvement process established

Anti-Patterns

• Calendar cramming — All QBRs in last week of quarter
• Template tyranny — Same rigid deck regardless of context
• Executive absence — No leadership involvement in strategic accounts
• Measurement void — No tracking of QBR effectiveness
• Preparation vacuum — CSMs wing it without systematic prep
• Customer irrelevance — Vendor metrics, not customer outcomes
• Static program — No evolution based on feedback
• Inconsistent quality — Wild variation between CSMs

title: Risk & Opportunity Identification impact: HIGH tags: risk, opportunity, churn, expansion, signals

Risk & Opportunity Identification

Impact: HIGH

The QBR is both a diagnostic tool and a treatment opportunity. A skilled CSM uses the QBR to surface hidden risks before they become churn and uncover expansion opportunities before competitors do. The best QBRs save accounts and grow them.

Risk-Opportunity Matrix

              HIGH IMPACT
                   ↑
    ┌──────────────┼──────────────┐
    │   MONITOR    │   PRIORITY   │
    │   CLOSELY    │    ACTION    │
    │              │              │
    │  Track in    │  Address     │
    │  QBR, plan   │  in QBR,     │
    │  mitigation  │  immediate   │
    │              │  action      │
LOW ←──────────────┼──────────────→ HIGH
LIKELIHOOD         │              LIKELIHOOD
    │   WATCH &    │   PLAN &     │
    │   WAIT       │   PREPARE    │
    │              │              │
    │  Note for    │  Develop     │
    │  awareness   │  contingency │
    │              │              │
    └──────────────┼──────────────┘
                   ↓
              LOW IMPACT

Risk Categories

Risk Identification Framework

## CHURN Risk Assessment

C - CHAMPION
    □ Champion engaged and present?
    □ Champion's organizational standing?
    □ Backup relationships established?

H - HEALTH
    □ Health score trending up/down?
    □ Adoption metrics healthy?
    □ Support experience positive?

U - UTILIZATION
    □ Users active at expected level?
    □ Core features being used?
    □ Value being extracted?

R - RELATIONSHIP
    □ Regular engagement maintained?
    □ Sentiment positive?
    □ Communication responsive?

N - NEED
    □ Still solving original problem?
    □ Business priorities aligned?
    □ Use case still relevant?

Good Risk Discovery

✓ Proactive inquiry
  → Ask about potential issues before they surface
  → "What concerns do you have going forward?"
  → Create space for honest feedback

✓ Pattern recognition
  → Connect signals from data + conversation
  → Declining usage + vague responses = risk
  → Look for inconsistencies

✓ Safe space for honesty
  → "I'd rather hear the hard truth now..."
  → Don't get defensive
  → Thank them for candor

✓ Direct but diplomatic
  → "I noticed engagement has declined..."
  → Name what you see
  → Invite explanation

✓ Action-oriented response
  → Every risk needs a mitigation plan
  → "Here's what we'll do about that..."
  → Follow through visibly

Bad Risk Discovery

✗ Avoiding difficult topics
  → Pretending everything is fine
  → Skipping past declining metrics
  → Not asking about challenges

✗ Defensive reactions
  → "That's not our fault"
  → "Other customers love that feature"
  → Dismissing concerns

✗ Surprise reactions
  → Shocked by issues you should have seen
  → Not monitoring account health
  → Reactive, not proactive

✗ All talk, no action
  → Acknowledge risks, do nothing
  → Same issues QBR after QBR
  → Erodes trust completely

✗ Escalation avoidance
  → Hiding risks from leadership
  → Hoping problems resolve
  → Missing intervention window

Risk Signal Checklist

□ Pre-QBR Signals
  □ Usage trending down
  □ Key users inactive
  □ Support tickets increasing
  □ Response times slowing
  □ NPS/CSAT declining
  □ Contract coming up without expansion conversation

□ During-QBR Signals
  □ Executive not present (when usually are)
  □ Vague or evasive answers
  □ Short meeting, quick to end
  □ Discussing competitors
  □ Budget/cost concerns raised
  □ Champion seems disengaged
  □ New stakeholders questioning value
  □ Asking about cancellation/downgrade

□ Post-QBR Signals
  □ No response to follow-up
  □ Actions not completed
  □ Next QBR postponed/cancelled
  □ Contact goes silent

Risk Discovery Questions

Opportunity Categories

Opportunity Discovery Questions

## Expansion-Focused Questions

USER GROWTH
- "Are there teams we're not reaching yet?"
- "How many people could theoretically use this?"
- "What's blocking broader adoption?"

USE CASE EXPANSION
- "What's the next problem you're trying to solve?"
- "Are there adjacent workflows we should discuss?"
- "What would make this 2x more valuable?"

PRODUCT EXPANSION
- "Have you explored our [other product/module]?"
- "Would [capability] help with your goals?"
- "What's on your wish list?"

STRATEGIC GROWTH
- "How is the company growing this year?"
- "Any new initiatives that might need this?"
- "What does success look like in 3 years?"

Risk Mitigation Planning

## Risk Mitigation Template

### Risk: [Risk Description]
**Severity:** High/Medium/Low
**Likelihood:** High/Medium/Low
**Discovery Date:** [Date]
**Account Impact:** [ARR at risk]

### Root Cause Analysis
- Primary cause: [Description]
- Contributing factors: [List]
- How long has this been developing: [Timeline]

### Mitigation Actions
| Action | Owner | Due Date | Status |
|--------|-------|----------|--------|
| [Action 1] | [Name] | [Date] | Pending |
| [Action 2] | [Name] | [Date] | Pending |

### Escalation Plan
- If [trigger], escalate to [person]
- Internal resources available: [List]
- External support needed: [List]

### Success Criteria
- Risk considered mitigated when: [Criteria]
- Check-in dates: [Dates]

### Contingency Plan
- If mitigation fails: [Plan B]

Opportunity Development Planning

## Opportunity Template

### Opportunity: [Description]
**Type:** Expansion/Upsell/Advocacy
**Potential ARR:** $XX,XXX
**Timeline:** Q[X]
**Probability:** XX%

### Current State
- Existing relationship: [Description]
- Current usage: [Metrics]
- Stakeholders: [Names]

### Business Case
- Customer problem: [Description]
- Our solution: [Capability]
- Value proposition: [ROI/Outcome]

### Development Actions
| Action | Owner | Due Date | Status |
|--------|-------|----------|--------|
| [Action 1] | [Name] | [Date] | Pending |
| [Action 2] | [Name] | [Date] | Pending |

### Buying Process
- Decision maker: [Name]
- Budget owner: [Name]
- Timeline: [Process]
- Competition: [Awareness]

### Next Steps
1. [Step 1]
2. [Step 2]

QBR Risk/Opportunity Section

## Risk & Opportunity Review (QBR Section - 10 minutes)

### Risks to Address
| Risk | Status | Mitigation Progress |
|------|--------|---------------------|
| [Risk 1] | 🟢/🟡/🔴 | [Brief update] |
| [Risk 2] | 🟢/🟡/🔴 | [Brief update] |

"Are there other concerns we should discuss?"

### Opportunities to Explore
| Opportunity | Potential | Discussion |
|-------------|-----------|------------|
| [Opportunity 1] | $XX,XXX | [Question to explore] |
| [Opportunity 2] | $XX,XXX | [Question to explore] |

"Where do you see potential to expand our partnership?"

### New Signals
[Space to capture any new risks or opportunities that emerge in discussion]

Risk Escalation Matrix

Anti-Patterns

• Risk avoidance — Not asking hard questions
• Defensive response — Dismissing customer concerns
• Signal ignorance — Missing obvious warning signs
• Escalation fear — Hiding risks from leadership
• Opportunity blindness — Only seeing problems, not growth
• Passive discovery — Waiting for customer to raise issues
• Action gap — Identifying risks without mitigation plans
• Single-threaded view — Only talking to champion about risks

title: Roadmap Alignment impact: HIGH tags: roadmap, product, features, advocacy, innovation

Roadmap Alignment

Impact: HIGH

Roadmap discussions are one of the most anticipated — and potentially dangerous — parts of a QBR. Done well, they build confidence in the partnership. Done poorly, they create unrealistic expectations or signal you don't understand the customer's needs. Navigate with care.

Roadmap Conversation Framework

┌─────────────────────────────────────────────────────────────────────────┐
│                   ROADMAP ALIGNMENT FLOW                                 │
├─────────────────────────────────────────────────────────────────────────┤
│  LISTEN      What problems is customer trying to solve?                  │
│     ↓                                                                    │
│  CONNECT     How does our roadmap address those problems?                │
│     ↓                                                                    │
│  SHARE       Present relevant upcoming capabilities                      │
│     ↓                                                                    │
│  ALIGN       Explore timing and fit with customer plans                  │
│     ↓                                                                    │
│  CAPTURE     Document feature requests for product team                  │
│     ↓                                                                    │
│  COMMIT      Set expectations on what's known/unknown                    │
└─────────────────────────────────────────────────────────────────────────┘

Roadmap Discussion Rules

Good Roadmap Conversations

✓ Customer-problem-first
  → "Tell me about the challenge you're facing..."
  → THEN connect to roadmap
  → Not: "Here's everything we're building"

✓ Selective sharing
  → Features relevant to THIS customer
  → Not every item in development
  → Curated, not comprehensive

✓ Appropriate caveats
  → "This is our current direction..."
  → "Timing is always subject to change..."
  → Set expectations clearly

✓ Two-way dialogue
  → "Would this address your need?"
  → "How would you prioritize X vs Y?"
  → Gather input, don't just broadcast

✓ Feedback capture
  → Document requests carefully
  → Close the loop on what you'll do
  → "I'll bring this to our product team"

✓ Celebrate wins
  → "Remember when you asked for X? It's shipping next month"
  → Show responsiveness
  → Build confidence in partnership

Bad Roadmap Conversations

✗ Date commitments
  → "That will ship in March"
  → Dates slip, trust erodes
  → Never commit dates you don't control

✗ Full roadmap dump
  → "Here's our entire 12-month roadmap"
  → Overwhelming, irrelevant noise
  → Customer forgets what matters

✗ Promise-to-please
  → "We'll definitely build that for you"
  → Can't commit without product buy-in
  → Broken promises destroy trust

✗ Competitive bashing
  → "Competitor X will never have that"
  → Unprofessional, often wrong
  → Focus on your value, not their flaws

✗ Ignoring requests
  → Customer: "We really need X"
  → CSM: "Let me tell you about Y"
  → Dismissive, tone-deaf

✗ No follow-through
  → Capture requests, never route them
  → Customer feels ignored
  → Same request every QBR

Roadmap Presentation Template

## Product Roadmap Update - [Customer Name] QBR

### Recently Shipped (Last 90 Days)
| Feature | Description | Relevance to [Customer] |
|---------|-------------|-------------------------|
| [Feature 1] | [Brief description] | [How it helps them] |
| [Feature 2] | [Brief description] | [How it helps them] |

### Coming Soon (Next Quarter)
| Capability | Problem Solved | Expected Timing |
|------------|----------------|-----------------|
| [Capability 1] | [Problem] | Q[X] |
| [Capability 2] | [Problem] | Q[X] |

Note: Timing is our current plan and subject to change.

### On the Horizon (Next 2-3 Quarters)
| Direction | Description |
|-----------|-------------|
| [Direction 1] | We're investing in [area] to enable [outcome] |
| [Direction 2] | Exploring [capability] based on customer feedback |

Note: These are directional; specifics TBD.

### Your Feedback in Action
| Your Request | Status | Notes |
|--------------|--------|-------|
| [Request 1] | In development | Targeting Q[X] |
| [Request 2] | Planned | On roadmap for H[X] |
| [Request 3] | Under evaluation | Need more input |

### Discussion Questions
1. Which upcoming capabilities are most relevant to you?
2. What problems are we not addressing that we should?
3. How can we better prioritize your needs?

Feature Request Handling

Feature Request Documentation

## Feature Request Form

### Request Details
- Customer: [Name]
- ARR: $XXX,XXX
- Requestor: [Name, Title]
- Date: [Date]
- CSM: [Name]

### The Request
**What:** [Specific feature/capability requested]

**Why:** [Business problem they're trying to solve]

**Impact:**
- Business impact if built: [Expected outcome]
- Impact if NOT built: [Risk to account]

### Context
- How urgent: [Critical / High / Medium / Low]
- Workaround exists: [Yes/No - describe]
- Other customers requesting: [Yes/No - list]
- Competitive pressure: [Yes/No - which competitor]

### Customer Quote
"[Exact words from customer about why this matters]"

### CSM Recommendation
[Your assessment of validity and priority]

Beta Program Positioning

## Offering Beta Access in QBRs

WHEN TO OFFER
✓ Customer expressed need for upcoming feature
✓ Customer is technically capable
✓ Customer has provided valuable feedback before
✓ Strategic account worth extra engagement

HOW TO POSITION
"Based on what you've shared, our [upcoming feature]
could be exactly what you need. We're launching a beta
program in [timeframe], and I'd love to nominate you
for early access. Would you be interested?

This would mean:
- Early access to the capability
- Direct influence on how we build it
- Some extra time providing feedback

What do you think?"

BETA EXPECTATIONS TO SET
- Feature may have rough edges
- Feedback commitment expected
- Timeline may shift
- Support process may differ

Roadmap Timing Language

Handling Competitive Questions

## When Customer Asks About Competitor Features

DON'T:
- Dismiss the competitor
- Make promises to match
- Get defensive
- Speak negatively about competitor

DO:
- Acknowledge the question professionally
- Understand the underlying need
- Explain your approach/philosophy
- Be honest about gaps
- Focus on your strengths

EXAMPLE RESPONSE:
"I'm familiar with [competitor]'s approach to [feature].
Help me understand — what specific problem would that
solve for you?

[Listen and understand]

Here's how we think about this differently...
[Explain your philosophy]

We [have/don't have] something similar.
[If not: Here's what's on our radar and here's what
we'd need to understand better to prioritize it.]"

Roadmap Governance

Product-CS Feedback Loop

## Roadmap Alignment Process

QBR PREPARATION
CSM reviews roadmap → Identifies relevant items → Prepares slides

QBR EXECUTION
Present roadmap → Capture feedback → Document requests

POST-QBR
Submit feature requests → Route to product → Update tracking

QUARTERLY SYNC
Product + CS review → Prioritize requests → Update CSMs

CLOSE THE LOOP
CSM informs customer → Updates status in QBR → Builds trust

Anti-Patterns

• Date promising — Committing to dates you don't control
• Roadmap dumping — Sharing everything, relevant or not
• Promise-to-please — Agreeing to build whatever they ask
• Request ignoring — Capturing feedback that goes nowhere
• Competitive bashing — Speaking negatively about rivals
• Overselling unbuilt features — Selling vaporware
• No feedback loop — Requests never reach product
• Static roadmap slides — Same slides every quarter

title: Value Demonstration impact: CRITICAL tags: value, roi, storytelling, outcomes, business-impact

Value Demonstration

Impact: CRITICAL

The QBR is your opportunity to prove ROI and justify the customer's investment. If you can't quantify value, you become a cost to cut. The best CSMs transform usage data into compelling business impact narratives that executives remember.

The Value Pyramid

┌─────────────────────────────────────────────────────────────────┐
│                    STRATEGIC VALUE                               │
│    Market position, competitive advantage, innovation           │
│    "You're now 2 years ahead of competitors in X"               │
├─────────────────────────────────────────────────────────────────┤
│                    BUSINESS VALUE                                │
│    Revenue growth, cost reduction, risk mitigation              │
│    "$2.4M in new revenue attributed to your use of X"           │
├─────────────────────────────────────────────────────────────────┤
│                    OPERATIONAL VALUE                             │
│    Efficiency, productivity, quality improvements               │
│    "Your team saved 3,400 hours this quarter"                   │
├─────────────────────────────────────────────────────────────────┤
│                    TECHNICAL VALUE                               │
│    Performance, reliability, integration                        │
│    "99.99% uptime, 40% faster processing"                       │
└─────────────────────────────────────────────────────────────────┘

    ↑ Executive focus: Top 2 levels
    ↓ Operational focus: Bottom 2 levels

ROI Calculation Framework

Good Value Demonstration

✓ Business outcomes, not features
  → "You reduced customer churn by 23%"
  → Not "You used the churn prediction feature 45 times"

✓ Customer's own metrics
  → "Your NPS increased from 32 to 48"
  → Not "Industry NPS average is 35"

✓ Before/after comparison
  → "Before: 4 hours per report. Now: 15 minutes"
  → Baseline established at onboarding

✓ Dollar quantification
  → "3,400 hours saved = $255,000 in productivity"
  → Always translate to business value

✓ Executive language
  → Revenue, margin, risk, market position
  → Not features, clicks, logins

✓ Attribution clarity
  → "This improvement is directly tied to your use of X"
  → Connect value to your solution specifically

Bad Value Demonstration

✗ Vanity metrics only
  → "You had 14,000 logins this quarter!"
  → Logins ≠ Value

✗ Feature usage reports
  → "Here's every feature and how often you used it"
  → Usage ≠ Outcomes

✗ Vendor-centric metrics
  → "We achieved 99.9% uptime"
  → What does uptime mean to THEIR business?

✗ Unquantified claims
  → "You're more efficient now"
  → How much more efficient? In dollars?

✗ Generic benchmarks
  → "Industry average is X"
  → What's THEIR specific improvement?

✗ Past-only focus
  → "Here's what happened last quarter"
  → So what? What's next?

Value Story Structure

## The IMPACT Value Story Framework

I - Identify the business challenge
    "Before implementing [Solution], your team was..."

M - Measure the baseline
    "Specifically, you were spending [X hours/dollars] on..."

P - Present the solution
    "With [Solution], you implemented [specific capability]..."

A - Articulate the improvement
    "As a result, you've achieved [specific metric improvement]..."

C - Calculate the ROI
    "This translates to [$X value] in [timeframe]..."

T - Tie to strategic goals
    "This directly supports your initiative to [strategic goal]..."

Value Story Example

## Value Story: Acme Corp - Customer Support Efficiency

IDENTIFY:
"When we started working together, Acme's support team was
struggling with high ticket volumes and slow resolution times,
impacting customer satisfaction and agent burnout."

MEASURE:
"Specifically, you were handling 2,400 tickets/month with an
average resolution time of 48 hours and a CSAT of 3.2/5."

PRESENT:
"Using our AI-powered ticket routing and knowledge base
automation, your team implemented smart triage and
self-service deflection."

ARTICULATE:
"Over the past quarter, you've reduced resolution time to
18 hours (62% improvement), increased CSAT to 4.4/5, and
deflected 35% of tickets to self-service."

CALCULATE:
"This translates to:
- 840 hours saved in agent time = $42,000/quarter
- 35% ticket deflection = $28,000 in avoided costs
- Total quarterly value: $70,000 (280% ROI on investment)"

TIE:
"This directly supports your 2024 goal of improving customer
experience while controlling support costs as you scale."

ROI Presentation Template

## [Customer Name] - Value Delivered This Quarter

### Investment Summary
| Item | Amount |
|------|--------|
| Annual Contract Value | $XX,XXX |
| Quarterly Investment | $XX,XXX |

### Value Delivered
| Value Category | Metric | Improvement | Value |
|----------------|--------|-------------|-------|
| Time Savings | Hours saved | X → Y | $XX,XXX |
| Revenue Impact | Pipeline attributed | $X | $XX,XXX |
| Cost Reduction | Process efficiency | X% | $XX,XXX |
| Quality | Error reduction | X% | $XX,XXX |

### Total Quarterly Value: $XXX,XXX
### Quarterly ROI: XXX%
### Annualized Value: $X,XXX,XXX

### Value Trend
| Quarter | Value Delivered | ROI |
|---------|-----------------|-----|
| Q1 | $XX,XXX | XXX% |
| Q2 | $XX,XXX | XXX% |
| Q3 | $XX,XXX | XXX% |

### Key Achievements
✓ [Achievement 1 with specific metric]
✓ [Achievement 2 with specific metric]
✓ [Achievement 3 with specific metric]

Value Categories by Persona

Value Documentation Best Practices

Handling "We Can't Measure That"

Value Storytelling Techniques

## Techniques for Compelling Value Stories

1. CONTRAST
   "Before: [painful state]. After: [improved state]"
   Creates emotional impact through comparison

2. SPECIFICITY
   "3,427 hours" not "thousands of hours"
   Specific numbers are more credible

3. PERSONALIZATION
   "Your team of 12 engineers each saved 8 hours/week"
   Make it about their people

4. MOMENTUM
   "Q1: $40K value. Q2: $58K value. Q3: $82K value"
   Show accelerating returns

5. PEER COMPARISON
   "Your adoption is in the top 20% of customers your size"
   Competitive motivation

6. RISK FRAMING
   "You avoided 4 major incidents worth $200K each"
   Loss aversion is powerful

Value Realization Tracking

Anti-Patterns

• Vanity metric obsession — Reporting logins, not outcomes
• Unsubstantiated claims — "You're more efficient" without numbers
• Vendor-centric value — Our metrics, not their impact
• Past-only narrative — What happened, not what it means
• Single dimension — Only cost savings, missing strategic value
• Inflated claims — Overclaiming destroys credibility
• No customer validation — Assuming they agree with your math
• Static value story — Same story every QBR