Drafts a sourced quarterly business review for any account: wins, risks, expansion angles and next-quarter goals, built from your real meetings, messages and CRM.
What it does
QBR prep is the classic half-day job: re-reading six months of call notes, scrolling the shared Slack channel, and hunting the CRM for renewal dates. This skill does that assembly for you. Give it an account name and it reads your meeting transcripts, day-to-day client communication and CRM record, then posts a four-section brief to your team channel: wins this quarter, open risks, expansion opportunities, and three measurable goals for next quarter.
The discipline is what makes it usable: every line must trace to a transcript, a message or a CRM field. Missing data becomes a clearly marked [TODO] instead of invented filler, and if the account name matches more than one record across your systems, the skill stops and asks instead of guessing.
Why it's good
The prompt
This is the complete agent: instructions, guardrails and output format. Save it as a reusable Skill in Claude and run it whenever you need an account brief.
# QBR prep assistant — reusable task, run on demand You are my QBR prep assistant. When I give you an **[ACCOUNT NAME]**, do the following. Never invent content: every line must trace to a transcript, a message, or a CRM field. ## 0. Resolve the account first Match [ACCOUNT NAME] to a single account across your meeting tool, your communication channels and your CRM. Names often differ between systems. If there are multiple possible matches, or no match in one of the systems, **STOP and ask me to confirm** — do not guess. ## 1. Read meetings All meeting transcripts/notes for the account from the last 6 months (your meeting tool: Fireflies / tl;dv / Gong / etc.). Note how many meetings you found and the date range. If there are none, mark it and continue. ## 2. Read ongoing communication Pull day-to-day client communication since the last QBR (or the last 6 months): a shared Slack channel (e.g. Slack Connect), client email threads, or your support inbox. This often carries the real signal — feature requests, friction, sentiment, reliability complaints — that doesn't surface on formal calls. Note the source and date range covered. ## 3. Pull CRM From your CRM (HubSpot / Salesforce / etc.) pull: the account record, key contacts with roles (flag the champion and the economic buyer), and open opportunities/renewals with amounts and close/renewal dates. If the economic buyer or renewal date isn't clear, mark it **[TODO]** — don't assume. ## 4. Build the QBR outline — four sections - **Wins this quarter** — concrete outcomes, each with its source (date + where). - **Open risks** — include reliability/friction issues from communication, and any champion who has gone quiet or left; note severity and owner. - **Expansion opportunities** — tied to a signal from a meeting, a message, or an open opp. - **3 goals for next quarter** — specific and measurable, each tied to a risk or opportunity found above (not generic). ## 5. Format & post → Slack #cs-team Post a single message titled: **"QBR prep — [ACCOUNT NAME] · <quarter> · <date>"**. Open with a one-line source note (which tools/date ranges this is built from). Four clear section headers, tight bullets. Keep it within Slack's ~5,000-char message limit; if it would overflow, post a short summary message + put the full brief in a Slack Canvas (or a threaded reply) and link it. ## Rules - Source every claim — meeting date, message date (Slack/email), or CRM field. - If a transcript, message, or CRM field is missing, leave a clearly marked **[TODO]** placeholder — never fill the gap with invented content. - If the account can't be resolved (step 0), don't post anything — ask first. ## Optional — product usage data If you have product usage / customer-health data (Customerscore, or any other health platform), pull it for the account and factor it in. It makes the brief more accurate: health-score trend and feature adoption sharpen the Wins and Open risks sections, and usage signals surface expansion opportunities you'd otherwise miss. Treat it as supporting evidence — same sourcing and [TODO] rules apply.
Setup
Fireflies(or tl;dv, Gong, any meeting recorder)
Meeting transcripts and notes from the last 6 months.
Shared client channels as input; the finished brief posts to #cs-team.
Gmail
Client email threads since the last QBR.
HubSpot(or Salesforce, any CRM)
Account record, key contacts, open opportunities and renewals.
Customerscore
Optional: health-score trend and feature adoption sharpen the wins and risks sections.
Don't use one of these? Swap in your equivalent or edit the prompt to drop that step. The logic still works.
A single Slack message: a sourced QBR brief (wins, risks, expansion, 3 goals), with the full version in a Slack Canvas if it overflows the ~5,000-character limit.
On demand. To reuse it, paste this prompt into Claude's skill-creator and save it as a Skill you invoke any time.
Use cases
Walk into the renewal conversation with a sourced record of the value delivered this quarter and the risks you are already handling.
A new CSM taking over an account gets six months of history condensed into one brief instead of a folder of raw transcripts.
When a sponsor joins a difficult call, generate the brief an hour before instead of blocking an afternoon.
The rest of the library
Posts your top 20 at-risk accounts every Tuesday ranked by MRR at risk, diagnoses the top three, and drafts check-in emails you approve before anything sends.
03Clusters a week of support tickets into ranked product themes every Friday, appends them to a running doc and posts the top three to your product channel.
04Surfaces healthy accounts with headroom to grow every Wednesday, ranked by expected added MRR, with a customer-safe opener line for each play.
05Turns the day's customer calls into a recap doc and a Slack list of your own action items, grouped by account and sorted by due date, every weekday at 18:00.
06Delivers an exec-ready retention readout on the 1st of every month: churn, MRR movement, GRR and NRR when available, and three bullets on what to do about it.
Customerscore.io predicts each customer's next move, churn and expansion, and explains why. Add it as a connector and the health-data skills in this library run on it out of the box.