Find and land the next expansion
You keep selling the same team twice. The money is in the teams next door.
Find and land the next expansion
You keep selling the same team twice.
The money is in the teams next door.
Details
Details
Details
Details
The expansion score
Find the next team to sell inside an account.
A book-level read
The usage signals
The play
An executive ask that gets a yes
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.
Scores every account on health, lays out renewals due, shows product adoption, and flags accounts going quiet.
Turns raw usage into per-capability adoption tiers, a 12-week trend on each, power-user IDs, and a ghost-active flag.
Reads the ready signals, picks the fitting play, sizes it, and writes an outcome-anchored ask.
The value narrative tied to their strategic goals, the ROI story with math, and the one ask, higher altitude than a QBR.
A book-level read, the usage signals, the play, and an executive ask that gets a yes.
- 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: Palisade Health Systems is one of CSM Jordan's 30 accounts. Jordan wants to find the next expansion in the book.
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: CSMs find the money and nobody is paid to close it
Without it: The expansion story runs on anecdotes, not evidence
Without it: A yes in the room dies waiting on a quote
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 ›
Expansion is not re-selling your champion. It is finding the untapped team next door, and refusing to cross-sell off a beachhead that is already going dark. Score the whitespace, gate on the health of what you sold, and check the score against your CSMs gut, because the divergences are where the money is.
Dig into the full build →The signal is only as good as the ask it becomes
The skills hand a CSM the book rollup, the usage read, the play, and the executive room; the expansion lands when the ask is anchored to an outcome the executive already wants. Here is how a CS leader trains the ask instead of admiring the signals.
Before any exec-business-review is booked, the CSM delivers the ask to a mock executive room and takes the pushback cold. Certify on the rehearsal, then book the real one.
- 01Train the ready-versus-happy read
Teach the difference between an account expanding in usage and one that is merely content. product-usage-analyst shows both; only one earns the play.
- 02Run the book monthly
The book-of-business-analyst rollup lands on a fixed day, and every CSM names one expansion motion from it. No motion named is a finding in itself.
- 03Rehearse the outcome-anchored ask
The ask from expansion-playbook gets said aloud, price included, until it fits in one breath. An ask the CSM cannot say cleanly is not ready for an executive.
- 04Inspect asks against answers
Each quarter, review which asks got a yes, which stalled, and what the yeses shared. Feed that back into which plays get picked next.
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.