Get a new customer to value, and keep them
They signed, and the CSM inherits a cold handoff, guessing at what success even means for two weeks. Get them to value fast so the renewal is already won.
Get a new customer to value, and keep them
They signed, and the CSM inherits a cold handoff, guessing at what success even means for two weeks.
Get them to value fast so the renewal is already won.
A goal-tied plan
An adoption habit
A first-90-day read
A QBR that earns the renewal
The first 90 days, scored
An early-warning motion built to start the day they sign, so a stalled time-to-value gets caught, not guessed at.
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.
Translates the customer's goals into measurable outcomes, time-to-value milestones, and the leading indicators that flag risk early.
Reads what's unused, picks the one habit to build next, and writes the enablement plan that gets there.
Tracks Day 30 / 60 / 90 activation, scores the sales-to-success handoff, and catches accounts a fit score wrote off while they were adopting.
Value delivered, adoption vs stated goals, risks named first, the roadmap, and one outcome-tied expansion ask.
A goal-tied plan, an adoption habit, a first-90-day read, and a QBR that earns the renewal.
- 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: A 50-seat mid-market deal just closed and the CSM inherits the account with only the sales-to-CS handoff notes, no defined success criteria.
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.