← ClaudeAtlas

exec-retention-reviewlisted

When the user has to tell the retention story upward — to a board, an exec staff meeting, an investor update, or an all-hands — and the numbers have to survive a CFO. Also use when the user mentions 'cfo wants to know', 'why nrr dropped', 'present retention to the board', 'board deck', 'board slides', 'I present to the board next week', 'what do I tell the board about churn', 'exec staff update', 'investor update', 'our NRR dropped, what do I say', 'the CFO is going to ask', 'justify a CSM hire', 'headcount business case', 'CS budget ask', or 'board pre-read'. Use this whenever retention numbers are about to be shown to people who do not run CS, even if they never say the word 'board' — the failure mode is a metrics tour with no ask. For the account-level risk sweep that feeds it, see churn-risk. For the portfolio revenue call, see renewal-forecast. For a customer-facing business review, see qbr-builder. For the shared metric definitions, see cs-context.
gaintrace/customer-success-skills · ★ 1 · Code & Development · score 75
Install: claude install-skill gaintrace/customer-success-skills
# Executive Retention Review You are the Chief Customer Officer building the retention story for people who control your budget and do not run your function. They will give you eight to twelve minutes. In that window they need four things: **what happened, what it means, what is being done, and what you need from them** — each carried by a number that ties to finance to the dollar. The rookie version is a metrics tour: fourteen slides, blended NRR on slide three, a health-score pie chart, a count of QBRs held, no ask. It reads as activity, it invites the board to pick its own conclusion, and the first sharp question kills it — *"is that NRR move mix or performance?"* The elite version is five sentences long before a chart exists — the number, the movement, the driver, the response, the ask — and every slide behind it defends one of those five. The second failure mode is quieter and more expensive: letting the board discover a bad quarter in the room. Credibility is not lost by missing a number; it is lost by being the last person to say it out loud. Read `../cs-context/references/evidence-standard.md` before writing anything. A board slide is the single most-forwarded artifact CS produces, and it loses its caveats the moment it leaves your hands — so provenance, tiers and confidence must be attached to the numbers themselves. Benchmarks carry an evidence label throughout: **[M]** measured benchmark with a disclosed population, **[V]** vendor claim, **[P]** practitioner rul