Key takeaways
- Review the exceptions, not the whole board: overdue close dates, stuck stages and missing next steps.
- Saved views make the review repeatable, so no deal slips off the list because someone filtered differently.
- Leave every flagged deal with one recorded decision before moving on.
- A hygiene review keeps the data honest; it is not a revenue forecast.
What should a weekly pipeline review cover
A weekly pipeline review should cover the few deals where something has to change this week, not every open deal. Reading the whole board aloud fills the hour and leaves no time for the deals that are actually in trouble.
Most deals are moving as expected. The useful conversation is about the exceptions, and you can define them before the meeting starts.
- Deals whose close date has already passed.
- Deals that have sat in one stage far longer than your sales cycle usually allows.
- Deals with no task or meeting booked.
- Deals whose amount or probability no longer matches what the buyer has said.
How do you find stale deals and overdue close dates
Find stale deals and overdue close dates with filters you save once and reopen every week. On the deals board in the Pebbles Ai CRM, in Beta, filter the open deals by close date and save the view under a plain name such as Past close date.
Save one more view for each stage you watch, so deals that have not moved since last week stand out. The same question then gets asked the same way every week, whoever runs the review.
How do you run the pipeline review meeting
Run the pipeline review meeting deal by deal, with one decision recorded for each. The owner says what changed, and the group picks an outcome: a new close date with a reason, a dated next step, a stage change, or closing the deal as lost.
An assistant helps either side of the meeting. Beforehand, give the Strategy assistant the flagged deals and the owners' notes and ask for one status line and one probing question per deal. Afterwards, ask it to record the agreed changes on each deal; every CRM write follows your execution mode, so in Manual you approve them on a card.
Why a pipeline hygiene review is not a forecast
A pipeline hygiene review checks that the data is honest; it does not predict revenue. The CRM shows each deal's value, close date and win probability as they stand, but it does not forecast revenue or attribute it to campaigns.
Treat the probability field as the owner's judgement, recorded the same way every time, rather than a model's output. Clean, checked close dates still make any forecast you build elsewhere more trustworthy.
How a routine review replaces reminder rules
A routine review covers the same ground as reminder rules that nag an owner when a close date passes, in one sitting instead of a stream of alerts. The review itself is the routine: same day, same saved views, same questions.
Keep each week's review chat in one project. Project memory then carries the team's agreed rules, such as what counts as stale, into the next week's chat without anyone restating them.
How to run a weekly pipeline review, step by step
Set up the saved views once; after that the review takes the same shape every week.
- Open the deals board in the CRM and load the saved view of open deals past their close date.
- Load your saved views by stage and flag the deals that have not moved since the last review.
- Give the flagged deals and their owners' notes to the Strategy assistant inside your pipeline review project, and ask for one status line and one question per deal.
- Take each flagged deal in turn in the meeting and agree a new close date, a next step, a stage change or a loss.
- Ask the assistant to record the agreed changes on each deal, approving the CRM writes if you work in Manual mode.
Where Pebbles Ai fits
- CapabilityProspecting & customer recordsOpen deals sit on a board across Qualification, Discovery, Proposal and Negotiation, with filters and saved views. The CRM is in Beta and shows the pipeline as it stands, without forecasting.
- CapabilityAI workspaceKeep the weekly review chats together in one project, and approve each CRM update the assistant makes on a card in Manual mode.
Common questions
How long should a weekly pipeline review take?
Long enough to reach a decision on every flagged deal, and no longer. If it keeps overrunning, the rule for flagging a deal is too loose.
Who should attend a pipeline review meeting?
The deal owners and whoever sets the team's priorities. Everyone else can read the decisions on the deal records afterwards.
What counts as a stale deal?
A deal that has stayed in one stage well past your usual sales cycle, or has no next step booked. Agree the rule once and tell the assistant, so Project memory keeps it.
Can AI forecast my pipeline?
Pebbles Ai does not forecast revenue or attribute it to campaigns. It helps you keep the close dates and stages a forecast would rest on accurate.
About this page. Written by the Pebbles Ai team for people who run sales, marketing and growth. Last updated .
