qbr-ebr-builder

name	qbr-ebr-builder
description	Build QBR and EBR deliverables that align customer goals, business outcomes, risks, and next steps. Use when asked to prepare a quarterly business review, executive business review, or customer account review for leadership. Route internal-only account review prep to account-brief-builder. For one-off executive meeting prep, use executive-briefing-builder.

QBR EBR Builder

Create outcome-led QBR/EBR materials that help both teams agree what happened, what changed, and what to do next.

Confirm Inputs First

Collect the minimum required inputs:

• Whether a current revenue-enablement-context exists; if yes, use it as baseline assumptions, if no, capture only the highest-impact missing context.
• Review type (QBR or EBR)
• Review mode (customer-facing or internal account review)
• Customer goals and success criteria
• Time period and baseline
• Performance metrics and evidence
• Risks, opportunities, and desired decisions

If critical inputs are missing, ask for the smallest missing set. If the user wants speed, proceed with labeled assumptions.

Read The Right Reference

• For QBR vs EBR distinctions and default structure, read references/qbr-ebr-structure.md.

Default Workflow

1. Clarify review objective. Define what the review needs to decide, align on, or move forward. Confirm whether the output is customer-facing or internal-only.

2. Anchor on customer outcomes. Frame the review around the customer's business goals, not your activity volume.

3. Build evidence narrative. Show progress from baseline to current state with key metrics, customer feedback, and proof points.

4. Surface risks and opportunities. Call out risks, blockers, and expansion or acceleration opportunities that are actually supported.

5. Convert to joint plan. Define the next-quarter actions, owners, and check-in cadence. For internal-only reviews, keep internal controls and escalation notes outside the customer-facing version.

Tool Notes

• CRM and CS platform are useful for account health and commercial context.
• BI is useful for trend data and outcome proof points.
• Slides/Docs are useful for delivery; keep source tables reusable for next cycle.

Keep workflow tool-agnostic when these systems are unavailable.

Output Contract

Deliver:

1. Review objective and decisions requested
2. Customer goals and baseline snapshot
3. Outcome scorecard (progress and evidence)
4. Risks and opportunity analysis
5. Strategic recommendations
6. Joint action plan with owners and dates
7. Review mode notes (customer-facing vs internal)
8. Open questions and assumptions

Quality Bar

• Keep the narrative tied to customer outcomes and business impact.
• Use metrics with enough interpretation to drive a decision.
• Make risks explicit with trigger and mitigation.
• Make the action plan shared, with clear ownership on both sides.
• Remove internal-only commentary before customer-facing use.
• Do not overstate impact or fabricate metrics.