Running a QBR That Customers Actually Look Forward To
The QBRs I've seen go sideways all look the same. Forty slides. Three vendor logos on the title page. A CSM and a sales engineer talking at the customer for 50 minutes about logins, seats provisioned, and feature adoption percentages. A "leadership update" slide nobody asked for. The customer's executive sponsor "had a conflict" (again), so the meeting is two ops managers nodding politely while waiting for it to end.
That's the QBR most CSMs are still running. And it's why they keep losing accounts they thought were healthy.
A great QBR earns the renewal months before the renewal conversation starts. It's the only recurring meeting where you can put outcomes, ROI, and the forward roadmap in front of the people who actually sign the check. Skip it, phone it in, or fill it with usage charts and you've handed your competitor a window, usually one they're already prepping a deck for.
This is the playbook for running a QBR your customer's executives clear their calendar for. Not because they have to. Because the last one was useful.
The Mental Model: A QBR Is a Renewal Conversation in Disguise
Before any agenda or template, get the framing right. A QBR is not a status update. It is not a product demo. It is not a relationship-maintenance meeting where you swap LinkedIn pleasantries and call it a partnership.
A QBR is the renewal conversation, run quarterly, in disguise.
That changes everything about how you prepare. If the renewal is the real meeting, then the only questions worth answering on the day are:
- Did this customer get the outcome they were promised?
- Can we prove it in numbers their CFO will accept?
- What's the next outcome they'd commit to in the next 90 days?
- Is the right executive in the room to commit to it?
Every minute you spend on usage charts is a minute you didn't spend on those four questions. CSMs who internalize this run shorter QBRs, smaller decks, and bigger renewals. The teams still relying on a default 40-slide template tend to renew at list, lose on price, and get blindsided by the customer "going in a different direction" three months later.
Pre-QBR (T-3 Weeks): Build the ROI Math First, Not the Slides
Most CSMs build the deck first and try to back-fill the ROI in the last week. That's how you end up with a "value realized" slide that says "increased efficiency" with no number next to it.
Flip the order. Three weeks out, before you open the slide template, build the ROI calculation. The deck is the wrapper; the math is the meeting.
Here's the ROI template I use. Four lines, each with an input field tied to the customer's own data:
ROI Calculation Template
| Line | What it measures | How to source it |
|---|---|---|
| 1. Hours saved | Process cycle-time reduction times the loaded hourly cost of the people doing the work | Workflow logs, before/after baseline from the customer's own ops team |
| 2. Revenue influenced | Pipeline or closed-won revenue touched by the workflows you enabled | CRM, attribution data the customer already trusts |
| 3. Cost avoided | Headcount the customer didn't hire, tools they retired, contracts they didn't renew | Procurement, the customer's own CFO office |
| 4. Risk reduced | Compliance issues caught, errors prevented, SLAs hit (translated to dollars where possible) | Audit logs, incident tickets, internal reports |
Total realized value = sum of the four lines. Total annual contract value = whatever they're paying you. ROI = (realized value − ACV) / ACV.
Worked example for a mid-market CRM customer paying $48,000/year:
- Hours saved: 12 sales reps each save 4 hours/week on pipeline updates. 12 × 4 × 50 weeks × $75 loaded hourly cost = $180,000
- Revenue influenced: Faster quote-to-cash cycle accelerated $1.2M in pipeline; conservative 8% revenue lift attribution = $96,000
- Cost avoided: Customer retired a $24K/year reporting tool because dashboards replaced it = $24,000
- Risk reduced: Three compliance flags caught early, estimated remediation cost avoided = $30,000
Total realized value: $330,000 on a $48,000 contract. ROI: 588%.
That's the slide. One slide. With four numbers, four sources, and a ratio. If you can't build this slide three weeks out, you don't have a QBR. You have a status update with a fancy name. Either get the data or push the meeting.
Once the math is built, send the customer a one-page "what we'll cover" doc. Not the deck. A one-pager: the four ROI inputs, the proposed agenda, two or three "asks" you'll bring up. Then ask them what they want added. This single email turns the QBR from your meeting into theirs. The CSMs who do this consistently see executive-sponsor attendance rates jump 20-30 points within two quarters.
Pre-QBR (T-1 Week): Confirm the Executive Sponsor in Writing
A QBR without the economic buyer is a status update. Full stop.
One week out, send a calendar confirmation to the executive sponsor specifically. Not a forward, not a "looping you in." A direct note that says: "Quick confirm you're joining the QBR on [date]. We'll spend 30 of 60 minutes on the ROI math your team and ours built together. Worth your time."
If they decline or go silent, do not run the QBR with their delegate as a substitute. Reschedule. I know that sounds aggressive. It isn't. The single biggest predictor of churn I've seen across hundreds of accounts is "executive sponsor stopped showing up to QBRs and we kept running them anyway." You're training the relationship to function without the buyer. The buyer eventually decides they don't need you either.
The exception: if the sponsor genuinely can't make it but designates a clear delegate who has decision-making authority for the next quarter, run it, but get a written commitment from the sponsor for the next QBR before you accept.
Executive-Sponsor Invite Email Script
Use this verbatim or close to it. Short. Outcome-led. Pre-read attached:
Subject: QBR — [Customer name] / [Vendor name] — 60 min on outcomes, not usage
Hi [Sponsor first name],
Quick note to confirm you for our QBR on [date / time]. Sixty minutes. The agenda:
- 10 min — Recap of what we committed to last quarter and what shipped
- 30 min — The ROI math we built with [Champion name]'s team. Headline: realized value of $ against an ACV of $[Y]. We'll walk you through the four inputs and the sources.
- 20 min — What we want to do together next quarter, what we need from you to make it happen
One-page pre-read attached. If anything's missing or you'd like to swap a topic in, send it back to me by [date] and I'll work it into the deck.
Looking forward to it.
[CSM name]
What this email does: it tells the executive the meeting is about their money, not your product. It tells them you've done the work with their team already. It gives them a way to shape the agenda before the meeting starts. Executives clear their calendar for meetings about their money. They send delegates to meetings about your product.
The 60-Minute QBR Agenda (10/30/20)
This is the agenda. Run it. Stop adding slides.
10 minutes — Recap
Where we were last quarter. What we committed to. What shipped. Fast.
No usage charts. No screenshots of the product. Three bullets:
- We committed to [outcome A]. We delivered. Here's the evidence.
- We committed to [outcome B]. We're 80% of the way. Here's what's outstanding.
- We committed to [outcome C]. We missed. Here's why and what we're doing about it.
If you can't fill in those three bullets honestly, including the miss, you don't trust your customer enough to run a real QBR with them. Fix that before the meeting, not in it.
30 minutes — Outcomes and ROI
This is the meeting. Most CSMs spend 5 minutes here and 30 on usage. Flip it.
Walk through the four-line ROI math. Slow. One line at a time. Show your sources. Invite the sponsor and champion to push back on any of the numbers, and mean it. The first time a customer pushes back on your "hours saved" calculation and you adjust it on the spot, you go from vendor to advisor. That single shift is worth more than any slide in the rest of the deck.
End the section with the headline: "Realized value of $X against an ACV of $Y. ROI of [ratio]." Pause. Let the executive sponsor sit with the number. Don't fill the silence. The CFO mental math happens in that quiet five seconds.
20 minutes — Forward Roadmap and Asks
Next quarter's goals. What you need from them. What they need from you. End with explicit next steps and named owners.
Specifically, make at least one of your asks a non-product ask:
- "We'd like 30 minutes with your data team to scope a use case in their domain."
- "We'd like to bring [your CTO] and [their CTO] together for a working session."
- "We'd like a written intro to your peer at [related business unit]."
Non-product asks expand the relationship surface. They also test how strong your sponsorship really is. A sponsor who won't make a 15-minute introduction is a sponsor who isn't going to fight for your renewal in procurement.
Close the meeting with a slide titled "What we agreed to today." Three to five bullets. Names against each. Dates. That's the slide that gets recycled into the post-meeting recap email and the action-item tracker. If you can't fill out that slide in real time, the QBR didn't actually accomplish anything.
Post-QBR (Within 24 Hours): The Recap Email
Send this within a business day. Same day if possible. The 24-hour window is when the meeting still has memory; after that, you're translating a meeting your customer half-remembers.
Subject: QBR recap — [Customer name] — actions and owners
Hi [Sponsor], [Champion], [Others],
Thanks for the time yesterday. Sending the recap while it's fresh.
What we covered
- Realized value of $ against an ACV of $[Y]. Full ROI breakdown attached.
- Next-quarter focus: [outcome A] and [outcome B], with [outcome C] as a stretch goal.
What we agreed to do
- [Action 1] — owner: [Name from customer], by [date]
- [Action 2] — owner: [Name from us], by [date]
- [Action 3] — owner: [Name from customer], by [date]
Tracker
Live action-item tracker here: [link]. I'll update it weekly. You'll see edits in real time.
Anything I missed or got wrong, send it back and I'll correct it. Otherwise, I'll see you on the action-item check-ins on the dates above.
[CSM name]
Three things to notice. First, every action has a single named owner, not a team, not a function. Second, the tracker is a shared doc, not a slide deck. Slides are theater; a doc that updates in real time is operational. Third, you proactively invite corrections. That sentence ("anything I missed or got wrong, send it back") pulls the customer into the record-keeping. They start to treat the tracker as theirs.
Post-QBR (7-Day Follow-Up): Check the First Action Item
Customers judge you on follow-through, not slides.
Seven days after the QBR, check in on the first action item that was due. Not all of them. The first one. Specifically, send a short note that says: "Following up on [Action 1] — anything blocking on our side? Happy to push it through if so."
If it's done, great. Log it in the tracker, move on.
If it's stalled, you've just discovered the real friction in the account, seven days into the quarter instead of 80 days into it, when you would have walked into the next QBR with three open actions and an awkward silence. That early signal is worth more than any health-score dashboard.
The CSMs whose accounts renew quietly are the ones who do this 7-day check-in religiously. The ones who don't tend to find out about problems at the next QBR, when it's too late to fix them before the renewal cycle starts.
The Action-Item Tracker (Structure, Not a Slide)
The tracker is a shared doc (Notion, Confluence, a Google Doc, whatever the customer already uses). Six columns:
| Column | Notes |
|---|---|
| Action | Specific. "Schedule data team intro" beats "explore data team opportunity." |
| Owner | One named person. Not "the team." |
| Due date | A specific Friday, not "Q2." |
| Status | Open / In progress / Done / Blocked. Update weekly. |
| Last update | One sentence. Date the update. |
| Linked outcome | Which next-quarter goal this action serves |
Six columns. No statuses like "monitoring" or "pending." Either it's moving or it isn't. The discipline of forcing every action into a Done/Blocked binary by the next QBR is what separates real CS work from coordination theater.
Common Pitfalls
I've seen all of these in the field. They're more common than the playbook above.
Presenting usage stats instead of outcomes. Logins, seats provisioned, feature adoption percentages: none of this matters to a CFO. A CFO does not care that 92% of seats are active. A CFO cares that you saved $330K against a $48K spend. If your deck has more usage charts than ROI lines, you're in a status meeting, not a business review.
No executive sponsor present, and accepting "they're busy" as a permanent answer. This is the slow leak that sinks accounts. If your sponsor has missed two QBRs in a row, you have a sponsorship problem, not a calendar problem. Escalate it directly: "I want to make sure we're delivering enough value to your level of the org. Is the QBR working for you, or should we restructure it?" Better an awkward conversation now than a "we've decided to go in a different direction" email at renewal.
Leaving with "let's stay in touch" instead of named owners and dates. The QBR ends with a slide titled "What we agreed to today" or it didn't happen. "We'll connect on this" is not an action item. "Sarah will send the data-team intro by Friday" is.
Treating the QBR as a sales pitch for the next module. This kills trust in one slide. If the executive sponsor smells a pitch, they tune out for the rest of the meeting and likely the next one too. Cross-sell happens in dedicated discovery calls, not bolted onto the QBR. The closest you should get is a "what's next" slide with one line that says, "If [outcome A] lands well, we should explore [adjacent module] next quarter — separate conversation."
Running the same QBR template across all accounts. A $1M strategic account and a $30K SMB account do not get the same agenda. Strategic accounts often need a 90-minute QBR with two executives, an exec from your side, and a forward-looking strategy section. SMBs need a 30-minute outcome-and-roadmap call. Match the format to the relationship, or you'll over-invest in accounts that don't need it and under-invest in accounts that do.
Measuring Whether Your QBRs Are Actually Working
Four metrics. Track them quarterly.
- QBR attendance rate — target 90%+ of scheduled QBRs actually happen on time. Below 90% means you're letting customers reschedule too easily.
- Executive-sponsor presence rate — target 75%+. Anything below that means you're running glorified status meetings with delegates who can't commit on behalf of the buyer.
- Post-QBR action items closed within 30 days — target 80%+. This is the leading indicator that the QBR was real. Action items closed at 80%+ within 30 days is the signal your renewal cycle is going to be quiet. Action items stuck at 30% closure is the signal you're going to be in escalation mode by month two.
- Net Revenue Retention on accounts with QBRs vs. without — the only metric your CFO will fully care about. If the gap isn't at least 10-15 NRR points, your QBRs aren't pulling their weight, and you should cut frequency or reformat them entirely.
The teams that hit those four numbers don't have surprise churn. The teams that don't, do. It really is that simple.
Where Rework Fits
A QBR is operationally three artifacts: the ROI calculation, the live action-item tracker, and the running record of what each customer has been promised. Most CSMs juggle these across three tools: a spreadsheet for the math, a Google Doc for the tracker, and Slack DMs for the promises. Three places. None of them talk to each other. Action items quietly fall off. Promises get repeated to the next QBR's audience because nobody remembered the last one.
Rework Work Ops is built for this. Action items are tracked tasks with named owners and due dates, attached to each customer account. ROI inputs and source links live in the same record, so the math from QBR Q1 is one click away when you're prepping QBR Q2. The 7-day follow-up triggers itself. And Rework CRM keeps the QBR cadence, exec-sponsor presence rate, and NRR-by-account view in front of CS leadership so the patterns surface before they become escalations. Work Ops starts at $6/user/month, CRM at $12/user/month.
If you're hiring CSMs and want a job description aligned to the playbook above, the Customer Success Manager job description template is a good starting point.
Related Reading
- Customer Onboarding: The First 30 Days That Determine NRR
- Expansion and Upsell Without Becoming a Salesperson
- CSM Metrics That Actually Matter: NRR, GRR, and Health Scores
- The CSM Tech Stack: Tools That Earn Their Seat
The QBRs your customers actually look forward to aren't the ones with the slickest decks. They're the ones where the customer walks out with a number they can take to their CFO and an action plan with their name on it. Build the math. Confirm the executive. Run the 10/30/20. Send the recap in 24 hours. Check in at day 7.
Do that for four quarters in a row and you'll stop having renewal conversations. The renewal will already be done.

Principal Product Marketing Strategist
On this page
- The Mental Model: A QBR Is a Renewal Conversation in Disguise
- Pre-QBR (T-3 Weeks): Build the ROI Math First, Not the Slides
- Pre-QBR (T-1 Week): Confirm the Executive Sponsor in Writing
- Executive-Sponsor Invite Email Script
- The 60-Minute QBR Agenda (10/30/20)
- 10 minutes — Recap
- 30 minutes — Outcomes and ROI
- 20 minutes — Forward Roadmap and Asks
- Post-QBR (Within 24 Hours): The Recap Email
- Post-QBR (7-Day Follow-Up): Check the First Action Item
- The Action-Item Tracker (Structure, Not a Slide)
- Common Pitfalls
- Measuring Whether Your QBRs Are Actually Working
- Where Rework Fits
- Related Reading