← ALL PLAYBOOKS
── PLAYBOOK · REVOPS & DATA
✓ APPROVED

Stand up the RevOps foundation

You cannot trust the number because you cannot trust the data. Fix the plumbing first.

Install the whole playbook ↓
[ BUILT GTM ]

Stand up the RevOps foundation

Solvethe problem worth solving
Problem · 01RevOps &

You cannot trust the number because you cannot trust the data.

Fix the plumbing first.

Stackthe workflow, box by box
Salesforce01
Turn a messy CRM into a ranked cleanup list.
Turn a messy CRM into a ranked cleanup list.
Powers up with
AI
Salesforce02
Build funnel metrics the meeting will actually trust.
Pin the definitions so the numbers are trusted.
Powers up with
AI
Salesforce03
Design lead routing and SLAs that actually get built.
Design routing and SLAs that actually get built.
Powers up with
AI
Claude04
Cut the GTM stack without breaking it.
Cut the stack overlap without breaking it.
Connect to analyze
AI
Splithow control passes: agents branch left, humans right
HUMAN + AI, IN THE LOOP
How control passes.
AgentsHuman
Agent01
Turn a messy CRM into a ranked cleanup list.
Salesforce runs it.
Agent02
Build funnel metrics the meeting will actually trust.
Salesforce runs it.
Agent03
Design lead routing and SLAs that actually get built.
Salesforce runs it.
Agent04
Cut the GTM stack without breaking it.
Claude runs it.
The skills run the work. You stay in the loop on the calls that need judgment.
Outputwhat the workflow produces
OUTPUT · 01

A clean CRM

OUTPUT · 02

Pinned funnel metrics

OUTPUT · 03

Routing that gets built

OUTPUT · 04

A stack with the overlap cut

Outcomethe result it drives
OUTCOME · 01

Deal slippage down 50%+

Same plumbing-first approach: clean data and pinned definitions turned the pipeline number into one the room trusted.

Built GTM
── 01 / WHY RUN IT
RUN THIS AND YOU CAN
✓A clean CRM
✓Pinned funnel metrics
✓Routing that gets built
✓A stack with the overlap cut
── 02 / THE RUN, STEP BY STEP

The workflow that solves it, one step at a time.

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

1✓ TESTED
Turn a messy CRM into a ranked cleanup list.

Finds the hygiene problems that break reporting first: missing fields, stale records, duplicates, and bad stages, before the cosmetic ones.

YOU GETThe missing-field scan, the duplicate clusters, and a priority ranking by blast radius.
POWER IT UPSalesforceHubSpotAttioPipedriveDynamicsSnowflake
OPEN THE SKILL →
2✓ TESTED
Build funnel metrics the meeting will actually trust.

Conversion by stage, velocity, and win rate with every definition pinned, and the leak named.

YOU GETStage conversion, time-in-stage, win rate, and a definition ledger.
POWER IT UPSalesforceHubSpotAttioPipedriveDynamicsAmplitude
OPEN THE SKILL →
3✓ TESTED
Design lead routing and SLAs that actually get built.

The assignment rules, round-robin or account-based logic, SLA timers, and fallbacks, written as a spec.

YOU GETThe match logic, the SLA timers, and fallback paths.
POWER IT UPSalesforceHubSpotAttioPipedriveDynamicsZapier
OPEN THE SKILL →
4✓ TESTED
Cut the GTM stack without breaking it.

Maps every tool to a job, finds overlap, unused seats, and gaps, and sequences cuts to the renewal calendar.

YOU GETThe capability map, the overlap and unused finds, and a consolidation plan.
POWER IT UPZapierMaken8nTrayWorkatoDeepline
OPEN THE SKILL →
WHERE YOU LAND

A clean CRM, pinned funnel metrics, routing that gets built, and a stack with the overlap cut.

EVERY STEP, TESTED AND PASSED
EVAL RESULTPASS4/4 dimensions
HOW WE EVAL →
✓Skills resolve
✓Structure + proof
✓Example chat
✓Quality judge
  • All 4 chained skills resolve to real, scored skills.
  • Has a problem, an outcome, 2+ steps, and proof from a real build.
  • Ships an example chat showing the play run in Claude.
  • Reads in plain operator voice, grounded in a real build.
Last eval run 2026-08-05
DEEP EVAL · PASS
THE STANDARD →

We did not just check the structure. A judge read this play against the full text of every skill it chains (composition), then ran it on a real scenario end to end (simulated). It passed both. Test scenario: A Series B RevOps lead inherits a CRM nobody trusts and a Monday pipeline meeting that always turns into an argument about the number.

── 03 / SEE IT RUN

Watch the skills answer in order.

Describe your situation in plain language. The right skill fires on its own and hands its receipt to the next.

EXAMPLE CHATPriya, RevOps Lead, running the loop in one sitting
P
Our Salesforce is a mess and nobody trusts the pipeline number in the Monday meeting. I don't even know where the worst problems are. Can you look at it?
S
Step 1· Data Hygiene Audit
I scanned for the hygiene problems that actually break reporting first: missing required fields, records that haven't moved in months, duplicate accounts, and deals stuck in stages that don't match reality. Then I ranked them by how much they distort the number, not by how ugly they look.
dupes310
stale1,240
Receipt
Ranked cleanup list: 310 duplicate accounts and 1,240 deals with no activity in 60+ days flagged as the top two reporting-breakers.
P
Okay, cleanup is queued. Now the bigger fight: half the team defines a qualified lead differently. Can we pin the funnel so the metrics mean one thing?
S
Step 2· Funnel Metrics
I built stage-to-stage conversion, time in each stage, and win rate, and pinned a written definition for every stage so the meeting stops arguing about what counts. The leak is between MQL and SQL, where the handoff is undefined.
Receipt
Funnel metrics with a definition ledger for all 6 stages; biggest leak found at MQL to SQL, where conversion sits at 22 percent.
P
That MQL to SQL leak is partly because leads sit for days before anyone touches them. Can you design routing that our admin can actually build?
S
Step 3· Lead Routing
I wrote the assignment rules as a spec: account-based match first, round-robin fallback, and an SLA timer that reassigns if a lead sits untouched. Every path has a fallback so nothing lands in a black hole.
Receipt
Routing spec with a 15-minute first-touch SLA and reassignment fallback, written so your admin can build it without guessing.
P
Last thing. Finance is asking why we pay for so many tools. Some overlap and some barely get used. Can you help me cut without breaking anything?
S
Step 4· Tech Stack Audit
I mapped every tool to the job it does, found where two tools do the same thing, and flagged seats nobody logs into. Then I sequenced the cuts to line up with renewal dates so you don't eat a cancellation fee.
tools24
cuttable5
Receipt
Stack audit across 24 tools: 5 flagged for consolidation, sequenced to renewals for roughly 60K in annual savings.
── 04 / SEE 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, and what I actually did.

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 →
05 / INSTALL THE WHOLE PLAYBOOK

One plugin. 4 skills, bundled.

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

OR KICK IT OFF IN CHAT
“Here is my situation: [describe your workflow or account in a sentence or two]. Walk me through Stand up the RevOps foundation step by step, and run each skill as we go.”
── GET THE NEXT PLAYBOOK

One runnable workflow a week. Free.