Define pipeline stages by real progress: A deal enters a stage when a customer or process event occurs, not personal optimism.; Each stage must have clear evidence like a dated proposal or customer response.; Two people reading the same deal should agree on its stage without needing salesperson insight.
Image: CRM Stack

Pipeline Design

Part of CRM sales pipelines

Defining pipeline stages from observable progress

Write stage entry rules based on observable sales progress, resolve awkward cases and check that colleagues classify deals consistently.

Define a pipeline stage by the event that puts a deal into it, not by how optimistic a salesperson feels. Two colleagues should read the same deal record and reach the same stage decision. The test is whether they can point to progress the customer or the agreed sales process has produced.

Pros and Cons of Using Observable Progress in Stages

Pros
Reduces subjectivity; two colleagues agree on stage placement
Cons
May require more upfront effort to define clear entry criteria

Start with decisions, then name stages

Trace several recent opportunities from first serious discussion to a won or lost outcome. Mark when the team’s work changed: a need was confirmed, a proposal was presented or a decision was communicated. Group moments that lead to the same next decision. Do not create a stage for every email, meeting or internal approval.

Write each candidate stage as a sentence: “A deal enters this stage when…” Then identify the evidence someone would expect to find. Evidence can be a customer response, a dated proposal or an approval recorded in the deal. The rule should be understandable without a salesperson’s private impression.

Candidate stagePossible entry evidenceQuestion that remains
Need confirmedCustomer has described the problem and agreed that it is worth examiningWhat solution fits?
Proposal presentedThe proposed scope has been given to the customerWhat changes or decision are needed?
Decision pendingCustomer has described how a decision will be madeWhat is the outcome?

These names illustrate the method, not a default sequence. A team whose customers buy directly after a quotation may need fewer distinctions. Another may need a separate stage when a formal tender is submitted, because that changes what the seller can do next.

Stage Entry Criteria and Evidence

Need Confirmed
Customer described problem and agreed it's worth examining
Proposal Presented
Proposed scope delivered to customer
Decision Pending
Customer explained how decision will be made

Write the awkward-case rule

For every stage, decide what to do when progress reverses or becomes uncertain. If a customer rejects a proposed scope but remains interested, the deal may return to an earlier stage or stay in the current stage with a revision due. The answer depends on the meaning the team gave the stage. Record the rule so a manager need not infer it from the board.

A customer pause is also a status question. If a credible purchase decision remains, keep the deal open with a reason and a review date. If no current decision path exists, apply the team’s agreed pause or closure rule rather than leaving it indefinitely in an early stage. A stalled deal is not evidence that a new sales milestone occurred.

Check whether two stages really differ

Show the draft definitions to people who handle ordinary sales and exceptions. Give them a few anonymised deal histories and ask where each deal belongs. When answers differ, inspect the rule: perhaps “qualified” means budget confirmed to one person and customer need confirmed to another. Rewrite the entry condition before adding a field or a new stage.

Keep the final list short enough that each stage changes a decision or hand-off. Microsoft says Dynamics 365 Sales uses opportunity stages in sales charts and dashboards, so inconsistent stage use can also make those views harder to interpret. Its documented stages and fields are product examples; they do not establish the right sequence for your business.

Put the definition into routine use

Publish a brief stage guide with the entry event, acceptable evidence and the next question for each stage. When a deal moves, its record should show why. Sample deals that have stayed in one stage for a long time and deals moved rapidly through several stages. Ask whether the stage reflects customer progress or simply a convenient place on the board.

Review the definitions when the sales process changes. Change a stage when it represents a different decision, not just to make a chart look tidier.

More from Pipeline Design