GM! It’s going to be a great week!
Most pipeline stages are far too easy to advance.
A discovery call happened, so the deal moves to Discovery Complete. A demo happened, so it moves to Solution Fit. A proposal was sent, so it moves to Proposal. The rep did work, the CRM changed, and the forecast now assumes progress.
But buyer progress may not have changed at all.
The buyer may not have agreed there is a business problem worth solving. The economic buyer may not know the project exists. Legal may not have reviewed the contract path. Procurement may not have confirmed process. The internal champion may like the product but have no ability to move the account.
This is how healthy-looking pipeline becomes forecast risk.
The CRM records seller activity. The forecast interprets it as buyer commitment.
Those are not the same thing.
If you want fewer late-stage surprises, tighten stage control around buyer evidence, not rep effort.
Seller activity is not stage evidence
A sales stage should answer one question:
What has the buyer done or confirmed that makes this opportunity more real than it was last week?
That question changes how you inspect pipeline.
A demo is not evidence by itself. Evidence is the buyer connecting the demo to a specific operational pain, confirming who else needs to evaluate it, and agreeing on the next decision step.
A proposal is not evidence by itself. Evidence is the buyer confirming the commercial path, approval process, decision criteria, legal route, and timing constraints.
A champion update is not evidence by itself. Evidence is the champion introducing you to the people who own budget, risk, implementation, or final approval.
The rep can create activity. Only the buyer can create commitment.
That distinction should be visible in your stage definitions.
Use the buyer-evidence ladder
A simple way to rebuild stage discipline is to create a buyer-evidence ladder.
Each stage needs two things:
Seller action: what the rep usually does at this point
Buyer evidence: what must be confirmed before the opportunity advances
For example:
Stage: Discovery
Seller action: run discovery, identify pain, document current state.
Buyer evidence: the buyer confirms the business problem, why now matters, who is affected, and what happens if nothing changes.
Stage: Solution Fit
Seller action: present relevant use case, map product to pain, handle early objections.
Buyer evidence: the buyer confirms success criteria, required stakeholders, and the decision path for evaluating fit.
Stage: Business Case
Seller action: build ROI logic, scope requirements, align commercial value.
Buyer evidence: the buyer agrees on impact logic, priority relative to other projects, and who must approve the investment.
Stage: Proposal
Seller action: send pricing, contract terms, implementation outline.
Buyer evidence: the buyer confirms budget path, procurement route, legal process, approval sequence, and target signature timing.
Notice the pattern.
Seller action describes work completed. Buyer evidence describes risk reduced.
The second one is what should control stage movement.
Make stage exit criteria inspectable
Stage definitions usually don't fail because they're missing.
They fail because nobody can inspect them consistently.
“Confirmed business pain” sounds useful until every rep interprets it differently.
RevOps needs stage exit criteria that managers can inspect inside the CRM and pipeline review.
Weak exit criteria:
Strong discovery completed
Demo went well
Proposal sent
Champion is engaged
Verbal interest received
Better exit criteria:
Buyer named the business problem and consequence of inaction
Buyer identified who owns budget and implementation risk
Buyer confirmed decision criteria and evaluation timeline
Economic buyer has been contacted or the gap is logged as risk
Procurement/legal process is documented before proposal forecast moves up
Next step is buyer-confirmed with date, owner, and purpose
The goal is not to make reps fill out more fields.
The goal is to make stage confidence auditable.
If a manager cannot inspect why a deal advanced, the stage is probably decorative.
Separate progress, risk, and forecast category
One common failure mode is using stage as a proxy for everything.
Stage becomes progress, forecast confidence, manager sentiment, and rep optimism in one field. That creates dirty pipeline logic.
A deal can be in Proposal and still be high risk.
A deal can be in Business Case and be more forecastable than a later-stage deal if the buyer process is clearer.
A deal can have strong product fit and weak commercial path.
Separate the concepts:
Stage: where the buyer is in the buying process
Risk: what evidence is missing or weak
Forecast category: whether the deal belongs in commit, best case, pipeline, or omitted
Next inspection: what must be learned before confidence improves
This gives managers a cleaner review.
Instead of asking, “Why is this still in Proposal?” they can ask, “What buyer evidence is missing for this Proposal-stage deal to stay in best case?”
That question surfaces reality faster.
Use manager review to enforce stage control
Stage discipline will not hold if it is only a RevOps policy.
Managers have to enforce it in pipeline review.
The review should test stage evidence before deal strategy:
What stage is the opportunity in?
What buyer evidence supports that stage?
What evidence is missing?
Is the missing evidence acceptable risk or a stage problem?
What buyer action must happen before the deal advances again?
This is not bureaucracy. It is forecast hygiene.
A rep should not lose a deal because the CRM stage was strict. They should lose less time pretending a deal was further along than the buyer had earned.
When stage movement requires buyer evidence, the pipeline may look smaller for a week.
That is usually not a problem.
It means the forecast is getting closer to the truth.
Weekly action
Pick one stage that creates the most forecast surprises.
For many teams, it is Proposal or late Solution Fit.
Rewrite that stage with four fields:
Seller action completed
Buyer evidence required
Common missing evidence
Manager inspection question
Example:
Stage: Proposal
Seller action completed: pricing and terms shared.
Buyer evidence required: buyer has confirmed budget path, approval sequence, legal/procurement route, decision criteria, and target signature timing.
Common missing evidence: proposal sent to champion only; procurement unknown; economic buyer not engaged; next step is “review internally.”
Manager inspection question: “What buyer-confirmed process makes this proposal forecastable?”
Do this for one stage before rebuilding the whole process.
If you can make the riskiest stage more inspectable, forecast quality improves before you touch dashboards, automation, or reporting.
Pipeline control starts when stage movement stops rewarding activity and starts requiring evidence.
— Pipeline Playbook