The QBR is on the calendar for Thursday. On Tuesday afternoon the account manager opens last quarter's deck, duplicates it, and starts replacing numbers: seats active, logins, tickets closed, adoption by feature. By Wednesday night the deck is 22 slides, the renewal date is on slide 3, and the expansion slide says "Opportunities: Module B, additional seats." Nobody in the room will ask why Module B, and nobody on your side will have an answer if they do.
That last slide is where the quarter's expansion gets raised or does not. It usually does not, and the reason is not effort. Every QBR preparation checklist in circulation tells you to gather data from inside the relationship: usage, health score, support history, goals from the last review. That data proves the customer is getting value. It cannot tell you what changed at the customer, and a change is the only thing that turns "you should also buy Module B" into a conversation the buyer wants to have.
This checklist keeps the parts of QBR prep that work and adds the part most teams skip: the evidence for the expansion ask, gathered from outside your own dashboards and put on the slide, not left in the account manager's head.
Why the expansion slide is the weakest slide in the deck
Expansion is no longer a side motion. In Benchmarkit's 2025 SaaS Performance Metrics, expansion from existing customers made up a median 40% of total new ARR, up five points in a year. The same report put the median Expansion CAC Ratio at $1.00 of sales and marketing spend per $1.00 of new ARR, against $2.00 for new customers. Growing an account you already serve costs half as much as landing a new one.
The older version of the same argument is Amy Gallo's summary in Harvard Business Review: acquiring a new customer costs five to 25 times more than keeping an existing one, and Bain's Frederick Reichheld found that a 5% lift in retention raised profits by 25% to 95%.
So the QBR, the one scheduled hour where the economic buyer is in the room, should be the best-prepared expansion conversation you have all quarter. Read the guides that rank for this topic and you see why it is not. Gainsight's QBR guide lists executive summary, metrics, ROI, progress against goals, benchmarks, health and next steps, and says only that in some cases the QBR might be a good time to bring up expansion. ChurnZero's guide warns, correctly, against building the meeting around the upsell you want to promote.
Both are right about what they cover. Neither tells you to look at what happened at the customer's company since the last review. The result is a deck that is thorough about the past and silent about the reason to buy more now. When the expansion slide has no reason on it, the account manager either skips it or pitches it cold, and the buyer hears the pitch the guides warned about.
The reason test: what every expansion line has to pass
An expansion opportunity is worth putting in front of a buyer when you can answer three questions about it:
- What changed? A new leader, a new region, a hiring push in the team your other product serves, a funding round, a product launch, a system they announced they are replacing.
- Where did you see it? A link: the press release, the job posting, the earnings call, the LinkedIn announcement. Not "I heard."
- When did it happen? A date, and a recent one. A reorganization from two years ago is background, not a reason.
No answer to all three, no expansion line. That rule does two things. It removes the generic "Opportunities" slide that makes QBRs feel like a sales call, and it forces the account manager to find something specific enough that the buyer will want to talk about it. "You opened a Dallas office in August and posted eleven support roles there" is a sentence a VP of Customer Support engages with. "Have you considered our workforce management add-on" is not.
The same test works for prospecting. We wrote it up for new accounts in trigger events in sales. The difference at a QBR is that you already have the relationship, so the bar for the reason is lower and the payoff is higher.
The QBR preparation checklist
Three weeks is enough lead time for most accounts. Compress it for smaller ones. The first two phases are standard and every good template covers them. The third is the one that decides whether expansion happens.
Three weeks out: the relationship
- Confirm the date and the attendees on both sides. If the economic buyer declined last time, find out why before you send the invite.
- Ask the customer what they want from the session. One email: what is top of mind for your team this quarter? Their answer is often the first expansion clue you get.
- Re-read the notes and action items from the last QBR. Mark each one done, in progress or dropped.
- Check the renewal date and any open commercial terms.
Two weeks out: the value you delivered
- Pull usage, adoption by feature and seat utilization. Look for the teams that use the product heavily and the ones that barely touch it.
- Pull support history. A ticket spike in one area is either a risk or a product gap you can fill.
- Tie results to the goals the customer set, in their numbers where possible, not yours.
- Write the one-paragraph health story you would tell their CFO.
Ten days out: what changed at the customer
This is the phase most checklists leave out, and it is where the expansion evidence comes from.
- List every product you sell that this account does not own. For each one, write down which problem it solves and who at a company feels that problem.
- For each product, look for a change at the customer since the last QBR that makes that problem bigger: hiring in the team that feels it, a new executive who owns it, an expansion into a region or segment, a funding round, an announced initiative, a tool they said they are replacing.
- Run every finding through the reason test. Keep the ones with a what, a where and a when. Drop the rest, including the ones you like.
- Check who owns the change. The new VP of Operations is often not in your CRM, and the person you usually meet may not be the one who buys the second product.
- Rank what is left. One strong reason beats three weak ones. If nothing passes, the expansion slide is empty this quarter and you say so internally, which is also useful.
One week out: build and rehearse
- Put the expansion evidence in the deck itself: the change, the source link, the date, and the question you want to ask about it.
- Share the draft with the account executive or whoever owns the commercial side, so the ask is agreed before the meeting, not improvised in it.
- Rehearse the transition from the value section to the change section. It should sound like "here is what we did together, and here is something we noticed about where you are going."
What the expansion slide should look like
The slide should read as observation first and offer second. Compare two versions for a customer who bought a support platform and does not own the workforce management module:
| Element | The usual slide | The slide that passes the reason test |
|---|---|---|
| Headline | Growth opportunities | Your support team is growing in Dallas |
| What changed | Not stated | New Dallas office announced, eleven support roles posted since August |
| Where it was seen | Not stated | Company press release and careers page, linked |
| When | Not stated | August and September this year |
| Why it matters to them | Unlock more value | Scheduling across two sites and time zones is the problem the workforce module solves |
| The ask | Let's schedule a demo | How are you planning to staff and schedule the new site? |
The second version does not pitch. It asks a question the buyer is already thinking about, and it proves you were paying attention. If the answer is "we have that covered," you learned something and lost nothing. If the answer is "honestly, not well," the expansion conversation starts itself.
Notice what the second version needed: a product-to-problem map and a fresh, sourced fact about the customer. That is the same pairing covered in cross-sell vs upsell, and it is the difference between a whitespace grid and a reason. The grid in account whitespace analysis shows you which cell is empty. The reason tells you why to raise it this quarter.
Where this breaks: the book of business, not the single account
An account manager can run the ten-days-out phase by hand for one strategic account. It takes an hour or two of reading press releases, job boards and LinkedIn, with a list of your products open in another tab. The trouble is the rest of the book. A CSM with 40 accounts and a QBR cadence is preparing three or four reviews a week, and the external research is the first thing cut when the week gets busy. The deck still ships, full of usage charts, with an empty or generic expansion slide.
That is the gap PitchSmart was built for. Put the contacts at those accounts on a list and it researches each one against every product you sell, then returns a plan per account: which product to lead with, the buying signals behind that call with a source on each one, who to contact, and what to say. It is allowed to say hold or skip when nothing has changed, which is the reason test applied for you. The account manager still owns the relationship and the meeting. The research that fills the expansion slide is done before the prep starts.
Whether you do it by hand or not, the rule is the same. For a broader view of running expansion across a book, see the customer expansion playbook and net revenue retention strategy.
Common mistakes when preparing a QBR
- Reporting what the customer can already see. If the usage chart is on their admin dashboard, one summary line is enough. Spend the slides on what they cannot see.
- Treating the health score as the story. A green score says the product is working. It says nothing about whether the customer's needs have grown past what they bought.
- Pitching without a trigger. An add-on offered with no change behind it is the "thinly veiled upsell" every guide warns about. The fix is a reason, not a softer tone.
- Researching only the person you meet. Changes that create expansion often sit in another department, under a leader you have not met yet.
- Keeping the evidence in your head. If the reason is not on the slide with its source, it will not survive the meeting, the handoff to the AE, or the next CSM on the account.
After the QBR
Send the deck the same day with the action items at the top. For any expansion thread that opened, write down who owns it, what the customer said, and the date you will follow up. For any reason that did not land, note why. "Already solved in-house" and "budget frozen until Q2" are both findings, and the second one tells you when to raise it again.
Then start the next quarter's list of changes. The best QBR preparation is not three weeks of work before the meeting. It is a running record of what changed at each account, with a source and a date on every line, so the expansion slide is half written before the invite goes out.
