ADR / 011

Define pipeline stages by business state and exit criteria, not probability

A stage says what is true about the deal and what must happen to leave it. Probability and forecast category are derived from that—never typed in its place.

Reference pattern

Independently created. Contains no employer or client implementation detail, internal names or figures.

01Context

Opportunity stages were configured from a vendor template and sellers pick them by feel. Each team reads them differently, probability is typed by hand, and the weekly review debates whether deals are really where they say. Forecasts built on these stages cannot be compared across teams or explained afterwards.

02Decision drivers

  1. D01

    Stages must mean the same thing to every reader

  2. D02

    Reviews need evidence, not opinions

  3. D03

    Forecast categories must be consistent across motions and regions

  4. D04

    Sellers should not maintain fields nobody uses

03Options considered

Options considered: when each would be the right choice, what it costs, and the verdict under these premises
OptionRight whenCost / trade-offVerdict
Probability-led stages: a percentage per deal, typed by the sellerVery small teams with one seller typeMeasures optimism; cannot be coached or auditedRejected
Vendor-default stages with default probabilitiesA first pipeline is needed before the sales motions are understoodStages describe the tool, not the business; no exit criteriaRejected
Stages as business states with entry and exit criteria; probability and category derivedAny pipeline that is reviewed and forecastCriteria must be designed per motion and kept currentSelected

Every option is right under some premises. The verdict applies to the context above.

04Decision

Define each stage as a business state: what must be true to enter, what must be true to leave, the owner, the evidence and the expected next action. Capture exit evidence with as few fields as possible. Derive the forecast category from the stage mapping and calibrate probability from history by motion; managers adjust the forecast, not the stage. Changes to stage definitions go through the RevOps governance forum.

05Consequences

What this choice changes elsewhere in the system.

  1. Management cadence

    Reviews discuss evidence and next steps instead of percentages.

  2. Forecast

    Forecast categories mean the same thing in every region and motion.

  3. Measurement

    Probability becomes a measured output that can be calibrated.

  4. Governance

    Stage definitions become a governed asset with an owner.

06Revisit when

The decision holds while its context holds. Challenge it when:

01

Deals are fully transactional and close in one interaction.

02

A motion has too little history for stage-based calibration.

07Where this decision is applied

The decision says why this path was chosen; each case shows how it takes part in a larger architecture.

  1. RevOps case / 05Designing forecast governance and pipeline coverage that trigger actionForecast categories from stage semantics, overrides recorded at the forecast level, one owner of the final number, weekly snapshots—and a coverage contract whose threshold starts pipeline generation.Revenue OperationsData & IntegrationsSystems & CRM ArchitectureArchitecture case · 8 min

Decisions this one depends on, or constrains.

  1. ADR / 012Govern targets as versioned data with a publication and freeze pointPublish targets from planning at a declared grain and phasing, freeze them per period and revise them as new versions—so year-to-date performance is reproducible.Proposed patternRevOps · Targets · Data