Run the weekly revenue cadence
The Monday number is always a surprise because nobody agrees on what moved it. Turn the weekly number into the operating rhythm instead of a rear-view mirror.
Run the weekly revenue cadence
The Monday number is always a surprise because nobody agrees on what moved it.
Turn the weekly number into the operating rhythm instead of a rear-view mirror.
Details
Details
Details
Details
Deal slippage down 50%+
Reporting that drove action, not a dashboard.
A revenue read
A pipeline read
A defensible forecast
A one-screen digest
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.
A weekly or monthly recap that ends in decisions, not a dashboard screenshot: position vs plan, what moved, the risks, the next moves.
Coverage, creation, movement, and aging on one page, ending in the deals to decide this week.
Sorts each deal into commit, best-case, or pipeline by evidence, flags one risk, and scripts what to press each rep on.
The three numbers that matter, what changed week-over-week, and what needs attention across the funnel.
A revenue read, a pipeline read, a defensible forecast, and a one-screen digest.
- 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: It's Monday morning and the VP Revenue needs a defensible read before the leadership standup, without re-litigating what moved.
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: Two dashboards disagree and the meeting argues math
Without it: The board hears one number and the team runs another
Without it: The forecast is a mood, restated weekly
Without it: The number surprises you from the retention side
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 →A forecast is only as good as the argument it survives
The skills hand a revenue leader the revenue read, the pipeline read, the forecast prep, and the one-screen digest; the cadence earns its slot when the room argues about what to do, not about whose number is right. Here is how a revenue leader runs the hour so it changes the week.
One agreed source per metric, set before the cadence starts. Any number that cannot be traced to it does not enter the room, and the meeting opens with deltas, not totals.
- 01Teach the room to read deltas
Train every presenter to open with what moved since last week and why. The revenue-report and pipeline-report exist so the total is already known before anyone speaks.
- 02Lock the rhythm and the order
The gtm-weekly-digest lands before the meeting, the reports run in the same order, and the forecast segment ends with a committed number and its owner. Same day, every week.
- 03Make every number carry names
In forecast-call-prep, each committed dollar traces to specific deals. A number without deal names is a mood, and the room should say so.
- 04Read past calls against the closes
Once a month, put the last forecast calls next to what actually closed, and coach the gap between confidence and outcome. The cadence learns or it decays.
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.