How to Run a 30-Minute Weekly Pipeline Review

It is Monday at 9:30. Four people are on a call and the deals board is shared on someone's screen. The first deal is a $40k contract that has been "closing next week" for five weeks. Forty minutes later the team has talked about six deals, heard a lot of call recaps, and nobody has changed a single field in the CRM.

Most weekly pipeline reviews fail the same way. They turn into story time. The fix is a tighter agenda, a little preparation, and one rule: the meeting exists to make decisions, not to report status.

Here is the 30-minute version I use with small teams of two to eight people.

What a weekly pipeline review is for

A good review produces three things, and you should be able to point at each one when the call ends:

1. An honest number. What you expect to close this month or quarter, split into what you would bet on and what could happen if things go right.
2. A dated next step on every deal that matters. Not "follow up". A specific action, an owner, and a date.
3. A short list of help requests. Deals where a rep needs a second opinion, an intro, or the founder on a call.

If the meeting does not change the forecast, a close date, a stage or a next step, it was a status update. Status updates belong in the CRM, where anyone can read them in two minutes.

Prepare before the meeting, not during it

The review only fits in 30 minutes if the data is already clean when people join. Ask every rep to spend ten minutes before the call on this checklist:

• Every open deal has a close date in the future. Anything in the past gets a new date or gets closed.
• Every deal in the current period has a next step with a date.
• The stage matches what the buyer has actually done, not what the rep hopes. (If your stages have no written exit criteria, fix that first. Here is a set you can copy.)
• Amounts reflect the latest conversation about pricing.
• Each rep picks one to three deals they want help with.

The manager, or the founder if you are still doing founder-led sales, prepares one thing: what changed since last week. Which deals are new, which moved forward, which slipped, and which closed. That list drives the first half of the meeting.

A 30-minute pipeline review agenda

Minutes	Topic	Output
0 to 5	The number	Commit and best case against target, and how both changed since last week
5 to 15	What changed	A quick pass over deals that moved, slipped or appeared
15 to 25	Help requests	Decisions on the two or three deals reps flagged
25 to 30	Confirm	Final commit number, owners and dates for every action

Minutes 0 to 5: the number

Start with the forecast, not with deals. "Commit is $84k against a $120k target. Last week it was $96k. Northwind slipped to next month." Starting here tells everyone what the rest of the meeting is for. If commit plus best case does not cover the target, the conversation is about creating or speeding up pipeline, not polishing it. If you are unsure what belongs in commit, this guide to forecast categories spells it out.

Minutes 5 to 15: what changed

Walk through the deltas only. A deal that moved from Demo to Evaluation gets one question: "What did the buyer do that moved it?" A deal that slipped gets two: "Why?" and "What is the new date based on?" New deals get a quick sanity check on amount and close date.

Deals that did exactly what they were supposed to do since last week get no airtime. That is the single biggest time saver.

Minutes 15 to 25: help requests

This is the part worth the meeting. A rep says, "Brightpath went quiet after pricing. I want to try their CFO directly. Does anyone know her?" The team spends a few minutes, someone owns an action, and you move on. If a deal needs more than five minutes, schedule a separate 15-minute call with the two people who need to be there.

Minutes 25 to 30: confirm

Read back the commit number and every action with its owner and date. Update the CRM while everyone is still on the call. If an action is not written down with a date, it will not happen.

Questions that get honest answers

"How is the deal going?" gets you "Good, they're excited." These questions work better:

• "What has to be true for this to close by the 30th, and which of those things are true today?"
• "Who besides your champion has seen the pricing?"
• "When did we last hear from them, and who started that conversation?"
• "What is the next meeting on the calendar? Is it accepted?"
• "If this slips, when will we know?"

None of these are traps. They separate what the buyer has done from what the rep believes. Ask them in a flat, curious tone and people will answer them honestly most of the time.

Which deals to skip

You cannot review 60 deals in 30 minutes, and you should not try. A simple filter:

• Discuss: deals closing this period that moved, slipped or have no next step. Deals a rep flagged.
• Skip: deals that are on track with a dated next step that happened as planned. Early-stage deals closing in a later period.

If someone wants to talk about a skipped deal, they can bring it as a help request next week.

Use the CRM as the agenda

Do not build slides. Every slide is a copy of data that was out of date the moment it was exported. Share the deals board filtered to the current period and update fields live as decisions are made. If something is wrong on screen, fix it on screen.

The "what changed" list is the most tedious part to build by hand. Some CRMs do it for you. In Heed, the This Week report compares the pipeline against nightly snapshots and lists what moved, slipped, closed and appeared, so the manager's prep is mostly reading.

Common ways the review goes wrong

• Story time. A rep retells the whole call. Interrupt kindly: "What did they agree to do next?"
• Solving deals live. A ten-minute debate about one deal while five people wait. Take it offline.
• Skipping weeks. The review only works as a habit. A 15-minute version is better than none.
• The manager talks the most. If the person running the meeting talks more than half the time, it is a lecture.
• No written output. If actions live only in people's heads, the next review starts from zero.

A pre-read template you can copy

Send this in your team channel or email an hour before the meeting. It takes the manager five minutes when the CRM is up to date.

Pipeline review, week of October 6

Target this quarter: $120k
Closed won so far: $31k
Commit: $84k (last week: $96k)
Best case: $41k

Moved forward
- Ledgerly: Demo to Evaluation (trial started Thursday)
- Corvid Labs: Proposal to Negotiation (legal review booked for the 14th)

Slipped
- Northwind: close date moved from Oct 24 to Nov 14 (budget sign-off moved)

New
- Pinecrest, $18k, Discovery, close date Dec 12

Help requests
- Brightpath (Sam): quiet since pricing, wants an intro to the CFO

Run this for four weeks without skipping one. By the fourth week the meeting will be shorter than 30 minutes, the forecast will move less from week to week, and the reps will start fixing their deals before Monday because they know which questions are coming.