← ALL PLAYBOOKS
PLAYBOOK · REVOPS & DATA
✓ APPROVED

Find the funnel leak and fix it

Demo-to-proposal has quietly halved and nobody noticed until the forecast call. Diagnose the leak and close it. If the real question is whether this quarter's number is real, run diagnose-the-miss first; run this once you know which stage and which reps need to change.

[ SALES OPERATOR ]

Find the funnel leak and fix it

G / Groundthe problem that started all of it
RevOps &

Demo-to-proposal has quietly halved and nobody noticed until the forecast call.

Diagnose the leak and close it. If the real question is whether this quarter's number is real, run diagnose-the-miss first; run this once you know which stage and which reps need to change.

A / Assignthe build, block by block, and who owns each one. Open a step to see it run.
HUMAN + AI, IN THE LOOP
The skills run the work. You stay in the loop on the calls that need judgment.
Salesforce01
Find where the funnel leaks and what to fix.
Details
Diagnose why the funnel converts, and where it leaks.
Powers up with
AI
Salesforce02
Build funnel metrics the meeting will actually trust.
Details
Make that leak defensible: pin the exact numbers so the room argues the fix, not the math.
Powers up with
AI
Salesforce03
Know if you have enough at-bats for next quarter.
Details
Check coverage per channel and per rep.
Powers up with
AI
Salesforce04
Walk into every 1:1 with the gap already found.
Details
Turn the gaps into per-rep coaching.
Powers up with
AI
T / Tie backthe result it drove, and how they know
RESULT · 01

The metrics the room stopped arguing with

Pinned funnel definitions turned a diagnosed leak into a coaching plan reps could actually run on.

OUTPUT · 01

The leak named

OUTPUT · 02

The metrics pinned

OUTPUT · 03

The coverage math

OUTPUT · 04

A coaching plan per rep

The Sales Operator
01 / WHY RUN IT
RUN THIS AND YOU CAN
The leak named
The metrics pinned
The coverage math
A coaching plan per rep
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
Find where the funnel leaks and what to fix.

Finds the leak, the accounts to work next, and where the scoring model is quietly letting you down.

YOU GETThe funnel-leak diagnosis, the account ranking, and the scoring audit.
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.
OPEN THE SKILL →
3✓ TESTED
Know if you have enough at-bats for next quarter.

Forward-looking coverage math per channel and per rep, so you see the gaps before they cost you the number.

YOU GETThe coverage math per channel and per rep, and the gap read.
OPEN THE SKILL →
4✓ TESTED
Walk into every 1:1 with the gap already found.

Turns rep data into a specific coaching priority per person, plus the team-level pattern underneath them.

YOU GETThe per-rep gap logic and the team-pattern rollup.
OPEN THE SKILL →
WHERE YOU LAND

The leak named, the metrics pinned, the coverage math, and a coaching plan per rep.

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-09-12
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 VP Sales sees Q3 coming in soft and can't name the stage that's actually broken.

03 / WHO ELSE HAS TO MOVE

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.

SALES LEADERSHIP
Coaching delivery and stage discipline on the floor

Without it: The diagnosis is right and nothing changes

MARKETING
Top-of-funnel volume and quality when the leak is upstream

Without it: Sales coaches harder at a problem coaching cannot fix

FINANCE
Coverage targets tied to the plan's real math

Without it: The team fixes the leak and still misses the number

04 / 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 CHATDana, VP Sales, running the loop in one sitting
D
Our Q3 number is coming in soft and I honestly can't tell you where it's breaking. Can you find the leak?
S
Step 1· Strike Zone Analyst
I pulled the full funnel and looked at conversion between every stage, then checked which accounts are stuck and whether the scoring model is pointing reps at the right ones. One stage is dragging the whole thing down.
Receipt
Leak is demo to proposal: 22% vs 41% at every other step.
D
So it's the demo-to-proposal step. Pin the actual numbers so I can take this to the team without getting picked apart.
S
Step 2· Funnel Metrics
I locked the definitions first so nobody argues the math, then measured conversion, time in stage, and win rate quarter over quarter. The slowdown is real and it's recent.
Receipt
Time-in-stage at demo doubled to 34 days; win rate off demos fell 12 points.
D
If we fix that, do we even have enough coming in to hit next quarter?
S
Step 3· Pipeline Creation Analyst
I ran forward coverage per channel and per rep against target so we see the shortfall now, not in week 10. Outbound is where you're thin.
Receipt
Coverage is 2.3x vs 3x target; outbound at 1.4x, two reps under.
D
Which reps, and what do I actually coach them on?
S
Step 4· Coaching Analyst
I turned each rep's data into one specific coaching priority, then rolled it up to the pattern sitting under the whole team. It's the same gap in both.
Marcusdiscovery depth
Priyadiscovery depth
teamno confirmed pain pre-demo
Receipt
6 of 10 stuck deals had no confirmed pain before the demo was booked.
05 / 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
65% → 90%+
forecast accuracy, on a Deal Confidence Score instead of a guess
-50%+
deal slippage, via the Deal Confidence Score
6 motions
one weekly read: leads, deals, expansion, churn, renewals, forecast
2 teams
sales and CS, running the week off one read
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
06 / ROLL IT OUT AND INSPECT IT · THE OTHER HALF

The diagnosis is only as good as the coaching after it

The skills hand a RevOps leader the leak, the pinned math, the coverage read, and a per-rep plan; the funnel actually changes in the one-on-ones where a manager coaches a specific rep on a specific stage. Here is how a RevOps leader gets the diagnosis off the dashboard and into those rooms.

THE FRAMEWORK BEHIND IT
The name-the-leak review

One working session where the leak gets named with funnel-metrics numbers pinned in advance, and nobody leaves without an owner, a coaching plan, and a re-check date on the same stage.

  1. 01
    Teach managers the stage reads

    Train frontline managers on what a halved demo-to-proposal rate means and does not mean, so they trust the strike-zone-analyst read enough to coach from it.

  2. 02
    Pin the math before the room

    The funnel-metrics numbers get agreed before the meeting, not during it. The session argues the fix; the spreadsheet argument happens in advance or not at all.

  3. 03
    Put a re-check date on every fix

    Each named leak carries a date to re-read the same stage. No re-check, no closure: the leak is presumed open until the numbers say otherwise.

  4. 04
    Coach one rep plan per week

    The coaching-analyst output is a list of per-rep gaps. Walk one rep's plan in the manager cadence each week, and inspect whether last week's plan changed a behavior.

07 / 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 Find the funnel leak and fix it step by step, and run each skill as we go.
GET THE NEXT PLAYBOOK

One runnable workflow a week. Free.