Stand up the RevOps foundation
You cannot trust the number because you cannot trust the data. Fix the plumbing first.
Stand up the RevOps foundation
You cannot trust the number because you cannot trust the data.
Fix the plumbing first.
Details
Details
Details
Details
Deal slippage down 50%+
Same plumbing-first approach: clean data and pinned definitions turned the pipeline number into one the room trusted.
A clean CRM
Pinned funnel metrics
Routing that gets built
A stack with the overlap cut
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.
Finds the hygiene problems that break reporting first: missing fields, stale records, duplicates, and bad stages, before the cosmetic ones.
Conversion by stage, velocity, and win rate with every definition pinned, and the leak named.
The assignment rules, round-robin or account-based logic, SLA timers, and fallbacks, written as a spec.
Maps every tool to a job, finds overlap, unused seats, and gaps, and sequences cuts to the renewal calendar.
A clean CRM, pinned funnel metrics, routing that gets built, and a stack with the overlap cut.
- 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.
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.
This play runs across the org, not inside sales.
Every function below owns a piece of the play. Skip one and it stalls where most GTM plays stall: in the handoff.
Without it: Reps skip the fields and the debt rebuilds in a quarter.
Without it: Two funnels, two numbers, and the argument returns.
Without it: The board sees a number the CRM cannot back.
Without it: The renewal number stays a guess.
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.
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.
WHAT I DID ›
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 number is only as trusted as the plumbing under it
The audits hand a RevOps leader a ranked cleanup list, pinned definitions, and routing that can ship; the trust comes from the first forecast call where nobody argues the numbers. Here is how to run the rollout so the foundation holds after the project ends.
Pin the funnel definitions before touching a single record, then review every hygiene, routing, and stack decision against those definitions in a weekly standup. Anything that cannot be stated in the pinned terms does not ship.
- 01Teach the definitions, then defend them
Walk sales and marketing through what each pinned stage means and what it excludes, and rehearse the moment someone asks to bend a definition for one deal. The answer is the same pinned sentence every time.
- 02Work the hygiene list top down
The data-hygiene-audit ranks the cleanup; run a standing weekly block that clears it in order, and publish what got fixed so the team sees the debt shrinking.
- 03Hold the routing SLA in public
Lead-routing only matters if the clock is visible. Report response times against the SLA every week, by owner, and start with the leads that sat.
- 04Inspect drift quarterly
Rerun the hygiene and tech-stack audits on a quarterly cadence, before the debt turns invisible again. The foundation is a motion, not a project.
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.