How many stages should a sales pipeline have?

Most pipeline reviews spend the first ten minutes arguing about stages instead of deals. Teams disagree on whether a proposal counts as a stage or a task, whether “qualified” means interest or budget, and whether “negotiation” starts before or after legal gets involved. The fix is to stop negotiating the funnel and start auditing it against reality: every stage should end with evidence a customer could verify, and the whole funnel should fit on a slide.

The answer is four to seven

A pipeline that fits in a single row on a slide usually has four to seven stages. Fewer than four and the funnel is too coarse to forecast; more than seven and the team spends more time debating which stage a deal is in than moving it forward. A study of 140 B2B sales teams found that those using five to six stages consistently hit their forecast within 10%, while teams with eight or more stages missed by 22% on average.

The exact count matters less than the clarity of each handoff. Every stage should have one question a customer could answer: “Have we agreed this problem is worth solving?” “Have we agreed the budget and timeline?” “Have we agreed on scope and price?”

Stages are exit criteria, not hope

The most common pipeline disease is “happy ears”: a stage added to capture a feeling rather than a fact. “Interested” is a feeling; “confirmed budget of at least $X by date Y” is a fact. Stages that exist only to keep hope alive in losing deals are the ones that inflate the forecast.

A clean B2B set looks like this:

• Lead — a real person with a real problem, confirmed by a first call within 48 hours of capture.
• Qualified — budget, authority, need, and timeline all confirmed. No exceptions.
• Proposal — a written scope signed off by the buyer’s process owner.
• Negotiation — commercial terms agreed, legal review in flight, no red lines remaining.
• Won or Lost — signed contract or a recorded reason for loss.

That is five stages, and each one is disputable only by facts, not by optimism.

Aging deals and the history trail

A stage is a snapshot; the history of stages is the diagnosis. A deal that sat in “Qualified” for 35 days is sending a signal — the problem may not be urgent enough, or the competition is stronger, or the handoff from marketing was incomplete. A pipeline with no stage history can hide those signals indefinitely.

The hygiene rules: review deals older than 30 days every week, and before any forecast meeting, audit the last stage change for each deal. If the owner cannot state the date, deal, and evidence of the last move, the deal is in the wrong stage.

When the pipeline is wrong, not the rep

Reps hit their quotas in bloated pipelines by over-promising on stage, and they look ineffective in undersized ones by being too conservative to call a deal qualified. The fix is not coaching on confidence but tightening the stage definitions until the forecast stabilizes. A healthy pipeline board should be able to predict quarter-end revenue within 15% two weeks before it closes.

In Atur, the CRM pipeline board keeps a full stage history for every deal, so the board shows not just where a deal sits but how it got there and how long it waited. Because feedback from the support portal links to the same contact record, a deal that carried an open ticket last week gets the honest look it needs in the review. Read how to close the customer feedback loop to see why that history matters beyond sales, and visit the CRM page for how the pipeline board and contact records fit together.