When pipeline stages describe sellers, not buyers
Seller-activity stages can weaken conversion and forecast analysis. Define buyer evidence, then calibrate it against realized outcomes.
A familiar CRM pattern is a pipeline named for seller activity: Discovery Call, Demo Completed, Proposal Sent, Negotiation. Each label records something the seller did, not necessarily a change in buyer commitment.
That choice weakens metrics that assume every record in a stage carries comparable evidence, including conversion, coverage, and weighted forecast measures.
Activity is not progression
Consider a hypothetical deal in which a demo is completed with an enthusiastic individual contributor, but budget authority and a decision process are still unknown. Advancing the record on the calendar event changes weighted pipeline and coverage without adding the buyer evidence the model assumes.
A second deal may contain a recorded problem, budget owner, and security-review request but remain in the earlier activity stage because no demo was scheduled. The records then carry different evidence and risk while the stage model treats them alike. That mismatch is a signal; it is not a probability estimate by itself.
Stages as buyer state
For the operating model in this series, a stage represents a measurable change in buyer commitment, risk, or obligation. The exit criteria should be testable against the record:
- Instead of "Discovery Call" — the buyer has articulated a problem, and its cost to them is recorded.
- Instead of "Demo Completed" — a person with budget authority is identified on the record and has engaged.
- Instead of "Proposal Sent" — the buyer has confirmed the evaluation criteria and the decision timeline.
- Instead of "Negotiation" — commercial terms are agreed in principle and only paper remains.
Each criterion can be evidenced in the deal record. That supports comparison across sellers, segments, and periods when the criteria, population, and data-capture rules remain stable. It does not make unlike segments comparable or prove that the evidence is current.
Enforce at transition, not in review
Review-only enforcement is weak because the stage may already have entered reports. Put the criteria at the transition through required evidence or an approved exception, then use the weekly review to inspect edge cases and rule quality.
What it buys you
Buyer-evidence stages create three useful outputs: conversion rates that can be calibrated against realized outcomes, forecast weights that can be tested by cohort, and coverage based on stated qualification rules.
Those outputs improve the measurement basis; they do not guarantee forecast accuracy. Buyer evidence may be incomplete or stale, and probability still requires calibration by segment, motion, and time horizon.
Terms used in this note
Write the stop rule before the pilot starts
A market-entry pilot with no decision rule written before exposure cannot end. It gets extended until it is the default motion, without anyone choosing that.
Your pricing is a list, not a logic
A price list says what things cost today. It cannot say what to charge the deal in front of you, which is why realised price drifts and nobody owns the drift.
You just inherited RevOps. Start with a charter.
Being told to "own revenue operations" is not a mandate. Until authority is written down, every decision you make is reversible by whoever objects loudest.