A pipeline review changes deal outcomes when it inspects what moved since last week and ends with dated actions. Run it from saved Salesforce views, not a spreadsheet. Look at new pipeline, stage movement, slipped dates, idle deals, missing next steps and missing buyers. Then ask each owner what evidence supports the deal's current stage.
How is a pipeline review different from a forecast call or a deal review?
Each meeting answers a different question. Blending them is why many weekly sessions turn into a status recital.
- Pipeline review: is the whole pipeline healthy enough, and moving fast enough, to hit future periods? Its scope is every open deal plus newly created ones.
- Forecast call: what will we close this period, and how confident are we? Its scope is the current period and the committed number.
- Deal review: what does this one deal need to win? It goes deep on a single opportunity, usually in a 1:1 or a small group.
Our guide on why Salesforce forecasts go wrong covers the forecast call. This article stays with the pipeline review and the deal reviews it triggers.
What should a manager inspect in Salesforce every week?
Inspect change, not totals. A total that looks flat can hide large deals leaving and small ones arriving.
- New pipeline created since the last review, by owner and source.
- Stage movement: deals that advanced, regressed or skipped stages.
- Slipped close dates, especially deals whose date has moved more than once.
- Stale deals with no logged activity since a cutoff your team agrees on.
- Open deals with a blank or outdated Next Step.
- Opportunities with no contact roles, which usually means nobody knows who the buyer is.
| Signal | Where to see it in Salesforce | Question to ask | Action |
|---|---|---|---|
| New pipeline | Report on opportunities filtered by Created Date this week, grouped by owner | Which of these came from a real buyer conversation? | Disqualify weak entries now rather than next quarter |
| Stage movement | Pipeline Inspection change metrics, or a report on stage field history | What did the buyer do that met the exit criteria? | Move the deal back if the criteria are not met |
| Slipped close date | Close Date field history, or Pipeline Inspection highlights | What changed on the buyer's side? | Record the reason and set a dated next step |
| Stale deal | List view on Last Activity date older than your cutoff | Is anyone still engaged on the customer side? | Re-engage with a plan or close it out |
| Missing next step | List view where Next Step is blank, sorted by amount | What is the next thing the buyer agreed to do? | Owner updates the field before the meeting ends |
| No contact roles | Report on opportunities without contact roles | Who signs, and who influences the decision? | Add contact roles and plan outreach to gaps |
Which Salesforce views should the review run from?
Build a small set of saved views and open them in the same order every week. Most of what you need ships with Sales Cloud; some pieces depend on licensing.
List views on Opportunities handle the exception lists: no next step, no recent activity, past-due close dates. Share them with each manager's team so reps can clean up before the meeting. The Kanban display of a list view shows deals by stage and allows drag-and-drop updates, which suits a quick walk through one rep's board.
Pipeline Inspection is the purpose-built workspace. It shows pipeline metrics by forecast category and by change type, such as new, moved in, moved out, increased, decreased, won and lost. A Changes Since filter sets the comparison window. Changed amounts, close dates, stages and forecast categories are highlighted on the opportunity list, and managers can save filtered views.
Pipeline Inspection also has an insights panel. It can show AI-based deal insights, activity details and, where configured, signals from calls and emails. Einstein Opportunity Scoring appears as tiers once it is set up. Which of these you get depends on edition and add-ons such as Revenue Intelligence, so confirm with your Salesforce account team.
Reports fill the gaps. Turn on field history tracking for Stage, Close Date, Amount and Next Step, then report on those changes. Historical trend reporting on opportunities lets you compare today's values with earlier snapshot dates. Dashboards then show the trend lines leaders track between meetings; our dashboard guide covers that design work.
What questions should a manager ask about each deal?
Ask for evidence that matches your stage exit criteria. If your stages have no written criteria, fix that first using our pipeline design guide.
- What did the buyer do last week that proves this stage is right?
- Who on the buyer side has agreed to the next step, and when?
- Who signs, and have we spoken with them directly?
- What has to be true for this to close on the date shown?
- If this deal stalls, what will be the reason?
- What do you need from me or anyone else to move it?
Avoid questions that invite a story, such as how a deal is going. Questions about specific buyer actions are harder to answer with optimism alone.
How do we capture notes and next steps without double entry?
Write decisions into Salesforce during the meeting, on the record itself. If notes live in a manager's notebook, the next review starts from memory.
Have the owner update Next Step and Close Date live while the deal is on screen. Pipeline Inspection supports inline edits to some fields, and list views allow inline editing where page settings permit. Log manager actions as tasks on the opportunity with an owner and due date. If you need a running manager comment, add a dedicated field or use Chatter on the record, and decide once which one is standard.
Drop the pre-meeting spreadsheet entirely. When the spreadsheet stays, reps update it instead of Salesforce, and the review inspects a copy.
Can activity data or conversation intelligence serve as evidence?
Yes, as supporting evidence rather than a verdict. Activity and call data show whether engagement is real, but they need a human read.
Logged emails, meetings and calls show recency and who on the buyer side is responding. Einstein Activity Capture or an email integration can fill this in without manual logging. Captured activity may not report the same way as logged records, though. Confirm how your setup stores it.
Conversation intelligence tools such as Gong go further, with call transcripts and deal-level engagement views. Our Gong guide explains how teams turn that into coaching. Either way, use the data to frame a question, not to replace one.
What cadence and meeting format work best?
A weekly team review plus regular 1:1 deal reviews covers most teams. The exact length and order matter less than doing it the same way every week.
- Before the meeting: reps clear their exception lists by an agreed time.
- Team review: walk the change metrics first, then the exception lists, then the largest deals at risk.
- Pick a few deals for deeper inspection and move the rest of the detail to 1:1s.
- 1:1 deal reviews: one rep, a short list of deals, and a coaching focus.
- Close with actions logged as tasks, each with an owner and a date.
Keep the team meeting about patterns that affect everyone. Individual deal strategy is better handled privately, where reps will admit what they do not know.
How do we keep pipeline reviews from becoming interrogations?
Make the questions predictable and the standard the same for every rep. People defend themselves when the rules seem to change by mood.
Publish the question list and the exit criteria so reps can prepare. Praise accurate bad news, such as a deal moved back a stage, as loudly as a win. Separate inspection from coaching: in the team meeting, note the gap; in the 1:1, work through how to close it. When a manager only appears to challenge numbers, reps learn to hide deals until they are safe.
Which pipeline metrics should we track over time?
Track a handful of measures calculated from your own history. Benchmarks from other companies rarely match your sales cycle or deal mix.
- Pipeline coverage: open pipeline for a future period divided by the target for that period. Decide your own healthy level from past periods.
- Stage conversion: of deals that entered a stage, the share that later reached the next stage or closed won.
- Sales velocity: number of opportunities times win rate times average deal size, divided by average cycle length in days.
- New pipeline created per week or month, by source and owner.
- Slippage rate: the share of deals whose close date moved out of the period they started in.
Stage conversion depends on stage field history or historical snapshots, so turn tracking on before you need the numbers. Reporting snapshots can store a copy of report results on a schedule if you need longer history than trend reporting keeps.
Why do pipeline reviews fail to change outcomes?
Most fail because nothing is different after the meeting. These patterns show up repeatedly.
- Reviewing every deal in order of amount instead of starting with what changed.
- Running the meeting from a spreadsheet exported the night before.
- Stages with no exit criteria, so stage questions have no right answer.
- Actions agreed aloud but never logged, so nobody follows up.
- Forecast questions crowding out pipeline creation and health.
- Managers editing reps' deals themselves, which teaches reps to stop updating.
What does a phase-one setup look like?
Start with views and habits before buying anything new. A few configuration changes and a written routine usually expose the biggest gaps.
- Write stage exit criteria and the weekly question list.
- Enable field history on Stage, Close Date, Amount and Next Step.
- Enable historical trend reporting for opportunities.
- Build shared list views for each exception signal in the table above.
- Turn on Pipeline Inspection if your licensing includes it, and save a view per team.
- Build one report each for new pipeline, slipped dates and missing contact roles.
- Set a weekly deadline for rep updates and log every review action as a task.
Inspection can also be scheduled. For Sync Payments, we connected Claude to its Salesforce data to run read-only pipeline and forecasting analysis on a schedule. It looks at deal age, close-date changes, coverage and forecast quality. Leadership receives ranked recommendations, which are verified against Salesforce reports. In a separate pilot, follow-up tasks were written to Salesforce only with human approval before each one.
