---
name: weekly-pipeline-digest
description: Generates a weekly pipeline digest from your CRM's deals covering what moved, what stalled, and the top deals to push this week, formatted for email or a Monday standup. Use when the user asks for a "pipeline digest", "Monday pipeline brief", "what changed in pipeline this week", or sets up a recurring weekly pipeline summary.
license: MIT
compatibility: Requires a connected CRM. Read-only.
metadata:
  author: Builder.org
  version: 2.0.0
  persona: Operator Owen, Strategic Steve
  rave: R4 A4 V4 E4
  category: crm
---

# Weekly Pipeline Digest

## What it does

The Monday-morning read on the open pipeline: totals, what moved last week, what is stuck, and the three deals to push this week. Written to be skimmed in ninety seconds before standup and forwarded without edits. Read-only: it reports, it changes nothing.

## When to use

- "Give me the pipeline digest", "Monday pipeline brief", "what changed in pipeline this week".
- As a scheduled weekly summary for an owner, a team, or a whole pipeline.
- Not for per-deal coaching or drafts; the push list hands names to `deal-stage-nudges` and `stalled-deal-revival` for the follow-through.

## Inputs

None required. Optional: a pipeline name, owner, or segment to scope it. Works with any CRM your assistant can read (HubSpot, Salesforce, or similar); it only needs deals, stages, and amounts.

## The bar

- Ninety seconds to read, top to bottom. Every line earns its place or goes.
- The push list is exactly three deals, each with a reason a teammate could act on.
- Deltas are honest: a first run says "no baseline yet" instead of implying flat.
- Numbers agree with each other. If new plus advanced minus slipped does not reconcile with the total change, say what the gap is (usually closed or created deals) rather than letting a reader find it.

## Workflow

1. **Snapshot now.** Open deals: total count and value, per-stage counts and value, and each deal's days-in-stage.
2. **Compare to last week.** Pull the prior snapshot if one exists and compute deltas: pipeline value change, new deals, advanced, slipped, closed won and lost. First run: state there is no baseline and skip deltas without apology.
3. **Flag stalls.** Deals 14+ days in stage (the point at which "in progress" usually means "not being worked"), worst three shown, count for the rest.
4. **Build the push list.** Exactly three deals, chosen by closeness to close, value at risk, or a deadline this week. One line of reason each, concrete enough to act on before Friday.
5. **Write the digest** in the output format. Lead with the one-sentence headline of the week (up, down, or stuck, and why).
6. **Persist the snapshot** for next week's comparison: totals and the per-stage map only, nothing per-contact.

## Output

```
## Pipeline digest · week of [date]
[One-sentence headline: the week in plain words.]

**Open pipeline:** $[X] across [N] deals ([+/- $Y vs last week])
**New:** [N] · **Advanced:** [N] · **Slipped:** [N] · **Closed:** [W] won / [L] lost

### Stalled (14+ days in stage)
- [Deal] · [stage], [N] days ([count] more below)

### Push this week
1. [Deal] · $[amount]: [the reason, actionable]
2. [Deal] · $[amount]: [the reason, actionable]
3. [Deal] · $[amount]: [the reason, actionable]
```

## Worked example

```
Fictional example. Never reuse these names or numbers in real output.

## Pipeline digest · week of March 2
Pipeline grew on paper but the growth is all early-stage; the late-stage deals mostly sat still.

**Open pipeline:** $412k across 31 deals (+$38k vs last week)
**New:** 5 · **Advanced:** 3 · **Slipped:** 2 · **Closed:** 1 won / 2 lost

### Stalled (14+ days in stage)
- Fieldstone Payroll platform · Contract Sent, 24 days (4 more below)

### Push this week
1. Fieldstone Payroll · $52k: contract out 24 days; their COO promised legal review "in two weeks" on Feb 6. Nudge with the date.
2. Cobalt Build Co · $36k: their fiscal year ends March 31; every week from here is leverage lost.
3. Meridian Freight · $48k: CFO went quiet after pricing; the payback one-pager is the unblock, send it Monday.
```

## Never

- Never pad a quiet week. "Nothing moved" in one line is the report.
- Never list more or fewer than three push deals. Two reasons and a shrug is not a push list.
- Never present a first run as a flat week. No baseline means no delta, said plainly.
- Never include per-contact detail in the persisted snapshot. Totals and the stage map are all next week needs.

## Recovery

- No prior snapshot: full current-state digest, deltas skipped, one line noting the baseline starts today.
- Multiple pipelines and no scope given: digest the default pipeline and name the others with their totals in one line each, so the reader can re-scope next run.
- Stage data is sparse (deals with no amount or no stage dates): report on what is clean, and count the unreportable deals in one honest line; that count is itself a hygiene finding.
- A huge close or loss dominates the deltas: pull it out as the headline explicitly so the totals do not read as a trend.