Most forecasts slip because stage definitions are vague and deals drift between stages invisibly. Here's how to build stage gates that force real decisions.
Your forecast is off by 20% because your pipeline doesn't have stage gates—it has stage suggestions. Deals sit in "Discovery" for three weeks with no movement, you have no signal they're stalled until deal review, and by then the quarter is half over.
Stage gates work because they make movement visible and force decisions. A gate is a non-negotiable set of criteria that must be true before a deal can progress. When you enforce them, you stop deals from hiding in middle stages and you catch stalls early enough to act on them.
A stage gate has three parts: entry criteria (what must be true to enter), a specific action during the stage, and exit criteria (what must be true to leave). The exit criteria are what most teams get wrong—they're vague ("we're moving forward") or they don't exist.
Real exit criteria are concrete and tied to buyer behavior, not to your internal schedule. "We have a second meeting scheduled with the budget owner" is a gate. "The buyer seems interested" is not. When you write gates this way, a deal either meets them or it doesn't. No ambiguity. No hiding.
A forecast slips when deals move sideways instead of forward: they get stuck in Negotiation for five weeks, they drop back to Proposal mid-quarter, or they sit in "Advanced Conversations" until you're not sure they exist anymore. Stage gates stop this because each stage has a time box and an exit condition.
If a deal doesn't meet the exit criteria within a reasonable time window, it moves backward or out. This forces you and your team to disqualify, keep pushing, or pause the deal—all of which are better than letting it rot in your forecast.
Start with your current pipeline. Look at the stages you actually use: Prospecting, Qualified Lead, Discovery, Proposal, Negotiation, Close. For each one, ask:
Write these as statements of fact, not intentions. "Economic buyer is aware of the deal" not "we'll loop in the economic buyer." "Decision criteria documented in writing" not "we understand their needs."
Then, for each stage, set a time box. Discovery might be two to three weeks. Proposal might be one week. If a deal hasn't met exit criteria in the time box, you make a decision: advance with more aggressiveness, pause it, or disqualify it.
Before a deal enters your pipeline, it should clear a gate. This is where many teams fail—they let deals in that shouldn't be there, and they show up in your forecast as pipeline when they're really just noise.
A qualification gate might require:
Deals that clear this gate go into your pipeline. Deals that don't get a follow-up calendar hold but don't clog your forecast. This discipline alone improves forecast accuracy because your pipeline only contains deals that could actually close.
When you have real stage gates, deal review changes. Instead of asking "where are you with that deal," you ask "does this deal meet exit criteria for Discovery?" The answer is yes, no, or we need to do X. This is faster, more honest, and it surfaces exactly where a rep is stuck or where a deal is slowing.
A rep who can't answer whether a deal meets exit criteria probably hasn't been paying attention to it. That's coaching signal. A deal that's been in a stage for two weeks past the time box is a risk signal. These conversations move deals, not just update dates.
Without stage gates, your pipeline becomes a filing cabinet. Deals get added, they stay wherever they land, and they disappear only when they close or you clean up at year-end. Reps don't know when to push; managers don't know what to coach on. Forecasts slide. Velocity drops.
With stage gates, the pipeline becomes a system. Every deal has a location and a deadline. Every location has work that must happen. Every deadline forces a decision. Your forecast becomes predictable because it's based on what deals have actually done, not what you hope they'll do.
A pipeline stage is just a location—Discovery, Proposal, Close. A stage gate is a set of entry, exit, and action criteria that must be met before a deal can advance. Stages without gates are just folders; gates make stages into decision points.
Write exit criteria as observable facts you can verify: 'stakeholder agreed to attend proposal meeting,' 'budget approved in writing,' 'decision made.' If you're unsure whether something is true, the criteria isn't specific enough. Vague criteria like 'moving forward' don't work.
You have three choices: increase activity to push the deal forward, pause it and reschedule for later, or disqualify it. The key is making an active choice rather than letting it sit. This keeps your forecast honest and your team focused on winnable deals.
Yes. Build separate gate sequences for different deal types or deal sizes—a 10K deal moves faster than a 250K deal. The structure stays the same; the time boxes and criteria shift based on what you actually observe in your closed deals.
Once a week, minimum. Weekly pipeline reviews catch drift before it becomes a forecast miss. You don't need long reviews—five minutes per deal, focused on whether it's meeting criteria or whether you need to intervene.
Part of our guide to MEDDPICC.
Repwing listens to your discovery calls and puts the next question on your phone while you are still in the conversation. Fourteen days free, no card.
Start free trial