How many stages does a good sales pipeline need?

Few questions divide sales teams as reliably as this one: how many stages should a sales pipeline have? Some swear by four lean steps, others maintain fourteen finely graded statuses with subcategories. Both believe they hold the one true answer. In reality there is no magic number, only one honest question: does your pipeline reflect how selling actually happens in your business, or does it reflect how some consulting PDF claims selling ought to happen?

What a stage actually has to deliver

A stage is not a label, it is a decision. It marks a point where something essential has changed in your relationship with the customer: a need is confirmed, a budget is in place, a decision-maker is at the table. When you move from one stage to the next, you should be able to clearly name what has changed and what needs to happen next.

This is where most overloaded pipelines fall apart. "First contact", "First meeting held" and "Follow-up meeting scheduled" are not three stages, they are three activities within the same stage. They inflate the structure without adding any new information. A good rule of thumb: if the transition between two stages doesn't depend on a condition but only on time passing, the two probably belong together.

The typical five to seven steps

For the vast majority of Swiss SMEs and startups, a pipeline with five to seven stages works excellently. A proven basic framework looks like this:

• Lead qualified: there is a recognisable need and a rough fit with what you offer.
• Need clarified: you understand the problem, the timeline and who is involved in the decision.
• Proposal created: a concrete solution with a price is on the table.
• Negotiation: terms, scope or timing are being discussed.
• Won or lost: the decision has been made and documented.

If you have a longer cycle, for example in software or machinery sales, it makes sense to add a stage like "Pilot" or "Proof of Concept". If you handle short, transactional deals, four steps are enough. What matters is not the number, but that every stage corresponds to a real moment in your sales process.

A pipeline is not a collection of drawers, it is a map for the next sensible action.

How to tell there are too many

You don't spot too many stages in a spreadsheet, you spot them in your team's behaviour. A few reliable warning signs:

1. Deals "stick" in a stage because no one knows exactly what moves them to the next one.
2. Two team members file the same deal differently, and both have good reasons.
3. Maintaining the pipeline feels like bureaucracy rather than orientation.
4. In your forecast, you argue about definitions instead of probabilities.

If three of these apply, your pipeline is too finely granulated. In that case, no extra field will help, only a decisive merge. Cut any stage you can't distinguish from the next one in a single sentence.

Sharpen rather than expand

The temptation to fight vagueness with more structure is strong. Usually the opposite is right. Instead of introducing a new "Proposal followed up" stage, define cleanly what "Proposal created" means and which activity comes next. Clarity comes from reduction, not from branching.

Stages are only half the battle

Even the best stage structure won't tell you which deal deserves your attention today. A lead in "Negotiation" may in fact be dead, while one in "Need clarified" is on the verge of closing. This is exactly where it gets interesting: it's not the position in the pipeline that counts, but the actual momentum behind it, meaning response times, the course of the conversation and the question of who last has the ball.

That's why at Advanzo we rely on a lean, customisable pipeline and complement it with AI-powered aids such as "deal scoring" and automatic conversation summaries. The structure stays simple while the assessment gets smarter in the background. That fits our stance of "remove complexity, not add it": a pipeline should make your work easier, not become yet another system that demands maintenance. So if you're wondering how many stages is the right number, the most honest answer is: as few as possible, as many as necessary, so that everyone on the team knows what to do next.