qbr-builderlisted

When the user needs to prepare or write a quarterly or executive business review — the qualification call, the objectives, the value case, the deck, next-period goals and the close. Also use when the user mentions 'build the qbr', 'qbr for', 'qbr deck by', 'build me a QBR', 'QBR deck', 'quarterly business review', 'EBR', 'executive business review', 'I have a QBR next week', 'what should go in the QBR', 'prove ROI to the customer', 'value realization', 'show them the value', 'their CFO is asking what we get for this', 'what does my champion tell their CFO', or 'do we even need a QBR'. Use this whenever a recurring strategic customer meeting has to prove value and agree next-period goals, even if they never say 'QBR' — including an annual review, a check-in with their exec, or a request to see ROI. For a single call, see pre-call-brief. For the renewal runbook, see renewal-prep. For account risk, see churn-risk. For the expansion case, see expansion-finder. For what to send after, see post-call-followup.
gaintrace/customer-success-skills · ★ 1 · Web & Frontend · score 75

Install: claude install-skill gaintrace/customer-success-skills

# QBR / EBR Builder You are building the one meeting each period where a customer executive decides, silently, whether this line item survives their next budget review. The standard is not "a deck that covers the quarter" but: **the economic buyer stays in the room, agrees a number they would repeat to their own CFO, and commits to something with a date on it.** The rookie version is a status report about us. The elite version opens on the biggest miss, proves movement against a baseline *they* agreed in advance, carries **one** number they said out loud, and hands the champion a page they present as their own. Three failures cost the most: a number their finance team rejects takes every other number down with it; a decision reaching the room unwired gets debated instead of ratified; and running the meeting when it should have been skipped (**R15**) teaches the customer our meetings are optional. Read `../cs-context/references/evidence-standard.md` first, then `../cs-context/references/operating-rules.md` for the rules enforced here — **R15**, **R20** bad news first and once, **R23** coverage caps confidence, **R18** the firewall, **R19** no date you do not own, **R11** never attach an ask to an apology, **R1** the opt-out calendar — and `../cs-context/references/business-model-profiles.md` on any account that is not seat-based annual-contract B2B. ## Before Starting 1. **Read `.agents/cs-context.md`.** If absent, run `cs-context`. Never ask what it answers — ARR, rene