The Pipeline Review Most Teams Are Having

The pipeline review most teams are having is not really a review. It is a round of updates, followed by a debate about which deals will close. I would rather use that time to examine what the buyer has actually done, help the salesperson think clearly, and agree on the next useful action.

You probably know the pattern. A salesperson describes a proposal as promising because the customer responded positively. The manager asks whether it will close this month. The salesperson offers reassurance, then everyone moves on. The meeting produces a more confident forecast, but no stronger reason for the customer to buy.

I do not think this happens because salespeople dislike honesty or managers dislike coaching. The meeting often rewards certainty more than clarity. When every question returns to the monthly target, people learn to defend dates and amounts. Admitting that a decision process is unclear begins to feel like admitting failure.

Preparation also matters. If the basic facts are missing from the sales record, the meeting gets spent collecting them aloud. You ask when the proposal went out, who attended the last call, and what was discussed. These details matter, but reading them together leaves little time to decide what they mean.

I would separate three tasks that are often squeezed into one conversation. Status reporting tells you what happened. Forecasting estimates what may close and when. Coaching helps the salesperson choose a better move. A sales pipeline review can support all three, but it becomes useful only when updates make room for judgement.

Start with evidence rather than the salesperson's level of confidence. A proposal sent is evidence of seller activity. A buyer sharing the approval steps is evidence of buyer involvement. Neither guarantees a sale. The distinction helps you see whether the deal is moving because the customer is acting or merely because your team is busy.

Consider a software sale to a manufacturing business in Pune. The operations manager likes the demonstration and asks for pricing. That is a reason to continue, not enough evidence to assume a purchase this month. I would want to know what problem needs solving, who controls the budget, and what must happen before approval.

The review should make those gaps visible without turning into an interrogation. Ask what the buyer has confirmed and what the salesperson is assuming. Then identify the assumption that could most affect the deal. In this example, access to the budget owner may matter more than another demonstration for the same operations team.

Good sales coaching questions help someone reason, not simply produce an answer that pleases the manager. I would ask what makes the problem important now, what the buyer did after the last meeting, and whose agreement is still missing. Each question should help you understand a buying decision, not fill an empty field.

Listen carefully to the answer before adding another question. If the salesperson says procurement is reviewing the proposal, ask what that review involves. It could mean checking documents, comparing suppliers, or waiting for an internal request. Those situations require different responses. A department name alone tells you very little about progress.

Dates deserve the same care. Suppose a distributor in Ahmedabad wants equipment delivered before a planned expansion. You still need to understand who confirms the order and how payment approval works. I would test the proposed closing date against those steps, rather than treat the customer's desired delivery date as a purchase commitment.

This is where forecast theatre begins to lose its hold. You stop debating whether a salesperson feels confident and start examining whether the remaining work fits the available time. If an important approval has not begun, say so. A less comfortable forecast is more useful than a reassuring number built on untested assumptions.

Coaching must then lead somewhere specific. Asking the salesperson to follow up is not enough. For the equipment deal, the next action might be to arrange a call with the buyer and finance contact to confirm payment approval requirements. Name who will arrange it, by when, and what you need to learn.

Do not turn that action into another demand for a result the salesperson cannot control. They can request the call and explain why it matters. They cannot guarantee attendance or approval. I would agree on the action and a fallback: if access is refused, find out why and reconsider the expected closing date.

Another common mistake is the manager solving every deal personally. You may know the question to ask or the person to contact, but taking over too quickly limits learning. Ask the salesperson what they recommend first. Then help them improve the plan, while keeping responsibility for the customer conversation clear.

You also do not need to discuss every opportunity at equal length. I would focus attention where a decision, a risk, or a coaching need deserves it. A deal with clear evidence and an agreed next step may need little discussion. A large deal with repeated date changes probably needs a closer look.

Over time, the quality of your pipeline review depends on what happens after it. At the next meeting, check whether the agreed action happened and what it revealed. Do not punish an unwelcome answer from the buyer. Use it to adjust the plan, reconsider the forecast, or stop spending time on a weak opportunity.

This week, choose one deal that has appeared in several reviews without meaningful progress. Replace its usual status update with a conversation about buyer evidence, the biggest unanswered question, and one action to resolve it. Write down the owner and date before moving on. That is a practical place to start changing your review.