Win a deal against an incumbent
You are in a bake-off against a competitor. Win it without trashing anyone.
Win a deal against an incumbent
You are in a bake-off against a competitor.
Win it without trashing anyone.
Details
Details
Details
Details
Final stage 25%+ faster
The deal hub that tightened late-stage and cut discounting.
A clear read on the deal
A battlecard
A real champion
A business case that lands
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.
A sixty-second summary, a multi-source activity audit, a qualification-vs-stage gap check, and an 8-state deal-risk verdict.
Lays out where you win, their traps, the landmines to set, the reframes, and the proof behind each.
Scores who can champion, arms them with the internal-sell narrative and a forwardable one-pager, and maps the multi-thread.
Frames the cost of the problem, the change, the value model, and the risk of doing nothing, in the buyer's own numbers.
A clear read on the deal, a battlecard, a real champion, and a business case that lands.
- 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: Bramwell Logistics Software, a ~$200K ARR deal. AE Alex is in a bake-off against Outreach; the deal has been stalled 3 weeks with one engaged contact.
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: Reps fight this quarter's rival with last year's card
Without it: A rep bluffs a gap and the buyer catches it
Without it: You lose on price without ever getting to value
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 ›
Speed in a deal is not pressure. It is removing the places a deal goes to wait. Find where your deals stall, then remove the wait, not the patience.
Dig into the full build →The battlecard is only as good as the rep mid-call
The skills hand a rep the deal read, the battlecard, the champion plan, and the business case; the bake-off turns on how the rep handles the trap the competitor planted before your call. Here is how a sales leader trains recall under pressure, not familiarity with a document.
Reps take the competitor's three sharpest traps in live roleplay and must land the reframe without notes. Nobody enters a bake-off until the reframes come out sounding like them, not the card.
- 01Teach the tells of a wired deal
Use the crm-analyst read to train reps on the signs an incumbent wrote the requirements: a rigged scorecard, a single thread, a rushed timeline. Naming it early changes the play.
- 02Run the reframe drill on a cadence
A standing weekly slot, one trap per rep, live pushback. The card updates; the reflex has to update with it.
- 03Test the champion every week
The champion-plan carries one test per week: an intro made, a document shared, a meeting they set up. A champion who never passes a test is a contact.
- 04Audit losses against the card
After every bake-off, check whether the loss matched a known trap or revealed a new one, and update the battlecard the same week. A card that does not learn is a brochure.
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.