Five to seven stages works for most B2B SaaS pipelines, and the count matters less than the reason behind it. A stage earns its place by changing what you know about a deal. If moving a deal from stage three to stage four tells you nothing new about whether it will close, you have two labels for one state.
The two tests a stage has to pass
The first test is discrimination. Compare the eventual win rate of deals sitting in each stage. If deals in evaluation and deals in proposal close at the same rate, the boundary between them carries no information and the two should be one stage with clearer stage exit criteria.
The second test is sample size. A team closing 200 deals a year, reported across three segments and nine stages, produces cells with a handful of deals in each. Conversion rates computed from those cells swing wildly quarter to quarter, and every swing gets explained as a trend. Fewer stages give you cells large enough to read.
Why extra stages make forecasts worse
Each additional stage adds an update the rep has to make for the record to stay accurate. Compliance drops as the count rises, and reps start batching edits at the end of the week or the end of the quarter. Once that happens, stage position reports what the rep decided to type, not what the buyer did.
The stale-record problem compounds it. ORM sees more than 10% of pipeline sitting untouched for 12 months at a typical customer. More stages means more places for a dead deal to sit and look plausible, since a deal parked in one of nine stages draws less attention than one parked in one of five.
Add a field instead of a stage
Most requests for a new stage are really requests for a new attribute. Teams want to know whether security review has started, whether procurement is engaged, or whether the champion has an approver. Those are fields on the opportunity, and they can be reported, filtered, and required without splitting the stage sequence.
Fields also survive process changes. Renaming a stage forces you to rebuild historical conversion baselines. Adding a field leaves the sales pipeline stages sequence intact and keeps your history comparable.
When more than seven is correct
Long enterprise cycles sometimes justify eight or nine. The test is whether each extra step has a separate owner, separate exit criteria, and a measurably different conversion rate from the step before it. A procurement gate run by a different team, against different evidence, with a different pass rate, is a real stage. A step added so a dashboard looks more detailed is overhead that shows up later as noise in forecast accuracy and in time-in-stage averages computed from too few deals.
Frequently Asked Questions
How many stages should a sales pipeline have?
Five to seven is a reasonable starting range. The number matters less than the two tests each stage has to pass: crossing it changes the probability of closing, and enough deals pass through it to compute a stable conversion rate for each segment you report on.
What happens if you add too many stages?
Update compliance falls, reps batch their edits, and stage position starts describing intent rather than evidence. Stage-weighted forecasting then spreads probability across steps that carry no information, which produces a confident number built on distinctions the data cannot support.
Is four stages too few?
Four works for short transactional cycles where a deal moves from qualified to closed in a few weeks. It stops working when procurement, security review, and legal are separate gates run by different people, because a single late stage hides which of those steps a deal is stuck in.
Should different segments use different stage counts?
Use one stage set and let segments differ in dwell time and conversion. Separate stage sets per segment split your history into groups too small to read and make cross-segment pipeline reporting impossible without a translation layer nobody maintains.
Put these metrics to work
ORM builds custom revenue forecast models that turn concepts like number of pipeline stages into prescriptive action for your team.
Schedule a Demo