Sales pipeline management: how it works and how to set it up

Sales pipeline management is the weekly routine that keeps an existing pipeline honest: deals that have stalled get noticed, values and close dates stay realistic, and every card has a next action with a date on it. This article answers the operating question, not the design one. Your pipeline already exists; how do you run it each week so the forecast means something and no deal dies quietly? Once the routine is in place, a sales lead can say on Monday morning which deals need help, and be right.

Why a well-built pipeline still goes stale

A pipeline decays from the day it goes live. Salespeople move cards forward after a good call and rarely move them back after a bad one. Close dates slip one week at a time. Deals the buyer abandoned months ago stay open because closing them as lost feels like admitting defeat.

The result is a board that looks full and forecasts badly. In a firm with flat revenue, that false comfort is dangerous: leadership believes the next quarter is covered when much of the value on the board is dead.

What good pipeline management looks like

Four habits do most of the work.

• Every open deal has a next step and a date. No date means no deal.
• Any deal without activity for a set number of days is flagged automatically, not discovered in a meeting.
• A close date in the past is treated as an error. The owner either moves the date with a reason or closes the deal.
• The weekly review is run from the board itself, filtered by owner, so the meeting and the data are the same thing.

Before you start

• A working pipeline in Opportunities with stages your team agrees on. If you have not built one yet, start with setting up a pipeline on the platform.
• Custom fields for next step and next step date, or a habit of using tasks for the same job.
• A stall threshold for each stage, in days. A discovery stage might allow a week, a contract stage might allow two.
• A standing 45-minute slot in the sales lead's week.

How to set it up

1. Open Automation and select Workflows.
2. Click + Create Workflow and start from scratch.
3. Click + Add new Trigger and select Stale Opportunities.
4. Name the trigger after the stage it watches, for example proposal sent stall.
5. Click Add Filters and set Duration in Days to that stage's stall threshold.
6. Under In Pipeline, choose your sales pipeline.
7. Under Pipeline Stage, choose the stage the threshold belongs to.
8. Click Save Trigger, then add the actions that tag the deal and give its owner a task.
9. Repeat with one stale trigger per stage, each with its own threshold.

For the leadership view of the same board, see building a tracker view for leadership.

The weekly review, step by step

Keep the meeting short and the order fixed. Start with stalled deals, because they carry the most risk. Then move to deals with close dates this month. Finish with anything new that entered the pipeline since last week.

For each stalled deal, the owner answers one question: what is the next step, and when? If there is no honest answer, the deal is closed as lost with a reason. That single rule does more for forecast accuracy than any report.

What it replaces and what it costs in time

Pipeline management replaces the round-the-table status meeting where each salesperson narrates their deals from memory. It also replaces the end-of-quarter scramble when finance asks why the forecast was wrong.

Each salesperson spends around five minutes a day keeping next steps current. The sales lead spends about 45 minutes a week on the review and ten minutes reading the dashboard beforehand. Building the workflows and dashboard takes half a day.

The mistake most people make

A related mistake is letting the sales lead update cards on behalf of the team. It feels faster, but owners stop feeling responsible for their own data.

When not to run a formal review

If you have fewer than ten open deals at any time, a weekly meeting is too much. A quick look at the board and the stall tasks is enough. The same applies to very short sales cycles, where deals close or die within days and the stall workflow does the job on its own.

Stage design problems will not be fixed by management either. If deals stall in the same stage every week, the stage itself is probably wrong; the guide to configuring and changing CRM pipeline stages helps there.

Troubleshooting

The stall workflow flags too many deals. Your thresholds are tighter than your real sales cycle. Look at how long won deals actually spent in each stage and set the threshold just above that.

Owners clear the stall task without changing anything. The task can be completed without updating the deal. Have the stall tag removed only when the next step date changes, not when the task is ticked.

The dashboard and the board disagree. The dashboard is probably filtered by a date range that excludes older deals. Remove the date filter for open-value widgets.

Follow-up after a review never happens. Agreed actions live only in the meeting. Turn each one into a task on the card during the review, or use follow-up workflows after a conversation so the next message sends itself.

Frequently asked questions

How often should the pipeline be reviewed?

Weekly for most firms with a sales cycle longer than two weeks. Daily stand-ups are only worth it for high-volume teams where deals move within days. Monthly is too slow; stalled deals go cold between meetings.

Who should attend the pipeline review?

The sales lead and every person who owns deals. Leave marketing and delivery out of the weekly review and give them a monthly summary instead, so the weekly meeting stays focused on actions.

What is a sensible stall threshold?

Roughly the time a won deal usually spends in that stage, plus a few days. Start with a single figure for all stages if you have no history, then adjust each stage after a quarter of data.

Should lost deals be deleted?

No. Close them as lost with a reason and keep them. Lost reasons show you what to fix, and old lost deals are often worth a reactivation message six months later.

The journey this guide describes