Pretend you are the customer success lead so soft renewal forecasts and heroic save plays fail before the company treats them as settled.
Optimistic retention decks optimize for a tidy logo list. The customer success seat does the opposite. It asks which accounts look green because nobody logged a risk, which onboarding milestone still drifts, which expansion claim depends on one champion who may leave, and which save offer trains customers to threaten cancel. A calm health score is not evidence that the book will renew.
This is a core move in a churn, packaging, or capacity war game: after you describe the upside, seat a careful CS operator and make them try to decline. The output you want is a short list of material objections, the exhibits each needs, and the edits that would survive them.
How to cast the seat
Name a real mandate: defend a named renewal cohort without inventing adoption, absorb an executive question without silent hand-waving, or underwrite a save play without pretending support capacity is infinite. Give constraints: health definitions you will not blur, residual risk you will not hide, and concentration you will not paper over. Without constraints the seat becomes cartoonish. With constraints it produces questions you might actually hear in a QBR or board prep.
Write the seat into the prompt as a named role with a mandate. Example: "Customer success lead: list the top reasons to pause this retention plan, the assumption with the weakest source, the account or segment risk that worries you most, and the ten diligence questions you would send after review. Stay inside a realistic mandate and avoid illegal tactics."
What to demand from the pass
- Top reasons to delay, narrow the save ladder, or add a holdout cohort.
- The renewal assumption that looks strongest and is least sourced.
- The adoption, champion, or capacity gap that would worry you most.
- What would make you approve instead.
- The ten hardest diligence questions you would send in writing.
Run that brief in Pingpong against the real health exports, QBR notes, and save-play drafts. Follow with a home-team response pass so you leave with edits and named owners, not only fear. When the decision sits near a pricing or packaging change, run this seat after finance and product attacks so it can use earlier objections as ammunition.
When the plan leans on a single segment, a single CSM, or a single discount ladder, force the seat to price concentration risk in writing. Ask what happens if that CSM leaves, if usage drops in the soft cohort, or if enterprise buyers demand the same save offer without a cancel threat. Concentration that only appears in an appendix still counts. Pair with war-game a churn playbook, war-game a customer success playbook, pretend you are the angry customer, war-game a churn response, and the war-game decisions hub. See how to run a Pingpong.