Turn any build or framework into rep-ready enablement
You shipped the system, or rolled out the framework, and adoption is uneven. Most enablement is a deck and a kickoff that evaporates. Turn it into a module reps can practice and be certified on.
Turn any build or framework into rep-ready enablement
You shipped the system, or rolled out the framework, and adoption is uneven.
Most enablement is a deck and a kickoff that evaporates. Turn it into a module reps can practice and be certified on.
Details
Details
Details
Details
Details
The other half of the deal hub
The system cut the busywork; the deal review and the coaching are what moved the deal.
Coached reps to earn the room
The love test found the gap; rehearsing the reach-up is what closed it.
Rehearsed the save before the call
The score saw the churn coming; the renewal review and the roleplay did something about it.
An account tier
The buyer persona inside it
The questions
The talk track
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.
Names your tiers with explicit criteria, the fit signals, the anti-ICP you exclude on purpose, and a qualification framework, plus an evolution log. A category is not a definition.
Tailored discovery questions sequenced problem to impact to next step, each mapped to your qualification framework.
Maps every feature you plan to show to a problem the buyer actually stated, and cuts what does not map.
Turns a deal, framework, or objection into a live AI roleplay partner, then scores the rep against the framework with a cert bar.
A 30/60/90 with milestones, a certification bar before full load, and the manager touchpoints that catch a slow ramp early.
An account tier and the buyer persona inside it, the questions, the talk track, an AI roleplay to practice against, and a 30/60/90 ramp with a certification bar. The people half of every build, made runnable.
- All 5 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 Head of Sales rolled out the product-channel play last month; adoption is inconsistent because half the team never got real enablement on it, just a Slack announcement.
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 module evaporates like the deck it replaced.
Without it: Certified reps demo things the product cannot do.
Without it: Reps drill the wrong buyer, fluently.
Without it: Nobody can show the module moved the 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 ›
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 →WHAT I DID ›
Reps invest effort where interest already exists. The fix is not more leads, it is a prospecting motion that earns attention before the account gives it: multi-step, every channel, threaded across the whole buying committee.
Dig into the full build →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 →A module is only as good as the manager inspecting it
The skills hand the team a persona-anchored module: the questions, the talk track, the roleplay, and the ramp; the adoption comes from managers holding the bar after the kickoff ends. Here is how an enablement leader makes the module stick past week two.
Every rep clears the roleplay cert bar before running the motion live, then a manager listens to a real call within two weeks to verify the module survived contact. Gaps go back into the module, not into a reminder email.
- 01Anchor every rep in the persona
Before the questions or the talk track, have each rep describe the persona from define-your-icp in their own words: the person, the day, the problem. A rep who cannot say it will not discover it.
- 02Run the cert bar for real
The roleplay-scenario-generator sets the scenario; the bar is pass or not yet, with a scheduled retry. A cert everyone passes on attempt one is a ceremony, not a bar.
- 03Keep manager touchpoints on the calendar
The 30/60/90 in the enablement-plan names manager checkpoints; hold them as standing meetings, not intentions. The ramp slips exactly where the touchpoints do.
- 04Verify on live calls, then revise
Listen to real calls against the demo-script and question set, and treat every recurring gap as a module defect first. Fix the module before coaching the rep on it twice.
One plugin. 5 skills, bundled.
The whole playbook installs as a single plugin in Claude Code, no copy-pasting 5 times. Or grab any single step above. It runs on what you paste; connect your stack to go live.