My QBR Presentation Framework for C-Suite
I used to present quarterly business reviews as backward-looking performance reports. Then I learned QBRs are about forward strategy, not historical data.
My first QBR presentation to the C-suite was thirty slides of backward-looking metrics: pipeline generated, deals won, campaigns executed, features launched, win rates by segment, competitive losses analyzed.
I spent two hours building comprehensive retrospective analysis. Fifteen minutes into the presentation, our CEO interrupted: "This is all helpful context, but what should we do differently next quarter based on what we learned?"
I didn't have an answer. I'd spent all my time documenting what happened—I hadn't thought about strategic implications for what should happen next.
The CEO moved on. After the meeting, our CMO said: "QBRs aren't performance reports—they're strategy conversations. The exec team can read your metrics in Salesforce. What they need from you is pattern identification and strategic recommendations."
That feedback forced me to rebuild how I approach QBRs.
The shift: From "here's what happened last quarter" to "here's what we learned and what we should do differently."
Three months later, I presented my next QBR using a completely different framework. The CEO said afterward: "This is exactly what I need from QBRs—less reporting, more strategy. Let's make this the template for all QBRs."
What QBRs Are Actually For (vs. What I Thought They Were For)
I thought QBRs were: A comprehensive review of last quarter's performance across all PMM activities.
QBRs are actually: A strategic forcing function to identify patterns, surface risks, and set direction for the next quarter.
I thought my job was: Document everything we accomplished and present complete performance data.
My actual job is: Identify 3-4 strategic insights from last quarter's data and recommend specific actions for next quarter.
The questions executives want answered in QBRs:
- Did last quarter's strategy work? (Performance vs. plan)
- What patterns emerged that should inform strategy? (Insight identification)
- What risks or opportunities are we not talking about? (Strategic blindspots)
- What should we do differently next quarter? (Forward recommendations)
Executives can read performance metrics themselves. They need PMMs to interpret patterns and recommend strategy adjustments.
The QBR Framework That Actually Works
After rebuilding my QBR approach, I settled on a framework that takes 15 minutes to present and drives 45 minutes of strategic discussion.
The framework: 3-2-1
- 3 Strategic Insights: Patterns from last quarter that matter for strategy
- 2 Risks/Opportunities: Things we're not talking about enough
- 1 Recommendation: The single most important action for next quarter
Total: 6 slides. Maximum.
Section 1: Performance vs. Plan (2 minutes)
One slide with 4-6 key metrics comparing actual vs. target.
Example:
Q3 2024 Performance Summary
| Metric | Target | Actual | % |
|---|---|---|---|
| Pipeline | $8.5M | $9.2M | 108% ✓ |
| Win Rate | 42% | 48% | 114% ✓ |
| Deal Size | $160K | $180K | 112% ✓ |
| Sales Cycle | 4.5mo | 5.2mo | 84% ✗ |
| New Logos | 35 | 28 | 80% ✗ |
Summary: Exceeded revenue targets but missed new logo acquisition. Sales cycles lengthened.
That's it. One slide. Two minutes. The exec team understands whether we hit plan or missed it.
What I don't include: 15 slides of campaign metrics, launch breakdowns, program details, enablement completion rates. None of that matters for strategy discussion.
Section 2: Three Strategic Insights (6 minutes)
Three slides—one insight per slide—identifying patterns that should inform strategy.
What makes a good strategic insight:
- Backed by data (not anecdotal)
- Non-obvious (not "we hit our targets")
- Actionable (leads to specific strategic choice)
Example Insight #1:
Insight: Mid-Market is our competitive advantage
Data:
- Mid-market win rate: 61% (up from 52% in Q2)
- Enterprise win rate: 18% (down from 22% in Q2)
- Mid-market deals close 2.4x faster than enterprise
- Average mid-market deal size increased 30% to $180K
Strategic Implication: We're winning when we compete on speed and simplicity. We're losing when buyers need enterprise compliance. Doubling down on mid-market generates higher ROI than chasing enterprise.
Example Insight #2:
Insight: Positioning shift is working—but sales hasn't fully adopted
Data:
- Deals using new positioning: 68% win rate
- Deals using old positioning: 34% win rate
- Only 45% of reps consistently using new positioning
- Top performers adopted new positioning 2x faster
Strategic Implication: We have a proven winning message but an adoption problem. If we get full sales adoption, we could improve overall win rate from 48% to 55-58%.
Example Insight #3:
Insight: Sales cycles lengthening due to economic headwinds
Data:
- Average sales cycle increased from 4.2 to 5.2 months
- Pattern: Budget approval taking 6 weeks longer
- No change in deal size or win rate—just longer close times
- Affecting all segments equally
Strategic Implication: This isn't a PMM or product problem—it's macro. We should adjust pipeline coverage assumptions from 4x to 5x to account for longer cycles.
Total: Six minutes to present three insights.
Notice what I'm NOT doing: Presenting raw data and letting executives interpret it. I'm identifying the pattern and stating the strategic implication directly.
Section 3: Two Risks or Opportunities (4 minutes)
Two slides surfacing things that aren't urgent today but will matter in 6-12 months.
This is where I bring up uncomfortable truths or emerging opportunities that might not be on the exec team's radar.
Example Risk:
Risk: Top 3 competitors all launching AI features in Q4
Evidence:
- Competitor X announced AI roadmap in earnings call
- Competitor Y job postings show ML engineer hiring surge
- Competitor Z acquired AI startup for $12M
Impact if we don't respond: They'll have differentiation we don't in 40% of buyer evaluations. Based on current trends, could cost us 8-12 points of win rate in segments where AI matters.
Options to discuss:
- Build our own AI features (18-month timeline)
- Partner with AI platform (6-month timeline)
- Reposition away from AI-dependent use cases
Example Opportunity:
Opportunity: PLG motion gaining traction faster than expected
Evidence:
- Self-serve trial sign-ups up 180% in Q3
- Trial-to-paid conversion at 18% vs. expected 12%
- Average trial-to-paid deal size $45K vs. assisted sales at $180K
Potential: If we invest in PLG infrastructure, we could build a $5-8M annual revenue channel with minimal sales overhead. Currently leaving this opportunity on the table due to product limitations.
These aren't performance reports—they're strategic conversation starters. I'm bringing forward risks and opportunities that require exec-level decisions.
Section 4: One Recommendation (3 minutes)
One slide with the single most important strategic recommendation for next quarter.
Not three recommendations. Not five priorities. One clear recommendation that would have the biggest impact.
Example:
Q4 Recommendation: Accelerate new positioning adoption to 85%+ of sales team
Why this vs. other priorities:
- Proven 2x win rate improvement when adopted (68% vs. 34%)
- Currently only 45% adoption—massive untapped upside
- Faster ROI than any other initiative (8-12 weeks vs. 6+ months)
- Requires minimal investment ($30K enablement + my time)
What this requires:
- Weekly positioning workshops for lagging reps (2 hours/week)
- Call recordings analysis to identify adoption blockers
- Manager scorecards showing positioning usage by rep
- Incentive: $500 spot bonus for first closed deal using new positioning
Expected impact:
- Win rate improvement from 48% to 55%
- Revenue impact: $3.2M additional ARR
- Timeline: Full adoption by end of Q4
Decision needed: Approval for $30K enablement budget and commitment from sales leadership for weekly workshops.
That's the entire QBR: 6 slides, 15 minutes.
The remaining 45 minutes is exec team discussion:
- Debating the insights
- Challenging the recommendation
- Deciding on the risk/opportunity responses
- Setting Q4 strategic direction
That's what good QBRs do—they drive strategic decisions, not just report performance.
What to Leave Out of C-Suite QBRs
I used to include everything: Campaign results, launch metrics, content performance, event attendance, tool adoption, program completions.
What I learned: Including too much detail dilutes strategic focus.
What to leave out:
Activity metrics (campaigns run, content created, events attended)
- Executives don't care about activities—they care about outcomes
Granular performance breakdowns (every campaign, every segment, every channel)
- Put this in an appendix if needed, not in the presentation
Process updates ("We implemented a new tool," "We changed our workflow")
- Unless it drives strategic outcomes, it's not QBR material
Good news you want to celebrate but that doesn't inform strategy
- Save this for all-hands or team meetings
Defensive explanations for misses
- Own the miss, state the fix, move on. Don't dwell on excuses.
The rule: If removing a slide wouldn't change the strategic discussion, remove it.
I went from 30 slides to 6 slides by ruthlessly cutting anything that didn't drive strategy conversation.
How to Handle Tough QBR Questions
Tough question executives always ask: "Why did X metric miss target?"
Low-presence answer: "We faced several headwinds including market conditions, timing challenges, and resource constraints..."
High-presence answer: "We missed because I misjudged demand in enterprise segment. I assumed buyers would prioritize innovation over ROI, and I was wrong. We're adjusting positioning to emphasize ROI for Q4. Early testing shows 40% improvement in interest."
The pattern: Own the miss, explain what you learned, state the fix. Don't make excuses.
Tough question #2: "How confident are you in this recommendation?"
Low-presence answer: "I'm very confident this is the right approach."
High-presence answer: "I'm 75% confident. The data strongly supports this, but there's 25% risk that sales adoption takes longer than projected. If we don't see 60% adoption in 4 weeks, we should revisit."
The pattern: Give honest confidence level and state the risk. Executives trust calibrated confidence more than false certainty.
Tough question #3: "What if we disagree with your recommendation?"
Low-presence answer: "Well, there are other options we could consider..."
High-presence answer: "If you disagree, I'd want to understand what I'm missing. The data points to this approach, but I could be wrong about prioritization or timing. What concerns you about this path?"
The pattern: Defend your recommendation while staying open to being wrong. Show you've thought deeply but aren't attached to being right.
The Follow-Up That Makes QBRs Matter
The biggest mistake: Presenting QBR, getting through it, then doing nothing until next quarter.
What actually works: Following up on decisions made in the QBR every 2-3 weeks.
After my Q3 QBR where I recommended accelerating positioning adoption, I sent bi-weekly updates:
Week 2: "Positioning adoption update: Completed first round of workshops with 12 reps. Adoption now at 52% (up from 45%). Tracking toward 85% by end of quarter."
Week 4: "Positioning adoption at 61%. Win rate for deals using new positioning holding at 68%. Early signal: Pipeline up 18% vs. same period last quarter."
Week 6: "Positioning adoption at 74%. Win rate overall improved from 48% to 53%. On track to hit 85% adoption and 55% win rate by end of Q4."
This follow-through did more to build credibility than the QBR itself.
Executives remember whether you executed on QBR commitments more than they remember the presentation.
The Uncomfortable Truth About QBRs
Most PMMs treat QBRs as performance reports: "Here's everything we did last quarter."
Executives want strategy sessions: "Here's what we learned and what we should do differently."
The difference is massive.
Performance-report QBRs:
- Backward-looking
- Comprehensive but unfocused
- Low strategic value
- Executives zone out
Strategy-session QBRs:
- Forward-looking
- Focused on 3-4 key insights
- Drive specific decisions
- Executives engage actively
The PMMs who build executive credibility: Present QBRs that identify patterns, surface risks, and drive strategic decisions.
The PMMs who stay stuck in tactical roles: Present QBRs that comprehensively document what happened without strategic interpretation.
My career trajectory changed when I stopped treating QBRs as reporting obligations and started treating them as strategic opportunities to influence direction.
The QBR framework:
- Performance vs. Plan: 1 slide, 2 minutes
- Three Strategic Insights: 3 slides, 6 minutes
- Two Risks/Opportunities: 2 slides, 4 minutes
- One Recommendation: 1 slide, 3 minutes
- Total: 6 slides, 15 minutes presenting, 45 minutes discussing
Use this framework, and your QBRs become strategy sessions instead of performance reviews.
That's when executives start seeing you as a strategic advisor instead of a metrics reporter.
That's when QBRs drive actual decisions instead of just checking a box.
Kris Carter
Founder, Segment8
Founder & CEO at Segment8. Former PMM leader at Procore (pre/post-IPO) and Featurespace. Spent 15+ years helping SaaS and fintech companies punch above their weight through sharp positioning and GTM strategy.
More from Executive Communication
Ready to level up your GTM strategy?
See how Segment8 helps GTM teams build better go-to-market strategies, launch faster, and drive measurable impact.
Book a Demo
