QBR Agenda Template: A 45-Minute Customer Review That Ends in Decisions

Start by asking what the customer should be able to decide after the meeting. They may need to approve a rollout, change a target, assign an owner or decide which problem deserves attention first. If there is no meaningful decision, a written update may be enough.

Asana’s QBR agenda guidance distinguishes customer reviews from internal reviews and connects performance, goals and follow-up. The schedule below is our own shorter working format.

Agree on the purpose with the customer contact. An invitation that says “review the quarter” gives little reason for a busy decision-maker to attend. An invitation that names a decision and the input needed is easier to assess.

Share the agenda and the short evidence summary in advance. The timings are an example, not a rule. Assign a facilitator who can keep the discussion focused and reserve the final ten minutes for commitments.

Start with the outcome in the customer success plan. Show the starting point, the target and the latest result using the same definition. Explain which result is measured and which conclusion still needs customer confirmation.

For a reporting product, usage may show that a dashboard is opened weekly. That is useful context, but the customer’s goal may be to prepare reliable decisions with less manual work. Include evidence about the actual reporting process rather than filling the review with feature counts.

Put detailed support history, usage breakdowns and technical notes in the pre-read or appendix. Bring a detail into the conversation when it changes the decision. This keeps the meeting understandable for people who do not work in the product every day.

Consider a fictional customer whose goal was to get six regional teams using a shared planning process. Four teams now use it. The other two lack a manager who can approve the new process. A product training session for everyone would not solve that ownership problem.

The QBR decision could be to appoint the missing regional owners before expanding training. Record the current result as four of six, explain the obstacle and agree who can resolve it. Avoid presenting the target as achieved because the four active teams generate a large amount of usage.

If the customer’s priorities have changed, revise the target with them. A smaller agreed scope can be a sound decision. Preserve the reason and date of the change so a later review can distinguish a deliberate adjustment from unfinished work.

A useful follow-up for the example might read: “We agreed to appoint owners for the two remaining regions before scheduling training. Jordan will confirm the names by Tuesday. Priya will then offer a working session. We will review readiness on Friday.” The names and timing are illustrative.

Keep the decision separate from the task. “Expand adoption” is a direction. “Jordan confirms the two owners by Tuesday” is an action. If the person who can make that commitment is absent, label it as a proposal and ask for confirmation.

Use the stakeholder map to check who needs to attend next time. Inviting more people is less useful than including the person who can resolve the specific dependency.

Send the short decision log promptly and update the shared plan. Track whether commitments were completed, whether they helped and whether a new issue requires an earlier conversation. The next QBR should build on those decisions rather than rediscover them.

A quarterly review is one part of the relationship. A current support incident, a missing owner or an approaching commercial deadline may need action before the next meeting. Our guide to what to monitor between QBRs covers that separate operating need.

Judge the meeting by the clarity and usefulness of its decisions. A polished deck can support the conversation, but the customer should leave knowing what changed, who owns the next step and when progress will be checked.