← ALL PLAYBOOKS
── PLAYBOOK · LEADERSHIP
✓ APPROVED

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.

Install the whole playbook ↓
[ BUILT GTM ]

Run the weekly revenue cadence

Solvethe problem worth solving
Problem · 01Leadership

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.

Stackthe workflow, box by box
Salesforce01
Turn revenue data into a wrap-up that drives action.
Turn revenue data into a wrap-up that drives action.
Powers up with
AI
Salesforce02
Build the pipeline report a review actually needs.
Build the pipeline report a review actually needs.
Powers up with
AI
Salesforce03
Walk into the forecast call with a number you can defend.
Walk into the forecast call with a defensible number.
Powers up with
AI
Salesforce04
Put the whole GTM funnel on one screen every week.
Put the whole funnel on one screen.
Powers up with
AI
Splithow control passes: agents branch left, humans right
HUMAN + AI, IN THE LOOP
How control passes.
AgentsHuman
Agent01
Turn revenue data into a wrap-up that drives action.
Salesforce runs it.
Agent02
Build the pipeline report a review actually needs.
Salesforce runs it.
Agent03
Walk into the forecast call with a number you can defend.
Salesforce runs it.
Agent04
Put the whole GTM funnel on one screen every week.
Salesforce runs it.
The skills run the work. You stay in the loop on the calls that need judgment.
Outputwhat the workflow produces
OUTPUT · 01

A revenue read

OUTPUT · 02

A pipeline read

OUTPUT · 03

A defensible forecast

OUTPUT · 04

A one-screen digest

Outcomethe result it drives
OUTCOME · 01

Deal slippage down 50%+

Reporting that drove action, not a dashboard.

Built GTM
── 01 / WHY RUN IT
RUN THIS AND YOU CAN
✓A revenue read
✓A pipeline read
✓A defensible forecast
✓A one-screen digest
── 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
Turn revenue data into a wrap-up that drives action.

A weekly or monthly recap that ends in decisions, not a dashboard screenshot: position vs plan, what moved, the risks, the next moves.

YOU GETPosition vs plan, what moved, sized risks, and owned next moves.
POWER IT UPSalesforceHubSpotAttioPipedriveDynamicsSnowflake
OPEN THE SKILL →
2✓ TESTED
Build the pipeline report a review actually needs.

Coverage, creation, movement, and aging on one page, ending in the deals to decide this week.

YOU GETCoverage vs target, creation vs goal, aging, and a decision list.
POWER IT UPSalesforceHubSpotAttioPipedriveDynamicsClari
OPEN THE SKILL →
3✓ TESTED
Walk into the forecast call with a number you can defend.

Sorts each deal into commit, best-case, or pipeline by evidence, flags one risk, and scripts what to press each rep on.

YOU GETThe evidence-based sort, one risk per deal, and the press question.
POWER IT UPSalesforceHubSpotAttioPipedriveDynamicsClari
OPEN THE SKILL →
4✓ TESTED
Put the whole GTM funnel on one screen every week.

The three numbers that matter, what changed week-over-week, and what needs attention across the funnel.

YOU GETThree headline metrics, one line per stage, and an attention list.
POWER IT UPSalesforceHubSpotAttioPipedriveDynamicsAmplitude
OPEN THE SKILL →
WHERE YOU LAND

A revenue read, a pipeline read, a defensible forecast, and a one-screen digest.

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-08-05
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: It's Monday morning and the VP Revenue needs a defensible read before the leadership standup, without re-litigating what moved.

── 03 / 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 CHATAlex, VP Revenue, running the loop in one sitting
A
It's Monday. Give me where we stand on revenue and what actually moved last week.
S
Step 1· Revenue Report
Here's position versus plan, what moved since Friday, the risks sized, and the moves those risks call for. It ends in decisions, not a dashboard shot.
Receipt
78% to plan with 3 weeks left; two deals slipped, one pulled in, net down $140K.
A
What's the pipeline picture behind that, and what do we need to decide this week?
S
Step 2· Pipeline Report
Coverage, creation, movement, and aging on one page, ending in the specific deals that need a call this week rather than a status update.
Receipt
Coverage 2.8x; 4 deals aged past 60 days at proposal need a decision now.
A
Forecast call is Thursday. Help me get to a number I can defend.
S
Step 3· Forecast Call Prep
I sorted every deal into commit, best-case, or pipeline by the evidence in it, flagged one risk each, and scripted what to press each rep on.
commit$1.2M
reps called$1.6M
Receipt
Commit is $1.2M by evidence, with one press question per slipping deal.
A
Now boil the whole thing to one screen I can drop in the leadership channel.
S
Step 4· Gtm Weekly Digest
The three numbers that matter, what changed week over week, and what needs attention across the funnel. One screen, no scrolling.
Receipt
Three headline metrics, one line per stage, five accounts flagged for attention.
── 04 / 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
Deal Confidence
a forecast the team trusts, built on a score not a guess
-50%+
deal slippage, via the Deal Confidence Score
6 motions
one weekly read: leads, deals, expansion, churn, renewals, forecast
Sales + CS
one operating rhythm for the whole GTM org
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 →
05 / 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 Run the weekly revenue cadence step by step, and run each skill as we go.”
── GET THE NEXT PLAYBOOK

One runnable workflow a week. Free.