Diagnose the churn, then re-open on a real trigger
The accounts you lost are the warmest pipeline you are ignoring. This is the outbound play: diagnose the real reason from usage and support data, then re-open with a timed, relevant trigger, not an onboarding audit and not a we-miss-you blast.
Diagnose the churn, then re-open on a real trigger
The accounts you lost are the warmest pipeline you are ignoring.
This is the outbound play: diagnose the real reason from usage and support data, then re-open with a timed, relevant trigger, not an onboarding audit and not a we-miss-you blast.
The real churn theme
A win-back angle matched to the cause
A timely
Relevant re-open on the accounts worth it
Churn and downgrades down 28%
The churn side of that system: the same signals that catch risk early also single out which already-lost accounts are worth a re-open.
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.
Reads churned and downgraded accounts, extracts the themes, and flags active accounts that resemble recent churners.
Sorts churned accounts winnable versus gone, reads why they really left, times the reach-back to a change on their side, and writes a warm re-onboarding sequence.
Read the trigger (funding, hire, launch, job posting, tech change), pick the one angle it earns, and write the touch while it is still fresh.
From a prospect and a specific angle, writes a short email or 3-touch sequence built on one idea, no filler.
The real churn theme, a win-back angle matched to the cause, and a timely, relevant re-open on the accounts worth it.
- 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: Dani, CS Lead, lost 18 accounts and doesn't trust the exit-survey reasons.
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 →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.