A 45-Minute Pipeline Review Agenda That Finds Problem Deals

The meeting is only as good as the data going in. Set a deadline, such as the evening before, for reps to update these items:

• Stage, amount and close date on every open deal, with the category (commit, best case or pipeline).
• A dated next step on each deal in the second half of the pipeline.
• A one-line note on anything that changed since last week.
• New opportunities created, with source.

Whoever runs the meeting should scan the changes beforehand and mark three to six deals for discussion. Reps who know the list in advance prepare answers, and the meeting shrinks because nothing is a surprise.

Use fixed time boxes and hold to them:

1. Numbers first (5 minutes): coverage against quota, changes in the called number since last week, and anything that moved between categories.
2. Deals that moved or stalled (20 minutes): the selected deals, about five minutes each. The owner states the situation in two sentences, then the manager asks questions.
3. New pipeline (10 minutes): what was created, from where, and whether it matches your target profile.
4. Risks and help needed (5 minutes): what could slip, and who from outside the team could unblock it.
5. Actions (5 minutes): read back each action, owner and date.

If a deal needs a longer conversation, schedule it separately. The review shouldn't become a deal strategy session for one account.

Pick by rule, so the meeting doesn't drift toward whichever rep talks most. Include:

• Deals in commit, since a miss there hurts the forecast most.
• Large deals, whatever their category.
• Deals that moved backward, slipped their close date or changed amount.
• Deals with no buyer activity for a set number of days.
• Deals where you have met only one contact at the account.

For the last group, remember that one contact is fragile: if that person leaves or loses interest, the deal has no other path. Everything else gets a glance at the numbers and a line in the notes.

Questions beat commentary. Useful ones are specific and about the buyer, not the rep:

• What has the buyer done since our last review that they weren't asked to do?
• Who else has to approve this, and have we spoken to them?
• What's the buyer's reason to decide this quarter, and what happens if they don't?
• What's the next step, who owns it, and when?
• What would make you take this out of commit?

Watch the answers, not just the deal. Vague replies like "they're interested" or "waiting to hear back" are signals to dig. If a rep can't answer three of these, the deal isn't ready for commit.

Write the actions in the CRM during the meeting, not afterward, so each has an owner and a date. At the next review, start by checking last week's actions before discussing anything new. Unfinished actions with no reason are worth a direct conversation.

Watch for three drift patterns. The meeting becomes a status read-out, in which case cut the narrating and ask questions. It turns into a rescue session for one deal, in which case move it offline. Or reps update deals only right before the call, in which case set the deadline earlier and use the CRM's change history in the meeting.

Revenue intelligence tools such as Clari or Gong can surface which deals changed and which have gone quiet, but the discipline of deciding what to inspect stays with you. Tie the review to your forecast worksheet so the numbers discussed are the numbers you report.