Many sales teams hold one long weekly meeting where each rep goes through their deals, the manager asks about numbers, someone gets coached, and everyone leaves tired and unsure what was decided. It feels thorough. I think it is the weakest design, and the strongest alternative is three separate conversations with different purposes. Let me compare the one-meeting approach with the three-meeting one, and say where I land.
Pipeline review: is there enough, and is it real?
The subject here is the whole pool of opportunities, not any one deal. The questions are about quantity and health. How much pipeline do we have for this quarter and the next, relative to the target? How much of it was created recently, and how much is old? Are deals moving between stages at the usual speed, or piling up? Which stage shows the biggest drop-off? Where are the gaps in what we need to start prospecting now?
It looks forward, often months ahead, and its output is action on generation: more outbound in one segment, a campaign, a hygiene cleanup of stale opportunities. A weekly rhythm works, and the manager and sales operations can run most of it from a dashboard. A rep’s individual story is not the focus.
Forecast call: what number will we commit to?
This is about the current quarter only, and its product is a number. Each rep, or each manager when it rolls up, states what they will deliver and in which category: commit, best case, or pipeline. The manager challenges the categories and asks what changed since last week. The output is a single figure for the quarter and a short list of what could move it.
The discipline needed is consistency. If a deal is called commit, it needs agreed evidence: a signed order form is not required, but perhaps a confirmed decision date, a named approver and a procurement path. Without that, the call turns into hope. Over time, compare what was forecast with what closed. A person who consistently under-calls and over-delivers, or the reverse, tells you something about their judgement and not just their luck.
Deal review: how do we win this particular one?
Here the lens narrows to one opportunity, usually a large or stuck one, and the conversation is about strategy. Who is the economic buyer and have we met them? What is the compelling event? Who else is the customer talking to? What is the mutual plan to the signing date? What is missing? The aim is to improve the odds, so the manager acts as a coach and sometimes brings in an executive or a technical specialist.
The danger is turning it into an interrogation. A rep who expects to be grilled will present only good news. A deal review works when the rep asks for help and leaves with a concrete next step, such as an introduction or a revised proposal.
Why mixing them goes wrong
Each purpose needs a different attitude. A forecast call needs pressure to be precise. A deal review needs safety to admit weakness. If both happen in one meeting, reps learn that revealing a doubt in the coaching part will lower their forecast category, so they stop revealing doubts. The result is a worse forecast and worse coaching at once. A pipeline discussion, meanwhile, drowns in anecdotes about specific deals and never reaches the question of whether there are enough deals.
Time is the second problem. Ten reps with ten deals each cannot be covered in sixty minutes in any useful depth, so people either rush or the meeting runs long and the real issues come last, when attention is gone.
My side
Separate them, but keep each light. A reasonable pattern: a short weekly forecast call, a pipeline review that is largely data-driven and perhaps fortnightly, and deal reviews scheduled by exception for the largest or riskiest opportunities, not for all. A small team of four or five reps may combine the first two, and that is fine. What I would not combine is the forecast and the coaching.
Whatever the schedule, write down at the start what the meeting is for and what the output will be. If you cannot name the output, cancel the meeting. It sounds severe, but a sales team’s time is the scarcest thing it owns, and an hour that ends without a decision is an hour that did not happen.
Leave a Reply