QBR Template: The Six Sections of a Quarterly Business Review

The worst quarterly business review I have sat through opened with a slide titled "Our Q3 Highlights" and spent eleven minutes on the vendor's product launches, none of which the customer used. The customer's actual quarter had included two outages and a data export bug they reported in July and had heard nothing about since. Nobody mentioned it. The renewal conversation six weeks later was short and it did not go the vendor's way.

A QBR template does not fix that on its own. What it does is force the meeting to open where the customer's attention already is, which is their own goals and their own unresolved problems, rather than where the vendor's attention is. This guide gives you the six sections, an agenda that fits forty-five minutes, a worked example for an account heading into renewal, and a copy-paste template at the bottom.

What a QBR Template Actually Has to Do

A quarterly business review is the scheduled moment when a vendor and a customer compare what was agreed against what happened, and decide what the next three months are for. It exists so that the renewal is never the first time either side discovers they were holding different pictures of the relationship.

That is the whole job. Three things it is not, and each confusion produces a different bad meeting:

• It is not a product update

  Your roadmap is interesting to you. It is interesting to the customer only where it intersects something they asked for or something they are struggling with. A QBR that walks through everything shipped last quarter, most of which this account will never touch, teaches the customer that the meeting is for you and not for them. Bring the two roadmap items that matter to this account and cut the rest.

• It is not a status report

  A status report lists activity. A review makes a judgment: this worked, this did not, here is what we are changing. If every line of your deck could have been sent as an email without losing anything, you have written a report and booked a meeting for it. The parts that need a room are the disagreements, the tradeoffs, and next quarter's priorities.

• It is not a renewal pitch in disguise

  Customers recognize a commercial conversation dressed as a review immediately, usually by slide four. If you need to talk about expansion, put it in section six with everything else about next quarter, and only after you have been honest about what did not go well. Earning that conversation takes about twenty minutes of demonstrated candor and it is worth every one of them.

The Six Sections of a QBR

Six sections, in this order. The order carries most of the value. Their goals sit above your outcomes because a number only means something against a target somebody agreed to, and what-they-reported sits above next-quarter because unresolved problems poison forward planning if you try to skip past them.

1. 1

   1. Header: period, attendees, owner, and the one-line verdict

   The account, the quarter, who is in the room from both sides, and the account owner's name. Then one sentence stating where the relationship stands: on track, at risk, or expanding, with the reason. Writing that verdict before you build the rest of the deck is a useful discipline, because if you cannot state it in a sentence you do not yet understand the quarter well enough to present it.

2. 2

   2. The goals we agreed last quarter, and where each landed

   Pull the three or four goals from the previous QBR verbatim and mark each one hit, partially hit, or missed, with a sentence on why. This is the section that makes a QBR a review. It is also the one most often skipped, because the previous meeting's goals were never written down anywhere retrievable. If you are starting this template from scratch, section six is what makes section two possible next time.

3. 3

   3. Outcomes, in the customer's numbers

   Not your usage metrics. Theirs. Hours their team stopped spending, cases resolved faster, revenue their team attributes to the workflow, errors avoided. If you do not know their numbers, that is itself the finding, and the honest version of this slide says so and asks for them. A slide full of vendor-side metrics is the tell that nobody has ever asked this customer what success looks like in their own terms.

4. 4

   4. Adoption: who is actually using it

   Seats provisioned against seats active, which teams have taken it up and which have not, and where usage went up or down against last quarter. Adoption is the leading indicator that everything else lags. A flat outcome number with rising adoption is a timing problem and a good outcome number with falling adoption is a churn risk wearing a smile, and only this section tells you which one you have.

5. 5

   5. What you reported, and what shipped

   The specific list. Every problem this account raised last quarter, what happened to each, and what is still open with a date or an honest "no date yet". Not a ticket count, not an average response time. The named issues in their own words. This is the highest-trust slide available to you and almost nobody builds it properly, for a reason covered further down this page.

6. 6

   6. Next quarter: goals, owners, dates, and the ask

   Three goals, maximum. Each with a named owner on both sides and a date. Then whatever you need from them: a stakeholder introduction, a decision on a rollout, a reference call, a renewal date to put in a calendar. Ending a QBR without written commitments on both sides is what produces the next QBR that has nothing to review.

QBR vs Account Plan vs Customer Success Plan

Three artifacts that get conflated constantly, with three different audiences and three different lifespans. Most teams need all three and confuse at least two of them.

• Account plan template: internal, continuous

  Who is who, who has budget, who is a champion and who is a blocker, the renewal date, the expansion paths, the risks, the competitive situation. It is maintained continuously and it is never shown to the customer, because half of it is candid assessment of their own people. The QBR is a quarterly outward-facing edit of this document, and if your account plan only gets updated the week before a QBR, it is not a plan.

• Customer success plan template: shared, goal-oriented

  The agreed definition of success for this account, written jointly and referenced by both sides. Objectives, the metrics that prove them, milestones and dates, and who owns what. Where an account plan is your assessment, a success plan is a shared commitment. The QBR's section two is literally a progress check against this document, which is why accounts without one produce QBRs that drift into activity reporting.

• QBR: external, quarterly, a judgment

  The meeting and its deck. It draws on both documents above, presents a curated part of them, and ends in written commitments that feed the next quarter. It is the only one of the three that a customer ever sees, and it is the only one with a fixed cadence.

A QBR built from vendor activity asks the customer to care about your quarter. A QBR built from their goals and their unresolved problems asks them to evaluate a partnership.

The QBR Agenda: Forty-Five Minutes

Send the deck forty-eight hours ahead. The meeting is not for narration, it is for the parts that need two-way conversation. Time allocations below assume the customer has read it, and the first two minutes are for finding out whether they have.

1. 1

   0 to 5: the verdict and the goals from last quarter

   Open with the one-line assessment and go straight to the scorecard from last quarter. Do not open with introductions and a company slide. Everyone in the room knows who you are, and the first ninety seconds are the only moment when full attention is guaranteed.

2. 2

   5 to 15: outcomes and adoption

   Ten minutes for both, because these are the slides most likely to have already been read. Spend the time on the anomalies rather than the totals. A team whose usage dropped forty percent is a better use of this window than the aggregate number that went up.

3. 3

   15 to 30: what they reported, and what is still open

   The longest block, and the one that most often runs over, which is fine. This is where the customer has actual feeling invested. Go item by item, take the criticism without softening it, and be specific about what has no date rather than implying everything is in progress.

4. 4

   30 to 42: next quarter, goals and owners

   Propose three, let them cut or change them, and write the owners and dates in the document while everyone is still in the room. Goals assigned after the meeting by email have a much lower survival rate than goals someone agreed to out loud.

5. 5

   42 to 45: the ask, and the next date

   One ask, stated plainly. Then book the next QBR before anyone leaves. The single most common reason a quarterly cadence becomes an annual one is that nobody put the next meeting in a calendar while the room was still warm.

QBR Example: An Account Heading Into Renewal

Structure advice is easy to agree with, so here is the shape filled in. Compressed, but the proportions are right. Sections two and five take more room than the outcome slide does.

Header. Account: Northbeam Logistics. Period: Q2 2026, April to June. Attendees: their VP Operations (economic buyer), their support team lead (daily user), our account owner, our support lead. Renewal: October 14, 2026. Verdict: on track, with one unresolved product issue that is the main risk to renewal.

Goals we agreed last quarter. (1) Roll out to the second support team by May 15. Hit, completed May 9. (2) Cut average time-to-first-response below four hours. Partially hit, currently 4.6 hours, down from 7.2. (3) Get their reporting workflow off the manual spreadsheet. Missed. The export bug blocked it in May and we did not communicate the delay well, which is on us.

Outcomes, in their numbers. Their support team estimates 11 hours a week no longer spent copying case details between systems, which at their loaded rate is roughly $34,000 annualized. Escalations that reach engineering are resolved in 3.1 days against 8.4 in Q1. Both numbers came from their own reporting, not ours, which is why they are on the slide.

Adoption. 22 of 25 seats active in the last 30 days, up from 14. Team A at daily use. Team B onboarded in May and now at 80 percent of Team A's volume. Team C, the field operations group, has not started, and that is the third goal for next quarter rather than a criticism.

What you reported, and what shipped. Six issues raised this quarter. (1) CSV export dropping the final row on files above 10,000 records, reported April 3, shipped June 18, verified with their team. (2) Timezone offset wrong on scheduled reports for their Singapore office, reported April 22, shipped May 6. (3) Duplicate notifications on reassignment, reported May 11, shipped May 30. (4) Bulk edit timing out above 500 records, reported May 19, open, in progress with an estimate of late August. (5) Search not matching partial customer reference numbers, reported June 2, open, no date yet, and we should be straight about that. (6) A permissions question from June 9 that turned out to be configuration and was resolved the same week.

Next quarter. (1) Team C onboarded by September 12. Owner: their support lead and our account owner. (2) Reporting workflow off the spreadsheet, dependent on item 4 above, by September 30. Owner: our account owner. (3) Get time-to-first-response under 4 hours. Owner: their support team lead. Ask: a thirty-minute conversation with their IT lead about the field operations rollout, and a decision on the renewal term by September 20.

Notice item 5. Writing "open, no date yet" in a deck feels bad and it is the line that does the most work in the room, because it is the one the customer can verify against their own experience. A slide that showed all six issues as "in progress" would have been read as evasion by the one person who already knew otherwise.

The QBR Preparation Checklist

Run this before you build the deck. It takes about ten minutes and it catches the omissions that turn a review into a status update.

The fifth and seventh items are the ones that fail, and they fail for a structural reason rather than a discipline one.

Where the "What Shipped" Slide Comes From

Building a QBR deck is a two-hour job. Building section five is not, and the gap between them is almost entirely about whether anyone can tell you which of last quarter's fixes came from this specific account.

Ask a customer success manager how they assemble that list and the honest answer is usually that they search the help desk for the account's closed tickets, read them, then go and ask an engineer whether each one was ever fixed. Some of the tickets were closed with a note saying "escalated to engineering", which is where the trail ends. The engineering issue exists, it shipped in May, and nothing connects the two records. So the list gets built from whatever the account owner personally remembers, which systematically favors the loudest complaints and misses the quiet ones that were fixed without anybody circling back.

That is how a customer ends up learning in a QBR that something they reported four months ago is still open, when it actually shipped in week three and nobody told them. It is the same failure that makes closing the customer feedback loop the step teams skip, and it costs more here because it happens in front of the buyer.

The version that works is mechanical, and it depends on a link being recorded at the moment of escalation rather than reconstructed afterward:

• Attach the account at escalation time, not at review time

  When a support ticket becomes an engineering issue, the requesting account should be recorded on that issue right then. It costs nothing in the moment and it converts the quarterly question from a search problem into a filter. Linear's own customer requests model is built on exactly this idea, and the value of it only becomes visible a quarter later.

• Keep the customer's own words

  "Export issue" is not a QBR line. "CSV export dropping the final row on files above 10,000 records" is, and that sentence almost always already exists in the words of the person who reported it. Paraphrasing on the way into the tracker sands off the specifics, and the specifics are what make the customer recognize their own problem on your slide.

• Count accounts, not tickets

  One account reporting the same defect nine times and nine accounts reporting it once are very different facts, and a raw ticket count hides which you have. This matters for prioritization all year and it matters in the QBR, where "four other customers hit this too" is the honest explanation for why something got fixed quickly.

• Know who is still waiting when the fix ships

  A fix that shipped in May and reached the customer's awareness in August was worth a fraction of what it should have been. If the issue carries its reporters, then writing the release notes and telling the affected accounts become the same two-minute job, and section five of the next QBR writes itself from work already done.

That table is not really about quarterly reviews. It is about whether the handoff from support to engineering left a durable trail behind it, and the QBR is simply the moment a customer-facing person finds out that it did not. The same gap turns up when someone tries to write the problem section of a PRD and cannot reconstruct who asked, and it is why managing feature requests from support to engineering is a process problem rather than a tooling preference.

For teams where support runs on HubSpot Service Hub and engineering runs on Linear, IssueLinker is what keeps that trail intact. A ticket becomes a linked Linear issue in one click with the customer's own wording carried over, the requesting account travels with it, and the two stay in sync in both directions, so when the fix ships the ticket already knows. The Linear HubSpot integration guide covers how the two-way sync works, and how to get bugs fixed faster covers the handoff itself.

Mistakes That Make a QBR Not Worth Attending

Four patterns account for most reviews that quietly become annual, then optional, then cancelled.

• Opening with your own activity

  Company slide, product highlights, then eventually something about the customer. By that point the senior attendee has opened their laptop. Start at their goals from last quarter and everything after it gets read as a partnership conversation instead of a vendor presentation. The order of the deck does more work than its contents.

• Outcome metrics the customer does not recognize

  Logins, seats provisioned, features touched, tickets closed. These are vendor telemetry, not business outcomes, and presenting them tells the customer that nobody ever asked what they were trying to achieve. If you genuinely do not have their numbers, ask for them on the call and make getting them a goal for next quarter, which is a much better slide than a fabricated proxy.

• Only good news

  A review where everything went well is not a review, and customers grade it accordingly. Every account has at least one thing that missed. Naming it before they do is the cheapest credibility available in the entire meeting, and it is what makes the parts that did go well believable.

• No written commitments at the end

  A meeting that ends with general agreement and warm feelings produces a next QBR with an empty section two. Goals, owners on both sides, dates, written down while everyone is still present. If the customer will not commit to an owner for something, that is useful information about how much they actually want it.

The thread through all four is that a QBR is a trust instrument and gets judged as one. The measure is not whether the deck was thorough. It is whether the customer leaves believing you have an accurate picture of their experience, including the parts that reflect badly on you.

Copy-Paste QBR Template

Here is the template in plain text. Paste it into a doc, a slide deck outline, your CRM's account record, or wherever your team keeps this. Delete a section when it genuinely does not apply rather than writing "N/A", except for section two, which you should always fill in even when the answer is that no goals were set last time.

QUARTERLY BUSINESS REVIEW: [ account name ]

Period:       [ quarter, with dates ]
Prepared by:  [ account owner ]
Sent:         [ date the deck went out, 48h before the meeting ]
Attendees:    [ customer: economic buyer + daily user ]
              [ vendor: account owner + anyone with something specific to say ]
Renewal:      [ date ]
Verdict:      [ on track | at risk | expanding ] because [ one sentence ]


1. GOALS WE AGREED LAST QUARTER
- [ Goal, verbatim from the last QBR ]  -> [ hit | partially hit | missed ]
  [ One sentence on why ]
- [ ... ]


2. OUTCOMES, IN YOUR NUMBERS
- [ Time or cost their team saved, with the figure they use ]
- [ A business metric they own that moved ]
- [ Source of each number, so it is clear these are theirs, not ours ]

If we do not have these numbers: [ say so, and make getting them a Q+1 goal ]


3. ADOPTION
Seats:        [ active in last 30 days ] of [ provisioned ]
By team:      [ team ] - [ usage, and direction vs last quarter ]
              [ team ] - [ ... ]
Not started:  [ which groups, and whether that is a goal or a risk ]


4. WHAT YOU REPORTED, AND WHAT SHIPPED
- [ Issue in the customer's own words ] | reported [ date ] | SHIPPED [ date ]
- [ ... ] | reported [ date ] | OPEN, estimate [ date ]
- [ ... ] | reported [ date ] | OPEN, no date yet
- [ ... ] | reported [ date ] | resolved as configuration, not a defect

Accounts also affected: [ where a fix was prioritized partly for other customers ]


5. RISKS AND OPEN QUESTIONS
- [ Risk ] -> [ what we are doing about it, and by when ]
- [ ... ]


6. NEXT QUARTER
- [ Goal ]  Owner (them): [ name ]  Owner (us): [ name ]  By: [ date ]
- [ ... ]
- [ ... ]

Our ask:      [ one thing, stated plainly ]
Next QBR:     [ date, booked before anyone leaves the room ]

Section four is the one that gets cut when preparation runs late, and it is the one the customer would have valued most. Every line in it belongs to somebody on their team who reported a problem and then waited. A review that draws on their reports and never tells them what happened has left the cheapest goodwill in the relationship on the table.

Frequently Asked Questions

What is a QBR?

What should a QBR include?

How long should a QBR meeting be?

Who should attend a QBR?

What is the difference between a QBR and an account plan?

Which accounts should get a QBR?

How do you prepare for a QBR?