To prepare for a QBR, confirm the sponsor will attend, find one result in a measure they track, name the quarter's miss, map their next 90 days, and rehearse the opening out loud. Five working days is enough.
Most QBR prep goes into the deck. The account team pulls usage charts, support tickets and a roadmap slide, and walks in with forty slides and no idea what the sponsor wants from the hour. The plan below spends the week on the four things the sponsor will remember, and leaves the deck until last.
What QBR preparation involves
Preparing for a QBR means deciding, before the meeting, what the customer should leave believing and what you need to learn from them. The deck is a by-product of that work.
The account manager owns the prep. The customer success manager supplies the adoption and support detail, and a sales leader may review the plan for large accounts. For one account it takes about three to four hours spread across five working days. Spreading it matters, because the most useful inputs (the sponsor's confirmation, a reply from a user, a colleague's memory of the miss) take a day to come back.
The meeting itself is covered step by step in how to run a customer QBR. This piece is the week before it.
The five-day plan
Each day has one job. If the week gets squeezed, the order still holds, and day 5 is the one not to skip.
- Day 1Confirm the room
- Sponsor attending
- Agenda with one question
- Day 2Find the result
- One or two measures they track
- Day 3Name the miss
- What fell short and what changed
- Day 4Map the next 90 days
- Their priorities, other teams
- Day 5Say it out loud
- Opening, miss, pushback
1. Day 1: confirm the room and send the agenda
Email the sponsor to confirm they will attend, and ask who else should be there. If the sponsor says they will send a colleague instead, treat that as a signal about the account and ask for fifteen minutes with the sponsor before the QBR.
Send a short agenda with one question for the sponsor to think about: "What is your team being measured on next quarter?". It tells them the meeting is about their business, and it gives you the most useful input of the week.
2. Day 2: find the result in their measures
Pick one or two results from the quarter, expressed in a measure the customer already tracks. Dispatch rework, time to hire, cost per claim, days sales outstanding: whatever the sponsor's boss asks them about. Pull last quarter's starting point so the change is visible.
Usage figures belong on a supporting slide. A login count tells the sponsor the product is open, and nothing about whether it paid for itself. If you cannot find a result in their measures, that is the most important finding of the week, and the QBR should open by agreeing one.
3. Day 3: name the miss
Find what fell short this quarter: a late delivery, a support escalation, a feature that did not land, a target not hit. Write one sentence on what happened and one on what changed because of it.
You will name it first in the meeting, before the customer does. A miss the sponsor raises becomes the topic of the hour. A miss you raise, with the fix already in place, takes two minutes and earns trust for the rest of the meeting.
4. Day 4: map the customer's next 90 days
Collect what you know about the customer's next quarter: the sponsor's answer to the agenda question if it came back, anything said on calls with users, any news about the company. Note any reorganization, new leader or budget review.
Then list the other teams in the business that have the problem you solved for this one. These are the expansion conversations. Do not plan to pitch them. Plan to ask who runs each team and whether an introduction makes sense. The account plan template is a good place to keep this.
5. Day 5: say the opening out loud
Rehearse the first five minutes out loud: the opening line, the result, and the miss. Then rehearse the sponsor's likely pushback. Saying it out loud is the only way to find out whether it sounds like a person or a slide.
Build the deck last, from what the four days produced. Five to eight slides is usually enough: the agenda, the result, the miss and the fix, a slide of questions about the next 90 days, and next steps.
A worked example
This example is illustrative. An account manager is preparing a QBR with the operations director at Arrowmere, a 600-person logistics firm that uses her company's dispatch planning service.
Day 1. She confirms the director will attend and sends the agenda with the question about next quarter. He replies that his deputy will join too.
Day 2. She finds the result: dispatch rework down by a third since the spring, a figure the director reports to his own boss each month. She pulls the spring baseline.
Day 3. The miss is two delayed carrier integrations in August. She writes one line on why they slipped and one on the new testing step that has stopped it happening again.
Day 4. The director's reply to the agenda question arrives: his team is being measured on on-time delivery next quarter. She also notes that a user mentioned the warehouse team "has the same handoff mess". That goes on her list as a question for the meeting.
Day 5. She says the opening out loud and stumbles on the miss; her first version sounds defensive. She rewrites it as one plain sentence and says it three more times. Then she plans for the pushback she expects: "Why should we trust the next integration date?". The deck takes forty minutes and has six slides.
In the meeting she names the miss in the second minute and asks about the warehouse team in the thirtieth. The director offers an introduction.
Where it goes wrong
Starting with the deck. If the first day goes on slides, the slides will be about your product. Build the deck on day 5 from what the week found.
No result in their measures. A QBR built on usage charts gives the sponsor nothing to repeat to their boss. If there is no measure they track, agree one in the meeting.
Hiding the miss. Customers remember the miss whether you mention it or not. Leaving it out means the sponsor raises it, and then it runs the meeting.
Skipping the rehearsal. The opening that reads well in notes often sounds stiff out loud. Five minutes of rehearsal is the cheapest fix in the whole week.
Planning a pitch. A QBR that turns to the other teams with a slide of products feels like a sales call. Plan questions about who runs those teams, and let the introduction come from the sponsor.
When the sponsor has changed
A new sponsor changes the week. The person who bought the service may have left, and their replacement has no stake in the decision and no memory of the problem it solved.
Move day 4 to the front. Before anything else, find out what the new sponsor is being measured on and what they said in their first weeks in the role, from users, from the old sponsor if they are still at the company, or from any public announcement. Then ask for a short introductory call before the QBR, so the first meeting is not also the review.
On day 2, explain the result from the beginning: the problem the customer had, the measure it showed up in, and where that measure stands now. The new sponsor will judge the relationship on whether it helps with their own targets, so the questions about the next 90 days carry more weight than usual. Treat the QBR as the start of a new relationship with a history attached.
Preparing every QBR on the book
An account manager with forty accounts runs more than a hundred QBRs a year, and few of them get five days of prep. The day most often dropped is day 5, because rehearsing needs someone to rehearse with.
On Replicate Labs, account managers do day 5 on a call with Caty: they talk through the account, the result and the miss, say the opening out loud, and plan for the sponsor's pushback. Typing is there for when talking is not possible. The approach is under drive deal execution, and the account expansion guide shows where the QBR sits in the year. To get every QBR prepared this way, talk to us.
FAQ
How far in advance should you prepare for a QBR?
Start five working days before the QBR. That leaves time for the sponsor to confirm, for their answer to the agenda question to come back, and for a rehearsal on the last day.
What should a QBR deck include?
A QBR deck should include the agenda, one or two results in the customer's own measures, the miss and its fix, questions about the next 90 days and next steps. Five to eight slides is usually enough.
What data do you need for a QBR?
You need one or two results in a measure the customer tracks, with last quarter's starting point, plus the quarter's support and delivery history. Usage figures go on a supporting slide.
Who should prepare the QBR?
The account manager owns QBR preparation, with the customer success manager supplying adoption and support detail. For large accounts, a sales leader can review the plan on day 4.
How do you prepare a QBR when the results are bad?
Open with the miss, say what caused it and what has changed, then agree a measure for next quarter. Sponsors forgive a bad quarter more readily than a meeting that pretends it was good.