Guide
Sales pipeline management: stages, probabilities, reviews and metrics
Sales pipeline management means knowing, at any moment, how many deals are open, where each one stands and what it needs to move, then acting on that every week. This guide covers stage design, win probabilities, data hygiene, pipeline reviews and the metrics worth tracking.
What pipeline management is, and why it pays
A sales pipeline shows every open deal and the stage it has reached in your sales process. Managing it involves three jobs: designing stages that mirror what really happens with buyers, keeping what is recorded in them accurate, and using the result to steer reps toward the deals that deserve their time.
The payoff is measurable. In a survey of 62 B2B companies by Vantage Point Performance and the Sales Management Association, published in Harvard Business Review, 44% of executives rated their organisation ineffective at managing its pipeline. Based on executives' own ratings of revenue growth, companies with a formally defined sales process reported 18% higher revenue growth than those without one, and companies that mastered three specific practices reported 28% higher growth. Those practices, a clearly defined process, enough time spent managing the pipeline and managers trained to do it, are the backbone of this guide.
| Concept | What it measures | Who uses it |
|---|---|---|
| Pipeline | Open deals and where each one sits right now | Reps and their managers, weekly |
| Funnel | Conversion rates between stages over a period | Sales and marketing leaders improving the process |
| Forecast | What is expected to close in a given period | Leadership and finance, for planning |
Design stages around exit criteria, not labels
A stage with no definition becomes an opinion. One rep moves a deal to Proposal sent the moment a price list goes out on WhatsApp; another waits until the buyer has confirmed scope and budget. Both deals now sit in the same stage with the same probability, although their real odds are far apart. The fix is to define each deal stage by a verifiable buyer action. A stage's exit criterion is the next stage's entry criterion, so the table below lists, for each stage, the event that lets a deal in.
| Stage | Verifiable entry criterion | Starting probability | Typical days |
|---|---|---|---|
| Qualified | Need, authority and timeframe confirmed on a logged call | 10% | 7 |
| Discovery meeting | Met the decision maker or their delegate and documented requirements | 20% | 10 |
| Proposal sent | Written proposal sent, based on requirements the buyer confirmed | 40% | 14 |
| Negotiation | Buyer is negotiating terms, price or conditions in writing | 60% | 14 |
| Verbal commit | Decision maker has said yes and procurement has started | 80% | 10 |
| Won or lost | Signed contract or purchase order, or a clear no with its reason | 100% or 0% | Not applicable |
Rules of thumb for the design:
- Keep it to five to seven stages; fewer hides detail, more wears reps out.
- Name stages after what the buyer did, not what the rep did: “buyer requested a proposal” beats “we called them”.
- Run separate pipelines when the motion differs: new business, renewals and long government tenders.
- Keep unqualified leads out of the pipeline until interest is proven; they inflate the totals and add no information.
Win probabilities and weighted value
Weighted pipeline multiplies each deal's value by its stage probability and adds up the results. Take a SAR 400,000 deal at Proposal sent (40%) and a SAR 150,000 deal in Negotiation (60%): they contribute SAR 160,000 and SAR 90,000, so SAR 250,000 weighted in total.
That figure is useful across the whole pipeline and misleading for a single deal, because no deal closes at 40%. Use it for planning, never to judge one opportunity.
More importantly, probabilities have to be calibrated from your own history. A separate Harvard Business Review article observes that CRM systems weight revenue by stage automatically, yet few teams ask the obvious question: if 100 deals passed through a 25% stage, did 25 of them actually close? Ask it every quarter:
Collect decided deals
Take every deal closed won or lost over the last six to twelve months.
Measure reach-to-win
For each stage, calculate the share of deals that passed through it and ended up won.
Compare with the configured probability
If the gap is large, adjust the probability, or tighten the stage's entry criterion, which may be too loose.
Keep probability at stage level
Do not let reps tweak each deal's probability by feel. Give them a separate forecast category, such as Commit or Best Case, to express their judgement.
Pipeline hygiene: rules that stop phantom numbers
The same article lists human habits that inflate pipelines: holding back bad news, keeping two sets of books (one in the CRM and a truer one in a private spreadsheet), clinging to deals the rep privately knows are dead, and relying on fuzzy definitions. It also describes a company whose 10-factor deal-health score, rated by the sales team, was far less accurate than a simple velocity index that counted the days a deal had been pending and compared them with past wins and losses. A day is a day, whoever measures it.
Turn that into written rules everyone knows:
- No deal without a value, an expected close date, an owner and a linked contact.
- Every deal has a dated next step. Without one it is a wish, not a deal.
- A close date in the past triggers an update now: a new date with a stated reason, or close the deal as lost.
- Watch time in stage: a deal past twice its stage's typical duration needs a decision at the next review.
- A loss reason is mandatory: lost deals usually outnumber won ones, and without reasons you learn nothing from them.
- No stage skipping on entry: a deal that appears as won without passing through the stages means the CRM is a record of history, not a management tool.
A suggested routine: twenty minutes on the last working day of the week for each rep to update next steps and close dates and to close what is dead, so the first review of the new week starts from clean data.
Pipeline reviews that coach rather than inspect
Back to the Vantage Point survey we started with: it found that companies spending at least three hours a month managing each rep's pipeline saw 11% greater revenue growth than those spending less. It also warned that much of that time is wasted on forecasting: if the conversation is only about close dates, probabilities and deal sizes, you are forecasting. Managing the pipeline means helping the rep build a plan to move deals forward.
A practical format for a weekly one-to-one of 30 to 45 minutes:
New deals (5 minutes)
Does every deal added this week meet the first stage's criterion?
Deals that moved (5 minutes)
What did the buyer do to justify each move?
Stalled deals (20 minutes)
This is where coaching happens. What is blocking the deal, who have we not reached yet, and which step would break the deadlock? Or is it time to close it as lost?
Top three deals (10 minutes)
A detailed plan for each: stakeholders, risks and a realistic close date.
Commitments (5 minutes)
The rep leaves with dated next steps that open the following meeting.
Add a monthly team review focused on metrics and trends, and a quarterly calibration of probabilities and stage criteria. The same research found that 61% of executives admitted their sales managers were not adequately trained in pipeline management, and that companies which had trained them grew revenue 9% faster.
Metrics worth tracking
| Metric | How to calculate it | What it tells you |
|---|---|---|
| Pipeline value | Sum of open deal values | The size of the opportunity, not what will actually close |
| Weighted value | Sum of (value × stage probability) | A first estimate of revenue the pipeline should produce |
| Win rate | Won deals ÷ decided deals (won plus lost) | Qualification and selling quality; track it by count and by value |
| Average deal size | Won revenue ÷ number of won deals | Whether deals are trending larger or smaller |
| Sales-cycle length | Average days from deal creation to win | How fast opportunities turn into revenue |
| Stage conversion | Deals that moved to the next stage ÷ deals that entered the stage | Exactly where the pipeline leaks |
| Coverage ratio | Open pipeline value ÷ quota still to close in the period | Whether there is enough pipeline to hit the target |
| Days in stage | A deal's age in its current stage against the typical duration | Stalling deals, before they die |
Coverage needs calibrating. If you win roughly a quarter of the value entering your pipeline, you need open pipeline of about four times the remaining quota. Do not copy a fixed ratio from elsewhere; derive it from your own win rate.
Sales velocity combines four metrics in one number: (opportunities × win rate × average deal size) ÷ sales-cycle length in days. For example, 40 opportunities × 25% × SAR 60,000 ÷ 50 days = SAR 12,000 per day. Improving any one factor raises the result, which helps you decide where to focus: more opportunities, better qualification, bigger deals or a shorter cycle.
Common problems and their fixes
| Symptom | Likely cause | Fix |
|---|---|---|
| A huge pipeline, but revenue does not arrive | Old deals nobody is willing to close | Review every deal past twice its typical duration and close what is dead |
| Most deals pile up at the proposal stage | Proposals go out before requirements are confirmed, or are never chased | A stricter entry criterion and a mandatory follow-up task on every proposal |
| The forecast misses every month | Uncalibrated probabilities and optimistic close dates | Quarterly calibration and a rule for updating past close dates |
| Deals jump straight to won | The CRM is updated after closing, not during the sale | Run the weekly meeting from the pipeline view; what is not in it is not discussed |
| One rep's win rate looks suspiciously high | They only log deals they feel sure about | Compare how many deals they create with their peers |
| Almost every loss reason is price | An easy default picked without thought | A specific reason list and a monthly review of a sample of lost deals |
Putting it into practice in Naffes CRM
In Naffes CRM, many of these rules become settings the system enforces rather than instructions on paper:
- Stages with probabilities and durations: every stage is named in both Arabic and English and holds a win probability, from which weighted value is calculated, plus an optional typical duration in days. Run separate pipelines for new business and renewals, and limit who can see each one to chosen teams or users.
- Stalled-deal detection: once a deal outstays its stage's typical duration it is flagged Watch, then Stuck at twice the duration and Frozen at three times. These are default multiples an admin can change, and the Stuck quick filter gathers the flagged deals. Stages with no duration are never flagged, so fill those in first.
- Won and lost discipline: Naffes refuses to mark a deal won if its amount is zero or no contact or company is attached, and asks for a loss reason unless an admin makes it optional. Reps can also be restricted to a predefined list of reasons.
- The review numbers in view: a panel next to the deals list shows open and weighted value, this month's wins, win rate and average cycle length, plus at-risk and stuck deals; clicking either of the last two filters the list to those deals.
- Forecast categories and quotas (Pro plan): each open deal is placed in Pipeline, Best Case or Commit automatically by stage position. Only admins can override a category, with a reason, so reps argue their case in the review and the manager records the call. The Forecast page compares the team quota with each category and ranks reps by attainment. Neither is included in the Free or Starter plans.
- Kanban board: with a single pipeline selected, deals appear as cards on a Kanban board, and you can drag a card to its new stage during the review.
See deal management, forecasting and quotas and dashboards for detail. If you are still comparing systems, start with our guide to choosing a CRM, or step back to what CRM is.
Questions
Questions 5
How many stages does a sales pipeline need?
Five to seven suits most teams. The count matters less than the definitions: every stage needs a verifiable entry criterion, and win probabilities should differ meaningfully from one stage to the next; if two stages carry nearly the same odds, merge them.
What is the difference between a sales pipeline and a sales funnel?
The pipeline shows today's open deals and where each one sits, used to manage them day to day and week to week. The funnel looks at conversion rates between stages over a period, and is used to improve the process itself.
When should I close a stalled deal?
When it has sat in its stage for roughly twice the typical duration with no buyer engagement, and the rep cannot name a dated next step the buyer has agreed to. Closing it as lost with a clear reason beats letting it inflate the numbers, and a new deal can be opened if interest returns.
Who sets the win probability, the rep or the stage?
Set it at stage level and calibrate it from history, then let the rep express personal judgement through a separate forecast category. That keeps weighted value comparable across reps.
How often should the pipeline be reviewed?
Weekly with each rep, monthly as a team, and quarterly to recalibrate probabilities and stage criteria.