Designing pipeline governance across multiple commercial motions
A fictional RevOps case: four ways of selling, one pipeline leadership can compare, forecast and review.
Independently created. Contains no employer or client implementation detail, internal names or figures.
01The outcome
One pipeline that leadership can compare across motions and regions: shared definitions where comparison matters, motion-specific rules where the business really differs, and one review format that uses both.
Four motions share one pipeline report, but “qualified”, “stale” and “won” mean something different in each—so the global number cannot be trusted or compared.
Which rules must be common, which must be motion-specific—and how do both land in one review?
Govern a small set of common rules centrally—qualified pipeline, outcomes, forecast categories, review format—and let each motion own its stages, ageing benchmark and forecast logic under that frame.
A B2B manufacturer wins new customers, runs multi-year strategic projects with equipment makers, expands product lines inside existing accounts and generates demand through marketing. The CRM already supports the motions with a shared opportunity core (see the Systems & CRM case). What is missing is the governance: the same words are measured differently in each motion, regions apply their own forecast rules, and the weekly review compares numbers that are not comparable.
02The reality · current state
How the business is steered today.
- Qualified pipeline includes early conversations in one team and only priced proposals in another
- Strategic projects look stale after 90 days and are pushed out of the forecast by rule
- Product-expansion deals sit in early stages for months without anyone noticing
- Marketing reports sourced pipeline that sales never accepted
- “Won” means a signed order, a series award or a first shipment depending on the team
- Regions submit forecasts with their own category rules
03Operating loop
Each step with what happens, who owns it and how often.
- 01Qualify
Each motion applies its own qualification test; passing it makes the deal count as pipeline everywhere.
- Owner
- Opportunity owner
- Cadence
- Continuous
- 02Progress
Motion-specific stages with exit criteria; ageing measured against the motion’s benchmark.
- Owner
- Opportunity owner
- Cadence
- Daily
- 03Forecast
Shared categories; motion rules decide when a deal may enter commit.
- Owner
- Sales manager
- Cadence
- Weekly
- 04Review
One weekly format across motions; strategic projects add a monthly project review.
- Owner
- Sales managers; motion leads
- Cadence
- Weekly · monthly
- 05Normalize
Closed outcomes mapped to one won / lost semantics, with reasons, for reporting and accuracy.
- Owner
- Sales operations
- Cadence
- Monthly
The outcome of the last step changes the first one next period.
04Key dimension · Common governance + motion-specific rules
Common governance, motion-specific rules
What must be comparable is governed once. What genuinely differs is owned by the motion—and written down.
- Qualified pipeline
Counts only after the motion’s own qualification exit criteria are met.
- Outcomes
Open, won or lost, each close with a reason from one shared list.
- Forecast categories
Pipeline, best case, commit, closed—one meaning everywhere.
- Ageing
Always measured against the motion’s benchmark, never one global number.
- Review format
The same weekly questions for every motion, with motion evidence.
| Motion | Stages | Qualified when | Forecast | Ageing | Won means | Review |
|---|---|---|---|---|---|---|
| New customerMonths |
| Need, budget, timing and decision-maker confirmed | Commit only in Negotiate | Flag after twice the median stage duration | Signed first order | Weekly pipeline review |
| Strategic projectOne to three years |
| Customer programme confirmed; we are on the request list | By volume ramp over years, reviewed monthly | Milestone dates, not days in stage | Series award | Monthly project review; quarterly portfolio |
| Product expansionWeeks to months |
| Sample requested by a buyer at the account | Commit after sample approval | Flag after 60 days without a stage change | First order of the new line | Monthly account review |
| Demand generationLead to accepted within an agreed service level |
| Accepted by sales and qualified in one of the motions | Not forecast; reported as sourced pipeline | Unaccepted leads escalate after the service level | Accepted as a qualified opportunity | Weekly handoff review |
Demand generation is governed as a source that feeds the motions—with its own acceptance contract—not as a fourth lifecycle with its own “won”.
05KPI contracts
Every measure with an owner, a cadence and an action.
| Metric | Definition | Owner | Cadence | Action |
|---|---|---|---|---|
| Qualified pipeline | Open opportunities past the motion’s qualification exit, in the period horizon | Sales management | Weekly | Pipeline generation by motion where short |
| Stage ageing ratio | Days in stage ÷ the motion’s benchmark for that stage | Sales managers | Weekly | Update, requalify or close stale opportunities |
| Win rate by motion | Won ÷ (won + lost), by motion, on normalized outcomes | Motion leads | Quarterly | Revisit qualification criteria where it drifts |
| Sourced pipeline accepted | Marketing-sourced opportunities accepted by sales ÷ submitted | Marketing with sales | Weekly | Adjust lead criteria; clear the acceptance queue |
06Accountability
Who owns what, decides what—and escalates to whom.
| Role | Owns | Decides | Escalates to |
|---|---|---|---|
| Sales operations | The common rules and their definitions | Changes to shared definitions, via the governance forum | Sales leadership |
| Motion lead | Stages, exit criteria and ageing benchmarks for one motion | Motion-specific rules, within the common frame | Sales operations forum |
| Sales manager | The team’s pipeline and forecast call | Commit, push or close in the weekly review | Regional sales leader |
| Opportunity owner | Stage, next step, close date and evidence | When exit criteria are met | Sales manager |
07The trade-offs
Credible options, judged against these premises.
One process and one set of rules for every motion
Homogeneous, transactional selling
Cost: Stage semantics lose meaning; strategic projects distort the forecastEach motion governs itself completely
Separate businesses with separate leadership
Cost: No comparable pipeline or global forecastCommon governance with motion-specific rules
Distinct motions under one leadership and one forecast
Cost: A governance forum and a rule catalogue to maintain08The second layer
Questions that change the design.
Comparability
- Which stages can be shared, and which need motion-specific logic?
- What constitutes qualified pipeline in each motion?
- How are closed outcomes normalized?
Forecast
- How is probability handled—by stage, by motion, by history?
- When may a strategic project enter commit?
- How is stage ageing compared across motions?
Governance
- Who may change a shared definition?
- How are regional exceptions recorded?
- Which forum reviews each motion?
09Decisions & outputs
What the work produces.
- 01Motion model
- 02Shared governance rules
- 03Stage semantics per motion
- 04Forecast rules
- 05Ageing benchmarks
- 06Reporting model