Quick answer
A weekly pipeline review is twenty minutes, same time every week, run from the CRM screen with five fixed questions: what came in and from where, what moved, what is stuck, what was lost and why, and what closes next week. Every stuck deal leaves with one action, one owner and one date. The CRM supplies the numbers, so the meeting is about decisions, not descriptions.
Key takeaways
- Twenty minutes is enough when the CRM has already done the information gathering.
- Five fixed questions: came in, moved, stuck, lost, closing next week.
- The shape of the pipeline by stage shows where deals wait; a bulge is a follow-up problem.
- Stuck deals get one named action each, and "close it" is a valid action.
Module 2 ended with the CRM live and the team using it. Module 3 is about what you do with it. The first habit, and the one that makes every other number in the CRM worth collecting, is a short weekly look at the pipeline.
Not a sales meeting. Those run for an hour, go round the table, and end with everyone describing their deals from memory. A pipeline review is twenty minutes, from the CRM screen, with five fixed questions.
Same time every week. Same five questions.
Why Twenty Minutes Is Enough
Before a CRM, the weekly meeting is mostly information gathering. Who has what, where is it, what happened with Sharma. The owner spends the hour finding out what the CRM would have told them in a glance.
With the pipeline on a screen, the gathering is already done. The meeting becomes about decisions: which deals need help, what to stop chasing, what to expect next week. Decisions take less time than descriptions.
If the review takes longer than twenty minutes, that is useful information too. It usually means something the CRM should show automatically is being worked out by hand.
The Five Questions
Ask them in this order, every week, without adding to the list.
- What came in, and from where? New enquiries this week by source. This is the only regular check on whether marketing money is working.
- What moved? Deals that changed stage, forward or back. Movement is health. A pipeline where nothing moved is a pipeline nobody worked.
- What is stuck? Every deal past the time limit you set for its stage in Module 2. Each one leaves the meeting with one action, one owner and one date.
- What did we lose, and why? The lost reasons for the week. Three losses on price in a month is a pricing conversation. Three on “no response” is a follow-up problem.
- What closes next week? A realistic list, by name, with the one thing still needed. This is your forecast, and it needs no spreadsheet.
Question three is where the time goes and where the money is. The other four should take a minute or two each.
Reading the Pipeline by Stage
The screen for the review is the pipeline by stage: how many deals sit in each stage, what they are worth, and how many are past their limit. Here is what it looked like for a manufacturing distributor one Monday:
Enquiry: 14 deals ā Quotation sent: 22 deals, 9 stuck ā Sample sent: 6 deals, 4 stuck ā Negotiation: 3 deals ā Order: 5 this week
One line tells the story. Twenty-two quotes out and nine of them stuck means the team is good at sending quotes and poor at following them up. Four of six samples stuck means samples go out and nobody asks what the customer thought. The review that week produced two actions, not twenty: a quote follow-up rule, and a “sample feedback” call three days after dispatch.
Shape matters more than totals. A healthy pipeline narrows steadily from left to right. A bulge in one stage is where deals go to wait.
Stuck Deals: One Action Each
The stuck list is the heart of the review. Three rules keep it useful.
One action, not a discussion. “Call the son who handles purchasing, Vikram, by Wednesday.” Not “we should probably chase that one”.
Allow “close it”. A deal stuck for six weeks with no reply is not stuck, it is lost. Marking it lost with a reason is a decision, and it clears the view for deals that are alive.
Help, not blame. The question is “what would move this?”, and sometimes the answer is the owner making a call. A real estate agency owner found that two stuck bookings needed a five-minute conversation about a payment plan that only she could approve.
Forecasting Without a Spreadsheet
Question five is the forecast, and it works because it is small and named. Not “we expect ā¹12 lakh this month” but “Sharma Hardware, Patel Agencies and the Jalandhar dealer should order next week, if the samples are approved”.
Write it down in the CRM. Next week, question two tells you whether it happened. After a couple of months you know how reliable your own forecasts are, which is the number most businesses never learn.
Who Is in the Room
Everyone who owns deals, and nobody else. For a small team that is the owner and two or three salespeople. The person running it opens the CRM on a screen everyone can see and does not take updates from anyone’s notebook.
An immigration consultancy runs it on Monday at 9:30 with the case coordinators present too, because “waiting on documents” is their stage and the stuck list is mostly theirs. Put the people who own the stuck stages in the room.
The First Review Is Messy
Expect the first one to run long and to be mostly cleaning. Deals that should have been closed months ago, stages nobody updated, time limits that turn out to be wrong for your business. That is fine. The first review’s job is to make the second one possible.
Close what is dead, with a reason. Move what is in the wrong stage. Adjust a time limit if half the pipeline is “stuck” on day one, because a limit that flags everything flags nothing. By the third week the list is short, the questions take a minute each, and the twenty minutes is real.
Keep the time slot even when there is little to say. A five-minute review that happened beats a thorough one that was postponed.
Run It From the Screen
The sheet below is the review on one page: the stage table, the five questions, the stuck list with an action column, and a box for decisions. Use it printed for the first few weeks. After that, a CRM built for your process shows the same page automatically, filled in, every Monday morning before anyone arrives.
Next lesson: the automation that pays back first, so that half of what you just reviewed by hand happens on its own.
Check what you learned
3 quick questions. Pick an answer and see why.
What is the main difference between a pipeline review and a sales meeting?
Without a CRM the meeting is spent finding out where deals are. With one, that is already on the screen.
A pipeline shows 22 deals in "Quotation sent" and 9 of them stuck. What does that suggest?
A bulge in a stage is where deals wait. Nine stuck quotes is a follow-up rule waiting to be written.
What should every stuck deal leave the review with?
Help, not blame; and marking a dead deal lost is a decision that clears the view for live ones.
You finished Lesson 1
Up next Ā· Lesson 2 CRM Automation for Small Teams: Reminders, Assignments and Alerts Read the next lesson Previous: Lesson 5 Ā· Getting Your Team to Actually Use the CRMPlanning a CRM for your business?
We design and build CRMs around the way your team already works. Tell us about your process and we will suggest the simplest setup that fits.