Revenue Design
Sales Pipeline Design
A stage should mean the same thing to everybody.
Why it breaks
The operating problem
Pipeline stages get named after what the seller did, not after what the buyer proved. Deals sit in Proposal for months, forecasts are built on optimism, and the review meeting becomes a negotiation about the CRM rather than a conversation about deals.
Self-check
Signs you need this
Pipeline problems are easiest to spot in the review meeting. If the meeting is about the CRM rather than about deals, the design is the cause.
- Two sellers use the same stage to mean different things.
- Deals age in one stage with no rule to force a decision.
- Your forecast is a list of hopes.
- Closed-lost reasons are mostly price or no budget.
- The pipeline review is about updating the CRM, not about winning deals.
Page boundary
Where this capability ends
Sales Pipeline designs the business process. Opportunity Management implements that logic in the system. Qualification executes the decision on each individual deal.
Opportunity Management
System controls that operationalize the sales pipeline.
Qualification
Consistent decisions on fit, intent, need, timing and next action.
Revenue Intelligence
Turn commercial signals into diagnostic and management decisions.
Concrete intervention
What Revops delivers
A pipeline design is a contract between sellers and management about what a stage means and what evidence moves a deal out of it.
- DefinitionStage definitions with buyer-side evidence
- RulesEntry and exit criteria per stage
- ModelQualification framework and stage gates
- DefinitionRequired fields per stage
- DefinitionLoss and no-decision taxonomy
- RoutineDeal review cadence and agenda
- RulesForecast category rules
- DashboardStage conversion and velocity baseline
Concrete example
What it looks like in practice
Evidence-based stage
Discovery does not end because a call happened. It ends when the buyer has confirmed the problem, named who else decides, and stated a timeline. Three pieces of evidence, entered as fields, not as notes. The stage gate is then enforceable by the system.
The reasoning model
How ROUTE applies
For an opportunity, ROUTE governs progression: what counts as a real deal, what evidence it must carry, and what forces a decision.
Recognize
Recognise a real opportunity, not an interested conversation.
Organize
Attach the account, contacts, value and timeline to one record.
Understand
Read buying progress from evidence, not from seller confidence.
Trigger
Move, hold or close the deal against written criteria.
Execute
Run the next step, and record what the buyer actually did.
The operating architecture
Revops OS mapping
Pipeline sits in Workflows because its output is a set of gates. The evidence lives in Data, the forecast consequence lives in Control.
- 01
Data
Opportunity, account, contact roles, value, close date, products.
- 02
Context
Buying stage, evidence held, risk, competitive position.
- 03
Workflows primary layer
Stage gates, required evidence, review triggers.
- 04
Action
The meetings, proposals and negotiations themselves.
- 05
Control
Conversion by stage, velocity, forecast accuracy.
Outcomes
What changes
A pipeline is working when the same deal gets the same read from two different managers.
- Every stage has written buyer-side evidence attached.
- Stalled deals surface on a rule, not on memory.
- Forecast categories mean the same thing to every seller.
- Loss reasons usable for analysis, not just for closure.
- Stage conversion measurable month over month.
Questions
Frequently asked
Do we need to change our sales methodology?
Our sellers resist CRM discipline. Does this make it worse?
How is this different from Opportunity Management?
Next step
Where this gets repaired.
Pipeline design is worth doing before any CRM rebuild, because configuring stages nobody agrees on simply automates the disagreement.