A Pipeline Review Agenda That Ends With Decisions

Why last week actions come first

Because it is the only part of the meeting that creates accountability. Reading last week list aloud takes three minutes and immediately changes behaviour: people complete actions they would otherwise let slide, because they know the list gets reopened. Skip this section and the action list you write at the end becomes decorative within a fortnight.

For each deal in the middle section, four questions in this order. What has the buyer actually done since last week. What is the specific next step and when is it. What is the one thing that has to happen before they can commit. And if this does not close, what will the reason be.

That sequence works because it moves from fact to plan to obstacle to honesty. The final question is the most valuable and the most often skipped. Salespeople almost always know the real risk in their own deals and will name it when asked directly, but rarely volunteer it in a meeting where optimism is the expected register.

Following up

It sounds like an action and contains none. Replace it with a specific event: calling on Thursday at four, sending the revised quotation this afternoon, meeting the finance head on Monday. If nobody can name the event, the deal is not being worked and should be treated accordingly.

Verbal stage changes

If a deal has moved, it should have moved in the system before the meeting. When it has not, the correct response is to have the salesperson update it in the moment rather than accepting the verbal version. This takes fifteen seconds and stops the practice permanently.

Deal strategy in the group

A twenty minute discussion about how to win one complex account is valuable and belongs in a separate conversation between the manager and the salesperson. In the group meeting it costs everyone else twenty minutes and produces a room full of people waiting for their turn.

Forecast arguments

Whether the month will land at a particular number is a separate discussion with different inputs. Pipeline review is about what to do this week. Mixing them turns a decision meeting into a negotiation about a number, and the negotiation always wins because it is more interesting.

Three views, in order. Movement since last week, which most systems can produce as a stage change report. The middle of the pipeline sorted by age in stage, so the oldest appear first and get attention automatically. And a coverage view comparing open pipeline value against what you need to close next month.

That third view is the one small teams skip and then regret a month later. Pipeline problems are visible weeks before they become revenue problems, and the only cost of catching them early is glancing at a number for thirty seconds each week.

Run a separate fifteen minute conversation with each salesperson fortnightly. Different agenda: their own numbers, their two hardest deals, and one skill they are working on. This is where coaching belongs, where an uncomfortable performance conversation happens without an audience, and where a salesperson can admit that a deal they described confidently in the group is actually in trouble.

The pairing matters. A group meeting that stays short and decision-focused only works if there is somewhere else for the longer conversations to go. Teams that have only the group meeting end up with a group meeting that does everything badly.

Related reading: lead management software, what a CRM is, CRM for small business, pipeline features, sales automation, and see it in action.