1. The Situation
Every quarter, the same conversation happens in sales reviews: the pipeline looks healthy in week 4, starts wobbling in week 8, and collapses in week 11. Deals that were "90% likely to close" get pushed. Committed revenue disappears.
The CRM has thousands of data points. Stage names, probability percentages, close dates, next steps. The data is all there. And yet nobody saw it coming.
The problem isn't the data. The problem is what the stages actually measure.
2. The Usual Explanation
The instinctive response is rep accountability. Reps were too optimistic. They over-committed. They need to be more disciplined about forecasting.
So the organisation runs forecast accuracy reviews. Managers challenge reps harder. Everyone nods, the same deals go in, and the same collapse happens next quarter.
Rep accountability isn't the issue. The stage definitions are.
3. Why That Fails
In most CRMs, stage progression is defined by what the seller did, not what the buyer agreed to.
Stage 2: Demo completed. Stage 3: Proposal sent. Stage 4: Verbal commitment.
"Demo completed" is a seller action. It tells you nothing about whether the buyer moved toward a purchase decision. "Proposal sent" tells you nothing about whether the proposal has any internal support.
When stage advancement is based on seller activity, the pipeline becomes a log of what salespeople did — not a model of where buyers actually are. Those two things diverge sharply by late stage.
4. The Actual Constraint
The real constraint is the absence of buyer verification criteria at each stage gate. A stage should only advance when the buyer has done something — not the seller. Something that requires the buyer to invest their own time, credibility, or organisational capital.
- Did they introduce you to Finance or Procurement? Real signal.
- Did they share an internal document, budget code, or timeline? Real signal.
- Did they agree to a mutual action plan with their name on it? Real signal.
"They seemed enthusiastic on the call" is not a signal. It's seller optimism documented in a CRM field.
5. Consequences
When stage definitions are built on seller activity, three things happen consistently:
The pipeline looks bigger than it is. Late-stage deals stall — the rep has "done everything right" by the internal definition, but the deal has no real champion, no agreed timeline, no approved budget. And the wrong deals get the most attention — the most active rep with the most stage 3 deals looks like the strongest performer, even if none of those deals are real.
6. What Must Change
Rewrite stage definitions from scratch with one rule: every stage gate must require buyer evidence, not seller activity.
This is a two-hour workshop, not a six-month project. Get your best salespeople and sales leaders together and ask: "What does the buyer actually have to do or say for you to be confident a deal is real?"
Then enforce it. If a deal can't pass the buyer evidence test, it doesn't move. The pipeline number will compress. That's the point — what you see should reflect reality, not effort.
7. How GTM-360 Thinks About This
The single most common pipeline problem we see isn't rep skill, market conditions, or product gaps. It's stages designed to track effort instead of progress.
If your pipeline is consistently collapsing in the back half of the quarter, the stage definitions are the most likely culprit. A diagnostic will confirm it in a day.