Run founder-led sales, then hand it off
You are the best rep and the bottleneck. Run the motion, then build the team to take it.
Run founder-led sales, then hand it off
You are the best rep and the bottleneck.
Run the motion, then build the team to take it.
Details
Details
Details
Details
0 to #1 region
Built a market from zero, hands-on, beating remote incumbents.
A repeatable discovery
Outreach motion
The scorecard
Ramp to hand it to your first hires
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.
Runs your call against your qualification framework, captures the deal, and names the gaps you still have to fill.
From a prospect and a specific angle, writes a short email or 3-touch sequence built on one idea, no filler.
The outcomes the role must hit, the competencies that predict them, questions per competency, and a shared rubric.
A 30/60/90 with milestones, a certification bar before full load, and the manager touchpoints that catch a slow ramp early.
A repeatable discovery and outreach motion, and the scorecard and ramp to hand it to your first hires.
- 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: Solo founder closes most deals herself, is about to make her first two AE hires, and has never written down how she actually runs a call.
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: You improvise comp and live with it for a year.
Without it: The hire pitches a deck you stopped believing months ago.
Without it: The handoff is oral history, and it decays fast.
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 ›
Built Texas from zero to the number-one region in the country.
See the full story →A handoff is only as clean as the motion you documented
The discovery framework and outreach skills hand you a motion you can run alone; the company comes from the day a hire runs it without you on the call. Here is how a founder sells now while building the handoff from day one.
The first hire watches you run the documented discovery, then runs it while you watch, then runs it alone with call reviews. Each rung has a bar to clear before the next, and quota only starts at the top.
- 01Write the read down after every call
After each discovery call, note what you asked, what landed, and what you would change in the framework doc. The motion you can hand off is the one on paper, not the one in your head.
- 02Keep a weekly pipeline hour, even alone
Review your own deals against the discovery-framework every week before there is a team. The cadence you run solo is the one your first hire inherits.
- 03Hire against the scorecard, not the vibe
The hiring-scorecard exists so a great interview does not override the profile. Score every candidate the same way and rehearse the roleplay you will run them through.
- 04Certify the hire before the quota does
Run the enablement-plan ramp with a real cert bar: the hire clears your discovery roleplay and a shadowed live call before carrying a number. Ready is observed, not assumed.
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.