The Customer QBR Reboot — 60-Min Training

The account that made this Training necessary

Open the session cold, because everyone in the room already lives this pain: most Customer success teams watch three of every five scheduled QBRs get cancelled, no-showed, or downgraded to a rushed 15-minute call. That is not a calendar problem — it is a value problem. When a customer believes the QBR is *your* review of *your* performance, they cancel, because nothing on the agenda helps them. When they believe it is *their* review of *their* outcomes, they show up, and they bring their boss.

Picture the account most reps recognize instantly: $180K ACV, health score yellow, renewal 90 days out. The last QBR was a 14-slide deck titled "What We Shipped This Quarter." The champion sat through it politely, the exec sponsor declined the invite, and the meeting produced exactly one action item that nobody owned. Ninety days later the renewal became a fire drill and expansion never came up once. This 60-minute Training exists to break that precise loop, and it opens by naming that account out loud so the room stops treating cancellations as bad luck.

The frame change reps learn first is deliberately small and nearly free: stop calling the meeting a "QBR" on the invite, in the deck, and in chat. Call it a Value Review. Lincoln Murphy has argued this same point — pairing the word "review" with a customer-owned outcome is what convinces the exec sponsor to accept. The rename costs nothing yet changes who walks into the room. By minute 60, every AE and CSM present can run a session that lands an expansion conversation rather than merely confirming a renewal date.

Set expectations honestly, too: the Reboot is a sales-adjacent motion for Customer success, and some CSMs resist that framing on instinct. The Training addresses the resistance head-on — expansion is not a bolt-on pitch, it is the natural next sentence after "the ROI you got was X." You reboot the meeting's purpose first, because the tactics only work once the purpose belongs to the customer instead of the vendor.

How the four-part arc actually works

The spine of every rebooted QBR is a four-part arc that fits on a single slide. Teach reps to walk the customer through it in strict order, because each part earns the right to the next. Jumping to roadmap before proving ROI is the single reason so many QBRs still feel like a sales pitch, and the arc is designed to make that shortcut impossible.

Part 1 — use cases activated (about 4 minutes live). Pull the list of features and workflows the customer enabled this quarter from product analytics before the call. Read it back specifically: "Last quarter we agreed you would light up workflows A, B, and C. A is live with 47 users, B with 12, and C has not started — walk me through C." Specific adoption numbers signal you did the homework and shift the customer from defensive to collaborative in the first four minutes.

Part 2 — ROI delivered (about 5 minutes). Bring one number the customer's CFO would believe, and say it out loud. Three defensible constructions cover almost every account: hours saved times loaded labor rate; pipeline influenced times close rate times ACV; or risk events avoided times cost per incident. If a rep cannot state a dollar figure, they are running a friendly check-in, not a Value Review, and the Training says so bluntly.

Part 3 — blockers identified (about 3 minutes). Ask one question and stop talking: "What is the one thing that, if we removed it, would double your usage?" That surfaces the expansion lane without selling anything, because the customer names their own constraint. Log the answer verbatim — the exact wording becomes the anchor for the next quarter's plan.

Part 4 — roadmap ahead (about 3 minutes). Show two columns side by side: what is coming from your product team, and what is coming from theirs. Propose the expansion lane in the language of *their* roadmap, never your SKU list. A feature framed against the customer's own stated goal reads as help; the identical feature framed as an upsell reads as pressure. The arc closes with action items that have named owners and explicit exec sign-off, so the meeting cannot dissolve into the ownerless action item that killed the earlier QBR.

Real numbers, ranges, and benchmarks to put on the slide

The Training runs on hard numbers, because vague coaching never survives contact with a skeptical CSM. Give reps the ranges to plan against so nothing in the room is improvised.

Meeting length. For accounts in the $25K–$500K ACV band, block 60 minutes on the calendar, run the content in roughly 45, and hand back 15. Thirty minutes is too short to do the ROI conversation justice; 90 minutes simply invites status-update bloat to expand and fill the time. The 45-minute working length is the sweet spot the Reboot targets, and giving 15 minutes back leaves the customer remembering an efficient, respectful meeting.

Deck size. Cap the deck at six slides, no exceptions: their logo beside their stated business goal from last quarter; the ROI number; a use-case heatmap in green, yellow, and red; one blocker and one ask; the two-column roadmap; and action items with owners and dates. Anything past six slides is exactly where status-update filler creeps back in.

Prep window. Reps complete the pre-QBR prep doc 48 hours before every meeting. The doc captures ACV, renewal date, both exec sponsors, the top three activated use cases with adoption percentages, the one ROI number with its math shown, the health-score delta versus last QBR, open support tickets older than 14 days, and a one-sentence expansion hypothesis paired with a one-sentence risk hypothesis. If the doc is empty 48 hours out, cancel and rebook — the prep doc *is* the QBR, and a blank doc guarantees the winged status-update meeting the Reboot exists to eliminate.

Exec attendance. Invites sent exec-to-exec accept at meaningfully higher rates than invites an AE sends to a champion, which is why the Training teaches a two-step exec-sponsor tactic. At T-14 days, your exec emails their exec peer-to-peer with no CTA beyond "I would like to join the Value Review on [date]." At T-7 days, the CSM forwards that thread to the day-to-day champion: "Looks like our execs are syncing — want to make sure yours is set up to win the room."

Async fallback. When the exec sponsor still cannot attend, record a three-minute exec-summary video the day after and send it directly. Short async recaps consistently out-open written recaps, and a customer-facing video keeps the exec relationship warm between live sessions instead of going cold for a full quarter.

Measurement. Track three numbers quarterly so leadership can prove the Reboot works: exec-sponsor attendance rate, the percentage of QBRs that surface a logged expansion opportunity, and the net-revenue-retention delta between accounts on-cadence versus off-cadence. A clear double-digit NRR gap between the two cohorts is the outcome that justifies the entire program to a CFO.

Trade-offs and alternatives every rep must weigh

Not every trigger deserves the same play, and not every account can run the full arc. The core judgment the Training installs is reading *which* expansion trigger fired, because the correct response differs for each one. Teach reps to route on the signal they actually hear rather than defaulting to a single script.

Each play carries a verbatim opener reps rehearse until it is reflex. New exec joined: "Congrats on the new hire — want me to run a 30-minute version of this review with them next week?" Adoption above 80% in one team: "Your team is at 84%; the adjacent function usually gets there in half the time because you paved the road — worth a four-week pilot?" A cited value number bigger than ACV: "You just said this saved $1.2M; your contract is $180K — that is a 6.7x return, and customers at that ratio usually expand into the next module." Competitor named: "Are you running them in parallel or evaluating a switch? I would rather know now than at renewal." Roadmap feature ask: "That ships next quarter — I can get you into the early-access cohort if we move to a multi-year."

The trade-off to name explicitly is health. An aggressive expansion play on a red-health account backfires and can accelerate the churn it was meant to prevent. When health is poor, the alternative motion is the "Red QBR": lead with the blocker, spend the first 20 minutes on what is not working, and earn the right to discuss expansion only after proving you will discuss pain first. A green account runs the full arc; a red account inverts it. Reps who run the identical script on both lose the room, so the routing decision precedes every other tactic.

The second alternative worth teaching is ownership. The CSM owns prep and runs the meeting; the AE owns the expansion play when a trigger fires and owns the commercial renewal conversation. Co-present whenever possible. If only the AE shows, the meeting reads as sales pressure; if only the CSM shows, it reads as a support call. Both are losing frames, so the default is both in the room with clearly separated lanes.

Common pitfalls and how to avoid them

The fastest way to undo a QBR Reboot is to let old habits back into the deck, so the Training runs a live drill against the most common failures instead of just listing them.

Pitfall 1 — the status-update slide. The rule reps memorize: "If a slide could have been an email, it does not belong in the QBR." Banned outright are "here is what we shipped," the support-ticket summary, the CSM org chart, and the 14-slide product roadmap. Run a 90-second drill in the session — pair the room, one rep reads a past deck title by title, and the partner shouts "EMAIL!" every time a slide would have worked as one. Two or more "EMAIL!" calls means that deck gets rebuilt before the next meeting.

Pitfall 2 — no dollar number. Reps who show adoption charts but never state ROI in dollars leave the customer unable to justify renewal internally. The fix is the prep-doc field "The Number," with the math shown, filled 48 hours ahead. No number, no meeting — the Training treats a missing dollar figure as a hard stop, not a soft miss.

Pitfall 3 — "I'll follow up" on a live trigger. When a customer hands you an expansion signal in the room, the play runs before the meeting ends. Deferring to a follow-up email lets the moment cool and the champion's attention move on to their next fire. The Training makes the play a same-meeting reflex, which is the entire reason each trigger has a rehearsed opener.

Pitfall 4 — the empty prep doc. If the doc is blank 48 hours out, the honest move is to cancel and rebook rather than wing it live. A winged QBR reliably produces the exact status-update meeting the Reboot was built to kill, and it burns the customer's goodwill in the process.

Pitfall 5 — sending no pre-read. Send the deck 24 hours ahead with one line: "Here is the draft — the blocker slide is blank on purpose, fill it in or we will fill it in together." That forces engagement and defuses the cancellation reflex, because the customer now holds a task, not just a calendar hold. To close the Training, each rep writes three commitments on a card: the next QBR on their calendar with account and date, which trigger they expect to hear plus the verbatim play they will run, and who their exec sponsor is emailing and by when. End the session on time, always — the meeting discipline you model in the Training is the discipline reps carry into the customer room.

Related questions

How is a Value Review different from a standard QBR?

A standard QBR reviews vendor performance; a Value Review reviews customer outcomes. The rename shifts ownership to the customer, which lifts exec attendance and turns the meeting into an expansion surface instead of a renewal formality. Same 60-minute slot, opposite center of gravity.

Who should attend the customer QBR?

Both the exec sponsor and the day-to-day champion on their side, and both the CSM and AE on yours. The CSM runs the meeting; the AE runs the expansion play when a trigger fires. A missing exec sponsor is the single biggest predictor of a stalled renewal.

How often should QBRs happen?

Quarterly for strategic accounts, semi-annually for smaller ones. Documented reviews on a 90-day cadence expand faster than ad-hoc check-ins because value gets restated before the customer forgets it. Cadence, not intensity, drives net-revenue retention.

Can this Training work for a fully remote team?

Yes. Run the 60-minute session over video, use the same prep doc and drill, and swap the live "EMAIL!" drill for breakout rooms. Async exec recap videos matter more for remote teams, since face time with the exec sponsor is scarcer.

FAQ

How long should the live QBR actually run? Block 60 minutes and run about 45 for accounts in the $25K–$500K ACV range. Thirty minutes is too short for a real ROI conversation; 90 invites status-update bloat. Giving 15 minutes back leaves the customer remembering an efficient, respectful meeting rather than a filler-padded hour.

What if the customer's exec sponsor will not show up? Run the meeting with the champion, then record a three-minute exec-summary video the day after and send it directly to the exec. Short async recaps out-open written summaries, so the exec stays looped in even without attending live.

How do we run a QBR for an account with a bad health score? Lead with the blocker, not the ROI. Open with "Before the roadmap, I want 20 minutes on what is not working — walk me through it." This "Red QBR" frame earns the right to discuss expansion by proving you will address pain first.

Who owns the QBR — the AE or the CSM? The CSM owns prep and runs the meeting; the AE owns the expansion play and the commercial conversation. Co-present. If only one shows, the meeting reads as either sales pressure or a support call — both weaken the account relationship.

How do we measure whether QBRs are working? Track three numbers quarterly: exec-sponsor attendance rate, the share of QBRs that surface a logged expansion opportunity, and the net-revenue-retention delta between on-cadence and off-cadence accounts. A clear NRR gap between the cohorts is the proof leadership needs.

Should we send the deck before the meeting? Yes, 24 hours ahead, with a note that the blocker slide is intentionally blank. Sending a pre-read with one open field forces the customer to engage before the call and sharply reduces last-minute cancellations.

Sources

• https://www.gainsight.com/guides/the-essential-guide-to-quarterly-business-reviews-qbrs/
• https://sixteenventures.com/customer-success-definition
• https://hbr.org/2015/11/why-customers-churn-and-what-to-do-about-it
• https://www.gaingrowretain.com/
• https://churnzero.com/blog/
• https://tomtunguz.com/
• https://www.forrester.com/blogs/category/customer-success/

Related on PULSE

• [The Expansion QBR — 60-Min Training](/knowledge/st0031)
• [The Customer Kickoff Meeting Reboot — 60-Min Training](/knowledge/st220)
• [The Customer Health Scoring Reboot — 60-Min Training](/knowledge/st208)
• [Upsell and Cross-Sell Scenarios: Roleplay for Existing Customer Growth](/knowledge/st0740)
• [Top 10 Customer Storytelling Templates for Sales Meetings](/knowledge/st0739)
• [Top 10 Challenger Customer training exercises for sales managers](/knowledge/st0530)