> ## Documentation Index
> Fetch the complete documentation index at: https://relevanceai-docs-tsp-1335.mintlify.site/llms.txt
> Use this file to discover all available pages before exploring further.

# QBR and business review prep

> Auto-generate exec-ready QBR decks from CRM, support, and usage data — minutes, not hours.

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

<CardGroup cols={2}>
  <Card title="QBRs slip or shrink" icon="calendar-xmark">
    Reviews get cancelled or shortened because nobody had time to prep — the customer notices.
  </Card>

  <Card title="Inconsistent across CSMs" icon="scale-unbalanced">
    Senior CSMs ship excellent QBRs; newer ones ship rough ones — the customer experience varies wildly.
  </Card>

  <Card title="Manual data pulling" icon="hammer">
    CSMs are exporting from HubSpot, screenshotting Looker, copying from Zendesk — the same way every time.
  </Card>

  <Card title="Strategic content is rushed" icon="hourglass">
    The "next quarter recommendation" slide always gets written last, briefly, because data prep ate the time.
  </Card>
</CardGroup>

## The shape of this use case

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

<CardGroup cols={2}>
  <Card title="Inputs" icon="arrow-right-to-bracket">
    Account, review period, audience (operational vs exec), template / brand to follow.
  </Card>

  <Card title="Sources" icon="globe">
    CRM activity, support ticket history, product analytics, deal notes, your QBR template, segment playbooks.
  </Card>

  <Card title="Output" icon="file-lines">
    A draft QBR — usage summary, support summary, business outcomes, recommended next quarter, cited data — in your team's format.
  </Card>

  <Card title="Delivery" icon="paper-plane">
    Posted to a [Notion](/integrations/popular-integrations/notion) or Google Doc for the CSM to refine, emailed as a draft, dropped into a [Slack](/integrations/popular-integrations/slack) thread for review.
  </Card>
</CardGroup>

## Where to start

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

<CardGroup cols={2}>
  <Card title="Clone a pre-built Agent" icon="copy">
    Open the **[Customer Success Manager](https://marketplace.relevanceai.com/listing/b9b5e05c-4512-4749-8f66-4623ab895e21)**. More in the [Marketplace](/get-started/marketplace/introduction).
  </Card>

  <Card title="Build your own" icon="hammer">
    Start from scratch in the [builder](/build/introduction), or by describing it in Claude Code or Cursor with [Programmatic GTM](/get-started/core-concepts/programmatic-gtm).
  </Card>
</CardGroup>

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:

<CardGroup cols={3}>
  <Card title="Give it a playbook" icon="book">
    Shape it with a [prompt](/build/agents/build-your-agent/prompt), your QBR template in [Knowledge](/build/knowledge/create-knowledge), and a connected [CRM](/integrations/popular-integrations/hubspot), support, and analytics.
  </Card>

  <Card title="Automate it on signals" icon="bolt">
    Wrap it in a [workflow](/build/workforces/create-a-workforce) that fires on a [trigger](/build/agents/build-your-agent/triggers).
  </Card>

  <Card title="Let it improve" icon="arrows-rotate">
    Feed back which QBR sections landed into the Agent's [evals](/build/agents/build-your-agent/evals) so the format tracks what's used.
  </Card>
</CardGroup>

## Common pitfalls

<AccordionGroup>
  <Accordion title="Data without narrative" icon="chart-line">
    A QBR that lists metrics without telling a story is just a report. Force the prompt to summarize what changed and why it matters.
  </Accordion>

  <Accordion title="Same QBR for every segment" icon="clone">
    Enterprise QBRs and mid-market QBRs should look different. Branch the prompt on segment so the depth and audience tone shift accordingly.
  </Accordion>

  <Accordion title="Auto-sending without CSM review" icon="paper-plane">
    Tempting to skip the CSM read. Don't — a misread on a strategic account is a relationship cost. The Agent drafts, the CSM ships.
  </Accordion>

  <Accordion title="Stale or wrong attribution" icon="database">
    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.
  </Accordion>
</AccordionGroup>