QBR template for account managers: show the customer what its own customers received

A QBR template is the slide deck an account manager brings to a quarterly business review, from the account’s goals and results to the decisions it ends on. A complete one adds what the account’s customers received before and after last quarter’s changes, from the welcome email to the cart reminder, each dated with a screenshot. Obsession keeps what each account shows only to its customers, by API, MCP (the standard way AI agents call tools) or a table.

A QBR template is the slide deck an account manager brings to a quarterly business review, from the account’s goals and results to the decisions it ends on. A complete one adds what the account’s customers received before and after last quarter’s changes, from the welcome email to the cart reminder, each dated with a screenshot. The 9 slides suit account managers and customer success teams at software companies whose product reaches their accounts’ customers. That covers email and SMS platforms, help desks and AI support, messaging and login code providers, and loyalty and reviews apps.

In the deck, the account is the company that pays for your product, and its customers are the people who buy from it. Your product’s reports show what the account sent. The before and after slide shows what arrived at the other end, each message dated with its screenshot.

What a quarterly business review template contains

Gainsight’s guide to QBRs defines a quarterly business review as a strategic meeting held once every three months between a vendor and its customer. ChurnZero’s blueprint advises against focusing on adoption or usage rates. The free templates that rank for the phrase follow the same order as both guides.

Every number in those templates comes from the vendor’s product and the account’s own dashboards: sends, tickets, seats and usage. None of the 4 has a slide for what the account’s customers received. That is the part the account’s executives can check on their own phones, and it is what your product exists to deliver.

The QBR template, slide by slide

Nine slides fit Gainsight’s advice to keep the meeting to about an hour. Each slide states facts the account can check, and the deck ends on decisions.

Slides 4 and 6 are the ones published templates leave out. Slide 4 shows the account that its customers’ experience changed because of the work done since the last review. Slide 6 turns the same screenshots into the next thing to set up. It comes after the account has seen its results, which meets ChurnZero’s warning against QBRs built around the vendor’s upsell.

Where slide 8 needs the cost of a gap in the account’s own numbers, the sales business case template opens on a dated screenshot too. Keep each finding as a field on the account in your CRM too, as the guide to CRM data enrichment fields sets out, so the next QBR starts from last quarter’s rows.

Building the before and after slide

The slide puts 2 runs of the same journeys side by side: one from before last quarter’s changes, and one taken 1 to 2 weeks before the meeting. Each run is a new customer at the account’s own store or app, with every message logged as it arrives.

1. Pick the journeys your product powers

Choose the moments where your product reaches the account’s customers. For an email and SMS platform, that means the welcome series, the browse reminder, the cart reminder and the checkout reminder. For a help desk, it means a question sent by email and one asked in chat. For a messaging or login code provider, it means the code sent at sign-up and at log-in. For a loyalty app, it means the rewards welcome after joining.

2. Sign up as a new customer, with an address and number for each account

Agree it with your contact at the account first, so nobody there mistakes the test for a real customer. Then use the public form any customer sees, with a new email address and a spare phone number kept for that account. Buy nothing: stop at the payment step and screenshot every page up to it. Before you start, write down how long you will wait before calling a message missing, such as 48 hours for a cart reminder or 10 minutes for a login code.

3. Test the browse reminder in the same browser

A browse reminder goes only to a visitor the email platform already knows. Klaviyo’s help centre, updated 7 October 2026, says its browse abandonment flows are triggered by the Viewed Product metric and track identifiable browsers. Its onsite tracking guide says a visit alone doesn’t make a browser known, while a sign-up through its form or a click from one of the brand’s emails does.

So sign up through the form first, then open a product page in the same browser. Klaviyo’s build steps add a delay of at least an hour before the first message. Smart Sending, Klaviyo’s limit on how many emails one person receives, uses a 16 hour window by default, so let the welcome emails finish before you test. Other email platforms set their own rules, so check the account’s.

4. Log every message with its time and screenshot

Keep a sheet with one row per message. Give each row the journey, the time it arrived, the subject line, any code and a link to the screenshot. Save the original email too, because its headers carry the arrival time and the platform that sent it. The sample data has one real finding in that form: a £40 basket left at 02:57 on 22 September at a UK skincare store, and no reminder in the 48 hours watched.

5. Write each row as a fact the account can check

Put both runs in one table with their dates in the header. Write “None in 48 hours” rather than “broken”, and give the window you waited. Leave revenue out of it: the slide shows what arrived, and the account’s own reports show what it earned.

QBR template examples by vendor type

The same 2 slides work for any product that reaches the account’s customers. Each row is an invented example at a .example address.

• Email and SMS platform. The account’s head of ecommerce sees the cart reminder that started arriving after the flow was rebuilt, with both screenshots. Open slide 6 on the form that asks for no phone number.
• Help desk and AI support. The account’s head of support sees reply times as a customer meets them, beside the promise on its own help page. Open slide 6 on the chat question sent at 23:00 that waited until morning.
• Messaging and login codes. The account’s product lead sees UK codes arriving in seconds again after the sender change. Open slide 6 on the customer whose text never arrives and has no other way in.
• Loyalty and reviews. The account’s marketing lead sees new members get their points welcome within minutes. Open slide 6 on the referral programme no email mentions.

Agencies reporting to clients use the same idea weekly: the guide on how to show clients every flow fired gives the format for a retainer review.

Upsell signals: what the account hasn’t set up yet

Upsell signals usually come from inside your product: seats near a limit, a feature used every day, a new team asking for access. The account’s customers show a second kind, and a customer account at the account’s store sees it: messages they never receive, such as a text or a browse reminder.

• Texts never set up. No step of the sign-up form or checkout asks for a phone number with its own consent box, and no text arrives. Klaviyo’s guide to SMS consent, updated 21 October 2026, says email consent is not SMS consent. It recommends a separate checkbox, and a form that asks for the email on one step and the phone number on the next. Screenshot the form as it stands.
• No browse flow. A browse reminder is a triggered flow: it starts when a known visitor views a product. If nothing arrives within the window you set, test once more as in step 3 and write the window on the slide.
• No answer out of hours. For a help desk, log the time a chat question was sent at night and the time of the first reply.
• One channel for codes. For a messaging provider, a code sent by text only leaves a customer whose text fails with no other way in. Log a run on a number in each country the account serves.

Put slide 6 after the results. The account has just seen what improved for its customers, message by message, and the gap that remains comes with its own screenshot and the step that closes it. The guide to buying signals examples lists signals from what companies send their own customers, for companies your team hasn’t sold to yet.

Running the QBR presentation

• Cadence. Gainsight’s guide holds QBRs every three months. ChurnZero runs strategic accounts quarterly and smaller ones once or twice a year, and sees less value in a QBR on a monthly contract.
• Length. About an hour, per Gainsight, which leaves time for the decisions on slide 9.
• Before the meeting. Send the agenda well ahead, and run the customer account 1 to 2 weeks before so slide 4 is current. ChurnZero suggests sending supporting evidence ahead of the call.
• Who attends. Day-to-day users who know the product and a senior person who sets direction, as Gainsight advises. Show slide 4 to the senior person: it is their own store or app.
• After. Send the deck as a PDF with each decision’s owner and date, and book the next QBR before the meeting ends.

Time needed by hand

Count it per account. Setting up the address, number and sheet takes about 30 minutes. Logging what arrives takes about 10 minutes a day for 14 days, so one run is about 2 hours 50 minutes. Two runs a quarter across a book of 40 accounts comes to about 227 hours a quarter, as example inputs. Put in your own minutes and the size of your book.

Set those hours against what each review supports. As example inputs, take an account paying $500,000 a year, one paying $100,000 and one paying $25,000. Each renews on the date on slide 8, and slide 4 is the part of the deck its executives can check for themselves.

By hand, the method holds for the 5 to 10 accounts renewing soonest. Past that, it needs an address and number per account, kept for months, with every original saved. A welcome email that stops and a new sending platform are both churn signals to see before the renewal. The guide to churn risk indicators shows how to score them.

Obsession collects what companies show only to customers, step by step: their screens, emails and texts, member prices, trial limits, quotes and cancel offers, each dated with a screenshot. Teams and AI agents look up any company through the API or MCP, and a company not yet covered is added on request. For account managers, Account watch keeps a customer account open at every account in the book, so slides 4 and 6 are ready before each QBR. It shows the platform behind each email too, so the week an account’s emails start coming from a new platform lands on its page in your CRM. Most customer success teams use similar data, from health scores to public web search from Exa, “The world’s data for AI agents”. Obsession adds what each account sends the people who sign up with it, and an agent can call both (how the two compare). Start with the accounts renewing next quarter, so you can see what it does to renewals, retention and expansion.

QBR template tools compared

Each option fills a different part of the deck. We make Obsession, so every other option is described from its provider’s own pages as of 11 November 2026.

For slides 4 and 6 across a whole book, every quarter, use Obsession. For the layout, a free template is enough, and for health scores across many accounts, a customer success platform does the job. For 1 account a quarter, the sheet is enough. Sales intelligence from behind the login shows the same view for every role on a revenue team, with an example for each.

Questions