Quarterly business review template: agenda, deck and worked example

This page is for account managers, customer success managers and account executives who own renewals and expansion, and for agency or service leads who report to clients each quarter. It covers the customer-facing QBR. If you're looking for the internal version, where a rep reviews pipeline with sales leadership, there's a card for that too. Allow about three hours to prepare a QBR for a large account, most of it pulling and checking numbers.

Customer QBR, internal QBR or EBR?

The same initials cover three different meetings. Know which one you're running before you build the deck.

What makes a QBR worth the customer's time

A customer's senior people give you an hour four times a year. They'll keep coming if the hour helps them run their business. Five principles do most of the work:

1. Their goals, in their units. Report against the goals the customer set, measured the way they measure them (hours, cost, error rate, revenue), not logins and feature adoption. Usage is evidence, not the headline.
2. A written pre-read. Send a one-page summary two working days ahead. Amazon's founder described the company's habit of replacing slide decks with narrative memos read silently at the start of each meeting; you don't need six pages, but a written page forces you to make the argument rather than narrate charts, and lets the customer arrive with questions.
3. Bad news early. Open issues and missed targets go before the roadmap. Customers already know about the outage; what they want to know is whether you do.
4. Decisions, not updates. Every agenda item should end in a decision or an action. If it doesn't need the people in the room, put it in the pre-read.
5. Both sides own the plan. The action list has customer owners as well as yours. A plan only you are accountable for is a to-do list.

The 60-minute QBR agenda

The customer leads the next-quarter section. If you talk for more than half the meeting, it's a presentation, not a review.

QBR templates

Subject: Q[number] review: [customer] and [your company], [date]

Hi [sponsor's first name],

Ahead of our quarterly review on [date and time], here's what I'd suggest we cover in 60 minutes:

1. Results against the three goals we set in [month]
2. Open issues, including [the known issue], and what we're doing about them
3. Your priorities for next quarter
4. Actions and owners

I'll send a one-page summary by [date, two working days before]. It would help to have [decision maker or user lead] there for item 3. Is there anything you'd add or drop?

[Your name]

[Customer] and [your company]: Q[number] review, [date]

THE SHORT VERSION (three sentences)
What went well:
What didn't:
What we propose for next quarter:

GOALS SCORECARD
Goal | Measure | Baseline | Target | Actual | Status
1.
2.
3.

OPEN ISSUES (each with owner and date)
1.
2.

DECISIONS WE NEED FROM THIS MEETING
1.
2.

CONTRACT: renewal date [date]; current scope [summary]

1. Title: customer, quarter, date, attendees
2. Agenda and the decisions we need today
3. The short version: one slide, three sentences
4. Goals scorecard: goal, measure, baseline, target, actual, status
5. Evidence for the biggest result (one chart, one source)
6. Issues and risks: what happened, impact, fix, owner, date
7. What we heard: feedback from users and support trends
8. Next quarter: the customer's priorities and three proposed goals
9. Recommendations or roadmap items tied to those goals only
10. Actions: owner (both sides), date; next QBR date

Appendix: usage detail, ticket list, contract summary. Never present the appendix.

Goal (in the customer's words):
Why it matters to them (cost, revenue, risk, time):
Measure and source (whose system, which report):
Baseline (date):
Target for this quarter:
Actual:
Status: on track / at risk / missed
What drove the result:
What we'll change:

Account health: green / amber / red, and why
Renewal date and value:
Who's attending, their role and what each cares about:
Who should be there but isn't (and how to involve them):
What's changed at the customer since last quarter (leaders, acquisitions, hiring, new sites):
Risks to the renewal:
Expansion hypothesis (one, with evidence):
What we want to leave the meeting with:
The question we're most afraid they'll ask, and our honest answer:

Subject: Q[number] review: actions and owners

Hi [first name],

Thanks for the time today. Here's what we agreed:

Goals for Q[next]:
1. [goal, target, measure]
2.
3.

Actions:
- [action], [owner, their side], by [date]
- [action], [owner, our side], by [date]

Open issue update: [issue], fix expected [date], I'll confirm when it's done.

Next review: [date]. I'll send the pre-read by [date].

[Your name]

Last quarter: quota [amount], closed [amount], attainment [percent]
Wins: [deal, value, why we won]
Losses: [deal, value, why we lost, what we'd change]
Pipeline for next quarter: [amount] across [number] deals; coverage [pipeline divided by quota]
Commit / best case: [amounts]
Top three deals: stage, next step, risk
What I need from leadership: [specific help]
One thing I'll do differently:

For the forecast behind the last card, the sales forecast template shows how to weight pipeline by stage.

Worked example: a payroll provider's QBR

Illustrative example. The companies, people and figures are invented to show the method.

The vendor: Ledgerline Payroll (ledgerline.example). The customer: Brightwater Staffing (brightwater.example), a staffing firm with about 420 employees on payroll across three states. The sponsor: the Controller. Renewal: in five months.

Timing. Payroll customers are busiest at quarter end. Federal Form 941, the employer's quarterly return for withheld income tax and Social Security and Medicare taxes, is due by the last day of the month after the quarter ends (October 31 for the July to September quarter). Ledgerline books the Q3 review for the second week of November, so the quarter's filings are final and the Controller isn't mid-deadline.

The goals scorecard.

The arithmetic for the headline result. Each off-cycle run took the payroll team about 45 minutes. 46 minus 14 is 32 fewer runs, and 32 × 45 minutes is 24 hours saved in the quarter, roughly three working days. The Controller's own team timed the runs, so the figure is theirs, not Ledgerline's.

The issue raised early. Corrections missed target. The cause: timesheets from one client site arrive after the cutoff. Ledgerline proposes an automated reminder to site managers 24 hours before cutoff (owner: Ledgerline, by December 1) and Brightwater agrees to move that site to the standard cutoff (owner: payroll manager, by December 15).

The next-quarter goals. The Controller says Brightwater is opening an office in a fourth state in February. That becomes goal one: new-state registrations and the first payroll there run without corrections. It's also the natural expansion conversation, raised by the customer rather than pitched.

What made it work: the scorecard used the customer's numbers, the missed goal came before any roadmap slide, and the meeting ended with five actions, two of them owned by Brightwater.

How often, and for whom

Not every account justifies a full QBR. A tiered approach keeps the format meaningful:

Before each review, check what's changed at the customer: new leaders, acquisitions, hiring and new locations. Bebop researches an account and summarizes what's happening at the company, which is a quick way to start that list. The yearly view of the account, including the stakeholder map and growth plan, belongs in an account plan.

QBR checklist

• The goals on the scorecard are the customer's, agreed last quarter, in their units.
• Every number has a source the customer recognizes.
• The pre-read went out two working days ahead.
• A decision maker, not just your day-to-day contact, is attending.
• Missed targets and open issues come before the roadmap.
• The customer leads the next-quarter section.
• Every action has an owner, a side and a date.
• The follow-up email goes out the same day.
• The next QBR date is in both calendars before you leave.

Mistakes to avoid

• The product tour. New features belong in the meeting only when they serve a goal on the scorecard.
• Vanity metrics. Logins and tickets closed tell the customer what you did, not what they got.
• Surprises. If the customer hears about a problem for the first time in the QBR, you've already lost credibility. Raise it before, then report the fix in the meeting.
• Pitching expansion cold. Expansion lands when it follows from a goal the customer named. Otherwise it reads as the reason you called the meeting.
• No customer owners. If every action is yours, the customer has no stake in the plan.
• Waiting for the renewal quarter. A QBR two quarters before renewal gives you time to fix what it uncovers.

Next step: carry the next-quarter goals and the stakeholder map into a yearly account plan template.