124 deals entered
34% convertedRevenue decision guide · Stage conversion
Sales-stage conversion without false precision
Measure stage conversion by person and team while respecting customer-defined stages, history and changes to the operating model.
The operating question
A conversion rate is only comparable when the stages mean the same thing.
Two regions report exactly thirty-four per cent conversion from Stage 3 to Closed Won. The chart puts them side by side and one leader asks why the sales cycles are so different.
In the first region, a deal enters Stage 3 after a discovery meeting. In the second, it enters only after a written business case and access to the decision process. The percentages match because the labels match. The populations underneath have almost nothing in common.
The team agrees to publish a clearer definition. Three months later the conversion rate improves, partly because fewer deals are now allowed into Stage 3. The process may be better. The baseline has also changed, and the report quietly compares the new rule with the old data as though nothing moved.
58 deals entered
34% convertedCirculating better definitions is necessary and insufficient
Writing the stage definitions down is the right first move. People can't apply a standard they can't see. The limitation is that the document isn't the operating system. It doesn't prove which definition was in force, whether the CRM enforced it or what last quarter's deals meant when they were recorded.
A stage should name what has been established, not where a deal sits in a list. If the entry condition can't be tested against the record, teams will keep using the name while applying their own local rule.
Changing the definition can destroy the baseline
Improving a stage model changes who enters the denominator. That is often the point. It also means the conversion before and after the change isn't automatically comparable.
Version the definition with an effective date. A deal from last quarter should retain the rule that applied then. Without that history, a better process can produce an apparent conversion improvement that is partly an accounting change.
Choose the conversion that answers the question
Discovery-to-Won and Solution-to-Won answer different operating questions. RevOps should define the starting stage, outcome, cohort window and exclusions for each published measure.
Customers should keep their own stage names, order and number. PROOF should not impose a universal funnel. Flexibility doesn't mean ambiguity. Each customer-defined stage still needs one written meaning, one effective version and evidence that shows whether the entry condition was met.
Keep movement and time, not only entry and exit
A headline conversion rate hides backward movement, skipped stages and time spent waiting. A deal that moves from Solution back to Discovery is different from one that never left Discovery, even if both later close.
Keep every stage event, the previous and next stage, the effective model version, time in stage and the person or authorized system that made the change. That lets the team distinguish process performance from routing differences.
Where conversion analysis goes wrong
Don't compare people or teams until the definitions, cohort and opportunity types are aligned. A region selling larger deals may have a lower conversion and a better commercial result. A team that qualifies out earlier may look worse at the top and healthier at the point that matters.
Don't optimize one transition in isolation. Raising Stage 3 conversion by delaying entry may simply move the problem into Stage 2. The measure should help the team understand the whole path, not win an argument about one percentage.
A note on benchmarks
A universal stage-conversion benchmark would be false precision for a page making the opposite argument. Stage names, entry rules, deal types and measurement windows vary too widely for an external percentage to be useful without its full definition.
The defensible comparison is internal and version-aware: the same conversion, under the same definition, across a stated cohort and period.
How PROOF approaches it
Keep the evidence, decision and action connected.
PROOF keeps the source, timing and accountable decision together so the team can act while the outcome can still change and learn from what happened afterwards.
See the working product