Revenue Systems
Opportunity Management
The pipeline design, enforced by the system.
- Part of
- Revenue Systems
- Owned at
- Workflows layer
- Typical effort
- 3 to 5 weeks
- Runs on
- HubSpot, Salesforce, Zoho, Odoo or Pipedrive
- Part of the discipline
- What is revenue operations
Why it breaks
The operating problem
A well-designed pipeline decays within a quarter if the system does not hold it. Stages get skipped, required evidence is never entered, aging deals stay green, and the forecast is assembled by hand before every board meeting.
Self-check
Signs you need this
System decay is gradual. These signs mean the pipeline design is no longer being held up by the tooling around it.
- Deals advance without the evidence the stage requires.
- Stalled deals still look healthy on the dashboard.
- The forecast is rebuilt in a spreadsheet every month.
- Discounts are approved in a messaging app.
- Closed-lost is filled in months after the fact.
Page boundary
Where this capability ends
Sales Pipeline designs the process. Opportunity Management implements the controls, fields, alerts and hygiene that keep it true in the system.
Sales Pipeline
Design stages, evidence, progression rules and management cadence.
Reporting & Forecasting
Governed definitions, dashboards and forecast logic.
Workflow Automation
Triggers, rules, actions, exceptions and escalation.
Concrete intervention
What Revops delivers
This is configuration with intent: fields that feed decisions, gates that block, alerts that fire, and a forecast that assembles itself.
- DefinitionOpportunity object and field configuration
- RulesStage gate enforcement rules
- RulesRequired evidence per stage
- RulesAging and stall alerts
- RulesApproval and discount workflows
- DashboardDeal hygiene scorecard
- RulesForecast category automation
The reasoning model
How ROUTE applies
ROUTE runs inside the system here. The deal is recognised, held, read, gated and recorded without anyone maintaining a spreadsheet.
Recognize
Recognise the deal and every event attached to it.
Organize
Hold account, contacts, products and value on one record.
Understand
Read stage, age, evidence and risk from the system.
Trigger
Block, alert or advance the deal on written rules.
Execute
Record the activity and update the forecast automatically.
The operating architecture
Revops OS mapping
Opportunity Management sits in Workflows and is the reason a pipeline design survives its second quarter.
- 01
Data
Opportunity fields, products, amounts, close dates.
- 02
Context
Risk flags, age, evidence completeness.
- 03
Workflows primary layer
Gates, approvals, alerts, hygiene enforcement.
- 04
Action
What the seller is required to do inside the system.
- 05
Control
Hygiene scorecard, stall rate, forecast reliability.
Outcomes
What changes
Hygiene is the leading indicator. Forecast reliability follows it by roughly one quarter.
- Stage gates enforced by the system, not by the manager.
- Stalled deals alert automatically.
- Forecast built from CRM data, not from a spreadsheet.
- Approvals traceable end to end.
- Hygiene measurable per team and per seller.
Questions
Frequently asked
Will stage gates slow our sellers down?
Can the forecast really be built from the CRM?
Do we need administrator access?
Next step
Where this gets repaired.
This work is scoped alongside pipeline design, because a stage model that the system does not enforce reverts to habit within weeks.