ZoomInfo
HackerOne
Apollo
Clay
Sumo Logic
G2
Chrome Web Store
AppSumo
Updated October 8, 2026
What is a pipeline review?
A pipeline review is a recurring meeting, usually weekly, where a sales manager and the reps go through open deals to check that each one has a real next step, a believable close date and the right people involved. Its purpose is to catch deals that are slipping while there is still time to save them.
It is a different meeting from the forecast call: the forecast call asks how much will close this period, and the pipeline review asks, deal by deal, what happens next. Most teams spend it on exceptions: deals that went quiet, close dates that keep moving and the largest deals of the quarter.
- Who: the sales manager and the account executives; RevOps often prepares the data, and a sales leader joins for the largest deals.
- How often: weekly for most teams, often on Monday, so the week's actions come out of it.
- How long: 30 minutes is enough when the list of deals to discuss is ready before the meeting.
In Cleanlist AI the agent prepares the exception that is hardest to spot by hand: open deals with no logged activity in 14 days, sent to each owner before the meeting.
What are stalled deals?
A stalled deal is an open opportunity that has stopped moving: no calls, emails or meetings logged for a while, no change of stage, and often a close date that has passed or keeps slipping. The usual flag is a run of days with no logged activity, and 14 days is a common line for deals in active stages.
Two weeks covers a missed follow-up, a holiday and a slow reply, so a deal that is still silent after that has usually lost its next step. HubSpot's own example of a deal risk score counts more than 14 days without activity as a risk signal. Long enterprise cycles may need 21 or 30 days; short sales cycles, 7.
| Signal | What it tells you | Where to see it |
|---|---|---|
| No logged activity for 14 days | Nobody has talked to the buyer, or nobody logged it | The deal's last activity date; HubSpot calls it Last Activity Date |
| Close date pushed again | The buyer keeps moving the decision | HubSpot's deal push rate report; the week-to-week changes in Salesforce Pipeline Inspection |
| Too long in one stage | The deal is stuck at a step it should have passed | Salesforce's Stuck Opportunities and Opportunity Stage Duration reports; HubSpot's time in deal stage report |
| Open past its close date | The deal is still open after the date the rep expected | A report of open deals filtered by close date, in either CRM |
HubSpot also stamps a deal's Is Stalled After Timestamp when its time in the current stage runs 20% longer than the deal owner's average for closed-won deals in that stage.
The play: Monday morning, quiet deals, each owner's own list
The agent is two steps. A deal stalls checks your CRM every Monday at 8:00 AM for open deals that have gone 14 days without logged activity. Notify sends each deal owner one Slack message with only their quiet deals, longest quiet first, or posts one list in a channel. Reading the CRM and sending the messages cost no credits.
| Step | In the app | What it does |
|---|---|---|
| Trigger | A deal stalls: Days without activity 14; How often weekly, Monday, 8:00 AM | Finds open Salesforce opportunities or HubSpot deals that crossed 14 quiet days since the last check |
| Notify | Send: Digest; Recipients: Each record's owner; Owner from: Deal owner; Sort by: Days since activity | One message per rep, longest quiet first; deals of owners who cannot be reached go to the fallback channel |
The agent only reads the CRM and sends messages. It changes no deal, logs no activity and emails no buyer: what to do with each deal stays with the rep.
A 30-minute pipeline review agenda
Thirty minutes is enough when the list of deals to discuss is ready before the meeting. Spend the first minutes on the numbers, most of the meeting on the deals that need a decision and the last minutes on who does what by when. Deals that are on track get one line from their owner, or none.
| Minutes | Segment | What happens |
|---|---|---|
| 0 to 5 | Last week's actions and the numbers | Check last week's actions; new pipeline, won and lost since the last review |
| 5 to 20 | Quiet and slipping deals | Each owner takes their deals from Monday's list: a next step with a date, or close it out |
| 20 to 26 | Deals closing this month | Commit or not, what could block it, who else needs to be involved |
| 26 to 30 | Actions | Read back each action with an owner and a due date, then log it in the CRM |
Send the agenda and Monday's list before the meeting, so reps arrive with an answer for each of their deals.
Deal review questions for each stalled deal
Ask the same short set of questions about every quiet deal. They separate deals that are slow from deals that are lost, and they turn each discussion into one action. A rep should be able to answer each one in a sentence; a question nobody can answer marks the risk.
- When did we last speak to someone at the account, and who was it?
- What did they say would happen next, and did it happen?
- Who else is involved in the decision, and have we spoken to them?
- Is the close date still real, and what would have to be true to close by then?
- What changed on their side since the deal was created: budget, priorities, people?
- What is our next step, and is it on the calendar with a date?
- If nothing happens in the next two weeks, do we close it as lost?
If the answer to the last question is yes, put that date in the CRM, so the deal does not sit open through the quarter.
What does a well-structured outbound pipeline review look like for a VP of sales?
For a VP of sales, a well-structured outbound pipeline review is short, weekly and built on exceptions. It opens with outbound pipeline created against target, then reviews only the deals that need a decision: quiet, slipping or large. Every deal discussed leaves with an owner, a next step and a date, and the same few numbers are tracked week over week.
- Pipeline created: outbound meetings held and opportunities created this week, against the weekly target.
- Conversion: meetings that became opportunities, and opportunities that reached the next stage.
- Exceptions: deals with no activity in 14 days, close dates in the past and the five largest open deals.
- Coverage: open pipeline for the quarter against the quota still to close.
- Actions: one owner, one next step and one date for each deal discussed.
For outbound deals, watch the early stages most closely: a first meeting that ends without a booked next step is often the first deal to go quiet.
The pipeline review template
Copy this template into the meeting invite or a shared doc. It keeps the review on the deals that need a decision and leaves a record of what each owner agreed to do. Fill the quiet deals from Monday's list, and keep last week's actions at the top so the meeting starts by checking them.
- Last week's actions: [owner], [deal], [action], done or not.
- The week in numbers: new pipeline $[amount] ([N] deals), won $[amount] ([N]), lost $[amount] ([N]).
- Quiet deals (no activity in 14 days): [deal], [owner], [stage], [days quiet], next step and date.
- Slipping deals (close date passed or moved out): [deal], [owner], [old date] to [new date], why.
- Closing this month: [deal], [owner], $[amount], commit or not, what could block it.
- Actions: [owner], [deal], [action], [due date].
How to unstick a stalled deal
Unstick a stalled deal by giving the buyer a reason to reply that is about them: something new and useful, a smaller next step or a direct question about timing. If that gets no answer, reach someone else at the account. If nothing moves in two more weeks, close it as lost and set a date to come back.
- Send something new: a relevant customer story, an answer to a question they raised or a change in your offer. A check-in with nothing new gives them nothing to answer.
- Offer a smaller step: a 15-minute call, a pilot or a call with a reference customer.
- Ask directly whether the project is still a priority this quarter, and what changed.
- Go wide: reach a second person involved in the decision. People Search finds the other buyers at the account.
- Schedule the follow-up: a short sequence keeps the next touches on time; see six sales sequences with timing.
- Close it out: mark it lost with the reason and a date to revisit, so the pipeline shows what is real.
The agent tells each rep which deals went quiet. What to send, and whether to keep the deal open, stays with the rep and the manager.
Stalled deals inside Salesforce and HubSpot
Both CRMs can show stalled deals to someone who goes looking. Salesforce has a Stuck Opportunities report and Pipeline Inspection, and Sales Cloud for Slack reminds reps when an opportunity has not been updated in a while. HubSpot keeps a Last Activity Date on every deal and reports on time in stage and pushed close dates.
| What you want | Salesforce | HubSpot |
|---|---|---|
| Last activity on a deal | A last activity date on each opportunity | Last Activity Date: the most recent logged note, call, sales email, meeting, message or completed task |
| What changed this week | Pipeline Inspection: pipeline metrics, opportunities and week-to-week changes in one view | Deal change history: changes to stage, amount and close date |
| Deals stuck in a stage | Stuck Opportunities (open opportunities by stage, sorted by age) and Opportunity Stage Duration | The time spent in deal stage report and the Is Stalled After Timestamp property |
| A nudge in Slack | Sales Cloud for Slack reminders when an opportunity has not been updated in a while or a close date is near | Attach a deal to a Slack channel and its logged calls, notes, emails, tasks and meetings post there |
HubSpot workflows, on Professional and Enterprise, can also send custom Slack notifications, so a HubSpot team can build part of this job with workflows. The agent does it from one sentence on either CRM: a weekly list per rep of the deals that crossed your quiet line.
What it costs, and which plan runs it
The agent spends no credits. Reading deals from Salesforce or HubSpot and sending the messages in Slack or email are free, and there is no enrichment step in the play. What it needs is a plan that runs agents and connects your CRM.
Running the agent needs Pro (from $89 a seat a month, $67 billed annually), which includes 5 active agents across the workspace, or Enterprise for unlimited agents. The 14-day Pro trial lets you build the agent and review its play; testing it and turning it on need a paid plan.
Every agent Clu builds carries a records-per-run limit: set it above the number of deals you expect the first run to list, since that run takes every open deal already past the line.
