.webp)
.gif)
The majority of GTM systems I diagnose have the same structural problem: pipeline stages that were named but never defined. Marketing qualified leads flow to Sales. Deals move from Discovery to Proposal. Opportunities are marked Closed Won. But ask what exactly must be true for a deal to advance between those stages, and the answer is a description, not a criterion.
A description is not a definition. And an undefined gate is not a gate. It is a gap.
Revenue Operations (RevOps) — the function responsible for aligning Marketing, Sales, and Customer Success under a shared operational framework — depends entirely on the quality of the definitions at each stage. A process layer built on vague criteria produces polluted data. Polluted data produces inaccurate forecasts. Inaccurate forecasts produce missed numbers. Every time, at scale.
This article explains the three things every pipeline stage must have, the two gates where most revenue teams quietly lose control, and how to know whether your current stage design would survive a governance audit.
Every stage in a B2B sales process — whether you run a PLG motion, an enterprise direct sales model, or a hybrid — requires exactly three defined components. Without all three, the stage is a label, not a system.
Expected behaviour defines what the sales rep or SDR must do while a deal is in this stage. It includes the time-in-stage benchmark (how long should a deal normally sit here before advancing or stalling), the conversion rate target for this stage, and the minimum activity frequency by segment.
In enterprise segments, contact frequency must be specified precisely: a meaningful touchpoint every four weeks is a structural rule, not a preference. When contact frequency is not defined by segment, each rep makes their own judgment — and what you end up with is not a process, but 20 parallel interpretations of one.
Activity frequency standards should live in the CRM. They should fire automatically as flags, not as reminders to managers who then have to follow up manually. The moment a manager must personally check whether reps are following a process, the process has already failed.
Qualification criteria define what must be confirmed as true for a deal to remain in this stage. The operative word is confirmed. Not suspected. Not assumed. Confirmed with hard data.
Binary qualification is non-negotiable. If a criterion requires a sales rep to exercise judgment — “the prospect seems interested,” “the budget feels right,” “the decision-maker is engaged” — it is not a criterion. It is an opinion. Opinions at the qualification layer mean that your SQL count is not a count of qualified leads. It is a count of optimistic assessments.
The rule we apply across our Cremanski engagements is direct: if an SDR needs to make a judgment call to apply this criterion, that criterion is not ready. It needs to be reworked into a binary, data-checkable condition.
Exit criteria define the exact conditions that must be satisfied before a deal advances to the next stage. Not conditions that should be met. Not conditions that are usually met. Conditions that must be verified before advancement is permitted.
Exit criteria are where quality enters the pipeline. They are also where most sales teams resist most strongly — because enforced exit criteria expose the difference between a healthy pipeline and an optimistic one. That visibility is uncomfortable. It is also essential.
No senior override. No manager exception. If exit criteria are subject to negotiation, they are not exit criteria. The moment one exception is made, the message sent to the team is that the criteria are aspirational. And an aspirational criterion is functionally the same as no criterion.
Within the pipeline, three moments carry disproportionate weight: MQL, SQL, and Closed Won. Each represents a handoff between functions. Each handoff is either a quality checkpoint or a quality gap.
The Marketing Qualified Lead definition marks the boundary of Marketing’s output accountability. It must be fully defined per segment. Hard criteria only — engagement scores combined with firmographic thresholds, not either in isolation.
Soft scoring models that rely on “lead score above X” without anchoring to explicit activity and firmographic data produce MQLs that are statistically probable but individually unreliable. The SDR team receives leads. The conversion data looks fine on average. The variance underneath that average is where the pipeline quality problem is hiding.
The Sales Qualified Lead gate is where the costliest quality failures occur. An SQL that doesn’t actually meet binary qualification criteria costs an Account Executive time, disrupts forecasting, and pollutes the conversion denominator that your pipeline coverage ratio depends on.
In the case referenced earlier — 38% of pipeline with no buying evidence — every one of those deals had been marked SQL. The gate existed. It was not held. The forecast was structurally impossible to make from the moment those deals entered the pipeline.
Closed Won is the output of everything upstream. If the MQL definition was unclear, if the SQL gate was not held, if the exit criteria were overridden at the deal review — the contamination compounds. A pipeline with compromised qualification at the top cannot produce a reliable forecast at the bottom.
A stage design audit does not require external consultants. It requires honest answers to four questions applied to each pipeline stage.
One honest run of this audit across a ten-stage pipeline typically surfaces between three and six structurally undefined stages. That is not a failure of the team. It is a reflection of how most pipeline processes are built: iteratively, under pressure, without the time to define what each stage actually means.
The fix is not a training programme. It is a design session, followed by CRM implementation, followed by enforcement.
Qualification criteria define what must be true for a deal to be in a given stage. Exit criteria define what must be true for a deal to advance to the next stage. Both must be binary. A deal can meet entry criteria but not yet meet the conditions required to move forward — for example, confirmed budget (qualification) but no confirmed decision-making authority (exit criterion for advancing to proposal stage).
Between five and eight stages covers most B2B SaaS motions effectively. Fewer than five usually means exit criteria are compressed into vague definitions. More than eight usually means stages are tracking internal activities rather than buyer milestones. The right number is the one where each stage represents a distinct, verifiable change in buyer status.
The stage names can be shared, but the definitions must be segment-specific. Time-in-stage benchmarks, contact frequency standards, and conversion targets differ materially between enterprise and SMB. A single pipeline with undifferentiated benchmarks produces averages that are meaningful for neither segment.
Forecast accuracy degrades in proportion to the share of unqualified deals in the pipeline. In one Cremanski engagement, 38% of pipeline carried no buying evidence — all marked SQL. The forecast built on that pipeline was structurally impossible to achieve. After enforcing binary SQL criteria, forecast accuracy moved from 61% to 94% within one quarter.
The response is structural, not interpersonal. Exit criteria apply to deals, not to people. When the CRM does not permit advancement without criteria being met, enforcement becomes a property of the tool, not a leadership behaviour. Resistance decreases significantly when it is no longer directed at a person.
Presenting our distinguished clientele! We collaborate closely with visionary B2B tech and software companies, intricately shaping their comprehensive Revenue Architecture. Take a look at who we have already served.
Explore our captivating customer success
stories here.
You have questions? Our Founder and Managing
Partner Michael is looking forward to hearing from
you.
