Save an at-risk renewal
A renewal is slipping. Catch it early and save it before it is a loss.
Save an at-risk renewal
A renewal is slipping.
Catch it early and save it before it is a loss.
Details
Details
Details
Details
Churn and downgrades down 28%
Proactive retention: a 90-day early-warning motion.
An early verdict
The real reason
The right levers
A save sequence with exit criteria
The workflow that solves it, one step at a time.
Each step is the plain question you are already asking. The skills answer them in order, one handing its receipt to the next.
Combines adoption, champion stability, support sentiment, and competitive signals into one per-deal verdict.
Puts meetings, replies, and sequence activity on one timeline and flags the moment a champion goes dark.
Diagnoses the actual cause, matches commercial and non-commercial levers to it, and runs a multi-touch save sequence.
The value recap, price and term options, the concession ladder, and the answer to 'we want a discount,' protecting net retention.
An early verdict, the real reason, the right levers, and a save sequence with exit criteria.
- All 4 chained skills resolve to real, scored skills.
- Has a problem, an outcome, 2+ steps, and proof from a real build.
- Ships an example chat showing the play run in Claude.
- Reads in plain operator voice, grounded in a real build.
We did not just check the structure. A judge read this play against the full text of every skill it chains (composition), then ran it on a real scenario end to end (simulated). It passed both. Test scenario: Priya, a CSM, has a renewal in 45 days that 'feels off' and needs a straight read plus a save plan.
This play runs across the org, not inside sales.
Every function below owns a piece of the play. Skip one and it stalls where most GTM plays stall: in the handoff.
Without it: The save plan promises what nobody is building
Without it: Every save becomes a discount and net retention bleeds
Without it: The CSM fights an exec decision alone and loses
Watch the skills answer in order.
Describe your situation in plain language. The right skill fires on its own and hands its receipt to the next.
Before you run it, I ran it for real.
This workflow is genericized from a real build. Here is the number it moved, and what I actually did.
WHAT I DID ›
If your CSMs find out about churn from the customer, you do not have a retention motion, you have a notification system. Build the autopsy, score the risk, and start the renewal conversation ninety days out.
Dig into the full build →The verdict is only as good as the call that follows
The skills hand a CSM an early verdict, a read on the champion, a sequenced save plan, and a negotiation frame; the renewal is saved in one honest conversation about why it is really slipping. Here is how a CS leader makes that conversation happen early instead of at the eleventh hour.
A red flag from renewal-health-analyst starts a clock: diagnosis run, save plan drafted, customer conversation booked inside the window you set. CSMs rehearse the hard call before the drill ever goes live.
- 01Teach the reads behind the verdict
Walk CSMs through what a dark champion from conversation-analyst and a usage slide each mean, so a red flag earns action instead of debate.
- 02Set the flag-to-conversation SLA
Every red verdict gets a booked customer conversation within the week. Open the renewal review with the flags still waiting.
- 03Rehearse the why-are-you-leaving call
Roleplay the conversation where the CSM asks what is really wrong and does not flinch at the answer. The save-play only works on the real reason.
- 04Coach the saves and the losses together
Review which levers flipped accounts and which discounts just delayed the exit, then reweight the save-play. A save that holds through the next renewal is the only kind that counts.
One plugin. 4 skills, bundled.
The whole playbook installs as a single plugin in Claude Code, no copy-pasting 4 times. Or grab any single step above. It runs on what you paste; connect your stack to go live.