Diagnose why you are missing the number
The forecast is soft and the room is guessing. Find the real cause before you cut or spend.
Diagnose why you are missing the number
The forecast is soft and the room is guessing.
Find the real cause before you cut or spend.
The leak named
The deals that are real
The pattern underneath
A defensible forecast
A number the room stopped arguing with
The same forecast discipline that cut deal slippage 50%+, now defending a single quarter's number.
The number is soft, the room starts guessing, and the loudest voice wins the theory. Someone wants to cut spend, someone wants to cut heads, and nobody has actually named which stage is leaking, why, or which deals are real before the decision gets made.
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.
Conversion by stage, velocity, and win rate with every definition pinned, and the leak named.
Finds the leak, the accounts to work next, and where the scoring model is quietly letting you down.
Healthy, slipping, stuck, or dead. Checks real activity, whether the rep qualified it, and whether the deal is multi-threaded.
Reads closed-won, closed-lost, and churned accounts, then hands back a ranked list of lookalike accounts to work.
Sorts each deal into commit, best-case, or pipeline by evidence, flags one risk, and scripts what to press each rep on.
The leak named, the deals that are real, the pattern underneath, and a defensible forecast.
- All 5 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 Head of Sales is about to miss the quarter and the room is arguing theories instead of facts.
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. 5 skills, bundled.
The whole playbook installs as a single plugin in Claude Code, no copy-pasting 5 times. Or grab any single step above. It runs on what you paste; connect your stack to go live.