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.
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.
The leak named
The metrics pinned
The coverage math
A coaching plan per rep
The metrics the room stopped arguing with
Pinned funnel definitions turned a diagnosed leak into a coaching plan reps could actually run on.
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 leak, the accounts to work next, and where the scoring model is quietly letting you down.
Conversion by stage, velocity, and win rate with every definition pinned, and the leak named.
Forward-looking coverage math per channel and per rep, so you see the gaps before they cost you the number.
Turns rep data into a specific coaching priority per person, plus the team-level pattern underneath them.
The leak named, the metrics pinned, the coverage math, and a coaching plan per rep.
- 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 VP Sales sees Q3 coming in soft and can't name the stage that's actually broken.
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 →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.