Turn closed deals into a repeatable edge
You closed 30 deals this year and could not name the one thing the wins share. The pattern in your wins and losses is the edge you are leaving on the table.
Turn closed deals into a repeatable edge
You closed 30 deals this year and could not name the one thing the wins share.
The pattern in your wins and losses is the edge you are leaving on the table.
Details
Details
Details
Details
The number-one predictor was not in the model
The win/loss backtest that found the real signal.
What wins share
Why losses happen
A coded pattern
A change you can ship
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 your won deals, finds the signals, personas, and motions that repeat, and ranks active lookalikes to work.
Sorts lost deals into no-decision, price, competitor, timing, or fit, pulls competitive intel, and splits preventable from structural.
Who to interview, the question guide, how to code themes across deals, and how to turn the pattern into a messaging or product change.
Reads closed-won, closed-lost, and churned accounts, then hands back a ranked list of lookalike accounts to work.
What wins share, why losses happen, a coded pattern, a change you can ship, and the active accounts that already look like your winners.
- 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 RevOps manager just closed the quarter and wants to know what the wins actually have in common before the team forgets the specifics.
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 pattern gets found and the floor keeps selling the old way
Without it: The same gap loses the same deal next quarter
Without it: Your best sales argument never makes the website
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 ›
Before you trust a scoring model, backtest it against the deals you actually won and lost. Measure lift per signal. The ones that feel important and the ones that are important are rarely the same list.
Dig into the full build →The pattern is only as good as the change it ships
The skills hand a RevOps leader what wins share, why losses happen, a coded pattern, and the lookalike accounts; the edge shows up only when one concrete change ships to the floor. Here is how a RevOps leader turns analysis into a shipping habit.
Every win-loss cycle ends with exactly one change chosen, owned, and dated, and the next cycle opens by reading whether it moved anything. One shipped change per cycle beats ten findings per deck.
- 01Train the second why
Win-loss interviews die on the polite first answer. Teach interviewers to hold the silence and ask what was underneath the stated reason before they code anything.
- 02Set the close-to-review clock
Every closed deal enters closed-won-analysis or closed-lost-analysis inside a set window while memory is fresh. A deal reviewed a quarter later is fiction.
- 03Pick one change and name its owner
The pattern-analyst read will surface several threads. Choose one, give it an owner and a ship date, and hold the rest for the next cycle.
- 04Retire codes that stopped predicting
Each quarter, reread the win-loss-program codes against new closes. A code that no longer separates wins from losses is noise wearing a label.
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.