← BUILD LOGGTM OPERATING RHYTHM
BUILD LOG · REPORTING THAT DROVE ACTION

Our revenue reporting was a rear-view mirror. I turned it into the operating rhythm for the whole GTM org.

Most revenue reporting tells you what already happened, to an audience that cannot change it. I automated ours, let AI surface the insights a human read would miss, and delivered it weekly as an action list, so sales and CS ran off the same read: hot leads, deals, expansion, churn risk, renewals, and a forecast you could trust.

Steal this build ↓See the stackThe people part →
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
THE STORY, FROM THE SEAT

Here is one I actually shipped. What happened, what I did, and the stack if you want to run it yourself.

The number moved between Monday and Friday and nobody could say exactly why. Decks got built by hand, read in a meeting, nodded at, and forgotten by the next one: leadership learned what happened, and the people who could change it got nothing to do. A revenue report is usually a rear-view mirror. Ours was too.

My first version was guilty of it as well: I automated prettier slides that still nobody acted on, because I had sped up the rear-view mirror instead of replacing it.

Three ways to go from there: buy a BI tool and more dashboards, hire an analyst to assemble it weekly, or automate the read on the stack we had and add an action layer. The first two speed up the mirror. The third changes the object, from a report a leader reads to a list a team works.

The middle was uglier than the idea. Every historical was hard-coded. The CRM was a mess. Looker was full of old, unused tables that still got referenced. Early runs shipped stale data, schedules quietly broke, and it took multiple iterations before the read was right more often than the room. That is the unglamorous truth of automated reporting: the automation is easy, the truth underneath it is the work.

It landed as a weekly pre-read for reps, teams, and executives, so every meeting started at the action instead of the recap. And it stopped stopping at new business: expansion, churn risk, and renewals sat in the same read, so sales and CS ran the week off the same truth.

The Sales Operator
Keep Building,
Heath
FOUNDER, THE SALES OPERATOR
THE BUILD IN FIVE MOVES · THE GIANT METHOD
  1. GThe revenue report was a rear-view mirror: built by hand, read in a meeting, forgotten by Monday.
  2. In8n generated the weekly read from Salesforce and Snowflake, and Claude read the whole dataset for what a human scan misses.
  3. AThe report assembles and reads itself, AI surfaces the buried signal, and the team acts off one weekly truth.
  4. NWeekly pre-reads for reps, teams, and executives made every meeting start at the action, and the standing review ran the number as a rhythm.
  5. TThe Deal Confidence Score cut deal slippage by more than half, and six motions ran off one weekly read.
RUN THE PLAY YOURSELFThis exact build is a playbook. Run it on your own data.
→
01 / HOW WE APPROACHED THE PROBLEM

Ran the loop.

The build started with a confession: the first version automated prettier slides that still nobody acted on, a faster rear-view mirror instead of a replacement. The real work was underneath: hard-coded historicals, a messy CRM, and a Looker full of stale tables, worked through multiple iterations until the read could be trusted. The object had to change too, from a report a leader reads to a weekly pre-read every rep, team, and executive acts on.

  1. 1
    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.

  2. 2
    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.

  3. 3
    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.

  4. 4
    Extend it to the whole CS motion

    The same weekly read fed Customer Success: expansion signals, churn-risk flags, and the renewal watch, so CSMs saw the save and the upsell early instead of at the eleventh hour.

  5. 5
    Deliver it weekly, and align on it

    One cadence, one read, every motion. The weekly report became the meeting: GTM worked from the same truth, and the forecast came off the same weekly read every motion could see.

02 / WHAT IT TOOK CROSS-FUNCTIONALLY

Nobody ships this alone. Here is who had to move.

One weekly read for the whole GTM org only works if the whole org's data and rituals move with it. The report was the easy half. The truth underneath it belonged to everyone.

REVOPS AND DATA
The source of truth the report generated from.

Every historical was hard-coded, the CRM was a mess, and Looker was full of old tables that still got referenced. Cleaning the plumbing was the real project; the automation just made the cost of bad data visible weekly.

FINANCE AND THE BOARD
The number the company ran on.

The same weekly read fed the executive pre-read, so leadership and the team worked from one number instead of two versions of it.

CS LEADERSHIP
The other half of the read.

Expansion, churn risk, and renewals sat in the same data as new business. Running Revenue and CS as one org meant the report never stopped at closed-won.

Trust came the slow way: bad data got referenced, schedules silently failed, stale reads shipped, and every miss bought another iteration. The read earned the room by being right more often than the room.

03 / HOW WE TURNED IT INTO A SALES MOTION · THE PEOPLE PART

The reporting became the operating rhythm. Running that rhythm is a leadership skill, not a dashboard.

A live number is only as good as the meeting it drives. The leadership half was turning the reporting into a weekly operating rhythm: a pipeline review that catches risk early and a forecast the team can stand behind.

THE FRAMEWORK BEHIND IT
The Pipeline Review, plus a deal confidence read

Every week, read coverage by channel, flag the red deals against PLAN, and set a confidence on each commit. The report surfaces the risk; the review is where a leader does something about it before the quarter is decided.

  1. 01
    Ran the number as a rhythm, not a fire drill

    A standing weekly review meant risk showed up with time to fix it, instead of at the end of the quarter.

  2. 02
    Made the forecast a defensible call

    Every commit carried a confidence and a reason, so the number in the meeting actually meant something.

  3. 03
    Coached the reps whose deals kept slipping

    The report named the pattern; the review turned it into a coaching conversation with the rep who owned it.

Run the pipeline review →
04 / WHAT I LEARNED

Not proof. Just what the build taught me.

  1. 01
    Automating a bad report just makes it faster

    The first version automated prettier slides nobody acted on. That sped up the rear-view mirror instead of replacing it.

  2. 02
    A report read and a report acted on differ

    A deck of numbers tells leadership what happened and hands the people who could change it nothing to do. The action layer pointed every insight at the rep who could move it.

  3. 03
    Do not stop at new business

    The expansion, churn, and renewal signals sat in the same data while CS flew blind. The same weekly read fed CSMs the save and the upsell early instead of at the eleventh hour.

05 / THE WORKFLOW

The runnable version. Copy it into your stack.

SalesforceSnowflakeClauden8n
[ SALES OPERATOR ]

Reporting That Drove Action

Heath Barnett · Sales Operator
G / Groundthe problem that started all of it, with the receipt and the cost
Operating rhythm

The report was a rear-view mirror.

A deck of numbers, built by hand, read in a meeting, forgotten by Monday. Prettier slides nobody acted on.

Gap

It stopped at new business.

CS flew blind on the expansion, churn, and renewal signals sitting in the same data.

A / Assignthe build, block by block, and who owns each one. Open a step to see it run.
HUMAN + AI, IN THE LOOP
The report assembles and reads itself; AI surfaces the buried signal; the team acts off one weekly truth.
Assemble itself
n8n01
Generate the weekly report from the source of truth
Details
No one spends a day on slides. The time goes to the action, not the assembly.
AI
Salesforce02
Pull from the CRM and warehouse
Details
The source of truth the weekly read runs on.
AI
Read across the data
Claude03
Surface what a human scan misses
Details
The account quietly cooling, the team over-consuming seats, the deal whose activity does not match its stage.
AI
Snowflake04
Run it across revenue and usage
Details
The whole dataset, not just the new-business slice.
AI
Drive the week
Salesforce05
Point every insight at the rep who can move it
Details
Hot leads, deal risks, expansion, churn, renewal. Six motions, one read.
AI
The team06
Work from one read in the meeting
Details
The report became the meeting. The forecast comes off the same weekly read every motion can see.
Human
N / Normalizethe motion that made it stick
A workflow without a motion is dead. This is how it became the way the team works.
1

Ran the number as a rhythm, not a fire drill

A standing weekly review meant risk showed up with time to fix it, instead of at the end of the quarter.

2

Made the forecast a defensible call

Every commit carried a confidence and a reason, so the number in the meeting actually meant something.

3

Turned the pattern into coaching

The report named the rep whose deals kept slipping; the review turned it into a coaching conversation with the rep who owned it.

T / Tie backthe result it drove, and how they know
RESULT · 01

-50%+ deal slippage

cut by the Deal Confidence Score.

RESULT · 02

6 motions, one read

leads, deals, expansion, churn, renewals, forecast.

RESULT · 03

One operating rhythm

reporting, forecasting, and pipeline aligned.

OUTPUT · 01

A self-generating report

Built from the source of truth, weekly.

OUTPUT · 02

A six-motion action layer

Every insight pointed at an owner.

OUTPUT · 03

One forecast read

The same truth for every motion.

The Sales Operator
06 / HOW YOU DO IT TOO

Here is what I built. Here is how you build it.

The whole thing installs as one plugin. Or grab the skills a la carte. Everything on this page, runnable, on what you paste today.

✓ EVAL PASS · 4/4
THE PLAYBOOK · ONE INSTALL
Run the weekly revenue cadence

4 skills chained into one runnable play. Installs as a single plugin, no copy-pasting each skill. It runs on what you paste; connect your stack to go live.

SEE THE FULL PLAYBOOK →
SEE IT RUN IN CLAUDE
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.
THE SKILLS IT USES
Know if you have enough at-bats for next quarter.
pipeline-creation-analyst
Get a straight verdict on every open deal.
deal-health-analyst
Walk into every 1:1 with the gap already found.
coaching-analyst
THE OTHER HALF · LEAD THE TEAM
Run the pipeline review→
I write up one of these a week. Free, receipts only.
RELATED BUILDS
Proactive Retention
A quarter of the churn stopped happening
The Deal Hub
Final stage 25%+ faster
THE MARKET ON THIS
The craft behind it: PLAN and the Deal Confidence Score (PLAN Selling)Talent first, plumbing second, agents last: the operating order behind Owner.com (Kyle Norton, Tenbound)The RevOps playbook: how Owner.com scaled its operating cadence (SaaStr)