Pipeline software does not fix forecasting. Forecasts are wrong because stages mean different things to different people, close dates are guesses, and deals sit in the same stage for weeks without anyone noticing. A tool helps only after those three problems have an owner.
What pipeline software should do
- Enforce a small number of stages with exit criteria, not just labels
- Require a next step and a date on every open deal
- Show ageing: how long each deal has been in its current stage
- Produce a forecast by stage, owner, and close month
- Keep history when a deal moves backwards
Stage design that survives contact with reality
Five to seven stages is enough for most B2B sales. Each stage should be defined by evidence, not by optimism: “proposal sent” is evidence; “interested” is a feeling. Write the exit criteria down and keep them next to the pipeline in the tool.
| Stage | Exit criterion | Typical probability |
|---|---|---|
| Qualified | Budget and decision-maker confirmed | 10–20% |
| Discovery complete | Requirements documented and agreed | 25–35% |
| Proposal sent | Written proposal delivered and acknowledged | 40–50% |
| Negotiation | Commercial terms under discussion | 60–75% |
| Verbal yes | Buyer confirms intent to sign | 80–90% |
Why forecasts drift
Two habits cause most of the error. First, close dates are set to the end of the quarter rather than to the buyer’s procurement timeline. Second, stalled deals are not marked as stalled, so they keep their original probability while ageing. Fix both with two report filters: deals with no activity in 21 days, and deals whose close date has moved more than twice.
Tool categories and price
CRM-native pipelines (the board inside your CRM) cost nothing extra and are usually sufficient. Dedicated pipeline tools add forecasting, multi-team views, and inspection workflows; expect $25–$90 per user per month. Revenue intelligence platforms that record calls and score deals sit above that, often $100+ per user.
Hygiene rules worth enforcing
- No deal without a next step date
- Stage cannot advance without the exit criterion field filled
- Closed-lost requires a reason from a fixed list
- Weekly review of deals untouched for 14 days
FAQ
Do we need separate pipeline software if we have a CRM?
Usually not. The CRM’s board plus two saved reports covers most teams. Buy a dedicated tool when you need multi-team forecasting or inspection that the CRM cannot produce.
How many stages should we have?
Five to seven for most B2B cycles. More stages create administration; fewer hide the points where deals actually stall.
What is a healthy win rate?
It varies too much by industry to set a universal benchmark. Track your own trend quarter over quarter and by source rather than comparing to an external average.
How do we handle deals that go quiet?
Move them to a “stalled” stage with a reason and a re-contact date. Keeping them in an active stage inflates the forecast and hides the problem.