How to set up sales pipeline stages that reflect how you actually sell

When you set up a new CRM, it usually comes with a default set of pipeline stages: Lead → Qualified → Proposal → Negotiation → Closed. They look sensible on a demo call. In practice, most teams find them useless within a month.

The problem isn't that those stages are wrong in the abstract. It's that they were designed for a generic sales process, not yours. And a pipeline that doesn't match how you actually sell will never get updated consistently, which means you'll never be able to trust it.

Why generic pipeline stages fail

Generic stages fail for a specific reason: they describe the seller's perspective, not the buyer's journey. "Proposal Sent" tells you what your rep did. It doesn't tell you where the buyer actually is in their decision process.

A prospect can receive your proposal and be completely unengaged. They can be in active evaluation without you having sent anything formal yet. The stage name matches the activity log, not the commercial reality.

Good pipeline stages describe buyer behaviour. They answer the question: what has this prospect done that tells us they're ready to move forward?

How many stages does a small team actually need

Four to six stages is the right range for most teams selling a single product or service with a sales cycle under 90 days. More than six creates ambiguity, reps start guessing which stage a deal belongs in. Fewer than four compresses too much and hides where deals are actually getting stuck.

The test for whether you have too many stages: if two of your stages could share a deal at the same time, merge them.

Designing stages around how your buyer moves

Start by mapping your last ten closed-won deals. At what points did the buyer's behaviour change? Where did momentum accelerate? Where did it stall? These inflection points are your natural stage boundaries.

For a typical B2B product with a three-to-eight-week sales cycle, a solid set of stages looks something like this:

1. Qualified, You've spoken to a real decision-maker, confirmed budget and timeline exist, and identified a specific problem they want to solve. No deal belongs here that hasn't had that conversation.
2. Discovery complete, You have a clear understanding of their requirements, decision criteria, and any competing options they're evaluating.
3. Proposal out, A concrete, customised proposal has been sent and acknowledged. Not just forwarded, they've confirmed receipt and agreed to a follow-up.
4. Negotiation, Pricing or contract terms are being actively discussed. The prospect has indicated they want to proceed, pending agreement on specifics.
5. Verbal close, They've said yes verbally. Paperwork is pending. This is a stage many teams skip, which causes closed-won forecasting to be unreliable.

Your stages may look different. The point is that every deal in Stage 3 should have actually had a proposal acknowledged, not just sent.

Setting clear entry and exit criteria

The most important design decision isn't what to call your stages, it's what's required to enter and exit each one. Without written criteria, reps will interpret stages differently, and your pipeline will be inconsistent.

For each stage, document two things: what must have happened (not what you plan to do next) to enter this stage, and what specific outcome moves the deal to the next one.

For example, a deal can only enter "Proposal out" when a customised proposal has been sent and the prospect has confirmed a date to discuss it. It exits when they've given feedback, positive or negative.

This sounds rigid. In practice it makes your pipeline much faster to review, because every deal in a stage is genuinely at that stage. No surprises.

Your pipeline board in Klooser lets you define custom stages and move deals with a single drag, the entry criteria live in your team's shared notes on each deal card.

How to review and adjust over time

Pipeline stages aren't permanent. Your product evolves, your market changes, and your sales process matures. Review your stages every quarter by looking at where deals stall most often.

If 60% of your deals get stuck in the same stage for more than three weeks, that's either a process problem (you're not doing the right things at that stage) or a stage design problem (the stage is too broad and contains two fundamentally different situations).

Split stages that contain multiples. Merge stages that flow automatically into each other. The goal is a pipeline where every deal moving through it is a signal you can act on, not just a record of past activity.

Pair good stage design with deal rotting alerts and a weekly pipeline review and you have the core of a pipeline management system that actually works.