From customer-success
Prepare a Quarterly Business Review for a customer account. Produces a structured QBR document with value delivered, usage highlights, and strategic recommendations. Use before quarterly customer meetings.
npx claudepluginhub hpsgd/turtlestack --plugin customer-successThis skill is limited to using the following tools:
Prepare a Quarterly Business Review for $ARGUMENTS.
Compares coding agents like Claude Code and Aider on custom YAML-defined codebase tasks using git worktrees, measuring pass rate, cost, time, and consistency.
Designs and optimizes AI agent action spaces, tool definitions, observation formats, error recovery, and context for higher task completion rates.
Designs, implements, and audits WCAG 2.2 AA accessible UIs for Web (ARIA/HTML5), iOS (SwiftUI traits), and Android (Compose semantics). Audits code for compliance gaps.
Prepare a Quarterly Business Review for $ARGUMENTS.
A QBR is a strategic conversation, not a product demo. It must lead with value delivered, acknowledge challenges honestly, and propose specific next steps. The document should be ready for presentation to the customer's executive sponsor.
Collect all relevant data before writing anything:
/customer-success:health-assessment if none exists). Record the composite score and dimension breakdown.Rule: If data is unavailable for a dimension, state the gap explicitly. Do not fabricate metrics. "Usage data unavailable — analytics integration pending" is honest; an invented number is a trust-destroying liability.
Translate raw metrics into business outcomes the customer cares about:
| Goal (from last QBR) | Target | Actual | Status | Evidence |
|---|---|---|---|---|
| [Goal 1] | [metric target] | [metric actual] | [Met / Partial / Missed] | [specific data] |
| [Goal 2] | [metric target] | [metric actual] | [Met / Partial / Missed] | [specific data] |
| Metric | Last quarter | This quarter | Change | Interpretation |
|---|---|---|---|---|
| [Key metric 1] | [value] | [value] | [+/- %] | [what this means for the customer] |
| [Key metric 2] | [value] | [value] | [+/- %] | [what this means for the customer] |
Write 2-3 paragraphs summarising the value story in business language, not product language. "Your team resolved 40% more support tickets this quarter using the automation workflows" not "Automation workflow usage increased 40%."
Rules for value analysis:
| Risk | Severity | Evidence | Recommended action |
|---|---|---|---|
| [Underutilised feature] | Medium | [adoption rate, usage data] | [Training session, workflow review] |
| [Support pattern] | [severity] | [ticket trends] | [root cause fix, process change] |
| [Relationship gap] | [severity] | [engagement signals] | [executive outreach, sponsor identification] |
| [Renewal concern] | [severity] | [commercial signals] | [value reinforcement, pricing discussion] |
Identify specific expansion signals — but only recommend expansion for healthy accounts.
| Opportunity | Signal | Estimated value | Timing |
|---|---|---|---|
| [Upsell / cross-sell opportunity] | [what triggered this — usage pattern, team growth, feature request] | [ARR impact] | [this quarter / next quarter] |
Provide 3-5 specific recommendations for the next quarter. Each must be:
Assemble the final QBR using this template:
# Quarterly Business Review: [Customer Name]
**Quarter:** [Q1/Q2/Q3/Q4 YYYY]
**Prepared by:** [CSM name]
**Date:** [date]
**Next QBR:** [scheduled date]
## Executive Summary
[3-5 sentences: health status, key wins, key challenges, top recommendation]
## Value Delivered This Quarter
### Goals Scorecard
| Goal | Target | Actual | Status |
|---|---|---|---|
| [goal] | [target] | [actual] | [Met / Partial / Missed] |
### Key Wins
1. [Win with quantified impact]
2. [Win with quantified impact]
3. [Win with quantified impact]
### Usage Trends
| Metric | Last quarter | This quarter | Change |
|---|---|---|---|
| [metric] | [value] | [value] | [delta] |
## Challenges and Lessons Learned
| Challenge | Impact | What we did | Current status |
|---|---|---|---|
| [issue] | [business impact] | [response] | [resolved / in progress / monitoring] |
## Health Overview
- **Composite score:** [0-100] ([Healthy / Neutral / At Risk / Critical])
- **Trend:** [improving / stable / declining]
- **Key signals:** [top 2-3 health signals]
## Recommendations for Next Quarter
### Goals
| Goal | Metric | Target | Owner | Timeline |
|---|---|---|---|---|
| [specific goal] | [how measured] | [number] | [us / customer] | [by when] |
### Expansion Opportunities
| Opportunity | Business case | Next step |
|---|---|---|
| [opportunity] | [why it makes sense for them] | [specific action] |
## Appendix
- Detailed usage data
- Support ticket summary
- Feature adoption breakdown
/customer-success:health-assessment — feeds the health score and dimension breakdown into the QBR. Run a health assessment before preparing the QBR./customer-success:expansion-plan — when the QBR reveals expansion opportunities in a healthy account, use this skill to build a detailed expansion plan.