<img src="https://secure.leadforensics.com/804658.png" style="display:none;">

Sales Pipeline Stages That Work

by Mentor Group

Most pipeline management problems aren’t really “pipeline” problems.

They’re stage definition problems.

When stages are vague, sellers interpret them differently, managers can’t coach consistently, and the CRM becomes a collection of opinions. That’s when you see stage inflation, late-stage slippage, and forecasts that look confident until they aren’t.

This guide shows you how to build pipeline stages that work in the real world: short, observable, buyer-anchored criteria that your team will actually use.

What makes a stage “work” in practice

A stage works when it does three things:

  • Represents real buyer progress (not seller optimism)
  • Creates a shared language for coaching (so managers can reinforce behaviours)
  • Improves forecast credibility (because stage placement is evidence-based)

If a stage can’t be validated with evidence, it’s a label — not a management tool.

 

The core rule: observable evidence beats opinion

A useful stage criterion must be observable.

That means it can be proven by one of these:

  • A buyer-owned action (a meeting booked, a document shared, a decision step confirmed)
  • A dated commitment (timeline agreed, evaluation plan confirmed)
  • Recorded evidence in the CRM (notes, stakeholders mapped, risks documented)

Avoid criteria that rely on judgement alone:

  • “Buyer is interested”
  • “Strong relationship”
  • “Good fit”

Those may be true — but they’re not evidence.

Entry vs exit criteria (and why you need both)

Stage discipline improves dramatically when you separate:

Entry criteria

What must be true before the opportunity is allowed to enter the stage.

Exit criteria

What must be true before the opportunity can progress to the next stage.

Why this matters:

  • Entry criteria stop premature deals flooding a stage.
  • Exit criteria stop “stage inflation” that hides stalled deals.

The five-item rule (keep it usable)

If your criteria list is long, it won’t be used.

A practical standard:

  • No more than five entry criteria
  • No more than five exit criteria

If you can’t keep it short, the criteria are usually too vague.

 

How to write evidence-based criteria (a step-by-step method)

You can do this in a 60–90 minute working session with managers and reps.

 

Step 1: Start with the buyer’s decision journey (not your internal process)

Ask:

  • What does the buyer need to decide at this stage?
  • What reduces risk for them?
  • What proof would a rational buyer want before progressing?

Your stage definitions should mirror the buyer’s decision journey.

 

Step 2: Define the “minimum evidence” you want to see in every deal

Use a universal evidence baseline you can apply across stages:

  • Buyer outcome is clear (in buyer language)
  • Impact is quantified (or there’s an agreed plan to quantify)
  • Decision process is known (or actively mapped)
  • Stakeholders are mapped (at least champion + route to signature)
  • Next step is mutual and dated
  • Top risks are named

Then add stage-specific proof points (next step).

 

Step 3: Add stage-specific proof points (2–3 that really matter)

Stages differ mainly in what kind of proof is required.

Examples:

Early stage (Discovery / Qualification)

  • Buyer problem and impact are captured in writing
  • Stakeholders and decision roles are partially mapped
  • A next-step meeting is booked to progress discovery

Mid stage (Evaluation / Solution Fit)

  • Success criteria are agreed (what “good” looks like)
  • Evaluation plan or mutual action plan is agreed
  • Technical/security requirements are identified and sequenced

Late stage (Commercials / Procurement / Contract)

  • Procurement pathway and stakeholders are known
  • Commercial review is scheduled with buyer owner
  • Legal/security steps are documented with dates and owners

Step 4: Decide where the proof lives (remove ambiguity)

For each criterion, define: where do we record proof?

Examples:

  • Stakeholders mapped → contacts tagged with roles in CRM
  • Success criteria → captured in the deal note template
  • Mutual action plan → recorded in notes or attached plan
  • Next step → meeting logged with date/time and buyer owner

This is how you prevent endless debate in pipeline reviews.

 

Step 5: Create an “evidence note” template that matches the criteria

Criteria are only usable if reps can capture evidence quickly.

Use a consistent note format such as:

  • Buyer outcome (one sentence)
  • Evidence (3 bullets)
  • Risks (1–2 bullets)
  • Next mutual step (date, buyer owner)

This turns criteria into habit — and makes deals coachable.

 

Step 6: Operationalise the criteria (so people don’t ignore them)

Stage criteria fail when they live in a document and nowhere else.

Embed them into the operating rhythm:

  • Use them in weekly pipeline reviews (“Which criterion is not evidenced?”)
  • Use them in forecast reviews (“Which buyer commitment proves this?”)
  • Use them in deal coaching (“What’s missing to progress?”)

Managers make criteria real by coaching to them.

 

A practical stage framework you can adapt

Below is a simple pattern you can tailor to your stages without over-engineering.

 

Stage: Discovery / Qualification

Entry criteria (example):

  • Buyer problem is written in buyer language
  • Impact hypothesis exists (even if not fully quantified)
  • Next discovery step is booked (mutual and dated)

Exit criteria (example):

  • Impact is quantified (or buyer agrees how it will be quantified)
  • Stakeholders and decision roles are mapped at a basic level
  • Success criteria drafted and validated

Stage: Evaluation / Solution Fit

Entry criteria (example):

  • Success criteria agreed
  • Evaluation plan agreed (what will be tested, who is involved)
  • Technical requirements captured

Exit criteria (example):

  • Buyer confirms evaluation outcome and “go/no-go” step
  • Procurement and security steps identified with timeline
  • Commercial review meeting booked

Stage: Commercials / Contracting

Entry criteria (example):

  • Commercial route agreed (procurement/legal stakeholders known)
  • Buyer confirms timeline to decision
  • Mutual action plan includes contracting steps

Exit criteria (example):

  • Final decision meeting booked (or signature pathway confirmed)
  • Legal/security steps completed or scheduled
  • Risks actively reduced and documented

Use these patterns as a starting point, then tailor to your reality.

 

Common mistakes to avoid

  • Writing criteria that describe seller activity only
  • Using non-observable words (“strong”, “good”, “positive”)
  • Making criteria too long to remember
  • Changing criteria too often (people stop trusting them)
  • Enforcing criteria only at quarter-end (creates gaming)

How to know your stage criteria are working

Within 2–6 weeks, you should see:

  • Improved consistency across sellers
  • Cleaner next steps and stronger deal notes
  • Reduced stage ageing in congested stages
  • More credible close dates (less date dragging)
  • Improved conversion in the transitions you tightened

If you don’t see change, the criteria may be:

  • Too vague
  • Too hard to evidence quickly
  • Not being reinforced in weekly cadence

Summary FAQ

What are entry and exit criteria in a sales pipeline? Entry criteria define what must be true (with evidence) for a deal to enter a stage. Exit criteria define what must be true for it to leave the stage and progress.

Why do stages become inconsistent across reps? Because stages are often defined with vague language. Without observable proof requirements, each rep interprets stage labels differently.

How many criteria should each stage have? As a practical rule, keep entry criteria to five items or fewer and exit criteria to five items or fewer. If you need more, the criteria are usually too vague.

What’s the most important principle for stage criteria? Make criteria observable and buyer-anchored. If you can’t prove it with buyer evidence, it shouldn’t be a criterion.

How do stage criteria prevent pipeline inflation? They stop deals moving forward without evidence and prevent under-qualified opportunities flooding later stages.

Where should stage evidence be recorded? In a consistent place: CRM fields for stakeholders and dates, and a simple deal-note template for outcome, evidence, risks and next steps.

How do we make criteria stick? Embed them into weekly pipeline reviews and manager coaching prompts. Criteria become real when managers coach to them consistently.

 

Read our full guide on pipeline management best practices here.