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.
Founder, Task Machine
A weekly pipeline review is the operating brief that explains what changed in the sales pipeline since last week. It covers stage movement, new and lost deals, forecast deltas, at-risk deals, and the few opportunities that need focus next.
The point is not a dashboard screenshot. The point is a shared read of movement: what improved, what slipped, what explains the forecast, and what the team should do this week.
Why pipeline reviews quietly become theater
Most sales teams can open a CRM dashboard. Fewer can explain why the forecast changed without manually digging through deal history. The review meeting then becomes a tour of stale numbers, with the team discovering gaps live.
The hidden cost is inconsistency. If this week's forecast includes best-case deals and last week's did not, the delta is noise. If at-risk means "the manager feels uneasy", the list cannot be trusted.
What the manual process looks like
Done by hand, the weekly pipeline review has a fixed shape:
- Pull this week's CRM snapshot and last week's snapshot.
- Compare stage transitions, new deals, won deals, and lost deals.
- Recalculate the forecast using the same stage definitions every week.
- Decompose the forecast delta into deals added, grown, shrunk, slipped, or closed.
- Flag at-risk deals using written criteria.
- Pick three focus deals and one concrete next action for each.
- Review the brief against the raw numbers before sending it to the team.
The work is valuable because it is repetitive. Changing the format every week makes the brief harder to trust.
What an agent can automate
An agent can compile the brief and run the consistency checks:
- Compare snapshots. It reads the current CRM data and the prior week's brief or export, then calculates movement using the same window.
- Explain deltas. It ties forecast movement to named deals rather than reporting a number with no cause.
- Apply at-risk rules. It flags deals by criteria such as no activity, pushed close date, past close date, or single-threading.
- Choose focus deals. It recommends three deals with why now and the next action.
- Verify the brief. A reviewer agent checks numbers against the raw inputs before the human approval step.
What stays judgment: approving the brief, changing forecast definitions, and deciding whether recommended focus deals match the team's reality.
The guardrails that make it safe
The workflow is read-only. It reads the CRM, writes the brief, checks it, and waits. It does not change deal stages, owners, amounts, or close dates.
The definitions document is the control point. It fixes the review window, forecast weighting, at-risk criteria, and brief sections so every week is comparable to the last one.
Set it up in Task Machine
The Weekly pipeline review playbook installs the analyst, reviewer, review workflow, brief definitions document, goal, schedule, and CRM-connected skills. Setup takes a few minutes. You need a Task Machine workspace and permission to install playbooks (workspace owners have it). CRM access is useful but not required up front; until you authorize it, the agents work from attached deal exports.
1. Find the playbook
Open Playbooks in your workspace and search for "weekly pipeline", or browse to the Sales category.
2. Preview what it installs
Choose Preview & install to review the analyst, reviewer, workflow, definitions document, schedule, and HubSpot and Attio service choices.
3. Pick your CRM
Click Start setup and pick the CRM to read from: HubSpot or Attio. Pick at least one. Unpicked services are not installed.
4. Define the review rules
Fill in the pipeline scope, forecast definition, at-risk criteria, and brief audience. This is where you make the weekly numbers comparable.
5. Generate and review
Select Generate customized playbook. Review the generated analyst, reviewer, workflow, definitions document, selected CRM service, goal, and schedule.
6. Install
Use Install customized playbook to create the records. Follow-ups arrive to authorize the CRM, confirm the brief definitions, and start the first review. Each brief waits for approval before it goes to the team.
What good looks like
- Deltas are explainable. Every forecast change points to specific deals.
- The format stays stable. The team reads the same sections in the same order every week.
- At-risk means something. Each risk label names the signal that triggered it.
Common questions
Can it replace the pipeline meeting? It can shorten the meeting. The team still decides what to do with the focus deals.
Does it change CRM records? No. The review workflow reads and reports only.
What if our forecast definition changes? Update the definitions document and note the change in that week's brief so comparisons remain honest.
Can it run from exports? Yes. Attach current and prior deal exports until CRM access is authorized.