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.
Details
Details
Details
Details
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.
A goal-tied plan
An adoption habit
A first-90-day read
A QBR that earns the renewal
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.
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 CSM spends two weeks re-discovering what sales already knew
Without it: The same snag stalls every new customer, forever
Without it: Onboarding health is a feeling, not a number
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 handoff is only as good as the first goal written
The skills hand a CSM a goal-tied plan, an adoption habit, an activation read, and a QBR; the renewal is decided in the first weeks, when the customer learns whether anyone heard what they bought this for. Here is how a CS leader makes the first goal conversation a standard, not a talent.
Every new account opens with the success-plan goal conversation inside the first week, and CSMs certify on running that conversation before they take kickoffs solo. Inspect the written goal, not the kickoff deck.
- 01Teach the goal translation
Train CSMs to turn a stated business goal into time-to-value milestones instead of a feature checklist. The success-plan is only as useful as that translation.
- 02Make Day 30 a tripwire
The onboarding-analyst read at Day 30 either confirms the plan or changes it. A miss triggers a revised plan and a customer conversation, not a note in the CRM.
- 03Rehearse the habit pitch
The adoption-plan bets on one habit. Roleplay the moment the CSM sells that habit to a busy team that did not choose the tool.
- 04Read QBRs against the first goal
Before any qbr-builder deck ships, check it against the original success plan. If it cannot name progress toward the goal the customer stated, it is not ready for the room.
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.