Sales pipeline review: the weekly ritual

The pipeline review is the meeting where the team looks at open opportunities and decides, for each one that matters, the next action. It is not a reading of revenue already booked. It is not a round of good news either.

Thirty minutes held properly beat a new CRM. The ritual forces hygiene: dates, amounts, dead deals.

Who is in the room, and looking at what

The manager and the sellers who own deals. The view is the board, not only an export sorted by amount. Amount matters; card age and a missing next action matter as much.

If the board is stale because it lives outside the inbox, the review starts late. A pipeline inside Gmail shrinks that gap: the card moved when the thread did.

Agenda

1. Commit for the period. Each announced deal is defended in one sentence: who decides, which date, which risk. No commit without a date.
2. Still cards. Past a threshold (often seven or fourteen days without movement), three outcomes: a dated action, a push outside the period, or lost. The forecast keeps only the first inside the commit.
3. Columns over the limit. If Proposal is overflowing, you add nothing: you move something out. That is the Kanban method applied to the meeting.
4. Qualification gaps. Late-stage deals with no champion, no decision criterion, or no amount. Step them back on purpose, rather than flattering the probability. Frameworks: BANT and MEDDIC.
5. One improvement. An exit criterion to clarify, a follow-up pattern, a useless column. Not a redesign.

Questions that replace storytelling

• What is the next action, and on which date?
• Who on the buyer’s side is waiting for it?
• What changed since last week?
• Why is this deal still in this column?
• If we lost it today, what reason would we write down?

Meeting anecdotes come after the answer, and only if they change the stage or the amount.

Minimum hygiene

By the end of the review, every deal you touched has either a follow-up in the task tool or a closed status. The follow-up guide shows how to pin the due date to the thread. The words you use (commit, slippage, opportunity) stay the ones in the glossary.

Colossales keeps the comment, the Google Tasks reminder, and the stage on the same card. The review can use the board instead of a parallel spreadsheet.

Bottom line

The pipeline review exists to remove ambiguity: next action, date, or exit. A team that holds it every week has a narrower, more credible forecast than a team that keeps adding CRM fields.