How do you run a sales QBR that actually changes behavior?
Direct Answer
A sales QBR (Quarterly Business Review) is a 90-minute internal meeting where each AE presents last quarter's attainment, current pipeline coverage, the gap to next quarter's quota, and the three actions they will take to close it. The format that actually changes behavior is simple: a 6-9 slide pre-read due 48 hours before the meeting, 25 minutes of live discussion focused on the gap and the commitments, and three written commitments that show up in every Monday 1:1 for the next 12 weeks.
Anything else is theater.
TL;DR
- A sales QBR is an internal review, not a customer meeting (that is a CS QBR), and it should run 90 minutes per AE, not all day.
- Slides are a pre-read due 48 hours before, not a walkthrough; the meeting is for the gap analysis and the three commitments.
- Most QBRs fail in one of four ways: Salesforce screenshots instead of analysis, managers who do not push back, no commitments captured, or meetings longer than two hours.
- The only output that matters is three written commitments that get tracked weekly in 1:1s.
- One Series C team moved attainment from 67% to 78% in two quarters by cutting QBR length and enforcing the three-commitment format.
The Pre-Read Format That Works
The single biggest mistake teams make is treating the QBR like a presentation. AEs spend four to six hours building slides, then walk through them live while the manager nods. By the time the gap discussion comes up, everyone is tired and the meeting ends with vague encouragement.
The fix is to push every slide into a pre-read due 48 hours before the meeting, then use the live time exclusively for the gap and the commitments. Here is the slide template that actually works.
| Slide | What it covers | What good looks like |
|---|---|---|
| 1. Attainment summary | Last quarter quota, closed-won, attainment percentage, plus the trailing 4-quarter trend | One number and a sparkline, not a wall of text; honest if missed |
| 2. Pipeline coverage | Current quarter pipeline divided by remaining quota, by stage and by month | At least 3x coverage for the current quarter; called out if below |
| 3. Win/loss breakdown | Wins and losses by competitor, deal size, and primary reason | Patterns named; not just a list of logos |
| 4. Top 3 wins | What unlocked the deal, who the champion was, replicable play | A specific tactic another AE could copy on Monday |
| 5. Top 3 losses | Root cause not symptom; what the AE would do differently | Honest about own mistakes, not blaming product or pricing |
| 6. Top 5 in-quarter deals | Name, amount, stage, next step, risk level | Realistic dates and risks, no happy ears |
| 7. Plan to plug the gap | If pipeline is short, the specific sourcing actions for the next 30 days | Named accounts and named activities, not "more outbound" |
Slides 8 and 9 are optional and used for AEs with a specific learning ask or a territory shift. The Gong deal-review snippet for the top loss is the single highest-leverage addition in 2027 because it forces the AE to confront the actual call, not their memory of it.
The 4 QBR Failure Modes That Make It Theater
After watching dozens of these, the same four patterns kill QBRs everywhere. First, AEs paste Salesforce dashboard screenshots into the deck without any analysis. The slide says what happened, never why, and never what to do about it.
The manager has to do the analysis live, which is exactly backwards — the analysis is the prep work, and skipping it turns the QBR into a read-aloud session. Second, the manager does not push back on weak pipeline. Coverage is 1.4x and the AE says "I'll close this list of deals," and the room moves on.
No pushback means no behavior change, and the AE walks out of the QBR with the same plan they walked in with. Third, no commitments are captured. The meeting ends, everyone says "great QBR," and by week two nobody remembers what was agreed; the document, if it exists at all, lives in a manager's notebook nobody else can see.
Fourth, the meeting runs longer than two hours per AE. A 25-AE team running three hours of QBR per AE burns 75 hours of manager time per quarter on theater, and by the eighteenth AE the manager is on autopilot and the last reps get a worse review than the first ones did. Cutting to 45 to 90 minutes per AE with the same three-commitment format is what moved one Series C company from 67% to 78% attainment in two quarters, because the manager had energy left for every AE and the format forced the work into the pre-read where it belongs.
The 3 Commitments Format (the only thing that drives behavior change)
The entire QBR exists to produce three written commitments per AE. Not five, not seven, not a long action list nobody reads. Three.
Each commitment has an owner (the AE), a specific behavior change (not an outcome), and a weekly check-in mechanism. Examples of real commitments that drive change: "I will run a multi-threading play on every deal over 50k by week 4, defined as at least three contacts engaged in the last 14 days, tracked in Salesforce custom field." Or: "I will book 12 new discovery calls per week in Q3, measured every Monday in the 1:1." Or: "I will use the Gong scorecard for objection handling on every demo, with the manager spot-checking two calls per week."
The commitments live in a shared Notion or Coda doc the manager opens in every Monday 1:1, never in a private notebook or a slide nobody looks at again. Red, yellow, or green status against each commitment, with one or two sentences of notes about what moved and what blocked. At the week-6 mid-quarter check the manager and AE review whether the commitments are still the right ones; sometimes a major deal slip or a territory change means a commitment needs to be retired and replaced, and that is fine as long as the conversation is explicit.
At the next QBR, slide one is no longer attainment, it is the commitments scorecard from last quarter. Did the behaviors actually happen? Green, yellow, or red, with evidence.
That single change converts the QBR from a status meeting into a closed-loop coaching system, which is the entire point and the only reason to spend the time at all.
Frequently Asked Questions
Should QBRs be quarterly or monthly? Quarterly for the formal deck and three-commitment exercise. Monthly business reviews (MBRs) can be useful for pipeline health and forecasting, but they should be 30 minutes, not a full QBR. Doing the full QBR every month kills it.
Manager-only or full team? Manager and AE one-on-one for the conversation, with the wider team invited to read the deck async. A team-wide QBR where everyone sits through 25 individual reviews wastes 24 people's time. Use a separate team kickoff for the next quarter's plan.
Should reps present each other's deals? No. Peer presentations sound collaborative but dilute accountability and slow the meeting to a crawl. Each AE owns their own deck and their own commitments, and the manager owns pushing back. Peer learning belongs in weekly deal-review office hours or a separate top-deal jam session, not the QBR.
Sources
- Force Management — "Quarterly Business Review Playbook for Sales Leaders" (2024 update).
- Sales Hacker — "The Sales QBR Template That Drives Behavior Change" by Max Altschuler (2023).
- Pavilion 2024 Sales Cadence Survey — manager 1:1 and QBR benchmarks across 1,200 RevOps leaders.
- Bessemer Venture Partners — "State of the Cloud 2024: Sales Productivity Benchmarks."
- Gong Labs — "What 100,000 Sales Calls Reveal About Effective Deal Reviews" (2024 dataset).
- OpenView Partners — "The PLG Sales Org: QBR Templates and Cadences" (2023).
- SaaStr — Jason Lemkin, "The Top Sales QBR Mistakes I See at $1M-$20M ARR" (2024).
- Clari — "Forecast Confidence and QBR Discipline: 2024 Revenue Operations Benchmarks."