QBR prep in an hour, not a day

Watch a CSM build a QBR and most of the time is not spent on slides. It goes on opening the CRM, the ticketing system, the usage dashboard, three email threads and a couple of call recordings, and trying to remember which of it mattered.

One data point from a neighbouring world: a commenter on r/msp, who was selling reporting software, said the MSPs they spoke to spent between 2 and 8 hours preparing each QBR even after standardising their templates. Weigh that for what it is, a vendor describing the problem their product solves. The shape will still be familiar.

The template was never the slow part. Remembering was.

Every Friday, all quarter · Owner: CSM

One document per account, one line per entry, dated, with a link to wherever it happened. Four kinds of entry, and only four.

Asked: something the customer requested. Shipped: something you delivered. Promised: a commitment either side made, with a due date. Moved: a number that changed against a goal they care about.

That is the entire habit. Friday afternoon, five minutes per account, straight after you have closed the week's tickets while it is all still in your head. If you want a stricter definition of what counts as a promise, the commitment taxonomy is how we draw it.

The first two weeks feel pointless. By week six the log already holds more of the account's story than the CRM does.

Date        Type      Entry                                              Link
2026-07-03  Asked     Export of tickets by region for their Q3 board     ticket 4412
2026-07-10  Shipped   Regional export live, sent to ops lead             email
2026-07-17  Promised  Us: SSO for the second team by 2026-08-15           call 07-17, 14:32
2026-07-24  Moved     First-response time 9h to 5h, their Q3 target 4h   dashboard
2026-07-31  Promised  Them: name an admin for the second team by 08-07   call 07-31, 22:10

Quarter start · Owner: CSM

A usage chart proves the customer logged in. Their sponsor does not care. Their sponsor needs to walk into their own leadership meeting and explain why this renewal is worth defending, and a chart of daily active users does not help them do that.

So every QBR starts from the goal the customer stated when they bought: the success criterion in the handoff pack, if you ran a proper handoff. Where does it stand now, and what moved it?

If there is no stated goal on file, the first QBR has one job: get one, in their words, with a number and a date. We made the longer case for what counts as evidence in the room in customer evidence that survives a QBR.

Two weeks before · Owner: CSM

Email a four-line agenda two weeks out and ask what they want added. A QBR the customer helped shape is one they turn up to, and it tells you in advance what they are worried about, so nothing lands on you cold in the room.

Invite the sponsor, not only the day-to-day user. If the sponsor will not come, that is information too, and it belongs in the log.

It is also the right moment to ask whether quarterly is even the right rhythm for them. A CSM on r/CustomerSuccess put the question directly: does every customer really need to talk to you every three months? Some want it, some would rather have two good reviews a year than four thin ones. Ask.

One week before · Owner: CSM

Five slides. No more.

Open the log, filter to the quarter, and pick the three entries that moved their goal the most. Those are the story. Everything else stays in the appendix, or better, stays out.

The slide most teams skip is the fourth one, what is not working. Put it in anyway. It is the slide that makes the other four believable.

1. Your goal: what you set at kickoff, and where it stands today
2. What moved it: the three log entries that mattered most
3. Open commitments: ours and yours, each with a date
4. What is not working: named plainly, with the fix and its owner
5. Next quarter: three priorities, for you to agree or change

Owner: CSM

One CSM on r/CustomerSuccess described setting the expectation up front that a QBR is a quarterly audit: a hard look at what is working and what is not. That framing does most of the work for you. The customer stops waiting to be sold to and starts telling you things.

Spend the least time on slide two and the most on slides four and five.

Leave the meeting with next quarter's priorities written down and agreed, then put them straight into the log as Promised entries with dates. The next QBR is already half built before this one has ended.

The log dies the first busy week. It always does, because it is a separate task and separate tasks lose to urgent ones. The durable fix is to stop making it a task: draft the entries automatically from calls, tickets and email, and have the CSM approve or delete them on Friday instead of writing them. That is the version we build, and it is the same pattern as post-call execution.

How often a given account really needs a QBR is the question this playbook leaves with you. There is no right answer across a book of business, only a right answer per customer, and most teams never ask.

A QBR is not a presentation of your work. It is the meeting where your sponsor collects what they need to defend renewing you. Give it to them in their terms.