// GuidesHow-to
How to run a pipeline review meeting: 30-minute agenda, 7 questions, template (2026)
Short answer
Run the pipeline review weekly, 30 minutes per rep, same day and same five blocks: 2 minutes on wins and misses, 3 on the exception counts from the pre-read, 17 on three to five priority deals, 5 on one coaching moment, 3 on written commitments. Spend 10 minutes before it pulling the exceptions from your CRM (stale deals, pushed close dates, single-threaded deals, deals with no next step) so the meeting starts from a short list instead of the CRM screen. Ask the same 7 questions on every priority deal and leave with one written action item per deal, with an owner and a date. The number belongs in the forecast call; deep work on one big deal belongs in a deal review.
How long should a pipeline review be, and how often?
Thirty minutes per rep, once a week, at the same time each week. Sybill’s 2026 guide puts it plainly: “The best pipeline reviews run 30 minutes, follow a consistent agenda, focus on 3 to 5 priority deals rather than the entire pipeline”. Rework’s cadence guide budgets 30 to 45 minutes for the weekly pipeline review, inside about 6 to 8 hours of structured management time per week.
Thirty minutes is enough when you review three to five deals, read the rest before the meeting, and keep the CRM updating out of the room. Run it one rep at a time.
- Weekly is the default for a B2B team with sales cycles of 30 days or more. A week is short enough that a deal that went quiet gets a nudge before the buyer has moved on.
- Bi-weekly can work for experienced reps with short cycles and steady results. Sybill states the cost well: “two weeks is long enough for a deal to stall completely without intervention.” If you go bi-weekly, keep the exception pre-read weekly so the stalls still reach you.
What should be prepared before the meeting? The 10-minute pre-read
Before every review, pull the exceptions from the CRM and pick the three to five deals the 17-minute block goes to. Ten minutes is enough with saved reports. Most agendas skip this step, which is why most reviews become a walk through the pipeline list.
Pipelines get inflated by exactly the deals a pre-read catches.
The 10-minute pre-read
- Stale deals. Open deals with no logged activity past your threshold. Pick one and keep it; a rule of thumb is 7 days for a sales cycle under 30 days, 14 days for 30 to 90 days, 21 days for over 90, adjusted to your data. Sort by amount.
- Pushed close dates. Deals whose close date moved since the last review, and deals pushed more than once this quarter. A second push is a signal on its own.
- Single-threaded deals. Deals past discovery with one contact on the account. Filter on contact count or roles; if your CRM cannot, the second of the 7 questions covers it.
- No next step. Deals with an empty next-step field, or a next-step date in the past. An empty field usually means the buyer owns the next move and nobody knows what it is.
- By-rep exceptions. Count the four exceptions per rep. A rep with 12 stale deals has a hygiene problem to fix before the meeting; a rep with 2 has two deals to talk about. Bring the counts and leave the lists in the CRM.
- Pick the three to five priority deals. Largest amounts closing this quarter with at least one exception, plus anything the rep asked to discuss. Write them into the action-item table before the meeting starts.
Tip
If you would rather score than filter
A HubSpot agency, NBH, rates each deal 1 to 5 on next-step quality, close-date realism and amount credibility, and reviews the five worst-scoring deals. It is the same pre-read folded into one number.
The fuller list of early warning signs is in how to identify at-risk deals.
The 30-minute agenda
Five blocks, fixed minutes, the same order every week. A block that runs over takes its time from the priority deals, so hold the line on the first two.
| Block | Minutes | Purpose | Question to ask |
|---|---|---|---|
| Wins and misses | 0–2 | Confirm what closed, note why anything was lost, move on. | “What did we learn from the one we lost?” |
| Exceptions from the pre-read (counts by rep) | 2–5 | Coverage against the number, then the exception counts from the pre-read: stale, pushed, single-threaded, no next step. | “Is there enough qualified pipeline for the number, and how much of it is real?” |
| Priority deals: 3 to 5, seven questions each | 5–22 | The three to five deals from the pre-read, 3 to 5 minutes each, using the 7 questions below. | “What has the buyer done since we last spoke?” |
| One coaching moment | 22–27 | One pattern across the deals just discussed (always single-threaded, close dates set by hope, no next step after demos) and one thing to try this week. | “What is the pattern across these three, and what would you do differently on the next one?” |
| Commitments, written | 27–30 | Read the table back: deal, owner, next step, date. Nothing leaves the meeting without an owner and a date. | “Who owns each of these, and by when?” |
Coverage in the exceptions block deserves one number, and it depends on your win rate. Landbase’s 2026 guide gives the formula: “The right ratio is 1 divided by your historical win rate.” A team that wins 25% of qualified deals needs 4x. Per the same guide, an SMB team with a 60% win rate needs 1.7x, and the common 3x rule assumes a 33% win rate. Use your own number, per rep if the win rates differ.
Sybill’s published agenda uses a similar five-block shape; what this page adds is the pre-read, the seven questions and the action-item table.
What questions do I ask on each deal? The 7 questions
Ask the same seven questions on every priority deal, in this order. The first three are facts and the last four are judgments, and a rep who cannot answer the facts should not be asked for judgments yet.
- What has the buyer done since we last spoke? Buyer actions only: replied, booked, introduced someone, sent a redline. What the rep did answers a different question.
- Who on their side is involved, and who is pushing this internally? One name means single-threaded. Then ask who else has to say yes, and whether the rep has met them.
- What is the next step, who owns it, and is it on a calendar? A next step without a date is a wish. If the buyer owns it, ask what happens if they miss it.
- What is the evidence for the close date? Something on the buyer’s side: a budget meeting, a contract review slot, a go-live they committed to. A quarter-end date with no buyer event behind it moves.
- What is the amount based on? Seat count, a quote they have seen, a written scope. A round number that has not changed since stage one is a placeholder.
- What could kill this deal, and what would we do about it? Every deal has one. A rep who says nothing has not asked the buyer.
- What do you need from me? An executive call, pricing approval, a reference customer. Write it as your own action item, with a date, in the same table as theirs.
Five of these are close to Sybill’s questions (buyer action, champion, close-date evidence, what could kill it, what the rep needs). The next-step and amount questions are the additions, because those two fields are where an inflated pipeline hides.
Tip
Three to five minutes per deal
If a deal needs more than five minutes, it needs a deal review, which is a separate meeting. Write “deal review” as the next step, put a date on it, and move on.
The action-item template (copy and paste)
One row per deal discussed, written in the last three minutes and read back aloud. Keep one document, newest review on top, so next week’s first question on each deal is whether last week’s step happened.
| Deal | Owner | Next step | By when |
|---|---|---|---|
| [Account, amount, stage] | [One name: the rep, or you] | [One verb, one object: “send the redlined MSA to their legal”] | [A date, and the meeting it is checked in] |
| Example: 120-seat expansion, $48k, Negotiation | Rep | Book the security review with their IT lead | Thursday, before next review |
| Example: same deal | Manager (you) | Approve the multi-year discount and send it to the rep | Tuesday |
| Example: platform renewal, $22k, Proposal | Rep | Ask the champion who signs, and get a meeting with that person | Next review |
- The owner is a person. “Team” or “us” is nobody.
- The next step is something the owner can do without the buyer, or a buyer action with a date the buyer agreed to.
- Open next week by reading last week’s rows. An unfinished row moves forward once; the second time, it becomes the coaching point.
Pipeline review vs forecast call vs deal review
They answer three different questions, and a meeting that tries to answer all three runs long and answers none. ORM Technologies’ forecast-call guide draws the line: “A forecast call is about the number for this period and what changed since last week. A pipeline review is about the inventory that will produce future periods.”
| What differs | Pipeline review | Forecast call | Deal review |
|---|---|---|---|
| Question it answers | Is the inventory real, and what moves each priority deal forward? | What is the number for this period, and what changed since last week? | How do we win this one deal? |
| Format and length | One rep at a time, 30 minutes, weekly | Whole team, deltas only; ORM sizes it at 45 minutes for eight reps | One deal, the rep and whoever can help, 30 to 60 minutes, as needed |
| Deals in scope | The 3 to 5 priority deals, plus exception counts for the rest | Commit and best-case deals whose category, close date or amount changed | One |
| Who prepares what | Manager: the pre-read. Rep: answers to the 7 questions. | Reps: the deltas, including committed deals with no buyer contact in the last week | Rep: the account map, the history and the ask |
| Out of scope | Debating the commit; solving one deal for 20 minutes | Coaching; deals outside the period | The rest of the pipeline |
The tell that a meeting has drifted is its length. ORM’s rule for the forecast call applies to all three: “If it runs longer, it has turned into a deal review.” When that happens in a pipeline review, book the deal review and take the deal off the agenda.
How do you stop it becoming a CRM-update session?
Move the updating out of the meeting and make current fields a condition of being discussed. Send the exception list the afternoon before, and the rep fixes hygiene items (a missing next step, a past close date, an amount nobody believes) in the CRM before the meeting. Whatever is still an exception at meeting time is a real question about the deal, which is what the 17 minutes are for.
Watch out
The failure mode
Sybill describes the result: the manager spends the meeting asking what the CRM should already answer, the rep spends it reconstructing calls from memory, and the strategy discussion never starts. If “let me pull that up” is said more than once, either the pre-read did not happen or the fields are not in the CRM.
- You read the CRM before the meeting, never during it. Do not share the pipeline list on screen.
- A deal whose fields are still missing gets one question, why the field is empty, and is then skipped until it is fixed.
- Track hygiene as a count per rep in the exceptions block. The conversation about it belongs in the 1:1, or in a separate, asynchronous weekly hygiene checklist if it is the recurring problem.
How diffi helps
diffi builds part of the pre-read for you. It reads Salesforce or HubSpot without writing anything back, and turns changes into plain facts: a close date pushed, a stage regressed, an amount changed and, from Salesforce, a deal with no change for 21 days. The single-threaded and no-next-step checks stay in your saved CRM view. Before the review, ask it in plain language what changed this week, who needs attention, or what the pipeline and win rate look like, and the answer links to its sources. The review itself can run as a recurring meeting series with a suggested agenda and prep items the rep fills in through a link. When you agree an action item, diffi can carry it out once you confirm, whether that is creating a tracker for the follow-up, sending the rep a Slack message, or booking the customer meeting with the invite. Book a demo to see your own pipeline this way.
See it on your own teamHow to start next week
Do not change everything at once; reps read a new meeting format as a new inspection. Add one piece a week and tell them the shape in advance.
- Week 1. Do the pre-read and run the five blocks with the minutes visible. Send the exception list the day before. Leave the 7 questions for later if the meeting feels crowded.
- Week 2. Add the 7 questions on the priority deals and the action-item table. Read the table back at the end.
- Week 3. Open by reading last week’s rows and count how many were done. That count, tracked weekly, is the measure of whether the review works.
- Week 4. Compare each rep’s exception counts with week 1. If a rep’s counts did not move, the problem is hygiene or capacity and belongs in the 1:1, using the sales 1:1 template.
Frequently asked questions
How long should a pipeline review meeting be?
Thirty minutes per rep. That is enough for a 3-minute pass over the exception counts and three to five priority deals at 3 to 5 minutes each, provided the exceptions were pulled before the meeting. Reviews that run much longer are usually doing the CRM update in the room.
Should pipeline reviews be weekly or bi-weekly?
Weekly for most B2B teams. Bi-weekly can work for experienced reps with short cycles and steady results, but two weeks is long enough for a deal to stall without anyone noticing, so keep the exception pre-read weekly even if the meeting is not.
What questions should I ask on each deal in a pipeline review?
Seven, in order: what the buyer has done since last time; who is involved and who is pushing it internally; the next step, its owner and its date; the evidence for the close date; what the amount is based on; what could kill the deal; and what the rep needs from you. The first three are facts, the rest are judgments.
What is the difference between a pipeline review, a forecast call and a deal review?
The pipeline review asks whether the inventory is real and what moves each priority deal, one rep at a time, weekly. The forecast call asks what the number is for this period and what changed since last week, with the whole team and deltas only. The deal review works one deal in depth with whoever can help win it, whenever a deal needs more than five minutes.
How do I stop a pipeline review turning into a CRM update session?
Send the exception list the day before and make current fields a condition of being discussed. Read the CRM before the meeting and never share the pipeline list on screen. A deal with a missing field gets one question and is skipped, and hygiene becomes a count per rep that you discuss in the 1:1.
What should be prepared before a pipeline review meeting?
Ten minutes of pre-read by the manager: stale deals past your activity threshold, close dates pushed since the last review, single-threaded deals, deals with no next step, the count of each per rep, and the three to five deals the meeting will spend its time on. The rep prepares answers to the 7 questions on those deals.
Should I review the whole pipeline or only some deals?
Only some. Three to five priority deals, with the rest covered by the exception counts in the exceptions block. Walking every deal is what turns a 30-minute review into an hour of status updates.