Every Monday someone burns their Sunday night building the pipeline review: what moved, what's stuck, where coverage stands. Build that doc automatically and have it in Slack before the 9am call.
Happy to take Sunday night back. Three questions so the doc matches what your leadership actually reads: do they want the full pipeline or just what changed since last Monday? How do you define a stuck deal? And where do the targets live that coverage gets measured against?
Changes only — nobody reads the full dump. Stuck = no activity in 14 days, or the close date pushed twice. Targets are in HubSpot goals, quarterly per segment, and we run a 3x coverage rule.
Build
Built. Before you trust it on a Monday morning, I rebuilt the last three weeks' reviews from historical snapshots and diffed them against the decks your team made by hand. Two matched. One didn't — and the difference is interesting.
Test
It caught a real reporting error
The May 25 manual deck overstated new pipeline by $310k — a renewal had been hand-counted as a new deal. The generated doc computes new vs renewal from the deal type, so the error can't recur. Leadership saw the corrected trend line the following Monday.
That's exactly the kind of thing nobody catches at 8am. One add: for stuck deals, show whether they're even using the trial — that usually settles whether to chase or close it.
Perfect. Mondays at 7, and don't be late.
Go live
Liveagent · pipeline-review
Pipeline Review Agent
Mondays 07:00
Diff pipeline
Stuck + why
Coverage vs target
Doc to Slack
Posts by 07:05 · stuck-deal owners get private DMs · sources flagged if stale
Scheduled. The review doc lands in #pipeline-review every Monday at 7 — what changed, what's stuck and why (with trial activity), and coverage against target. Whoever was building it by hand gets their Sunday back.
HubSpot
Stripe
PostHog
Slack