Less status theatre.
More useful decisions.

What a pipeline review should achieve

A pipeline review is a working session for deciding what happens next to open opportunities. It should identify missing evidence, unblock decisions, correct misleading records and assign specific actions. Reading every deal aloud is only useful if it helps the team make those decisions. Otherwise the meeting duplicates information people could have read beforehand.

The review also creates a shared view of risk. A deal can have a high proposed value but no confirmed decision process. Another may be small and close to agreement, yet depend on a delivery commitment the business cannot meet. Looking at those conditions together helps the team decide where attention is needed.

This is Meibo’s suggested operating format. Salesforce recommends a regular weekly review and continued refinement of the sales process [1], but the exact cadence and agenda here are recommendations to test. A short sales cycle may require more frequent attention; a slow procurement process may benefit from a lighter weekly check and deeper milestone reviews.

Prepare one shared view before the meeting

Choose the scope: the pipeline, team and decision period under review. Ask opportunity owners to update their records before the session. The minimum useful picture includes stage, proposed amount and currency, expected decision date, next action, action owner and the last meaningful buyer interaction. Link to supporting context instead of copying the same notes into several places.

Define “meaningful interaction” for your process. An automated delivery receipt does not establish that a buyer is considering the proposal. A reply confirming an evaluation meeting does. Keep system activity separate from evidence of commercial progress so a busy activity feed does not hide a stalled relationship.

Prepare an exception list rather than an arbitrary list of the largest deals. Look for missing next steps, overdue actions, changed decision dates, unresolved dependencies and opportunities whose stage evidence is unclear. Treat these as prompts for investigation. An unusually long stage duration may be normal for a particular procurement cycle.

If your CRM cannot preserve a historical snapshot, keep a dated export for the review and document its scope. Do not overwrite the only copy when preparing the next meeting. A snapshot helps explain what changed, but it does not replace the live record as the working source of truth.

A 30-minute agenda to try with a small team

The agenda below is a starting format for a small, prepared team. It is not a benchmark or a promise that every pipeline fits into half an hour. If there are more substantive decisions than the time allows, narrow the scope or schedule separate deal sessions. Rushing through a longer list does not create clarity.

Begin with actions from the previous review. Confirm what happened and whether the evidence changed. Then look at changes in the pipeline, work through the selected exceptions and finish by reading back decisions. Reserve the final minutes for ownership and deadlines; an unresolved discussion should not quietly become an unassigned task.

One person should facilitate and keep the review focused. Deal owners provide context; people who can resolve a dependency should join the relevant discussion. Bringing everyone to every review can consume time without improving the decision. Make the resulting notes available to colleagues who need the outcome.

Five questions that make a deal discussion useful

First: what changed since the last review, and what evidence supports it? An owner’s confidence may change without the buyer doing anything different. Distinguish a new fact from a revised interpretation. A buyer confirming a budget meeting is a fact; “they seem more interested” needs further context.

Second: what decision does the buyer need to make next, and who is involved? This keeps the conversation connected to the customer’s process. It may reveal that a proposal is waiting on an internal stakeholder who has never seen it, or that the team has mistaken a helpful contact for the final approver.

Third: what is blocking progress? Name the dependency precisely. “Waiting for feedback” hides whether the buyer needs technical answers, an adjusted scope or time to coordinate internally. The response could be an introduction, a revised document, an honest delay or a decision to stop pursuing the opportunity.

Fourth: what will we do, who owns it and by when? Fifth: what evidence will tell us the action is complete? Together these turn discussion into accountable work. “Follow up soon” fails both tests. “Jules will confirm the procurement contact with Alex by Friday and record the reply” is specific enough to review.

Worked example: a proposal with no agreed review

Imagine a fictional consultancy with a £24,000 proposal marked “Proposal under review”. The owner has sent two reminders, but there is no buyer reply and the expected decision date is approaching. The CRM shows activity, yet there is no evidence that a review is scheduled. Neither the value nor the email count resolves that uncertainty.

The review identifies two separate issues. First, the stage may not meet the team’s documented entry condition. Second, the expected decision date has no current basis. The owner agrees to clarify who will review the proposal and when. The team records the missing evidence and updates the forecast judgement without inventing a new buyer commitment.

The action log records the owner, a due date and the required evidence: a confirmed reviewer and review plan, or a documented decision to defer or close the opportunity. If the buyer does not respond, the next review considers that outcome explicitly. The example demonstrates a decision process; it does not claim that the follow-up produces a sale.

Separate pipeline health from forecasting and coaching

Pipeline health asks whether opportunities have a credible stage, useful context and an owned next action. Forecasting asks what is likely to close within a particular period. A healthy opportunity can sit outside the current forecast because its decision date is later. A weak record can sit inside the forecast because someone has assigned an optimistic date.

Use the pipeline review to correct the underlying facts and surface judgement calls. If the team needs a formal forecast decision, give it a defined section or separate meeting with a consistent reporting period. Do not quietly treat the total open pipeline value as the amount the business expects to receive.

Coaching can also need a different setting. A long discussion about discovery technique or a sensitive performance issue can consume the meeting and discourage honest updates. Record the need for coaching and arrange it separately. The shared review should remain a place where uncertainty can be reported accurately.

Close the loop with an action log

Each decision should produce a record that someone can act on: the opportunity identifier, decision, next action, owner, due date and completion evidence. Include a link to the source record where possible. If the outcome is “no action”, document the reason and the condition that would trigger another review.

Use a single authoritative task location. A meeting worksheet can help structure the conversation, but a separate private task list quickly becomes another place to reconcile. After the review, put the actions into the system the team uses for daily work and preserve the meeting log as context.

Revisit overdue actions at the next session. Do not simply move every due date forward. Establish whether the task is still useful, whether ownership is wrong or whether the dependency needs escalation. A changed deadline should have a reason. This makes the process more informative than a recurring list of the same promises.

Measure whether the review is helping

For the first few cycles, observe the operation of the review itself. Are records ready beforehand? Does the meeting produce clear decisions? Do assigned actions get completed or deliberately revised? Are the same unresolved questions returning? These observations can improve the format before there is enough outcome history to assess commercial effects.

Avoid attributing every improvement in revenue to a meeting change. Sales outcomes also depend on demand, deal mix, timing and many other factors. Track operational changes separately from business outcomes, and keep the comparison period and sample size visible.

Download the action log below and try the format with one team. After several reviews, keep the questions that lead to decisions and remove sections that merely repeat the dashboard. The useful output is a better next step for each relevant opportunity, supported by evidence the team can find.

Common questions.