Pipeline review: the weekly ritual of predictability

The pipeline review is the weekly ritual in which the sales manager and the team read the open deals in the CRM together to decide where to act before the week is gone. It moves deals when it happens with the CRM on screen, starts from lists the system itself generates (deals with no next activity, stalled beyond the cycle, with no decision maker mapped, with the close date shifting) and ends with a next step and an owner for every deal discussed. In most of the companies I work with, the meeting follows a different script: the manager walks through the funnel rep by rep asking “so, is this one closing?”, and the team prepares by updating the CRM the night before. That version eats up an hour of the whole team’s time, produces a number nobody stands behind on Friday, and teaches the rep that the CRM exists for the Monday meeting.

I wrote this for the people who run the ritual, for the CS and marketing leaders who depend on what comes out of it and for the HR team that organizes leadership development. After more than 200 companies served, what I see separating a useful meeting from a round of guesses is the way the manager runs that hour, and that is a skill people can learn. In CRM adoption the ritual appears as one piece of the 30-day plan; here I detail the meeting itself.

What is a pipeline review and what does it decide?

A pipeline review, also called a pipeline meeting, is the weekly review of open deals aimed at unblocking the ones that need action. It looks at the coming week: which deals are stalled, which have lost contact with the person who decides and which the rep is carrying on hope. The output is a short list of actions with an owner and a date, recorded in the CRM during the meeting. The month’s number shows up at the opening as context, and the discussion about how much the team will close belongs to a different ritual.

Pipeline review, forecast call and coaching 1:1

Many companies merge three rituals into one meeting. The manager who tries, in the same hour, to unblock deals, lock the month’s number and correct the rep who never asks about budget does all three halfway, with the whole team watching a colleague get corrected.

Ritual	Core question	Frequency and length	Who attends	Output
Pipeline review	Where is the deal stuck and what do we do this week?	Weekly, 45 to 60 minutes	Manager and sales, with presales and CS when the deal involves renewal or expansion	Next step with owner and date on every deal discussed
Forecast call	How much will we close this period and on what evidence?	Weekly or biweekly, 30 minutes	Manager, sales leadership and RevOps	A signed number by category, with a justification for each exception
Coaching 1:1	What does this person need to do differently?	Biweekly, 30 to 45 minutes	Manager and one rep	One behavior to practice and how the manager will follow up

The forecast call builds on what the pipeline review cleaned up: if the deals without a decision maker and the pushed dates went across the table on Monday, Tuesday’s commit starts from a reviewed base. The forecasting method, with categories and entry criteria, is in sales forecasting. The 1:1 receives what the meeting revealed about each person, such as a gap a rep repeats across several deals, and deals with it behind closed doors.

Why does the weekly sales meeting turn into a round of guesses?

The four patterns below show up together in most of the meetings I observe before any change. None of them depends on the tool. The manager runs the meeting the way their own manager ran it, and nobody trained them to do anything else.

The team updates the CRM the night before

When the meeting depends on what the rep says, the CRM becomes a board the rep tidies up before walking into the room. Open the change history and you will see stage, amount and date changes concentrated on Sunday night or Monday morning. That batch update shows the funnel the rep wants to present and hides from the manager the deal that stalled three weeks ago and got a new task the night before. That is why I first look at when the team records, and only then at what it recorded.

The manager asks about the rep’s hopes

“Is it closing this month?” and “is it hot?” are questions only the rep can answer, with their opinion, and no CRM data confirms or contradicts them. The optimist says yes, the cautious one says maybe, and the manager leaves the meeting with the team’s temperament in place of the customers’ situation. Since the question does not depend on the record, the rep concludes that filling in the system changes nothing in Monday’s conversation.

The meeting walks through the whole funnel

With eight reps and thirty deals each, a meeting that goes through all of them spends less than a minute per deal, and the stuck deal gets the same time as the deal that moves on its own. Going rep by rep also turns the meeting into public accountability in front of colleagues, and whoever is having a bad month learns to show only what is going well.

Nobody records what was agreed

The meeting ends with spoken agreements, such as calling the CFO or sending a case study, that never reach the CRM. The following week, the manager doesn’t remember what to follow up on, the rep doesn’t remember what they promised, and the meeting starts from scratch.

Pipeline management in the CRM: the lists that prepare the meeting

The meeting that moves deals starts before the room, with lists the CRM generates from saved filters. They do the selection the manager used to do from memory and bring to the table the deals that need a conversation, each with the evidence that justifies being there. Whoever administers the CRM or owns RevOps builds the views once, and the manager opens them on screen every week. The day thresholds depend on your sales cycle, which the CRM shows when you look at how long won deals spent in each stage.

List	CRM filter	What it usually means	Manager’s question
No next activity	Open deal with no future task or meeting	The rep lost the thread or didn’t record what was agreed	What is the next meeting agreed with the customer?
Stalled beyond the cycle	Time in stage above the median of won deals in that stage	The customer stopped moving and the rep hasn’t admitted it yet	What does the customer need to do for the deal to leave this stage?
No decision maker	Deal in proposal or negotiation with no contact in a decision maker role	The conversation is with whoever recommends, with no access to whoever signs	Who signs and what does that person already know about the proposal?
Close date shifting	Date changed two or more times in the quarter	The deal went cold or the date was never agreed with the customer	Who on the customer side agreed to this date?
Amount or stage changed with no activity	Amount reduced or stage changed this week with no meeting recorded	A night-before adjustment or a concession nobody discussed	What happened at the customer for the deal to change?

With the five lists, the meeting discusses ten to fifteen deals instead of walking the funnel. Keep the lists open to the team during the week: the rep who checks their list on Wednesday and books the missing meeting solves the problem before Monday. An AI agent can build these lists with the evidence for each signal, as I show in AI for sales managers, and the manager still needs to know what to ask about each deal. CS uses the same logic in the portfolio review, with renewals 90 days out with no meeting booked and low-health accounts with no plan recorded.

Pipeline review agenda for 45 to 60 minutes

The agenda below works for teams of five to twelve reps. With larger teams, split the meeting by squad or region, because with more people in the room each rep waits half an hour for their turn.

Block	Time	Question	Output
1. Funnel reading	5 minutes	How much came in, moved forward and left since the last meeting, and what is coverage against target?	Shared context, no deal discussion
2. Last week’s agreements	5 to 10 minutes	Did the actions recorded in the last meeting happen?	Completed actions closed in the CRM and pending ones with a new date or dropped
3. Exception lists	20 to 25 minutes	For each deal, what has the customer done and what is missing to move forward?	Next step with owner and date, recorded live
4. Large or strategic deals	10 minutes	What could change the period’s result and whom do we depend on?	A plan for the accounts that need support from leadership or another team
5. Wrap-up	5 minutes	What goes to the forecast call and what goes to the 1:1?	Actions read out loud and coaching topics noted by the manager

Block 2 is the one the team finds strangest in the first weeks and the one that shifts behavior the most. When the manager opens the meeting by checking last week’s agreements, the rep realizes that Monday’s promise will be remembered.

Rules for running the meeting

The CRM stays projected from the first minute to the last, and the manager opens the deal in the system before asking the question. The rep updates the record right there, in front of everyone, and the next activity is born in the meeting with a date and an owner. No side spreadsheet comes in, not even the manager’s: if the information is not in the CRM, the question becomes why it isn’t. A deal with a next step, a decision maker and a stable date stays out of the discussion, and the manager says so out loud so the team understands what the meeting values. Individual correction goes to the 1:1.

Who attends besides sales

CS joins for renewal and expansion deals and for new deals close to closing, to read what the rep promised before receiving the customer. Marketing doesn’t need to be there every week, but once a month the marketing lead gains a lot from seeing which sources generate deals that move and which generate deals that stall at the first stage, and takes that reading into the review of the lead criteria.

What questions does the manager ask in a pipeline review?

A useful question is about the buyer and has an answer that can be checked in the CRM or in the customer’s calendar. “Do you think it will close?” measures the rep’s confidence; “what has the customer done since the last meeting?” measures the progress of the purchase. The questions come from the exit criteria of each stage in the sales playbook: if the proposal stage requires an identified decision maker and a confirmed pain, the manager asks about both and the rep answers with what is recorded.

The map of who signs, influences and vetoes is what is most often missing in deals that stall at the proposal, and I explain how to build it in B2B buying committee. In the first weeks, the rep answers “I’ll check” to a good share of these questions, and that answer shows how much of the funnel rests on assumptions. The manager records the “I’ll check” as a next step with a date and reviews it in block 2 of the following meeting. The manager who uses these questions to expose someone in front of the team gets shorter and shorter answers and more and more generic records.

How does the pipeline review increase CRM adoption?

The team records what the manager reads in the meeting. If the meeting runs on what the rep says, recording becomes Sunday-night paperwork; if it runs on the CRM, recording becomes the rep’s preparation for Monday’s conversation, and the rep starts recording on the way out of the customer meeting. In operations where leadership trades the round of guesses for the list-based ritual, changes stop piling up the night before within a few weeks, an effect a new mandatory field rule doesn’t usually produce.

The gain reaches the other teams. Marketing receives, by source, the deals that move and the ones that stall, and adjusts channel and criteria with sales data. Post-sale receives won deals with decision makers and promises recorded, because they were followed up week after week during the sale, and starts onboarding without asking the customer the same questions again. Leadership receives a forecast built on deals that went through inspection.

To measure it, track four numbers in the CRM: the share of deal changes made in the 24 hours before the meeting, the share of open deals with a next activity scheduled, the share of deals in proposal with a decision maker associated and the share of actions agreed in the meeting completed by the next one. The first goes down and the other three go up when the ritual works.

The manager also needs to be trained to run the ritual

Most sales managers I know got the job because they were good salespeople. They learned to run their own sale and never learned to read other people’s funnels, to ask about the buyer without sounding like an interrogation or to separate what belongs in the meeting from what belongs in the 1:1. In a Gartner study released in 2021, only 42% of sales reps said managers at their organization are held accountable for providing good coaching, and the same release cites Gartner research according to which effective coaching from sales managers can unlock an 8% improvement in sales performance. The pipeline review is where that coaching starts, because it is where the manager sees, week after week, the gaps each rep repeats.

Running a meeting is learned through practice and feedback. In the CRM training I run with leadership teams, the exercise that changes the meeting most is having the manager run a pipeline review on the team’s real funnel, in front of peers, and get feedback on the questions asked, the time spent on each deal and the actions left unrecorded. Afterward, each manager writes their own agenda and the questions for each stage, and the CRM administrator leaves with the list of filters to build.

What HR and L&D need to know

HR spots the need in conversation with sales leadership: the meeting runs past an hour and nobody can say what came out of it, the forecast changes from one week to the next with no explanation, and there are managers promoted in the last year who have never run a management ritual. The cohort includes sales directors, managers and coordinators, the CS lead who runs the portfolio review and whoever administers the CRM or owns RevOps. Reps come in later, in a short session on what the new meeting will ask, in the format I describe in sales training that changes behavior. To measure, take a baseline with the four numbers from the previous section and the average meeting length, repeat it over the following eight weeks and schedule an observation of a real meeting a few weeks after the training.

Four-week roadmap to change your pipeline review

Week 1: observe and measure. Sit in on two meetings without running them and note the length, how many deals were discussed and how many actions were recorded. Pull the change history and see how much recording happens the night before.

Week 2: build the lists and write the questions. With the CRM administrator, create the five views and adjust the day thresholds to your sales cycle. Write the questions for each stage and present the new format to the team, with the lists open to everyone.

Week 3: run the new agenda. Run the meeting with the CRM on screen, record each action live and note the topics that go to the 1:1. Move the discussion of the month’s number to the forecast call.

Week 4: check and adjust. Open with last week’s agreements and compare the four indicators with week 1. Remove the filter that brought in deals with no problem, add what was missing and schedule the meeting observation with HR.

This ritual is part of the in-company training on CRM adoption and base management: I train managers to run the pipeline review and the portfolio review with the CRM on screen, build the exception lists with whoever administers the system and prepare the team to record what the meeting will ask. The team finishes with the CRM best practices guide and the account and base management manual, written for your operation, and HR receives the before-and-after indicators.

Frequently asked questions

What is a pipeline review?

A pipeline review is the weekly review of open deals in the CRM, run by the sales manager with the team. The goal is to identify stuck deals and leave with a next step, an owner and a date for each one, based on exception lists the system generates.

What is the difference between a pipeline review and a forecast call?

The pipeline review decides where to act during the week to unblock deals and ends with recorded actions. The forecast call decides how much the team will close in the period, involves the manager, sales leadership and RevOps and ends with a signed number. When they happen together, the discussion of the number eats up the time meant for stuck deals.

How long should a pipeline review last?

Between 45 and 60 minutes, once a week, for teams of five to twelve reps. If it often runs past an hour, the meeting is usually walking the whole funnel instead of discussing the exception lists.

Which deals should the pipeline review cover?

The ones on the exception lists: no next activity, stalled beyond the cycle, in proposal with no decision maker, with a shifting close date or with amount and stage changed with no activity. Add the period’s large deals. A deal with a next step, a decision maker and a stable date needs no discussion.

How do I get the team to stop updating the CRM only the night before?

Run the meeting with the CRM on screen, keep the lists open during the week and start by checking the agreements from the previous meeting. When the answer to the manager’s question has to be in the system, the rep starts recording on the way out of the customer meeting. Track the share of recording done in the 24 hours before the meeting.

How do you train managers to run a pipeline review?

Through practice on the team’s real funnel and feedback on the questions asked, the time per deal and the actions recorded. Sales directors, managers and coordinators, the CS lead and the CRM administrator take part, and reps go through a session on the new format afterward. HR measures it through CRM indicators and an observation of a real meeting.