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.
Inside: Three headline metrics, one line per stage, and an attention list.
Install it in one line, or paste it in.
~/.claude/skills/ and runs automatically when it is relevant.Connect your context. Set it to your motion.
it reads pipeline, deals, and retention automatically.
pulls the trend and the prior weeks without a copy-paste.
adds top-of-funnel and usage signals cleanly.
This was built for a B2B SaaS org tracking a full funnel. Set these to your stack:
Report on any funnel you like. The skill reads your stages and your top three against last week, so point it at your metrics, not anyone else's.
| Set this | What it is | Default / Example |
|---|---|---|
| FUNNEL stages | the stages you report | leadspipelinedealsretention |
| TOP THREE | the numbers that lead the digest | your three most-watched metrics |
| MARKETING source | where top-of-funnel lives | a marketing toola sheet |
| RETENTION source | where renewals and churn live | a CRMa CS platform |
| CHANGE flag | week-over-week move worth naming | +/- 15% (re-tune) |
| ATTENTION rule | what earns an attention flag | off planslippingor gone quiet |
Everything the skill does, in full.
Pulls the whole go-to-market funnel onto one screen: what marketing generated, what pipeline did, how deals moved, and where retention stands. It surfaces the three numbers that matter this week, what changed since last week, and the handful of things that need attention, so a team starts the week aligned instead of digging.
- 1The three numbers that matter
Pick the three that decide the week and put them first. Each with its value, its target, and the week-over-week move. If everything is a headline, nothing is. Three, chosen on purpose.
- 2Across the funnel
One line per stage: marketing generated, pipeline created and covered, deals moved, retention held. A digest is one screen. If it scrolls, it is a report, and it will not get read on a Monday.
- 3What changed
Week over week, not since the start of time. Name the moves that cross the change flag, up or down, and tie each to a cause you can see. A change with no cause is noise.
- 4What needs attention
The short list. Anything off plan, slipping, or going quiet, across any stage. Each item names the owner and the move. Attention without an owner is a shrug.
- Exactly three headline numbers. A fourth headline means none of them is.
- The whole digest fits one screen. Length is a bug here, not thoroughness.
- Every change ties to a cause you can show, never an unsourced "up nicely."
- Attention items are owned. No owner, no action, no point.
GTM WEEKLY DIGEST · Week of the 7th The three New ARR $110K wk vs $125K plan -12% wk/wk Pipeline $210K created +18% wk/wk Net retention 98% flat Across the funnel Marketing 240 MQLs (+8%), 34 SQLs Pipeline $210K created, 3.0x coverage Deals 4 advanced, 2 slipped, 1 closed Retention 1 renewal booked, 1 account gone quiet Needs attention 1. Sales: two deals slipped the week, ~$90K. Pull to a decision. 2. CS: Delta Co dark 30d with a renewal in 75d. Re-engage.
The change flag (+/- 15%) and the choice of three headline numbers are defaults, not laws. They suited a weekly SaaS cadence. If your week is noisier, widen the flag. If your funnel turns on different metrics, swap the three. The logic does not change. The thresholds are yours.
Where an operator takes this next.
The digest works from numbers you paste each week. Here is where it stops taking someone an hour to assemble.
The team starts Monday already looking at the right three numbers, not digging for them.
A scheduled Claude task pulls Salesforce and your CS tool every Sunday night and has the digest waiting in Slack Monday morning.
Instead of a shared list, DM each flagged item to the named owner so nothing needs a second pass to get assigned.
Push the weekly output into a sheet or BI tool so twelve weeks from now you can see the pattern, not just this week's snapshot.
One skill is the on-ramp.
A single skill does one job. Chained into a playbook, or run as a full build, it becomes a system. Here is where this one plugs in.