Claude for GTM · The Operator's Playbook

AI doesn't fix a broken revenue system. It runs whatever system you give it — faster. Fix the system, then put Claude on top of it, one stage at a time.

AI in GTM, 2026 · RevOps surveys

73%

of companies have a board or CXO-level AI mandate

<9%

of RevOps leaders say AI helped generate more pipeline

Very few have the system underneath it.

The state of play

Teams are using AI everywhere. Almost nobody can tie it to pipeline.

If your CRM can't answer "what's in pipeline and why," Claude can't either. It will just answer wrong, confidently, at scale.

38%

of companies have a unified customer data layer

Revenue Wizards

56%

of mandated companies are running AI on fragmented data

Revenue Wizards

1 in 4

orgs have no clear owner for AI adoption

Default

19%

name poor data quality as their top blocker

Default

Read this correctly

The winners aren't the teams with the most AI. They're the teams with a clean system and a few AI workflows wired into it.

1–2 workflows

Better time savings per use case

7+ workflows

Less saved per use case

Sources: Revenue Wizards, RevOps in 2026 (n=123, May 2026); Default, State of AI in RevOps H1 2026 (300+ leaders). Both surveys are self-selected and skew toward AI-engaged teams. The broader market is likely further behind.

The Claude-for-GTM maturity model

You don't skip stages. You earn them. The gate between stages is a measurable exit criterion, not a feeling.

Five stages. Each one pairs a GTM prerequisite (what your revenue system must already do) with an AI posture (what Claude is trusted to do).

Select a stage to see Claude's role and the gate to the next one

Stage 0

Foundations

Claude's role

None in production. Claude helps you fix the system (audits, cleanup scripts, documentation).

GTM prerequisite

None. This is where every rollout starts.

Exit criterion · gate to next stage

Lifecycle and pipeline stages defined and enforced; owner, amount, and close date populated on ≥90% of open deals; one source of truth for pipeline.

1 on 0

Where most teams actually are: Stage 1 usage (reps chatting with Claude) sitting on Stage 0 data. The fastest path to Stage 2 almost always runs through a short, aggressive Stage 0 cleanup.

Readiness self-assessment

Score each dimension 1 to 5. The score decides your starting stage. Overrating it is the most expensive mistake in this playbook.

Tap a score on each row. Your total, starting stage, and first 30 days update as you go.

Your total · 8–40

21

/ 40
Stage 08–16
Stage 117–24
Stage 225–32
Stage 3+33–40

Start at

Stage 1 · Assist

Your first 30 days

Roll out company plan, shared Projects, 2–3 skills (ICP, messaging, call prep). Fix your two lowest-scoring dimensions in parallel.

Your two lowest dimensions

Data centralization · Process documentation

Stage 2 play · S2-SAL-1 · Daily rep brief

Every rep starts the day knowing which deals matter. One of 22 plays in the playbook, each with an objective, surface, data, human checkpoint, and metric.

Runs

Each weekday at 7:30am. Read-only.

Connectors

CRM, calendar, email, Slack

Human checkpoint

Rep acts; manager reviews brief quality weekly for the first month.

Measure it by

Activity on stale deals; % of deals with next step set.

# sales-briefsRead-only
C
Claude · Daily brief for Maya R.Tuesday 7:30am · scheduled task

Today's meetings3

10:00Northwind LogisticsDemo · last touch: pricing questions from VP Ops$84K
1:30Brightline HealthDiscovery · new champion since last call$52K
4:00Arcfield SystemsNegotiation · legal redlines open$140K

No activity in 7+ days · by amount2

12dKestrel DataProposal · no next step set$210K
9dPinecrest GroupEvaluation · champion unanswered$66K
  • 1Set a next step on Kestrel Data before noon.
  • 2Reply to Pinecrest's champion (unanswered 48h).
  • 3Bring the legal redline owner to the 4:00 Arcfield call.

Guardrails and governance

Writes are earned. Every new workflow starts read-only and moves up only with an approval log showing low rejection rates.

Speed without guardrails is how an AI rollout becomes a data-cleanup project. These are the rules we install with every client.

01

Read

Learn how the agent behaves on your data before it can change it.

02

Propose

Claude drafts the CRM update. Nothing is written yet.

03

Approve

A human accepts or rejects each proposed write.

04

Automate low-risk only

Every agent write is logged and sampled weekly.

Low risk

notestaskstags

Can automate at Stage 3.

High risk · forecast-critical

stageamountclose_dateownerdeletions

Always human-approved.

The 90-day rollout

Go narrow, then deep. Two workflows that move a revenue metric beat twelve that save "some time."

Pick pilots with this filter

High frequency×Revenue metric×Clean-enough data×Willing owner

Days 1–14

Diagnose

Know your starting stage and your two highest-value workflows.

Done when

Starting stage agreed; 2 pilot workflows chosen, each tied to one revenue metric.

Days 15–30

Foundations

Remove the blockers the pilots depend on.

Done when

Core-field completeness ≥90% on open deals; Stage 1 tools live for all GTM.

Days 31–60

Pilot

Prove lift on two workflows.

Done when

Measured lift on each pilot metric vs. baseline; approval logs reviewed.

Days 61–90

Scale

Make it the operating system.

Done when

Stage exit criteria met; next-quarter roadmap approved.

The scorecard

Measure in revenue terms. Hours saved is a leading indicator. Speed-to-lead, conversion, forecast accuracy, and NRR are the scoreboard.

Starting thresholds. Calibrate to your own baseline after the Diagnose window. The trend matters more than the absolute number.

Metric
Weak
Acceptable
Strong
Core deal-field completeness (open pipeline)
<70%
80–90%
≥95%
Speed-to-lead (inbound hand-raisers, median)
>1 hour
5–60 min
<5 min
Follow-up sent within 24h of a call
<50%
70–85%
≥90%
Proposed agent writes rejected by humans
>25%
10–25%
<10%
Forecast accuracy at week 4 of quarter
Worse than ±25%
±10–25%
Within ±10%
Rep admin time recovered (hrs/rep/week)
<1
2–4
≥5

Thresholds are JayOh starting targets for planning, not industry benchmarks.

Results from the system underneath

100+ GTM engagements since 2016. For B2B SaaS and PE-backed companies, built on a library of 100+ documented plays.

HubSpot Platinum Partner, Salesforce Partner, and Anthropic partner.

25%

of all new pipeline from the engine · CAC −20%

Ramp

Re-architected the GTM engine + modern data stack

2×

ARR doubled, $8M → $16M · CAC −20%

15Five

Product-led growth rebuild + self-service motion

+45%

lead conversion · 90% fewer data errors

Vault Verify (PSG)

Full RevOps overhaul, no new FTE

180

portfolio companies · +25% marketing ROI

Samsung Next

RevOps framework across the portfolio

Start here

Hand us one project. We'll do it free. Where does your revenue system hurt most?

01

Free GTM Sprint

Up to 5 hours of real, senior hands-on work inside your stack, e.g. your first Stage 0 fix or a speed-to-lead QA.

02

Diagnostic + AI Readiness

2 weeks. Our 18-metric GTM scoring system plus the readiness assessment: every leak scored, your starting stage, and a prioritized roadmap.

03

Build & Run pod

An embedded pod installs foundations, connectors, skills, and governance, ships pilots in sprint one, and runs the cadence with you.

Start your free GTM sprint

Read-only or sandbox first. You keep everything.