How long should a pipeline review take?
Twenty minutes for a small team, and the length is set by the agenda rather than the pipeline. What to look at, in what order, and the three habits that turn a review into a status meeting.
Syncek Team · CRM reference library
/ 4 min read / Art. #79
Twenty minutes, weekly, for a team of two or three, in four blocks: one minute on the three numbers, ten on deals with no next step, five on deals that slipped their close date and four on anything a person wants to raise. If yours runs an hour, the length is not coming from the number of deals. It is coming from an agenda that walks the whole pipeline instead of the parts that need a decision.
The agenda, in this order
One minute: the three numbers. New deals, deals that moved, deals with no next step. Context, not discussion.
Ten minutes: deals with no next step. Each one gets a decision, and there are only three: set the next step, or move the stage, or mark it lost. "Leave it for now" is not one of them, because that is what produced the list.
Five minutes: deals that slipped their close date. A date that has moved twice is telling you the deal is not what the stage says it is.
Four minutes: anything a person wants to raise. Deliberately last and deliberately short.
That is twenty minutes. It fits because three quarters of the pipeline is never mentioned.
The twenty minutes, block by block:
| Minutes | Item | The rule |
|---|---|---|
| 1 | The three numbers: new deals, deals that moved, deals with no next step | Context, not discussion |
| 10 | Deals with no next step | Each gets one of three decisions: set the next step, move the stage, or mark it lost |
| 5 | Deals that slipped their close date | A date that has moved twice is telling you the deal is not what the stage says it is |
| 4 | Anything a person wants to raise | Deliberately last and deliberately short |
Does the size of the pipeline set the length of the review?
A team with 40 open deals does not need twice the meeting of a team with 20. Most deals in any pipeline need nothing said about them this week: they moved, or they have a next step with a date in the future, and both of those are already visible.
What needs discussing is the exceptions. Those are a roughly fixed number regardless of pipeline size, which is why the meeting can be short and stay short as you grow.
The three habits that stretch it
Walking every deal. A common one, and it feels thorough. It is the reason the meeting scales with pipeline size, which nothing about the work requires.
Reporting instead of deciding. "Still waiting to hear back" is a status, and a status is something the record should already say. If the meeting is where the CRM gets updated, you are paying meeting-time rates for data entry.
Solving the deal in the room. A deal that needs twenty minutes of strategy needs a separate conversation with the two people involved, not five people listening.
What has to be true before the review starts?
The meeting is short only if the record is current. Every open deal needs a stage and a next step with a date before it starts, and updating those is the work of the week rather than of the meeting.
When a review consistently overruns, the finding is usually upstream: nobody is updating stages, so the meeting is doing it live. That is worth fixing for its own sake, and it makes the review shorter as a side effect.
What do you do with the decisions a pipeline review produces?
The output is a short list of decisions and a shorter list of deals somebody now owns. If nothing was decided, the meeting was a report, and a report can be a message. Most of the recoverable revenue in a small pipeline is in the deals that stopped moving, and the review is the only scheduled moment anyone looks at them together. That is the whole justification for holding it, and it is also why the exception list belongs at the top of the agenda rather than the bottom.
Run it the same morning every week. A review that moves around gets skipped, and a skipped review shows up six weeks later as a pipeline that looks healthier than it is.
Frequently asked questions
How long should a weekly pipeline review take?
Twenty minutes for a team of two or three. The length comes from the agenda, not from the number of open deals: most deals moved this week or have a next step with a future date, and neither needs saying out loud. Only the exceptions get discussed, and those stay a roughly fixed number as the pipeline grows. A review that runs an hour is walking deals it could have skipped.
What should be on a weekly pipeline review agenda?
Four blocks, in this order: one minute on three numbers (new deals, deals that moved, deals with no next step), ten minutes on the deals with no next step, five minutes on deals that have slipped their close date, and four minutes for anything a person wants to raise. The order matters more than the timings. Exceptions go first because that is where the decisions are.
Who should be in a pipeline review?
The people who own deals, and nobody else. A deal that needs twenty minutes of strategy needs a separate conversation with the two people involved, not five people listening to it. If someone attends only to hear what is happening, they want a report rather than a meeting, and a report can be sent as a message on the same morning.
Why does our pipeline review always overrun?
Usually because the records are not current when it starts, so the meeting updates them live at meeting rates. The other common cause is walking every deal, which feels thorough and makes the meeting grow with the pipeline. Both are upstream problems: fix the habit of setting a stage and a next step during the week, and the review gets shorter without changing the agenda.
Does a one-person business need a pipeline review?
Yes, and it takes about ten minutes because there is nothing to explain to anyone. Open the same two lists, deals with no next step and deals that slipped their close date, and give each one a decision. The value is not the meeting, it is the scheduled moment when the exceptions get looked at together instead of whenever one of them comes to mind.
Should a pipeline review always be at the same time?
Yes. A review that moves around gets postponed, then skipped, and a skipped review shows up six weeks later as a pipeline full of deals nobody has decided anything about. The same morning every week is worth more than the perfect slot. Early in the week is the useful half of the rule, because the decisions it produces then have the rest of the week to be acted on.
What should come out of a pipeline review?
Two lists: the decisions taken, and the deals that now have an owner and a date. Anything else is a record of what was said. If the meeting ends and nothing in the CRM is different, it was a report, and a report is cheaper as a message. The test is simple: count the deals whose next step changed during the meeting.
Can a pipeline review be done asynchronously?
Partly. The three numbers and the list of deals with no next step can be posted in writing, and everyone can read them before anything is said. What does not work in writing is the decision on a deal nobody wants to call lost, which is exactly the one that needs two people in the same minute. Post the lists, meet for the exceptions.