Turning the QBR Into an Expansion Meeting, Not a Check In

Starting a QBR with a list of what shipped last quarter puts the meeting in your frame instead of theirs. Open instead by restating what the buyer told you their goals were for this period, and ask whether that is still accurate, since priorities shift and a QBR built around stale goals feels disconnected from the start. Anchoring the meeting in their language rather than your roadmap makes the rest of the conversation, including any ask, feel like a continuation of what they already care about rather than a pitch.

A slide full of every metric your product tracks is not insight, it is homework for the buyer. Pick two or three data points that connect directly to the goals you opened with, and frame each one as a finding: what happened, why it matters to them, and what it suggests as a next step. If your usage numbers show a team bumping against a limit or under using a feature tied to their stated goal, that finding is the natural bridge into the expansion conversation, not a separate topic bolted on afterward. Pull the data a day or two ahead of the meeting rather than the morning of, so there is time to actually think about what it means instead of just exporting a chart.

If the expansion ask is something you decide to bring up in the moment depending on how the meeting feels, it usually will not happen, because nobody wants to shift the tone of a relationship meeting into a sales pitch on the fly. Decide before the meeting whether there is a genuine ask this quarter, based on real usage signals, and if so, put it on the agenda explicitly, even just as a line like reviewing plan fit for the year ahead. A planned ask lands as a natural part of the conversation. An improvised one usually lands as a pivot the buyer notices.

Run the meeting in this order:

1. Open by restating the goals the buyer gave you for this period, and ask whether they are still accurate.
2. Present two or three usage findings tied to those goals, each framed as what happened, why it matters and what it suggests.
3. Raise the planned ask, such as reviewing plan fit for the year ahead, as a natural follow on to those findings.
4. Read back every commitment on both sides, with an owner and a rough date, before the call ends.

QBRs generate action items on both sides, and the ones that do not get an explicit owner and date rarely get done. Before the call ends, read back every commitment made, who owns it, and roughly when it will happen, on both sides of the table. This closes the loop on your side and also holds the buyer gently accountable for anything they committed to, which matters if part of your ask depends on them taking an internal step, like introducing you to another department.

Not every quarter is the right quarter to ask for more. If the account is dealing with a support issue that has not fully resolved, a champion transition mid process, or a rocky quarter internally on their end, pushing an expansion ask into that meeting reads as poor timing and can cost more trust than the potential deal is worth. In those quarters, the right move is a genuinely useful review with no ask attached, which protects the relationship for the ask that will land better next time. A CSM who can tell the difference between a quarter to push and a quarter to simply show up well is worth more to long term retention than one who treats every review as an equal opportunity to sell.

For example, a customer whose main sponsor just resigned and whose support ticket is still open does not need a plan fit conversation. A better agenda shows the status of the support fix, confirms who the new day to day contact is, and closes with a note that you will revisit growth next quarter. A common mistake is treating the skipped ask as lost revenue, when it is closer to protecting it. A decision rule: if the customer would have to rebuild trust before hearing your recommendation, hold the ask, deliver something clearly useful, and put the ask on the next agenda.