Sales Pipeline Stages

Design pipeline stages that reflect buyer progress and produce a forecast your team can trust.

Sales pipeline stages describe how an opportunity moves from early qualification to a decision. Clear stages help a team decide what to do next and make reports comparable across owners.

The best pipeline is not the one with the most detail. It is the one where each stage has a visible event that proves the opportunity belongs there.

On this page

What is a pipeline stage?

A stage is a named point in the buyer's decision process. It should describe evidence about the opportunity, not an activity somebody hopes to complete.

Good stage: Discovery completed.

Weak stage: Follow up.

“Discovery completed” has a test: the conversation happened and the required questions were answered. “Follow up” could mean an email, a call, a reminder, or no progress at all.

A practical pipeline example

A service business can begin with six stages:

StageEvidence required
New opportunityA potential engagement has been identified
QualifiedNeed, fit, timing, and decision path have been checked
Discovery completedDiscovery happened and requirements were recorded
Proposal sentThe prospect received a priced proposal
Decision pendingThe proposal is being reviewed by the decision group
Won or lostThe prospect made a final decision

Your exact labels may differ. Keep the evidence behind them explicit.

For an agency retainer, Proposal sent may require scope, monthly fee, and start date. For a short audit, a single quote may be enough. The stage means the same kind of progress, while the required data reflects the service.

Define entry and exit criteria

For each stage, write:

  1. What must be true before an opportunity enters?
  2. What information must be recorded while it is there?
  3. What event moves it forward?
  4. What event closes or disqualifies it?

Example for Qualified:

  • Entry: the opportunity matches the target market and has a defined need.
  • Required data: service interest, estimated value, decision contact, expected timing.
  • Exit forward: discovery is booked and confirmed.
  • Exit closed: no supported need, timing, or commercial fit.

These rules reduce interpretation. A manager can review the pipeline without learning each seller's personal definition of “qualified.”

Choose stage probabilities

A stage probability estimates how often opportunities in that stage eventually close. Do not assign percentages because they look reasonable. Start with rough values, then replace them with historical conversion rates when enough data exists.

Weighted pipeline value is:

$$ \text{Weighted value} = \text{Opportunity value} \times \text{Stage probability} $$

A €20,000 opportunity at a 40% stage contributes €8,000 to the weighted pipeline. This is not a prediction for that individual deal. It is an aggregate estimate that becomes useful across many opportunities.

Review probabilities periodically. If 62 of 100 qualified opportunities closed over a stable period, a 20% qualified-stage probability understates the observed result.

Handle stalled opportunities

An opportunity is stalled when it remains in a stage longer than the normal buying process without a credible next action.

Track expected stage duration alongside the stage itself:

StageExample review threshold
New opportunityNo owner or response after one business day
QualifiedNo discovery date after seven days
Proposal sentNo response after the agreed review period
Decision pendingNo dated decision event or next step

The threshold should trigger review, not silently move the opportunity. Time alone does not prove that a buyer progressed or declined.

Create a saved view for opportunities with no next action and another for those exceeding stage duration. Review both in the weekly pipeline meeting.

When to use multiple pipelines

Use separate pipelines when the buying processes have different stages, owners, or reporting needs.

A marketing agency might separate:

  • New-business retainers
  • One-time strategy projects
  • Existing-client expansions
  • Partnerships or referrals

Do not create separate pipelines merely to report by service. A service field may provide the same reporting without duplicating stage definitions.

Pipeline review checklist

A useful pipeline review asks for evidence and decisions:

  • Does every open opportunity have an owner?
  • Is the current stage supported by a completed event?
  • Is there a dated next action?
  • Is the value based on a credible scope?
  • Is the expected close date still realistic?
  • Has the deal exceeded normal stage duration?
  • Should the opportunity advance, remain, or close?

Avoid spending the meeting reading every field aloud. Focus on changes, risks, blocked decisions, and help the owner needs.

Frequently asked questions

How many sales pipeline stages should I use?

Use the smallest number that captures meaningful changes in the buying process. Five to seven stages often provide enough distinction without turning minor activities into stages.

Should “follow-up” be a pipeline stage?

No. Follow-up is an action that can happen within several stages. Keep the opportunity in the stage that reflects buyer progress and record the follow-up as its next action.

Should won and lost be separate stages?

Yes. Both close the active sales process, but they represent different outcomes and should be reported separately. Record a loss reason when it supports future changes.

Can different services use different pipelines?

Yes, when their buying processes materially differ. Keep one pipeline when only the service name changes and the decision path stays the same.

How often should pipeline stages be reviewed?

Review active opportunities weekly and review the stage model itself quarterly or when the sales process changes. The lead management guide explains how the pipeline fits into the broader process.

Cleo • © 2026