Pretend you are the lost customer so soft win-back copy and incomplete root-cause stories fail before outreach burns the last of the relationship.
Optimistic save packages optimize for the team that wants the logo back. The lost-customer seat does the opposite. It asks which failure still feels unresolved, which discount looks like hush money, which product promise broke in use, and which competitor now owns the workflow. A fluent apology is not evidence that trust can return.
This is one of the core moves in a serious churn or win-back war game: after you describe the offer, seat a careful former-customer perspective and make it try to decline. The output you want is not a performance. It 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 history: cancelled after a billing surprise, left after a reliability stretch, or switched after a missing feature. Give constraints: the competitor they moved to if known, the contract or invoice facts you will honor, and the outcomes you will not invent. Without constraints the seat becomes cartoonish. With constraints it produces questions you might actually hear on a save call.
Write the seat into the prompt as a named role with a mandate. Example: "Lost customer: list the top reasons you would ignore this outreach, the claim that feels least sourced, the repair that would matter most, and the ten questions you would ask before taking a meeting. Stay inside a realistic customer mandate and avoid illegal tactics."
What to demand from the pass
- Top reasons to ignore, delay, or decline the save offer.
- The claim that looks strongest and is least believed.
- The product, billing, or support wound that still dominates memory.
- What would make you take a meeting instead.
- The ten hardest questions you would send before restarting.
Run that brief in Pingpong against the real churn notes, offer draft, and product fixes. Follow with a home-team response pass so you leave with edits and proof packs, not only fear. When the save leans on a discount alone, run this seat after finance and product attacks so it can reject price theater that leaves the wound untouched.
When the plan assumes one champion still cares, force the seat to price champion risk in writing. Ask what happens if that person left, if procurement now owns the vendor list, or if the competitor is already embedded. A save path that only works with the old champion still in seat is not a plan.
Pair with war-game a churn response, pretend you are the angry customer, war-game a customer success playbook, pretend you are the first customer, and the war-game decisions hub. See how to run a Pingpong.