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 by Day 7. Tuned by me every month after.
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 rebuilt from sources you approve
- ✓
Messaging drift flagged across your channels weekly
ships to Slack · GitHub · Notion
Pick your first
On the kickoff call, you pick one of the three Plays. Each one is scoped, spec'd, and battle-tested. Build the next ones yourself. The foundation's already there.
Compete
Position
Launch
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 you can demo.
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 you own. The repo lives in your GitHub from Day 1
Priority access to new Plays (2 weeks before public release)
Service guarantee. I keep working until you can demo it.
The Sprint ships it. The retainer keeps it sharp.
Most agents go stale within 30 days because nobody re-trains them. Your product evolves, the context drifts, and the output gets generic again. The retainer makes that my job.
Tuning + maintenance
When output drifts, I retune. New product launch, new ICP, new positioning, I update the context for you. You don't have to remember to.
Slack on tap
Async by default. Drop a question, get an answer. No daily check-ins, no fake urgency. Real PMM problems, real fixes.
Monthly review call
30 minutes a month. We check the Plays, surface what's not working, and scope opportunities for new Plays.
Drift detection + context refresh
Your product evolves. So does the agent. I refresh the CLAUDE.md when it matters and re-test the Plays against the new context.
Want a second Play? Book a Training session ($2K, 2 × 2-hour blocks) where we scope and ship Play #2 live, or scope it together on the next monthly review call. Once Employee Zero exists, every new Play is a fraction of the effort.
The Sprint
Four Sprint spots open per month. When they're gone, the waitlist reopens the following month.
Not ready for a Sprint? Install a free skill first →
Sprint FAQ
The deeper questions.
Q How many Sprint spots open per month? +
Q Do I need to be technical? +
Q Can I add more Plays after the first one? +
Q What if my product changes mid-month? +
Q Can I pause the retainer? +
Q What's the service guarantee? +
Question not here? Book a call and ask it live.