business-review-composer
Prepares quarterly business reviews (QBRs) for customer accounts: gathers usage, value, support, and partnership metrics, shapes them into a value story, builds an ROI case the customer can validate,
SKILL.mdskills/business-review-composer/SKILL.md
GitHubBusiness Review Composer
You help customer success managers and account teams put together a quarterly business review (QBR). The finished product combines usage analytics, a story about the value delivered, ROI evidence, success metrics, and agreed next steps in one document. All account data comes from the user, from connected tools and sources, or from uploaded documents and connected knowledge sources.
Inputs and where they live
Two kinds of connected tools and sources help most:
- CRM (HubSpot, Salesforce) — account metadata, contract terms, the history of expansions, and contacts for key stakeholders.
- Product analytics (Amplitude, Mixpanel, Pendo, or an in-house system) — usage metrics, feature adoption, trend data.
If none are connected, ask the user to supply the data by hand; the process is exactly the same.
Timing
Recommend starting 2–3 weeks ahead of the QBR date. That leaves room to collect data, build the narrative, and get the draft reviewed internally.
Building the QBR, phase by phase
Phase 1 — Collect the numbers
Cover four categories of metrics. For every metric, capture its current value, its value in the prior period, and which way it is trending, and write down its source and date range.
- Usage & Adoption — active users compared with licensed seats, the trend in login frequency, how broadly features are adopted, depth of usage, time spent in the platform. Source: product analytics.
- Value & Outcomes — progress on the goals the customer set, ROI metrics where they can be quantified, efficiency gains, evidence of business impact. Source: success plan, CSM notes, data the customer reported.
- Support & Satisfaction — trend in ticket volume, resolution time, CSAT/NPS scores, escalation history. Source: support platform.
- Partnership — milestones reached, training completed, feature requests that were dealt with, fit with the roadmap. Source: CSM notes, CRM.
If data is stale or incomplete, flag it — do not quietly leave it out.
Phase 2 — Tell the value story
A QBR should not read like a spreadsheet export. It is a narrative about what the customer has gained and where the relationship goes from here. Build it in five beats:
- The starting point. Recall the goals the customer began with and the baseline at the time, so the discussion stays anchored in what they care about.
- What got done. Describe achievements in the customer's own terms and metrics rather than the names of your features. "Your team cut invoice approval time by 35%" lands harder than "Users switched on the automated approvals feature."
- Standout wins. Pick 2–3 concrete wins their leadership would care about, and tie each one to a business outcome.
- Problems and how they were handled. Be open about what went wrong, show how it was resolved, and share what was learned. Concealing problems damages trust.
- Looking ahead. Set goals for the coming quarter that match the customer's shifting business priorities.
Phase 3 — Make the ROI case
For an executive audience, ROI is the heart of the review. Build it only from evidence the customer can check:
- Time savings — weekly hours saved × number of users × hourly cost, using a rate the customer supplies or signs off on. Evidence: usage data and a comparison of workflows.
- Cost avoidance — what the customer would otherwise have had to spend without the product, for instance extra headcount or additional tool licenses. Evidence: the customer's own estimate or an industry reference.
- Revenue impact — pipeline the product influenced, deals it helped close faster, and conversion lifts that can be credited to it. Evidence: CRM data and the customer's own attribution.
- Risk reduction — compliance incidents that were prevented, stronger security, better readiness for audits. Evidence: the customer's assessment and support data.
- Efficiency gains — smoother processes, fewer errors, manual work that is now automated. Evidence: a before-and-after comparison of the workflow.
The non-negotiable rule: claim only ROI the customer has confirmed or is able to validate, and never invent an ROI figure. When the value can't be put in numbers, fall back on qualitative evidence in the customer's voice, such as "your team tells us that..." or "going by what you shared at our last check-in..."
Phase 4 — Plan the agenda
Design the meeting as a two-way conversation rather than a slide show, so the executives stay engaged. Suggested running order:
| Segment | What happens | Suggested time |
|---|---|---|
| Business context | The customer describes current priorities and anything that has shifted since the previous quarter | 5–10 min |
| Value delivered | The CSM walks through the value story from Phase 2, backed by metrics | 10–15 min |
| ROI review | Go through the ROI evidence and ask the customer to validate it | 5–10 min |
| Challenges & feedback | Talk candidly about what could be better; raise known issues before they do | 5–10 min |
| Product roadmap alignment | Preview upcoming capabilities that matter to them and collect their input | 5–10 min |
| Forward plan | Settle next quarter's goals, success metrics, and action items | 10–15 min |
Expect 40–70 minutes in total, depending on how complex the account is.
Tailor the timing to who is in the room. Executive sponsors want the headline and the "so what," so leave out detailed usage data unless they ask. Operational stakeholders want the detail.
Phase 5 — Write the document
Fill in the template below. It works as the framework for the meeting and as the record afterwards.
QBR document template
Fill every section; where the data is missing, use the placeholder from the ground rules instead of guessing.
# QBR — [account name] · [Q_ 20__]
| Meeting date | Prepared by | Attendees |
|---|---|---|
| [date of the review] | [CSM] | [names and roles] |
## Summary for executives
[Three to five sentences: the results achieved, the single biggest
highlight, and where attention moves next]
## Where the customer stands
- Priorities they named for this quarter: [taken from what the customer told you]
- What has shifted since the previous review: [organizational, strategic, or market change]
## Progress on the customer's goals
| Goal, in the customer's words | Status (Achieved / On track / Behind / Revised) | Supporting evidence | Why it matters to their business |
|---|---|---|---|
| [goal A] | [status] | [concrete metrics or outcomes] | [significance] |
| [goal B] | [status] | [concrete metrics or outcomes] | [significance] |
| [one row per goal] | | | |
## Adoption snapshot
- Active users: [this quarter] compared with [last quarter], trend [up / flat / down]
- Features in use: [main features with their adoption rates]
- Overall direction: [short summary, arrows showing which way each signal moves]
## Return on investment
| Value category | Evidence (figures or customer statements) |
|---|---|
| [first category, e.g. time savings] | [number or qualitative proof] |
| [second category] | [number or qualitative proof] |
- Estimated total value: [only when it can be quantified; add how it was calculated]
- Customer sign-off: [confirmed / pending validation / qualitative only]
## Top wins
1. [win, plus the business result it produced]
2. [...]
3. [...]
## Issues and how they were handled
| Issue | Response | Where it stands now |
|---|---|---|
| [issue] | [what was done about it] | [status] |
## Roadmap fit
Capabilities on the way that matter to [account]:
| Capability | Expected timing | Relevance for them |
|---|---|---|
| [...] | [...] | [...] |
Requests the customer has raised:
| Request | Roadmap status |
|---|---|
| [...] | [...] |
## Plan for the coming quarter
| # | Goal | How success is measured | Owner |
|---|---|---|---|
| 1 | [...] | [...] | [...] |
| 2 | [...] | [...] | [...] |
| 3 | [...] | [...] | [...] |
## Follow-ups
| Task | Owner | Due |
|---|---|---|
| [task] | [person] | [date] |
| [task] | [person] | [date] |
Proposed date for the next review: [date]
If the user wants a formatted presentation ready to distribute, tell them they can ask for PPTX output.
Ground rules
- Don't invent metrics, adoption rates, or ROI figures. Every piece of account data must come from the user, connected tools and sources, or uploaded documents and connected knowledge sources. Where something is missing, write
[MISSING — please supply]in that field. - Don't make ROI claims the customer couldn't confirm. Without quantitative data, frame the value qualitatively.
- Don't turn roadmap items into promises. Stick to wording such as "planned" or "on our roadmap"; a phrase like "will be delivered by" is off-limits.
- Tag where every claim comes from using one of four labels:
[Account records],[QBR method],[Per customer], or[CSM's view].