The Quarterly Business Review Template AI Fills for You
A quarterly business review template for customer success, and how an AI agent in Slack drafts the first pass: goals, progress, wins, friction, open decisions.
The QBR with Northwind is two weeks out, and the quarterly business review template is open and empty. The structure was never the hard part. Filling it is. Northwind's story is scattered across your CRM, a support queue you'd rather not reopen, product usage in another tab, and a hundred Slack threads. So you rebuild it from scratch, the way you did last quarter, and the quarter before.
Most of what goes in that pack, the filled-in template you carry into the review, is easy to know but hard to find. It's spread across four systems and three months, and it walks out the door when the teammate who lived it is on PTO the week you're prepping.
What should a quarterly business review template include?
A quarterly business review template is the repeatable structure a CSM uses to run a QBR: the customer's goals, progress against them, wins, friction, and the open decisions heading into next quarter. Fill those five honestly and you have the account story. Everything else on the deck is packaging.
Copy this and you have the whole template:
Goals: what the customer set out to do this period. Which metric were they chasing? What did they buy this for?
Progress: how far each goal got, with the numbers. What moved this quarter? What stalled?
Wins: outcomes worth showing the sponsor. What went live? Where did they save time or money?
Friction: what cost them time, and whether it's resolved. What broke? Is it fixed or still open?
Open decisions: what's unresolved heading into the renewal. What are they weighing? What do you need from them?
That's the structure. Filling it is the next section.
Runbear fills the template before you do
Say the same QBR comes up again. This time the pack doesn't start empty.
Two weeks out, Runbear posts a first draft of the Northwind pack right in #acct-northwind. The template itself, all five sections filled, a source on every line.
AI drafts a quarterly business review template in Slack, filling each section with its source.
It read the account plan in your CRM and pulled the two goals Northwind set at kickoff. Product usage filled in the rest: API adoption up 40% this quarter, three of five teams live. Then it worked the support channel and the account threads, sorting wins from friction. The workflow they shipped in May, a win. The billing dispute that dragged for three weeks in April, and the two support tickets that slipped past their response window in June, friction.
The line that matters most is the one you'd have skimmed past. Last week, in a thread three days old, Northwind's EU team asked about access, and their renewal is in Q3. The agent pulled it into open decisions before anyone else connected the two. That is the difference between walking into the review prepared and walking in blind, and it never leaves the channel where the conversation already happened.
Every line carries where it came from.
Progress: API adoption up 40% QoQ, 3 of 5 teams live. Source: the product usage export, and the #acct-northwind thread where their lead confirmed the rollout reached three of five teams.
When a number looks off, you can see why it's there and fix it in one reply, instead of wondering whether the agent invented it. The pack isn't the deck. It's the draft under the deck: the assembled, sourced account story you were about to spend a day rebuilding by hand.
Your CRM and Slack already hold the QBR story
The pack can start full because the answers were already written down, just never in one place.
Goals and progress live in your CRM and product data: the account plan, the usage curves, the fields your team updates as a byproduct of the work. Wins and friction are already in Slack and your support tool, in the thread where Northwind said the workflow saved their team an afternoon and the one where the billing dispute flared. Open decisions? Those sit in the newest threads, too recent to have reached any doc.
Because those sources update as the work happens, nobody keeps a QBR pack current on the side. When two of them disagree, say the CRM still shows the billing dispute open but the support thread shows it settled in June, Runbear flags the gap in the thread and asks, rather than guessing. It reads what's there and tells you where it's unsure.
Ask for the pack, or let it land before the review
There are two ways to use it.
You can ask when you need it: @Runbear draft the QBR pack for Northwind. It shows what it's reading as it goes, then hands back the pack as a report you open in the thread.
Once you've seen one, you don't have to ask again. Tell it "make this two weeks before every QBR" and it schedules the drafting on your renewal calendar. The schedule automates the draft, not the trust: every pack still lands as a draft you review, and none of it goes near the customer. You can start with one account, then put the rest of your book on the same schedule once you trust what it produces.
The CSM owns what the story means
Runbear assembles the evidence. You own the story.
You asked for the pack, opened the report it sent back, and now you shape it. The draft lists the April billing dispute under friction. You know it got sorted and Northwind was happy by June, so you cut it, or you keep it and frame it as a save. The draft shows API adoption up 40%. You decide whether that's the headline or a footnote, because you know the renewal hinges on EU expansion. You lead with what matters to the customer, and you make the renewal call. The agent never does.
Correct it once in the thread, and the next quarter's draft reflects it.
Setting it up takes one conversation
You don't configure this in a dashboard. You tell the teammate, in the channel, what to read and when: pull goals and progress from the CRM account plan, wins and friction from this support channel and Slack, and draft the pack two weeks before each QBR on the renewal calendar. It connects what it needs and registers the trigger.
No admin console, no config files. Slack is connected once the teammate is in the channel. Point it at your CRM and support tool, and it offers to run once right away so you can preview the first pack before the schedule takes over.
Why the other options leave the assembly to you
By now the honest alternatives are worth naming. You could paste your CRM and Slack into ChatGPT and prompt it every quarter. You could buy a QBR-automation tool that syncs your usage and tickets. You could rebuild the pack by hand. Each does part of the job. The part they all leave is the same one: pulling the story out of the unstructured conversation, where the billing dispute got resolved and the EU team asked about access, and handing it back sourced so you can trust it.
| Approach | How the pack gets filled | Stays current? | Where it lives | Best for |
| Runbear agent | Reads your CRM and usage and the Slack and support conversation, drafts all five sections, sources every line, and asks when two sources disagree | Yes, redrafts before each review, unprompted | Inside Slack, as a teammate you correct in one reply | The full story, including what only lives in a thread |
| General-purpose AI (ChatGPT + connectors) | Answers when you prompt it and wire up each source yourself | Only when you ask and re-paste the context | A separate chat window | One-off questions, if you assemble the inputs each time |
| QBR automation tool | Ingests CRM fields, usage, and tickets, generates slides | Only the structured data it syncs | A separate app | Metrics decks, minus the thread context that explains them |
| Static template gallery | You fill every field by hand | No | A doc you go find | The structure, not the content |
| Rebuild by hand | You reassemble it every quarter | Only when you redo it | Your afternoon | One account, when you have the time |
Two things on that first row are hard to copy: it shows up before every renewal without being asked, and it lives in the channel where your team already talks about the account. Runbear is used by 600+ companies, including Matillion. Add a teammate to one account's channel and let the next QBR pack draft itself.