War-game a renewal playbook before discount ladders, notice calendars, and success metrics harden into how every renewing account is handled.
Renewal playbooks fail when every at-risk logo gets the same concession, when notice windows are ignored until legal is late, when "retained" ARR is a one-year pause with a larger future cliff, and when CS capacity cannot clear the claimed touch plan. A polished QBR script is not evidence.
Package you must freeze
State the segments in scope, the lead times before renewal, the offer ladder with duration caps, the owners for product fixes versus commercial saves, and the success metric after renewal and ninety days later. Attach reason-code quality, margin after discounts, contractual notice rules, and CS headcount. If CS, sales, and finance disagree on why logos renew or leave, reconcile before seating.
Write the decision you will make if the war game finds nothing new, and the kill criteria if the ladder destroys margin without changing renewal quality.
Who sits
- Renewing customer. What still feels broken after the scripted save.
- Finance. Margin after discounts, cash timing, and fake retention.
- CS and account owners. Workload, playbook clarity, and escalation paths.
- Product. Which root cause the playbook ignores or dual-counts.
- Skeptic. The claim that looks strongest and is least sourced.
Optional counsel seat if auto-renew or notice statutes bind the language. Same pack for every seat.
Loop
Feed Pingpong the playbook memo and exhibits. First pass steelmans the ladder. Later passes attack from the seats above. Final pass turns surviving objections into narrower eligibility, clearer duration caps, or a product-first fix. Delete invented renewal rates and dual-counted pauses.
Force a day-after narrative: what renewing customers post publicly, which enterprise accounts demand side letters, and what competitors publish about your discount habit. If those stories are stronger than your root-cause plan, fix the package before the playbook ships. Separate expansion inside healthy accounts from save-in-flight on unhappy ones. If blended dashboards hide a soft segment, ask finance and CS seats to attack until each path has owners and kill criteria.
Ask every seat to mark which playbook steps are optional in practice. Optional steps that never run still appear in the flowchart. If CS skips health scoring under load, finance and product seats should treat that skip as a design failure. Write the mandatory steps into the package, then attack whether capacity can actually clear them.
When the playbook leans on a standing renewal discount, force finance to price the next cohort that will demand the same deal without a churn threat. Write eligibility, clawbacks, and exception owners into the package, then ask the finance and CS seats to attack those rules. Related: war-game a churn playbook, war-game a customer success playbook, pretend you are the customer success lead, war-game a discount policy, and the war-game decisions hub. Process: how to run a Pingpong.