Draft QBR decks and briefing docs weekly for accounts due a review
Every week, this agent finds accounts due for a quarterly business review and drafts the deck and a briefing doc from product, CRM and support data. Account managers start from a draft instead of a blank page.
Paste this into ChatGPT, Claude or your agent tool. See the prompt
- CS / Expansion
- intermediate
- CS
- Sales leader
- Category
- CS / Expansion
- Difficulty
- Intermediate
- Est. cost
- Not stated by source
Works with
Problem
QBR material is scattered across the product database, CRM notes and support tickets, so prep takes an afternoon per account and gets rushed or skipped.
Setup
A weekly cron on Kortix spawns an isolated session with read-only access to Postgres and HubSpot, finds every account with a QBR due in the coming window, and drafts a deck plus a companion briefing doc per account. It never writes to source systems or presents anything; the CSM edits the story.
Prompt
Starter prompt by The GTM Agent Weekly, written from the setup described on this page. It is not the source's own prompt; see the source link below for their write-up.
# ROLE
Each week you find accounts with a quarterly business review coming up and draft a deck
outline plus a briefing doc for each. The CSM owns the story and edits everything.
# INPUTS
- {{CRM}}: accounts with owner, renewal date and next QBR date (read-only).
- {{USAGE}}: product usage data per account (read-only).
- {{WINDOW_DAYS}}: how far ahead to look for QBRs.
- {{DECK_TEMPLATE}}: our QBR slide structure.
# TASK
1. List accounts with a QBR due in the next {{WINDOW_DAYS}} days.
2. For each, gather: goals from the last QBR, usage trend, adoption by feature or team,
support themes, open requests, renewal timing.
3. Draft the deck outline following {{DECK_TEMPLATE}}: slide titles and two to four bullets
each, using only the data.
4. Draft a one-page briefing for the CSM: what went well, risks, questions to ask, suggested asks.
# OUTPUT
Per account: deck outline and briefing doc, saved to {{FOLDER}} for the CSM.
# GUARDRAILS
- Read-only. Never write to source systems, never send or present anything.
- Every number comes from the data with its date range. Missing data: say so. Replace every {{PLACEHOLDER}} before running. Works with any capable LLM and runner.
Tools
Steps
- Schedule a weekly run with read-only credentials to product data and the CRM.
- Find accounts whose next QBR falls in the coming window.
- Assemble usage trends, health, notes, support history and expansion angles per account.
- Draft a deck and briefing doc, and stop there for the CSM to edit.
Results
Vendor describing its own use; no outcome data reported.
What goes wrong
Gotchas
- Write access to source systems is deliberately excluded; keep it read-only.
- Expansion angles are pattern-matched and can be wrong, which is why the CSM owns the story. (editor note)
- A quarter of support tickets is a lot of text; summaries may miss the one ticket that matters. (editor note)
Get 5 like this every week, free.
Real agent setups with sources and failure modes, in one short weekly email.
Free. One email a week. Unsubscribe anytime.
Source and credit
The Kortix Team · vendor
Source dated 2026-07-11 · last reviewed 2026-10-11. Summarized in our own words; see the source for details.