// Guides · Pipeline

How do you run a weekly pipeline review in 30 minutes?

By Kevin Bluett, co-founder of Ahoy · Updated September 2, 2026

A pipeline review takes all morning when it walks every deal and lets each rep narrate. It takes thirty minutes when the changes since last week are prepared before anyone sits down, only the deals that moved or stalled get discussed, and every deal discussed leaves with a next step and a date. The meeting is for decisions. The reading happens before it.

Why do pipeline reviews take all Monday?

I spent about a decade building CRM software and sat through more Monday pipeline reviews than I would like to count, on both sides of the table. The two-hour version further down is one I have run myself, and I would rather not run it again. Five things do most of the damage, and they compound.

The review walks every deal in stage order. Sixty deals, top of the board to the bottom, whether or not anything happened to them since last Monday. Most didn't move, and the meeting spends the same minute on each one finding that out.

Reps narrate history the manager could have read. "So I sent the proposal on Tuesday, they came back with a question about the security review, I looped in their IT lead..." The story is worth hearing once, but it is being told live, to the whole team, because nobody wrote it down anywhere the manager could have read it on Sunday.

The data is prepared by hand from a CRM that is a week stale. I did this myself as a manager: export the board on Sunday night, then spend the first half of Monday's meeting correcting it. That deal closed. That one went cold two weeks ago and nobody changed the stage. The review turns into the data-entry session the team skipped all week.

Nothing has to leave the meeting. There is no rule that a discussed deal exits with an owner, a next step, and a date, so the same deals come back the following Monday with the same story, one week older.

The review is three meetings at once. Coaching, the forecast roll-up, product feedback, and a general team check-in all get folded in because everyone is already in the room. Each of those would be a reasonable meeting on its own; stacked on top of the deal walk, they fill the morning.

I don't think any of this is a discipline problem. It is what happens when a meeting has no pre-read and no exit rule, and the only preparation on offer is a system of record that holds whatever people typed into it last week.

What does a 30-minute agenda look like?

The agenda has four blocks, and the time limits are doing most of the work, because a five-minute cap on the changes list forces that list to exist before the meeting rather than get assembled during it.

Changes since last week (5 minutes). New deals created, deals won, deals lost, deals that moved stage. Read as a list, not discussed. If the list is long, that is good news and it still takes five minutes.
Drifting and at-risk deals only (15 minutes). The deals that tripped one of the four filters below, and nothing else. This is the weekly sweep from the guide on why deals go quiet, run across the whole board. Each deal gets a decision, not a recap.
Commits for the period (7 minutes). For every deal in commit, one question: what has to happen for this to close on the date, and is that thing scheduled? A commit with no scheduled next event is not a commit.
Exit check (3 minutes). Every deal discussed today has an owner, a next step, and a date, written into the record now. If one is missing, fix it before anyone leaves.

Three things are missing from this agenda on purpose. Coaching on a specific deal happens in the rep's one-on-one, where there is time to open the thread and read it together. The forecast roll-up is a number the manager produces after the meeting, from the commit block, and sends to whoever needs it. Product feedback and "the buyer asked for X" go to a shared channel that product reads. Moving these out is what makes thirty minutes possible, and it is the part I would expect the most pushback on, because each item feels too small to deserve its own meeting.

Which four filters decide what gets discussed?

The answer to "which deals do we talk about" cannot be "all of them." Four filters, applied to every open deal before the meeting, produce the list: a deal that trips one is on the agenda, and a deal that trips none stays off it, however large it is.

Filter	What it catches	Threshold
Stage age past normal	Deals older than the usual number of days for their stage in your motion	Past your normal stage age; past double is a decision, not a discussion
Days since last inbound reply	Buyer silence, counted from the buyer's last reply, meeting acceptance, or forward. Rep activity does not count	Past the deal's normal reply cadence; a week for a thirty-day cycle, longer for enterprise
Close date moved	Slips, whatever the reason given	Second move, regardless of the reason
No dated next step	Deals with a stage but no agreed action and no date attached	Any open deal past Discovery

These four replace "let's go through the board." In sales calls this year the question we hear from managers is some version of where the pipeline gets stuck and why, and the filters are the closest thing I have to a short answer. The pre-read is the list of deals that trip at least one of them, nothing more, and on most boards that list is a fraction of the total, because most deals in a given week are either fresh or genuinely waiting on something with a date attached.

A note on the fourth filter. No dated next step is the most common flag and the cheapest to fix, since it usually takes one message to the buyer to turn "I'll follow up" into "Thursday at 10." It is also the one reps push back on hardest, because it turns an opinion about the deal into a commitment.

What has to be ready before the meeting?

The pre-read: one line per flagged deal, covering what changed since last week, what the buyer last did and when, and the action the rep proposes. Something like: "Acme, Proposal, 16 days since inbound. Buyer opened the proposal on the 19th, no reply since. Proposed: closing question to the champion, second thread to the VP who was cc'd in Discovery."

Either the manager prepares it or the system does. If the manager, it is an hour on Sunday afternoon reading threads and calendar invites; if the system, it is a view that already exists on Monday morning because the activity was captured all week. Either way it is ready before the meeting, or the meeting does not happen as a review.

It has to come from captured activity rather than the stage field, because the stage field is a rep's opinion, entered whenever they last had time, and a pre-read built from opinions spends its first ten minutes re-litigating whether the stage is right before it ever reaches a decision. Captured email, calendar, and call activity is not an opinion. "Sixteen days since inbound" is a number nobody has to defend, and the meeting can start from it.

The rule that makes this stick: if the pre-read is not ready, the meeting is a stand-up, not a review. Ten minutes on what changed, and everyone goes back to work. Holding a ninety-minute review on unprepared data does not get you a better review, only a longer one.

An illustration, not a benchmark. Say a manager with five reps and a 60-deal board. Last week the review walked all sixty at roughly two minutes each, which is two hours, and about half of those deals had nothing new since the week before, so the two minutes went to confirming that.

This week, the four filters run on Sunday night. Eleven deals trip at least one: four past stage age, three with more than two weeks of inbound silence, two with a close date that moved for the second time, and two with no dated next step. Some overlap. Eleven is the list.

The changes-since-last-week block is nine items, two new deals, one won, one lost, five stage moves, read aloud in five minutes. The eleven flagged deals get about eighty seconds each, which is enough to hear the proposed action, disagree with it if someone does, and settle on one. Fifteen minutes. Commits are six deals, and for each there is one question: what has to happen, and is it scheduled? Two of the six have nothing scheduled and get a next step on the spot. Seven minutes. The exit check finds one deal discussed without a date, and it gets one. The meeting ends at twenty-eight minutes with eleven dated next steps in the record, and the other forty-nine deals untouched, because nothing about them needed a decision this week.

Your board will produce a different list. What I would hold onto is the shape: a short changes list, a filtered discussion, an exit rule.

What rule keeps the same deals from coming back every week?

Every deal discussed leaves with an owner, a next step, and a date, written into the record during the meeting by the person who owns it rather than typed up afterward from someone's notes. The three-minute exit check exists to enforce this, and it is the block most teams are tempted to skip when the meeting runs long. Don't. Skip it and the meeting was a conversation about the pipeline, and the record looks the same on Tuesday as it did on Friday.

The second rule handles the deals that survive the first. A deal that trips a filter three weeks running gets a decision rather than another discussion: either the rep opens a second thread at the account and re-engages with something new, or the deal is parked in a stage that stays out of the forecast. There is no third option that involves talking about it again next Monday.

Both rules feel harsh for the first month, and I think that is fair. They stop feeling harsh around the time the meeting is reliably thirty minutes and the forecast stops surprising anyone.

What to look for in a tool

Most of the work described above is preparation, and preparation is the part a tool can take off the manager. I spent a long time building the traditional kind of CRM, and it is built to remember: it stores what was typed and shows it back. A pipeline review needs a system of action, one that reads the week's activity and prepares the list. Here is what I would ask of any tool you evaluate with this meeting in mind:

Does it produce a changes-since-last-week view built from captured activity, so the list reflects what happened rather than which fields somebody remembered to update?
Is days-since-inbound-reply a real number on every deal, counted from the buyer's side, with the rep's own follow-ups excluded?
Does it flag drift against your own stage norms, learned from your pipeline, rather than a fixed number of days that fits nobody's motion?
Is the pre-read prepared automatically before the meeting, or does the manager still build it by hand on Sunday?
When a deal gets a next step in the meeting, does the tool draft the follow-up for approval, so the rep leaves with the email already written and one tap from sent?
Does it keep a human in the loop, with guardrails? A tool that messages your buyers without approval is a different product; decide whether you want that separately.

This is the meeting Ahoy prepares. Because it captures the week's email, calendar, and call activity itself, the changes list and the days-since-reply numbers exist on Monday morning, drift is already flagged, and the next step agreed in the room comes with the follow-up drafted for one-tap approval. The AI prepares the work; you bring the judgment. If you want to see what a prepared pre-read looks like on your own pipeline, the free CRM audit is a 45-minute look at your current board: stale deals, deals with no dated next step, and how much of the week's activity actually reached the record. Nothing is connected and nothing is installed.

Frequently asked questions

What is a pipeline review?

A pipeline review is a recurring meeting where a sales team looks at open deals and decides what happens next on each one. Done well, it covers what changed since the last review, which deals are drifting or at risk, and what has to happen for committed deals to close. Its output is a set of dated next steps, not a set of updated stage fields.

How often should you run a pipeline review?

Weekly, for most revenue teams. A week is long enough for deals to move and short enough that a drifting deal gets attention before it goes dark. Teams with very long enterprise cycles sometimes run the full review every two weeks with a short changes-only stand-up in between. Monthly is too infrequent; by the time a quiet deal is noticed, the quarter is gone.

What should a pipeline review agenda include?

Four blocks: changes since last week (new, won, lost, moved stage), drifting and at-risk deals only, commits for the period and what has to happen for each, and an exit check confirming every discussed deal has an owner, a next step, and a date. Coaching, the forecast roll-up, and product feedback belong in other meetings.

How do you conduct a pipeline review using analytics?

Replace "walk the board" with filters. Before the meeting, apply four measures to every open deal: stage age against your normal stage age, days since the buyer's last inbound reply, the number of close-date moves, and whether a dated next step exists. Discuss only the deals that trip a filter. The analytics decide what gets discussed; the meeting decides what happens to it.

How do you automate pipeline review meetings?

Automate the preparation and the follow-ups, not the decisions. A tool that captures email, calendar, and call activity can build the changes list, compute days since inbound reply, flag drift, and draft the follow-up for each next step so it is ready for one-tap approval. Deciding whether to re-engage a deal or park it is still the manager's call, and it should stay that way.

Book a Demo Get a Free CRM Audit