Skip to main content
A QBR is supposed to take an hour to prep and instead takes half a day. The CSM pulls usage data, support history, deal notes, and an exec summary into a slide deck — and does that for 12 accounts a quarter. A QBR Agent does the assembly so the CSM spends time on the insight, not the data hunting.

​
When this pays off

QBRs slip or shrink

Reviews get cancelled or shortened because nobody had time to prep — the customer notices.

Inconsistent across CSMs

Senior CSMs ship excellent QBRs; newer ones ship rough ones — the customer experience varies wildly.

Manual data pulling

CSMs are exporting from HubSpot, screenshotting Looker, copying from Zendesk — the same way every time.

Strategic content is rushed

The “next quarter recommendation” slide always gets written last, briefly, because data prep ate the time.

​
The shape of this use case

A QBR Agent takes an account + time window and returns a structured review with sourced data.

Inputs

Account, review period, audience (operational vs exec), template / brand to follow.

Sources

CRM activity, support ticket history, product analytics, deal notes, your QBR template, segment playbooks.

Output

A draft QBR — usage summary, support summary, business outcomes, recommended next quarter, cited data — in your team’s format.

Delivery

Posted to a Notion or Google Doc for the CSM to refine, emailed as a draft, dropped into a Slack thread for review.

​
Where to start

Two ways in, depending on whether you want something running today or built to your exact spec.

Clone a pre-built Agent

Open the Customer Success Manager. More in the Marketplace.

Build your own

Start from scratch in the builder, or by describing it in Claude Code or Cursor with Programmatic GTM.
Either way, these are prompts your CSMs can use on day one:
  • “Draft a QBR for Acme Corp covering last quarter — usage, support summary, business wins, recommended next steps.”
  • “What did Globex achieve this year vs. their stated goals? Pull from CRM notes and product usage.”
  • “Give me the operational summary slide for Initech’s QBR — usage trends and support trend only.”

​
Where to take it

Once it’s running, deepen it in three moves:

Give it a playbook

Shape it with a prompt, your QBR template in Knowledge, and a connected CRM, support, and analytics.

Automate it on signals

Wrap it in a workflow that fires on a trigger.

Let it improve

Feed back which QBR sections landed into the Agent’s evals so the format tracks what’s used.

​
Common pitfalls

A QBR that lists metrics without telling a story is just a report. Force the prompt to summarize what changed and why it matters.
Enterprise QBRs and mid-market QBRs should look different. Branch the prompt on segment so the depth and audience tone shift accordingly.
Tempting to skip the CSM read. Don’t — a misread on a strategic account is a relationship cost. The Agent drafts, the CSM ships.
If the Agent pulls product usage but doesn’t filter by account properly, you get the wrong numbers in front of an exec. Validate the data sources for the top 10 accounts before going live.