Five to seven stages is the right range for most B2B SaaS pipelines
The number of stages should match the number of distinct buyer decisions, not the number of internal tasks your team completes. Each stage boundary should mark a moment when something changes in the buyer's commitment: they agreed to evaluate, they completed technical review, legal is now involved. Tasks your team performs within that window belong in fields, not in stage names.For most mid-market and enterprise SaaS motions, five to seven stages cover that range cleanly. A common skeleton:
| Stage | What changed for the buyer |
|---|---|
| Qualified | Rep confirmed fit against ICP criteria |
| Discovery | Buyer shared business problem and confirmed budget exists |
| Evaluation | Active technical or legal review underway |
| Proposal | Written terms delivered and under consideration |
| Negotiation | Buyer is negotiating specific terms |
| Closed Won / Lost | Decision made |
The two failure modes: over-staging and under-staging
Over-staging happens when teams add stages to model internal workflows rather than buyer milestones. "Demo Scheduled," "Demo Completed," and "Demo Follow-up Sent" are tasks. Collapsing them into one stage, "Demo," keeps the pipeline readable without losing information, since the CRM activity log captures the tasks.The cost: stage conversion rates lose meaning because each micro-stage has a high pass-through rate that obscures real attrition. Reps also start skipping updates when updates feel pointless.
Under-staging happens when a pipeline skips genuinely important buyer decisions. The classic gap is the jump from first meeting to proposal, with no qualification or discovery stage in between. When deals stall or go dark, you cannot diagnose whether qualification is weak or whether the deal was lost at discovery. You are flying without instruments.What the stage count does to your forecast
Stage count directly affects how much confidence you can assign to a weighted pipeline. A pipeline with three stages forces you to apply a single probability weight to a wide band of deal maturity. A five-to-seven stage pipeline lets you assign weights that correspond to measurable buyer behavior at each boundary, which tightens forecast variance.
If you are currently getting large swings between your weighted pipeline number and actual close rates, stage structure is one of the first places to look.
Where to go from here
Once you have the right stage count, the diagnostic work shifts to measuring stage conversion rate at each boundary and addressing pipeline hygiene to ensure the stage data you are seeing actually reflects where deals stand. A well-structured pipeline with clean data is the foundation for reliable forecasting. More stages without clean data just gives you more places for bad information to hide.
Frequently Asked Questions
How many stages should a B2B SaaS pipeline have?
Five to seven stages cover most enterprise and mid-market motions well. Fewer stages make it impossible to spot where deals stall. More stages create data-entry overhead without adding forecast precision.
What does over-staging a pipeline cost you?
Over-staging forces reps to move deals through micro-steps that do not correspond to real buyer behavior. Stage conversion data becomes noisy, rep adoption drops, and pipeline hygiene degrades. You end up with a longer list of stages and less reliable signal in any of them.
What does under-staging a pipeline cost you?
Under-staging collapses large spans of the buying journey into a single stage, hiding the actual bottleneck. If deals jump from first meeting directly to proposal, you cannot see whether the qualification step is failing or whether the technical review is the true drag on cycle length.
Put these metrics to work
ORM builds custom revenue forecast models that turn concepts like how many pipeline stages should you have? into prescriptive action for your team.
Schedule a Demo