QBR Meeting Agenda: Run an Evidence-Based Customer Review, Not a Slide Recital

A useful QBR meeting agenda helps the customer and provider interpret evidence, make decisions and commit to the next period. It is not a quarterly excuse to read charts aloud. Participants should leave knowing what changed, what remains uncertain, which risks matter and what each side will do next.

This page addresses the customer business-review format. It differs from meeting note templates, which provide general capture structures, and from an onboarding kickoff, which aligns a relationship before delivery begins.

Define the QBR decision outcome

Start by writing the decisions the meeting should enable. Examples include whether to expand a pilot, change an adoption plan, retire a low-value workflow or prioritize a new stakeholder group. If no decision or strategic adjustment is possible, a shorter operational review may be more appropriate.

Frame the outcome around customer value: “Review evidence against the agreed outcomes and choose the two priorities for next quarter.” Avoid provider-centric goals such as “show account activity” or “present the roadmap.”

Build the pre-read from verified evidence

Send a short pre-read several working days before the meeting. It should contain definitions, sources and limitations, not only polished graphs. Include:

• the customer’s stated priorities;
• previous decisions and commitments;
• outcome measures and their baseline;
• material changes in scope or context;
• unresolved risks and assumptions;
• decisions requested in the QBR.

Do not surprise the customer with disputed data. Ask the relevant owners to validate figures and interpretation first. A generated narrative can assist drafting, but humans must verify every consequential claim.

Copy this 60-minute QBR meeting agenda

QUARTERLY BUSINESS REVIEW — 60 MINUTES

Purpose:
Decisions required:
Facilitator:
Customer decision owner:
Note owner:

1. Priorities and context changes — 7 min
2. Previous commitments — 8 min
3. Outcome evidence and limitations — 15 min
4. Gaps, risks and lessons — 10 min
5. Next-quarter outcomes and options — 10 min
6. Decisions, actions and owners — 10 min

Pre-read sent:
Evidence cutoff date:
Next review:

Protect the final ten minutes. If evidence discussion runs long, assign an owner to investigate rather than sacrificing decisions and ownership.

Reconfirm the customer’s priorities

Ask what changed in the customer’s organisation, market or operating constraints. A metric can improve while becoming less relevant because the business priority moved. Conversely, a difficult quarter may make the original outcome more important.

Use the customer’s current language, and distinguish their statement from your interpretation. Do not speculate about internal politics or individual performance. Record only context needed for the relationship and handle sensitive information according to appropriate access and retention rules.

Review previous commitments before new ideas

Display the last review’s actions with owner, due date and current evidence. Use four honest states: completed, changed, blocked or not completed. Explain changes without rewriting history.

A missed action is not automatically failure by one person. Check whether dependencies changed, ownership was ambiguous or the action no longer served the customer outcome. The action-item ownership guide can tighten the recording and verification loop.

Present outcomes with limitations visible

Each metric needs a definition, period, source and comparison point. Separate product usage, operational output and business outcome. Increased logins may be useful adoption evidence, but it does not by itself prove customer value.

Use a compact evidence card:

Outcome question:
Measure and definition:
Baseline / comparison:
Current period:
Data source:
Known limitation:
Interpretation:
Decision this evidence informs:

Avoid fabricated benchmarks and decorative percentages. If the sample changed or data is incomplete, say so. The SMART goals examples show how to add measures and guardrails without pretending uncertainty disappeared.

Discuss gaps and risks without blame

Name the gap between desired and observed results, then explore plausible causes and missing evidence. Invite the customer to correct the interpretation. Keep “what we know,” “what we infer” and “what we will test” separate.

For each material risk, agree a trigger and response. “Adoption risk” is too vague. Better: “If fewer than two pilot teams complete the agreed workflow by 15 September, customer owner and CS will review access barriers and choose whether to extend or narrow the pilot.”

Turn the next quarter into choices

Present two or three credible options with tradeoffs rather than a long wish list. For example: deepen adoption in the current team, expand to another team or pause expansion to fix a workflow dependency.

For each option, state expected outcome, required effort, dependencies, uncertainty and what would cause a change of course. Do not present product roadmap ideas as confirmed commitments unless the authorized source supports that status.

Facilitate participation, not a performance

Send routine updates in the pre-read and use live time for interpretation. Ask the customer decision owner to respond before internal specialists add detail. Use pauses and explicit turn-taking so remote and quieter participants have a clear route into the discussion.

Accessibility needs vary. Share readable material in advance, describe important visuals verbally, avoid relying on colour alone and offer a way to contribute asynchronously. These steps improve access but do not guarantee compliance with every accessibility requirement.

Capture the conversation only by agreement

For an in-person QBR, recording may help create a reviewable source when all participants have been informed and agreed. Explain purpose, access, retention and the non-recording alternative. Applicable legal, workplace, customer and privacy requirements depend on context.

Need a source for an explicitly agreed in-person review? Kuno supports visible conversation capture and draft notes that responsible humans can check before use. Explore Kuno

Do not use recording analysis to infer sentiment, rank employees or automate renewal decisions. Verify the record and base consequential choices on appropriate evidence and human judgment.

End with decisions and next-quarter outcomes

Read each decision back in plain language. For every next-quarter outcome, record owner, target date, evidence, dependencies and review trigger. A proposal belongs under open questions until the authorized decision maker accepts it.

Use the objective summary guide to keep the recap factual. Send it promptly, invite corrections and retain one accepted version rather than separate provider and customer histories.

Follow up before the next quarter ends

A QBR is too infrequent for discovering that a critical dependency stalled. Schedule checkpoints based on risk and milestone timing. Use meeting follow-up to keep decisions connected to action between reviews.

Before planning the next QBR, ask which evidence changed a decision and which slides added no value. Remove anything that exists only because it was in last quarter’s deck. The agenda should become sharper as the relationship matures.

Keep quarterly review evidence grounded in the consented conversation. Kuno can support overt in-room capture, while customer and provider owners verify the final decisions and record. See Kuno