Prepare a customer business review around agreed outcomes, adoption evidence, delivered value, unresolved risks, roadmap-relevant needs, stakeholder decisions, and next-period priorities rather than a provider activity recap.
Scanned 9/11/2026
Install to Claude Code
npx -y skills add Dadmin88/hermes-profile-packs --skill qbr-prep --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Qbr Prep?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/dadmin88-qbr-prep)More formats (shields.io, HTML) on the badges page.
---
name: qbr-prep
description: Prepare a customer business review around agreed outcomes, adoption evidence, delivered value, unresolved risks, roadmap-relevant needs, stakeholder decisions, and next-period priorities rather than a provider activity recap.
---
# QBR Preparation
Use when a periodic customer review should evaluate shared outcomes and align the next phase of the relationship.
## Procedure
1. Revisit the customer's goals, success measures, contract or program context, prior commitments, and decisions from the previous review.
2. Gather current adoption, outcome, support, service, project, and stakeholder evidence with dates and definitions.
3. Compare results with agreed goals and explain material gaps or changes in context without hiding poor outcomes behind activity volume.
4. Summarize delivered value using customer-relevant evidence and identify areas where value is not yet proven.
5. Surface unresolved risks, dependencies, product gaps, process issues, and customer-owned actions before presenting future opportunities.
6. Identify the few decisions or priorities the meeting needs from each stakeholder group.
7. Coordinate product, support, commercial, technical, or executive input only where their ownership is needed.
8. End with a proposed next-period success plan, owners, measures, and follow-up actions that can be recorded durably.
## Decision rules
- A business review should center the customer's outcomes, not the vendor's list of completed tasks.
- Do not present roadmap promises without Product ownership.
- Use evidence and dates instead of vague health language.
- Every proposed next step should have an owner and reason.
## Quality gate
Preparation is complete when current outcomes and evidence are clear, gaps and risks are visible, the meeting has explicit decisions to make, specialist commitments are accurately represented, and the proposed next period is measurable rather than a list of good intentions.Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!