← ALL PLAYBOOKS
—— SERIES 1 · THE FLAGSHIP PLAYBOOK

Build the AI-Native GTM Operating System

Series 1 of Build Better, as one runnable playbook. The loop, the context, the signal-to-motion, and the closed loop that makes GTM compound, across all four episodes.

Install the whole playbook ↓BUILD BETTER · SERIES 1 Watch the episode →
POWERS UP WITH YOUR STACK
HOW TO CONNECT →
ClaudeChatGPTGeminiCopilotSalesforceHubSpotZapierMakeNotionGoogle DriveClayApolloZoomInfoClearbitCognismCommon RoomAmplitudeMixpanelPostHogHeapPendoSegmentAttioPipedriveDynamics
1Solve the problem

Everyone says go AI-native and hire a GTM engineer. So you buy more tools and add headcount, and the number still does not move. The org chart got more complex. The work did not get better.

RUN THIS AND YOU CAN
  • ✓Reframe your most expensive workflow as work to redesign, not a hire to make
  • ✓Give every teammate and agent one context repo to start from
  • ✓Turn a product signal into a booked motion before it goes stale
  • ✓Close the loop so each outcome sharpens the next play
2See it in production

Before you run it: I ran it for real.

This workflow is genericized from a real build. Here is the number it moved, what I actually did, and a way into the whole story.

THE BUILD · AI-NATIVE THESIS
The 7th Analyst
0.775 AUC
a won account outranks a lost one, on the model the loop rebuilt
1.5x lift
94% of the model Warm-plus accounts are wins, vs a 62% base rate
7 versions
each caught a flaw the last one shipped, by the loop not a customer
0 of 60
lost accounts that reached the top tier, the top of the funnel stays clean
WHAT I DID ›
01
Give every analyst an audit trail. Each agent logs what it decided and why, every override, every missing field, every enrichment miss. The exhaust of the system becomes its memory.
02
Build the seventh analyst to read them. A meta-analyst reads the other six's audit trails and turns each mistake into a training signal: a rule tightened, a gap flagged, a pattern learned.
03
Close the loop. The corrections feed back into the system, so the next run is better than the last. That is the difference between a tool and a system that improves itself.

AI-native is not how many agents you have. It is whether one of them watches the others and turns their mistakes into improvements. Build the analyst that reads the audit trail. That is the one that compounds.

Dig into the full build →
THE BUILD · GTM OPERATING RHYTHM
Reporting That Drove Action
Deal Confidence
a forecast the team trusts, built on a score not a guess
-50%+
deal slippage, via the Deal Confidence Score
6 motions
one weekly read: leads, deals, expansion, churn, renewals, forecast
Sales + CS
one operating rhythm for the whole GTM org
WHAT I DID ›
01
Automate the report itself. The weekly report generated itself from the source of truth, so no one spent a day assembling slides. The time went to the action, not the assembly.
02
Let AI surface what a human read misses. AI read across the whole dataset and pulled the insights a person scanning a dashboard would never see: the account quietly cooling, the team over-consuming its seats, the deal whose activity did not match its stage.
03
Build the sales action layer. The report did not end at a number. It surfaced the hot leads worth working and a deal tracker with every deal risk and next step, each pointed at the rep who could move it.

A report a leader reads and a report a team acts on are different objects. Automate the assembly, let AI surface the insights a human read misses, and build an action layer for every motion, sales and CS, so one weekly read drives hot leads, expansion, churn saves, renewals, and a forecast the team trusts. The report becomes the operating rhythm, not the rear-view mirror.

Dig into the full build →
THE BUILD · AI-NATIVE GTM
A mid-stage B2B SaaS
2x
win rate, roughly doubled
$1M+
product-led pipeline in 6 months, a channel built from zero
1.5x
average deal size
$10M to $25M
ARR, on ~80% fewer selling heads
WHAT I DID ›
01
Owned the full commercial number. New business, retention, and expansion across SDR, Sales, and Customer Success, unified so what a rep learns in the deal reaches the CSM and expansion compounds instead of leaking.
02
Made retention proactive. An expansion and churn-risk model that flags accounts before they slip. Held gross retention at 100% and grew net revenue retention to 125%, cohort-based, on household-name accounts already on the product.
03
Rebuilt the ICP on who actually buys. More than a thousand customer and prospect calls, pressure-tested against won and lost deals. Reps stopped chasing good-looking accounts that never close, and deal sizes and win rates both climbed.

Rebuilt GTM for the AI era, from headcount to workflows.

See the full story →
SEE IT RUN

The plain questions, answered in order.

Each step is the plain question you are already asking. The skills answer them in order, one handing its receipt to the next.

Episode 1 - The AI-Native GTM Playbook: Build, Buy, Keep
“What exactly is the problem to solve?”
OPEN THE SKILL →
Episode 1 - The AI-Native GTM Playbook: Build, Buy, Keep
“What tools and signals does this workflow need?”
OPEN THE SKILL →
Episode 1 - The AI-Native GTM Playbook: Build, Buy, Keep
“What is pulling reps off selling?”
OPEN THE SKILL →
Episode 2 - Context Is the Product
“Who exactly are we for?”
OPEN THE SKILL →
Episode 2 - Context Is the Product
Structure it into a CLAUDE.md brain any agent reads every session.
OPEN THE SKILL →
Episode 3 - Signal Without a Motion Is Just a Dashboard
“Which signals actually mean now?”
OPEN THE SKILL →
Episode 3 - Signal Without a Motion Is Just a Dashboard
Wire the freshest signal to a booked motion before it goes stale.
OPEN THE SKILL →
Episode 4 - The Loop
Feed outcomes back into your ICP and signal library.
OPEN THE SKILL →
Episode 4 - The Loop
Let the system propose its own improvements, you approve.
OPEN THE SKILL →
RUN IT YOURSELF

Two steps to run this yourself.

1

Install the skills. Grab the one-command install below. Once installed you never call a skill by name, you just describe your situation and the right skill fires on its own.

2

Paste this to kick off. Swap in your own situation and the skills run in order.

“Here is my situation: [describe your workflow or account in a sentence or two]. Walk me through Build the AI-Native GTM Operating System step by step, and run each skill as we go.”
3Run it in four parts, in order

A series, not a dump. Each part is its own runnable playbook, in order. Tab through them.

Run the GTM loop on one workflow

PART 1 OF 4
Run the GTM loop on one workflow

Episode 1, made runnable. Do not automate the org chart. Run the loop on the workflow that costs you the most.

YOU LEAVE WITH
The real problem named at its crux, the right tech and signals stacked to run it, and the reps free to sell with the human kept in the loop.
Open Part 1 →
WHERE YOU LAND

A workflow you framed instead of a hire, a context repo any agent can use, a signal wired to a booked motion, and a closed loop where the outcome changes the next action.

INSTALL THE WHOLE PLAYBOOK

One plugin. 9 skills, bundled.

The whole playbook installs as a single plugin in Claude Code, no copy-pasting 9 times. Or grab any single step from the run above. It runs on what you paste; connect your stack to go live.

── GET THE NEXT PLAYBOOK

One runnable workflow a week. Free.