Weekly pipeline review

Each week an analyst compiles the pipeline's movement — stage transitions, new and lost deals, the forecast delta, at-risk deals, and three focus deals — into a brief a reviewer re-checks against the raw numbers, then lands one approval where you sign off the brief before it goes to the team.

Saves you ~2 h / week

Start with this playbook

How it works

Trigger
On the “Weekly pipeline review” schedule.
Job
Compile the week's movement, draft the brief with risks and focus picks.
Outcome
A verified pipeline brief with risks and weekly focus.

What it installs

Agents 3

  • Pipeline Analyst

    Owns the weekly pipeline brief: stage movement, new and lost deals, the forecast delta, at-risk flags, and the three focus deals.

  • Pipeline Reviewer

    Independently recomputes the brief's numbers and verifies its at-risk reasons and focus rationales before the human sign-off.

  • Weekly pipeline review Quality Reviewer

    Checks primary evidence, domain controls, deliverable completeness, and communication quality, stopping the run when the work is wrong, unsupported, incomplete, or uncertain.

Teams 1

  • Pipeline Review Team

    An analyst who compiles the weekly brief, and a reviewer who re-checks it against the raw numbers.

Workflows 1

  • Weekly pipeline review

    Compile the week's movement, draft the brief with risks and focus picks, re-check it against the raw numbers, approve, and publish.

Documents 1

  • Pipeline brief format & definitions

    The brief's fixed sections, what counts toward the forecast, and the at-risk criteria the analyst applies every week.

Goals 1

  • The team starts every week knowing the pipeline

    A verified weekly brief covering movement, forecast delta, risks, and focus deals, published on schedule. Success looks like: Every week ends with a reviewer-verified, human-approved brief published to the team in which each number reproduces from the CRM, every at-risk deal carries its tripped signal, and three focus deals carry a why-now and a concrete next action.

Skills 3

  • pipeline-movement-analysis

    Compile a week's pipeline movement and forecast: stage transitions with direction, new and lost deals with reasons, a stage-weighted forecast with best/likely/worst scenarios, Commit vs Upside, gap-to-quota with coverage, and a delta decomposed into the deals that caused it. Adapted from anthropics/knowledge-work-plugins/forecast.

  • focus-deal-selection

    Flag stale, stuck, overdue, and single-threaded deals with evidence, score pipeline health with a hygiene audit and shape check, propose deals to remove, and rank the week's top three focus deals with a why-now and one concrete next action each. Adapted from anthropics/knowledge-work-plugins/pipeline-review.

  • brief-verification

    Re-check a pipeline brief against the raw CRM numbers: re-count the movement, re-compute the forecast delta and its decomposition, and verify every at-risk reason and focus rationale before sign-off.

Schedules 1

  • Weekly pipeline review

    Compiles, verifies, and publishes the pipeline brief every week. ## Professional quality control Objective: complete the recurring Weekly pipeline review operating cycle and deliver a review-ready, evidence-backed result rather than merely report that the schedule ran. Start by fixing the review period, reading the current source records and prior run, confirming required access, and listing missing or contradictory inputs. Execute the bundle's full authored method in order, retaining source, calculation, command, or before/after evidence for load-bearing findings. Separate facts from interpretation, apply supplied policy without inventing thresholds, and stop any branch that requires missing authority or an unconfirmed human rule. Produce the complete named deliverable plus an evidence record, assumptions, exceptions, unresolved questions, and concrete next actions with owners where the method calls for them. Run the workflow's independent verifier checks and fix failures before requesting approval. The task is done only when every requested section and quality criterion passes or a blocker is explicit; silence, inaccessible data, or polished prose is not proof of completion. Verify ICP fit, trigger evidence, contact lineage, conversation state, offer and policy limits, and every personalization detail. Outreach must sound like one informed person writing to another, without generic AI phrasing, fake familiarity, filler, hype, manipulative urgency, or reusable template lines disguised as research. The human retains authority over publication, sending, spend, signing, merging, deployment, and other consequential external actions.

Connectors pick at least 1 of 2

  • HubSpot

    HubSpot

    Connects to HubSpot so the analyst and reviewer can read deals, stage history, and activity for the weekly brief.

    Open the HubSpot connector
  • Attio

    Attio

    Connects to Attio so the analyst and reviewer can read deals, stage history, and activity for the weekly brief.

Folders 1

  • Pipeline review

Requirements

  • Browser access to your CRM — The agents work in your CRM through its web interface in your browser to read deals, stages, and activity for the weekly brief, and never change a record. Until you connect it, they work from attached exports (deal CSVs from this week and last) and the relevant document.

Setup guide

How to Run a Weekly Pipeline Review

A practical guide to turning CRM movement, forecast deltas, at-risk deals, and focus deals into a reviewed weekly brief.

Read the setup guide

Don't see your workflow? Describe it.

A sentence or two about a recurring job is enough. We design the playbook that runs it and show you exactly what it saves.

* What keeps taking time you don't have? *

Takes a minute · no account needed