Revenue Operations
Turn commercial signals into governed action.
I connect pipeline, customer lifecycle, targets, performance, CRM and management cadence into one operating model the business can actually steer.
Six ingredients make one commercial operating system; one loop runs it. Select a step of the loop to see what happens, who owns it and the evidence it runs on.
- ProcessStages, exit criteria and handoffs
- CRMWhere the work and its evidence live
- DataOrders, invoices and history, computed once
- TargetsWhat the business is expected to achieve
- MeasurementOne definition per KPI, with an owner
- Management cadenceWhen performance is reviewed, and by whom
Measure
Orders, invoices and pipeline are compared with target—one definition per metric, computed once.
- Owner
- Sales operations
- Evidence
- Performance to target, coverage, stage ageing
- System
- Data platform, shown in the CRM
Not “build dashboards and clean the CRM”. The commercial operating system.
I treat Revenue Operations as the design of how the business sells, measures and steers: stages, owners, targets, signals, actions and the forums that review them.
Dashboard administrationCRM housekeepingReporting supportAdding fields because management asksForcing every team into one process without understanding the businessMeasuring everything because it can be measured
- Commercial stagesWhat state commercial work is in—defined by business reality, not by picklist values.
- OwnershipWho owns each account, opportunity, stage and outcome—and who they escalate to.
- Exit criteriaWhat must be true to leave a stage, captured as evidence rather than opinion.
- KPI meaningOne definition, grain and time logic per measure—the same in every region.
- TargetsGrain, version, owner and freeze point: a target is data plus governance.
- Decision cadenceWhich forum reviews what, with which evidence, and what it can decide.
- Signal → actionEvery signal that matters names an owner, an action and a follow-up.
- ExceptionsOverrides, stale opportunities and missed plans are governed, not ignored.
- Execution qualityStage ageing, next-step discipline and forecast accuracy—measured, not assumed.
- Process ↔ systemsThe CRM, planning and data platform each hold the part of the model they are good at.
- 01A KPI without an owner and an action is reporting noise.
Every published measure names who acts, what they do and when it is reviewed.
Pipeline coverage - 02Pipeline stages should represent business reality, not CRM configuration.
A stage is a business state with entry and exit criteria; the picklist only records it.
Pipeline governance - 03A dashboard does not create accountability.
Management routines that run from the system do.
Management cadence - 04Segmentation without an operating response is just colour-coding.
Each segment carries an owner, an obligation and a review.
Segmentation → action
From commercial motion to closed loop.
Nine moves from the way the business sells to the review that changes the next plan. Dashboards come after the fifth.
01Define the commercial motion
What commercial motion are we operating?
Motions differ in cycle, evidence and what “won” means.
- New customer acquisition
- Account growth
- Product-line expansion
- Strategic project sale
- Reactivation
- Retention and recovery
One lifecycle forced on every motion makes stages meaningless; one per motion splits the pipeline
Define the commercial motion
What commercial motion are we operating?
Motions differ in cycle, evidence and what “won” means.
- New customer acquisition
- Account growth
- Product-line expansion
- Strategic project sale
- Reactivation
- Retention and recovery
Commercial motion modelOne lifecycle forced on every motion makes stages meaningless; one per motion splits the pipeline
Define the lifecycle
What states does commercial work move through?
A stage is a business state, not a percentage.
- Stages
- Entry criteria
- Exit criteria
- Ownership
- Next action
Pipeline and lifecycle modelStages without exit criteria turn every pipeline review into a debate about opinions
Define accountability
Who owns each stage and outcome?
One accountable owner per stage, account and outcome.
- Account owner
- Opportunity owner
- Manager
- Specialist roles
- Escalation
Commercial ownership modelShared ownership of an account usually means nobody owns its recovery
Define targets
What is the organization expected to achieve?
A target is data plus governance: grain, version, owner, freeze point.
- Annual target
- Period target
- Account target
- Segment target
- Product target
- Business-unit target
Target modelA target changed mid-year without a version rewrites every past performance figure
Define performance signals
Which measures tell us whether execution is healthy?
Each one a contract: definition, owner, freshness and action.
- Pipeline coverage
- Conversion
- Stage ageing
- Order intake
- Invoiced value
- Target achievement
- Forecast accuracy
- Customer activity
KPI contractsA KPI without an owner and an action is reporting noise
Define segmentation
When does a metric become a meaningful business state?
Inputs, definition, threshold, owner and action—together.
- On Track
- Underperforming
- At Risk
- No Sale
Commercial segmentation modelSegmentation without an operating response is just colour-coding
Link signal to action
What happens because of the signal?
Every signal names an owner, an action and a follow-up.
- Owner
- Task
- Campaign
- Review
- Recovery plan
- Escalation
- Pipeline-generation action
Signal-to-action modelAn action with no exit keeps running after the account has recovered
Define management cadence
When is performance reviewed, by whom, and using which evidence?
Forums run from the system, with the same definitions everywhere.
- Weekly pipeline review
- Monthly customer performance review
- Quarterly target review
Decision cadenceA review that runs from spreadsheets tells sellers the CRM is optional
Close the loop
How does action change the next measurement?
Outcomes are recorded, so the next plan learns from them.
- Outcome
- Status
- Recovery
- Reclassification
- Escalation
- Learnings
Closed-loop commercial operating modelWithout recorded outcomes, nobody can say which interventions work
The symptoms arrive as “we need a better dashboard”.
Underneath, a stage definition, a target owner, a forum or an obligation to act was never designed.
Pipeline stages mean different things in different teams.
Usually missingStage definitions with entry and exit criteriaManagers run the forecast review from a spreadsheet, not the CRM.
Usually missingA forecast model and a review that runs from the systemDashboards show performance—and nothing happens because of them.
Usually missingA signal-to-action model with named ownersTargets live in another system and nobody owns their publication.
Usually missingA target model with an owner, a grain and a freeze pointAccounts are flagged at risk every month; nobody owns the recovery.
Usually missingA recovery obligation with a review and a recorded outcomeForecast rules differ by region, so the global number is a sum of opinions.
Usually missingCommon forecast governance with motion-specific rulesCoverage is reported but never tied to pipeline generation.
Usually missingA coverage contract with a threshold, an owner and an action“Closed won” means a signature in one team and a first order in another.
Usually missingClosed outcomes normalized per motion
Artefacts that make the business steerable, not just visible.
Each one answers a question a dashboard leaves open.
- Commercial motion modelWhich motions do we run, and how do they differ?
- Pipeline architectureHow does pipeline flow from source to closed outcome?
- Stage & exit-criteria modelWhat must be true to enter and leave each stage?
- Account lifecycleWhich states does a customer move through, and why?
- Ownership matrixWho owns each account, stage, outcome and escalation?
- Target modelAt which grain, in which version, frozen when?
- KPI contractsOne definition, owner, freshness and action per measure
- Forecasting modelWhose number, from which inputs, overridden how?
- Segmentation modelWhen does a metric become a business state?
- Management dashboardsWhich view does each forum review, and decide from?
- Action modelWhich signal creates which task, campaign or review?
- Recovery processWhen is a plan mandatory—and how does it close?
- Performance review cadenceWho reviews what, how often, with which evidence?
- Governance frameworkWho changes a definition, a stage or a target?
- CRM adoption signalsIs the system actually used to run the business?
Targets become action—and action changes the next plan.
Eight steps, one loop. Read every step by owner, system, signal, action or cadence—or select a step to see all five.
Process+CRM+Data+Targets+Measurement→ Commercial operating system
Every step has one accountable owner. Where two teams share a step, the handoff is explicit.
Performance
- Owner
- Sales operations
- System
- Data platform
- Signal
- Performance to target; segment
- Action
- Publish segments with a version
- Cadence
- Monthly; provisional daily
Pipeline stages should represent business reality, not CRM configuration.
A stage is a business state: what must be true to enter, what must be true to leave, who owns it, which evidence proves it and what happens next.
Discovery
A named contact confirms a need worth exploring.
Need, buying context and decision process understood.
- Owner
- Opportunity owner
- Key evidence
- Discovery notes; contact roles
- Next action
- Qualify—or close as “no opportunity” with a reason
Qualified
Discovery exit criteria met.
Budget or volume, timing and decision-maker confirmed.
- Owner
- Opportunity owner
- Key evidence
- Qualification checklist; estimated amount and date
- Next action
- Agree the solution scope with the customer
Solution fit
Qualified pipeline—counted in coverage from here.
Customer agrees the proposed solution meets the requirement.
- Owner
- Opportunity owner with a specialist
- Key evidence
- Requirement match; technical sign-off
- Next action
- Prepare and approve the commercial proposal
Commercial proposal
Solution accepted in principle.
Proposal delivered and discussed with the decision-maker.
- Owner
- Opportunity owner
- Key evidence
- Approved quote; delivery date; customer feedback
- Next action
- Agree terms, or revise the proposal
Negotiation
Proposal discussed; the customer intends to proceed.
Terms agreed—or the customer declines.
- Owner
- Opportunity owner; sales manager for exceptions
- Key evidence
- Open points; approvals for any deviation
- Next action
- Close as won or lost, with a reason
Won / Lost
A recorded outcome: signed order, contract or award—or a loss.
Terminal. Reopening is a new opportunity.
- Owner
- Opportunity owner; confirmed by the manager
- Key evidence
- Order or contract reference; loss reason
- Next action
- Won: hand over to delivery. Lost: learn from the reason
Stage ≠ percentage
- A number someone typed—or a default the stage set
- Means different things to different sellers
- Says nothing about what is missing
- Cannot be audited or coached
- The proposal was discussed with the decision-maker
- Only commercial terms remain open
- The next action is known and dated
- The evidence can be checked in a review
Probability is an output of stage semantics and history—not a replacement for them.
One pipeline, several motions
Different motions need different stage semantics, forecast logic, cycle times, KPI expectations and review cadence. Comparability comes from governing what must be common—not from forcing one process on everyone.
- One definition of qualified pipeline
Every motion counts pipeline in coverage only after its own qualification exit criteria are met.
- One set of outcomes
Open, won or lost—each close with a reason from one shared list.
- Exit criteria and a next step on every stage
No stage without a test to leave it and a dated next action.
- Shared forecast categories
Pipeline, best case, commit and closed mean the same thing in every motion and region.
- Ageing against the motion’s own benchmark
A strategic project is not stale at 90 days; a product expansion may be.
- One weekly review format
The same questions for every motion, with motion-specific evidence.
New customer
- Stage semantics
- Discover · qualify · propose · negotiate
- Forecast logic
- Stage-based; commit only in negotiation
- Cycle time
- Months
- KPI expectations
- Qualified pipeline created; win rate; first-order conversion
- Review cadence
- Weekly pipeline review
- What “won” means
- Signed first order
Strategic project
- Stage semantics
- Specify · nominate · prototype · series award
- Forecast logic
- By volume ramp over years, not by one close date
- Cycle time
- One to three years
- KPI expectations
- Nominations; award rate; lifetime volume
- Review cadence
- Monthly project review, plus a quarterly portfolio review
- What “won” means
- Series award
Product expansion
- Stage semantics
- Identify · sample · approve · order
- Forecast logic
- Committed after sample approval
- Cycle time
- Weeks to months
- KPI expectations
- Lines added per account; sample-to-order conversion
- Review cadence
- Monthly account review
- What “won” means
- First order of the new line
Demand generation
- Stage semantics
- A source, not a lifecycle: lead → qualified opportunity in any motion
- Forecast logic
- Not forecast directly; contributes qualified pipeline
- Cycle time
- Lead to qualified within an agreed service level
- KPI expectations
- Qualified pipeline sourced; acceptance rate by sales
- Review cadence
- Weekly handoff review with sales
- What “won” means
- Accepted as a qualified opportunity
A target is not a number. It is data plus governance.
Grain, phasing, version, precedence, owner and freeze point decide what “performance” means—long before anyone draws a chart.
Target=Data+Governance
- CustomerAccount · product line · month
- SalespersonOwner · month—derived from accounts, or set top-down?
- TeamRegion or channel · quarter
- Business unitBU · product family · year
- SubsidiaryLegal entity · currency · year
- Product lineLine · segment · quarter
- PeriodMonth, quarter, year—calendar or fiscal
What is the target grain?
The lowest level at which a target is set and owned—often account × product line × month. Everything above it is an aggregation, not a second target.
Annual or monthly?
Annual targets need a monthly phasing to be measured during the year. The phasing is part of the target, not a reporting choice.
Cumulative YTD, or by period?
Both are legitimate. Each KPI declares which one it uses—they give different answers in the same month.
Signed target or budget?
The signed commercial target and the financial budget often differ. Name which one each measure compares against.
Which target takes precedence?
When account targets and top-down targets disagree, one is authoritative and the difference is visible as an unallocated gap.
How does a target change mid-year?
As a new version with an effective date. Past months keep the version they were measured against.
Who owns target publication?
One owner publishes each version—typically commercial planning with finance—and nobody edits targets inside the CRM.
When is it frozen?
At a declared date per period. After that, changes need approval and create a new version.
Year to date needs explicit semantics
One annual target, one actual, four legitimate definitions of what was expected by September. Synthetic units; no real figures.
- Annual target
- 1,200
- Month
- September
- Actual YTD
- 810
- JMonth 1: 100, counted
- FMonth 2: 100, counted
- MMonth 3: 100, counted
- AMonth 4: 100, counted
- MMonth 5: 100, counted
- JMonth 6: 100, counted
- JMonth 7: 100, counted
- AMonth 8: 100, counted
- SMonth 9: 100, counted
- OMonth 10: 100, not yet due
- NMonth 11: 100, not yet due
- DMonth 12: 100, not yet due
1,200 × 9 / 12. Every month weighs the same.
810 ÷ 900
90 %
Underperformingagainst an illustrative 95 % threshold
| Definition | Expected YTD | Performance |
|---|---|---|
| Linear phasing | 900 | 90 % |
| Seasonal phasing | 804 | 101 % |
| Revised in July | 840 | 96 % |
| As of 15 September | 850 | 95 % |
Calendar or fiscal year? · Which currency—and at which rate? · What if an account has no target? · Signed target, or budget?
Segmentation without an operating response is just colour-coding.
A segment is a business state with a definition, a versioned threshold, an owner and an obligation—not a colour on a dashboard. Thresholds here are illustrative; they are set per business.
Performance % to YTD target + Decline over consecutive periods + Order activity
Below expected and declining.
Illustrative: below 80 %, or declining for two periods
Account owner; reviewed by the sales manager
Create a recovery plan—mandatory, with a cause, an objective and dated actions.
Measurement must change behaviour
- At Risk account
- Account owner; reviewed by the sales manager
- Create a recovery plan—mandatory, with a cause, an objective and dated actions.
- Monthly recovery review, plan by plan
- Recovered
- Escalated
- Closed with a reason
How segments are computed and published: Data & Integrations
Customer performance is not just sales history
- Orders (used)
- Invoices (used)
- Targets (used)
- Open opportunities
- Activity
- Product penetration
Invoiced plus open orders against the YTD target.
- Recovery (triggered)
- Cross-sell
- Reactivation
- Pipeline generation
- Management review (triggered)
Recovery plans, structured
- 01Performance issue
Account at 72 % of YTD target, declining for two periods
- 02Cause
Volume on one product line moved to a second supplier
- 03Recovery objective
Back to 90 % of YTD target by period 12
- 04Actions
Three: price review with the pricing owner; technical visit; sample of an alternative line
- 05Owner
Account owner; reviewed by the sales manager
- 06Due date
Actions within six weeks; plan review at the next monthly forum
- 07Review
Monthly recovery review, plan by plan—not in totals
- 08Outcome
Recovered · Escalated · Closed with a reason
When is a plan mandatory?
When the segment says so—At Risk, typically—not when a manager remembers. The rule is written down and applied the same way everywhere.
Who owns it?
The account owner writes and runs it; the sales manager reviews it. Ownership does not move to whoever built the dashboard.
How many actions?
Few and dated—usually two to four. A plan with ten actions is a wish list.
How is closure decided?
In the review forum: recovered, escalated, or closed with a reason. The segment alone does not close a plan.
What if performance recovers on its own?
The plan still closes in review, marked as recovered without intervention—that is useful evidence, not noise.
What if no action is taken?
An overdue plan escalates to the next level at the following forum. Silence is visible.
How is history retained?
Plans are records, never overwritten: cause, actions, dates and outcome stay attached to the account.
A dashboard does not create accountability. Management routines do.
Four forums over one quarter. Each has participants, evidence, decisions and outputs—and runs from a system view, not from an export.
Operational execution
- Participants
- Sellers; inside sales
- Evidence
- My open opportunities, next steps due, new leads
- Decisions
- What to work on today
- Outputs
- Updated next steps; activities logged
- Runs from
- Seller home page in the CRM
Pipeline and opportunity review
- Participants
- Sales manager and team
- Evidence
- Stage changes, stale opportunities, commit changes, coverage
- Decisions
- Advance, push, close or requalify specific opportunities
- Outputs
- Forecast call by manager; actions per opportunity
- Runs from
- Pipeline review view, filtered by team
Customer performance and recovery review
- Participants
- Sales managers; sales operations
- Evidence
- Segments, open recovery plans, overdue actions, no-sale accounts
- Decisions
- Accept, challenge, escalate or close recovery plans
- Outputs
- Plan outcomes; escalations; reactivation list
- Runs from
- Performance review view with plan status
Target and strategy review
- Participants
- Sales leadership; finance; operations
- Evidence
- Target attainment, forecast accuracy, motion performance, coverage trend
- Decisions
- Reprioritize motions, segments and coverage goals; approve target revisions
- Outputs
- Updated plan; new target version where approved
- Runs from
- Leadership view, from the same definitions
CRM value increases when management routines run from the system. Sellers keep the CRM current when the review they attend uses it.
Why adoption is an operating-model outcome: Change & Adoption
Whose number is the forecast—and what does low coverage oblige?
There is no universal forecasting formula. There is a governed set of inputs, recorded judgement, one owner of the final number—and metrics that start work when they cross a line.
Six inputs, each with its failure mode
- Pipeline stage
Where the deal really is
Goes wrong whenStages without exit criteria - Expected close date
Which period it lands in
Goes wrong whenDates pushed silently, month after month - Amount
How much, in which currency
Goes wrong whenPlaceholder amounts that never get revised - Probability
A default per stage, or history
Goes wrong whenTyped by hand to make a number look right - Manager judgement
What the data cannot know
Goes wrong whenOverrides with no record and no reason - Historical behaviour
Conversion and slippage by motion
Goes wrong whenOne benchmark applied to every motion
Forecast governance
Stage-based or probability-based?
Categories follow stage semantics by default; probability is derived, not typed. History calibrates it by motion.
Can a manager override?
Yes—at the forecast level, never by editing the opportunity. Every override records who, when, from what, to what and why.
Which forecast categories?
Pipeline, best case, commit, closed—one set, defined once, used in every motion and region.
Who owns the final number?
The sales leader for the unit. Sellers own their call; managers own their adjustment; the leader owns the submitted number.
How are changes logged?
Weekly snapshots of the forecast and of each opportunity’s category, amount and date—so movement is visible, not reconstructed.
How is accuracy measured?
Submitted forecast against actual, by unit and motion, at a fixed lag. Accuracy is reviewed quarterly—as a signal about the process, not a blame list.
What happens to stale opportunities?
Past the motion’s ageing benchmark, or with a close date in the past, they drop out of commit until the owner updates them.
Pipeline coverage, as a metric contract
A KPI without an owner and an action is reporting noise. Coverage earns its place when a number below the line starts pipeline generation.
Pipeline coverage
Eligible open pipelineRemaining target
- Dimensions
- SegmentPeriodBusiness unitSalesperson
- Owner
- Sales management (definition stewarded by sales operations)
- Freshness
- Daily; reviewed weekly
- Action
- Pipeline generation where coverage falls below the agreed multiple
2.6×780 ÷ 300 remaining target
Below the contracted 3×: pipeline generation of 120 is required, owned by sales management.
Which opportunities are eligible?
Qualified stage or later, close date inside the horizon, owner active. Everything else is visible—but not counted.
Weighted or unweighted?
Pick one per contract and set the threshold for it. A 3× threshold means nothing against a weighted number.
Which target?
The remaining signed target for the period, in the published version—not the budget, not last month’s version.
What close-date horizon?
The rest of the period, or a rolling window per motion. Long project cycles need a longer one.
How are renewals treated?
Separately. Mixing renewals with new pipeline flatters coverage exactly where growth is missing.
Which currency?
The reporting currency at the planning rate, so movement in exchange rates does not look like pipeline.
Where coverage is computed and published: metric contracts in Data & Integrations
Six cases, one operating system.
Synthetic global B2B scenarios. The commercial performance reference and the recovery process case are read here through the RevOps lens; four new cases cover motions, targets, forecast and cadence.
- Case 01Reference architecture · RevOps lensTarget + actual + segment + action + review
Commercial performance management
Performance is measured against target every month—and the measurement stops at the dashboard.
How do target, actual, segment, action and review become one loop, with an owner at every step?
PlanningERPData platformCRMData & IntegrationsProcess Architecture - Case 02Process case · RevOps lensRecovery governance: owner, cadence, outcome
Designing a commercial performance recovery process
At-risk accounts are visible every month—and nobody is accountable for recovering them.
Who is accountable for recovery, in which forum is it reviewed, and who decides it is over?
Data platformCRMPlanningProcess ArchitectureAutomation - Case 03Selected workCommon governance + motion-specific rules
Designing pipeline governance across multiple commercial motions
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?
CRMData platformPlanningSystems & CRM ArchitectureProcess Architecture - Case 04Target grain, versions & YTD logic
Designing a target model with explicit period semantics
The same account shows 90 % in one report and 101 % in another, because targets are loaded as numbers without phasing, version or owner.
What makes a target measurable during the year—and who decides when it changes?
PlanningData platformCRMERPData & IntegrationsDigital Operating Model - Case 05Forecast ownership & coverage contract
Designing forecast governance and pipeline coverage that trigger action
The forecast is rebuilt every Monday in a spreadsheet, overrides are invisible, and coverage is reported without anyone being asked to generate pipeline.
Whose number is the forecast, how is judgement recorded—and what does low coverage oblige someone to do?
CRMData platformPlanningData & IntegrationsSystems & CRM Architecture - Case 06Forums, evidence & adoption signals
Running commercial management cadence from the CRM
Sellers are asked to keep the CRM current, but every management meeting runs from spreadsheets—so the system is maintained for nobody.
Which forums run the business, what evidence does each use—and how do we know they run from the system?
CRMData platformCollaboration toolsChange & AdoptionDigital Operating Model
Every RevOps request has a second layer.
The visible request is where the design starts, not where it ends.
“Build us a pipeline dashboard.”
A dashboard with pipeline by stage, owner and close month.
4 of 6 questions surfaced
If nobody can name one, the dashboard will be admired and ignored.
Process, systems and data—run as one operating rhythm.
Revenue Operations
- Process Architecture
Process defines the stages, handoffs, decision rights and recovery flows that RevOps then governs and measures.
- Systems & CRM Architecture
Systems decide where pipeline, targets and signals live—one opportunity core, many motions.
- Data & Integrations
Orders, invoices and targets are joined, computed once and published as governed signals.
- Automation
Segments and signals become tasks, campaigns and escalations—with exits when the state changes.
- Change & Adoption
CRM value grows when management routines run from the system; adoption is an operating-model outcome.
- Digital Operating Model
Owners, forums and decision rights make the operating rhythm stick after the project ends.
Architecture decisions
Writing & related work
Revenue Operations is not dashboards and CRM hygiene. It is the commercial operating system:
- Motions
- Stages
- Ownership
- Targets
- Signals
- Segments
- Actions
- Cadence
- Review
One commercial operating system, measured the same way everywhere.
Turn commercial signals into governed action.
Dashboards everywhere—and nobody obliged to act on them?
- What does “qualified” mean in each of your teams?
- Which target version was September measured against?
- Which review runs from the CRM today?