Build your first Play
in 7 days
I build your Employee Zero and ship your first Play on your real product. Scoped on Day 1. Running by Day 3. Yours forever by Day 7.
How a Play actually works.
Employee Zero is the agent. It holds your context. Product, customers, positioning, voice. A Play is a workflow the agent runs. Scoped to one PMM job. Producing one specific artifact. Always on.
Your context
loaded on Day 1
- ◆
Product
What you sell, plainly
- ◆
ICP
Who it's for, and who it isn't
- ◆
Positioning
Category, alternatives, wedge
- ◆
Messaging
POV, VP, benefits, proof
- ◆
Voice
Words you use, words you never use
- ◆
Proof
Quotes, metrics, customer names
lives in CLAUDE.md
Your Employee Zero
holds all the context
The brain that never sleeps. Never asks you to re-explain your product. Already sounds like you.
Runs your Play
Artifacts you can demo
starting Day 3
- ✓
Launch brief, running on your product
- ✓
Tested message variants, ranked by ICP fit
- ✓
Battle cards that update themselves
- ✓
Messaging score before anything ships
ships to Slack · GitHub · Notion
Pick your first
On the kickoff call, you pick one of the four Plays. Each one is scoped, spec'd, and battle-tested. Build the next ones yourself. The foundation's already there.
The Launch Play
The Positioning Play
The Enablement Play
The Message-Fit Play
What happens, day by day.
Kickoff + Context Load
45-minute call. We define the Play scope. I load your CLAUDE.md with product, ICP, positioning, voice, messaging hierarchy. Whatever you have today, we use.
Agent Build
I build your Employee Zero and scope your first Play. You get async updates on Slack. By Day 3, the Play is running on your real product. Not a toy example.
Tune + Trigger
We review the first live outputs together. I wire triggers and integrations (Slack, GitHub, Notion, cron). You start using it.
Handoff
30-minute handoff call. You own the code, the CLAUDE.md, and the Play. You walk out running it, not waiting for me.
A working system, not a deck.
Custom CLAUDE.md built with you (your product, customers, ICP, positioning, voice, proof)
Your Employee Zero (the agent that holds all that context, forever)
One Play scoped, built, and tested on your actual product
Triggers + integrations wired (Slack, GitHub, Notion, cron, webhook)
System docs + 30-day async Slack access
Alumni community (other Sprint-grad PMMs sharing what they're building)
Priority access to new Plays (2 weeks before public release)
Service guarantee. I keep working until you can demo it.
The Sprint is the foundation.
Once Employee Zero exists, building more Plays gets radically cheaper. The context is already there. Two paths forward, and you can take both.
Book Training
4-hour 1:1 block where I teach you to scope and build your next Play on the Employee Zero you already own. You walk out having shipped it live. $2,000.
- ✓ Live 4-hour build session on your real work
- ✓ Second Play scoped, built, and shipped during the session
- ✓ Recording + 14-day async Slack follow-up
Stack more Plays on Employee Zero
The hard part is done. Context loaded. First CLAUDE.md written. First Play scoped. Every Play after that is a fraction of the effort. You already have the pattern.
- ✓ Pull new skills from the public pmm-skillset
- ✓ Alumni Slack for patterns, questions, and prompt shares
- ✓ Priority access to every new Play I build. Two weeks before public release.
The Sprint was the unlock. This is the compound.
The Sprint
Four Sprint spots open per month. When they're gone, waitlist reopens the following month.
Not ready for a Sprint? Install a free skill first →