How to Run a Useful Sales Pipeline Review Meeting

Choose the question the meeting should answer

Decide what this meeting needs to achieve. If the question is which open opportunities need help, use a pipeline view. If it is how the business performed last month, use the appropriate sales report. Give each discussion its own time and the right records.

For a weekly pipeline review, ask the team to bring changed opportunities, overdue commitments and decisions they cannot resolve alone. There is little reason to read every healthy opportunity aloud when its record already explains the next step.

Ask owners to update records beforehand

Ask opportunity owners to update the last meaningful customer activity, current stage and next action before the review. A note saying “follow up” provides little context. A useful update identifies the customer’s decision, the missing information or the action your team promised to take.

Managers should check that everyone is looking at the same filters and reporting period. Exclude closed work when reviewing the open pipeline unless a specific lesson is relevant. A saved view can help, but the team still needs to understand what the filters include.

• Confirm the current owner and the customer contact.
• Check the evidence behind the stage.
• Record the next action and who owns it.
• Identify commitments that are already overdue.

Put customer commitments first

Begin with urgent customer commitments, then review stalled opportunities and decisions requiring another team. Finish with newly qualified work that needs an ownership or handover decision. This approach gives the limited meeting time to records where discussion can change the outcome.

Do not assume every old opportunity is unhealthy. Procurement, renewal and project schedules can create legitimate waiting periods. Ask whether the expected next event is documented and whether a person owns the follow-up. The distinction is between an agreed wait and an opportunity that nobody understands.

Look into deals that have stopped moving

Stage ageing can highlight work that deserves attention, but it should not replace judgement. Compare similar types of opportunities rather than treating every service and deal size as identical. A fast repeat purchase and a new enterprise contract may have different review rhythms.

Investigate a few records behind an unusual total. The issue may be a forgotten stage update, a changed customer plan or a genuine loss of interest. Correct the record when the stage is wrong. Agree a customer action when the information is accurate but the work has stalled.

Save the decisions while everyone is there

Record the action in the appropriate CRM task, reminder or activity so it survives beyond the meeting notes. If a manager promises to approve a quotation or introduce a specialist, that commitment also needs an owner and a follow-up date. Accountability should apply to managers as well as salespeople.

Avoid creating a second private pipeline spreadsheet to capture the meeting. That makes the CRM less trustworthy and creates another place to maintain. Use your enabled workflow to record decisions, then confirm that the next review can find them.

Example: a quotation waiting for approval

A salesperson marks an opportunity as quoted, but the last activity shows that internal pricing approval is still pending. The manager could ask for another customer follow-up, yet that would not resolve the real blocker. The team first agrees whether the stage accurately reflects what has happened.

The pricing reviewer receives a specific action with the document reference and the question needing a decision. The salesperson owns the subsequent customer update after approval. The opportunity’s next review is tied to those actions rather than an arbitrary request to “push the deal”.

At the following meeting, the manager checks whether the approval occurred, whether the correct quotation was sent and what the customer said. If the customer is waiting on procurement, the team records that event and an appropriate follow-up. Each conversation can then use the previous decision as its starting point instead of reconstructing the entire history.

Give the delivery team a usable handover

When the customer accepts, check what the next team will receive. Delivery needs the agreed scope and dates. Finance needs the correct customer and commercial documents. Both need to know who can answer questions and which commitments still await approval.

Keep that information with the relevant customer activity, quotation, task or handover record in Zeyora. At the next meeting, check that the receiving team had what it needed. That is a more useful test of the review than whether everyone attended.