The Agentic PMM
For product marketers at B2B SaaS

I build your employee zero before one replaces you

You bring the product, the messaging, the positioning. I build the AI system that runs on all of it. And makes your work visible. Feels like a cheat code. By Friday, it's how your team sees what product marketing actually moves.

Top 100 PMM consultant by Product Marketing Alliance, nominated 2 years running
Co-host of We’re Not Marketers, 40+ PMM expert interviews shipped
Book a call
The problem

You're stuck in hack-hunting mode.

Every PMM has AI budget and permission. Nobody has a system. You tried ChatGPT, got garbage, and moved on. The problem isn't the model. It's that nothing knows how your business works.

Tool Fatigue

Every week a new AI tool drops. You've got tabs open for three of them. None of them fit the work you actually do.

The Rewrite Tax

You ask AI to help with a launch. It gives you something generic. You spend an hour rewriting it to sound like your company.

The Mumble

Your CEO asks what you're doing with AI. You mumble. They ask the new hire next.

The pre-AI PMM only has 18 months to live.

The playbook still works. Positioning canvases, launch tiers, message maps. But running them by hand stops being enough the moment your peers turn them into infrastructure they own.

91% of PMMs already want AI tools in their stack. The PMM Software Report →

The solution

Meet your employee zero.

Your first AI hire. An agent that holds your entire PMM context. Product, customers, positioning, messaging, voice.

Built with you in 7 days. On Day 1, we load its brain. By Day 7, it's running your workflows.

You stay the PMM. The agent does the work you shouldn't still be doing by hand.

01 You keep

Your voice. Your positioning. Your judgment.

The PMM brain stays yours. You get more of it, faster.

02 You lose

The rewrite tax. The blank page. The hand-built launches.

The grunt work disappears. The thinking stays.

03 You walk out with

An agent loaded with your context. Plays you're running on your real work.

Demoable by Day 3. Yours forever after Day 7.

The Plays

Pick your first Play.

A Play is a workflow your employee zero runs. Scoped to one PMM job. Producing one specific artifact. Always on. We build your first one in 7 days on your real product.

The Launch Play

Turns a product spec into a full launch plan with tested messaging. Automatically.

Drop a product spec. Get back a launch brief, a messaging hierarchy, and 8–12 tested message variants ranked by ICP fit. Plugged into GitHub, Slack, or Notion.

The Positioning Play

Detects positioning drift across channels. Keeps messaging aligned to the hierarchy.

Watches your website, ads, emails, and sales decks. Flags anything that drifts from your locked hierarchy. Weekly digest lands in Slack.

The Enablement Play

Keeps battle cards, objection handling, and competitive briefs current. Without manual updates.

Tracks your top 3–5 competitors. Rebuilds battle cards when new features ship or review signals shift. Sales gets a fresh card every Monday.

The Message-Fit Play

Scores every piece of messaging against your ICP and brand voice. Before it ships.

Runs every draft through your locked messaging hierarchy. Flags vague claims, generic copy, and voice drift. Before the CEO sees it.

claude code · your CLAUDE.md
~ claude
> /launch-play --product "your SaaS"
Loading your context from CLAUDE.md
Product context, ICP, voice loaded
Generating launch brief on your actual positioning
Draft ready: launches/q2-feature.md
Sounds like you. Tested on your ICP. Ready to ship.
~

This is one Play running. Your Sprint builds yours.

What you get

Three shifts. One Sprint.

01 B1 · Built for PMM work

Not generic AI. Not marketing-broad. Yours.

Every skill runs on real launches, real positioning, real battle cards. Designed by a PMM. Tested by 200+ of them. You can inspect the whole repo before you commit to a single thing.

02 B3 · Walk into Monday with a system

Seven days from now, you have something to show.

A real system running on your real work. Something you can show your team, your CEO, and your next interviewer. Not a deck. A demo.

03 B2 · Sounds like you wrote it

Because it was trained on what you wrote.

On Day 1, the system learns your product, your customers, your voice. So the first draft already reads like something you'd actually send. You edit less because less is wrong.

Peer signal

PMMs are already in.

200+

PMMs running the free skills today. Public repo. Open-source code you can audit.

"This feels like a freaking cheat code. This stuff used to take forever and now all I do is type 'yes' and enter and it does it all. It's nuts."

David Lim

PMM

"Just tested the launch brief. It saved me hours of work."

Jenny

PMM

"Gab's groundbreaking approach to scoring message-market fit is just one of the ways he's helping PMMs elevate the industry. He's been instrumental in making us more competitive, differentiated, and known in the market."

Michele Nieberding

Director of Product Marketing, MetaRouter

Pricing

Two ways to build.

One where I teach you to build it yourself. One where I build it for you and keep it sharp every month after.

Done with you

The Training

$2,000 one-time · 4-hour block

I teach you to build your own. We set up Claude Code, scaffold your CLAUDE.md, and ship your first skill together. You walk out confident enough to keep going on your own.

  • Live 4-hour build session, 1:1 with me
  • Custom CLAUDE.md scaffolded with you, on your real product
  • First skill installed, configured, and tested live
  • Recording of the full session, yours to keep
  • 14-day async Slack support after the session
Book a training call
Done for you

The Sprint

$5,000 setup · 7-day build
+ $1,497/month ongoing retainer

I build your Employee Zero in 7 days. Then I keep it sharp every month after — tuning Plays, refreshing context, holding the system steady as your product evolves.

Week 1 · Setup

  • Custom CLAUDE.md built with you (your context, your voice, your ICP)
  • Your Employee Zero + first Play live on your real product by Day 7
  • Triggers + integrations wired (Slack, GitHub, Notion, cron)
  • You own the code, the agent, the Play from Day 7

Ongoing · Monthly

  • Tuning + maintenance of every Play I built for you
  • Slack support, async by default
  • Monthly 30-min review call
  • Drift detection + context refresh as your product evolves
Book the Sprint

Not sure which? Book a call and we'll figure it out.

Still skeptical?

Install a skill tonight. Feel the cheat code by morning.

Free, open-source Claude Code skills. 10 minutes to install. Run one against your product and decide whether the Sprint is worth it.

Messaging HierarchyPositioning AuditICP DefinitionLaunch BriefMessage-Market Fit + 6 more
See all skills

The call to build

The PMMs still running the plays by hand will be invisible in 18 months.

The first call: 30 minutes.

The Sprint: 7 days.

The only variable is whether you start.

Be the one who builds.

Newsletter

The builds. The systems. The results.

What I'm building, what's working, what flopped. No fluff. Just the work.

No spam. Unsubscribe anytime.

Common questions

What you actually want to know.

Q What if I cancel the retainer? Do I keep the agent? +
Yes. The CLAUDE.md, the agent, and every Play I built are yours from Day 7. The retainer keeps it tuned, maintained, and aligned with your product. Cancel and the system still runs — you just inherit the maintenance.
Q What does month 2+ actually look like? +
Async by default. I monitor your Plays, retune them when output drifts, refresh your CLAUDE.md as your product evolves, and respond to anything you flag in Slack. Once a month we run a 30-minute review call to align on what's working and what's next.
Q How is this different from hiring a consultant? +
A consultant bills you when they're working. Employee Zero works when nobody is. The setup builds the system. The retainer keeps it sharp. You're not paying for hours — you're paying for a running system that holds your context forever.
Q What if it doesn't work? +
I keep building until it does. The Sprint has a service guarantee — if you can't demo a working Play by Day 7, I keep working. The retainer doesn't start until your system is live and producing output you'd actually use.
Q Who owns the code? +
You do. The repo lives in your GitHub from Day 1. Your CLAUDE.md is yours. Every Play is yours. Even if you cancel the retainer at month 2, the entire system goes with you.
Q How much of my time does this take? +
Setup week: ~3 hours total. Kickoff call (45 min), one async review per day (10 min each), handoff call (30 min). Ongoing: ~30 minutes a month for the review call. Less if you don't need it.
Q What tools do I need before Day 1? +
Claude Code installed (free, 10 minutes). A GitHub account. Optionally Slack and Notion for triggers. That's it. We set up the rest on the kickoff call.
Q Why $5K setup + $1,497/month vs. a flat retainer? +
The setup is real work. Loading your context, building your CLAUDE.md, scoping and shipping your first Play — that's a 7-day build, not a subscription perk. The retainer is what keeps it sharp once it's running. Two different things, two different prices.

Still have a question? Book a call and ask it live.