Function cockpit
Revenue Operations
One revenue operating picture, recalculated continuously instead of quarterly.
Phase: Phase 4 — Cross-functional orchestration
Run territory, pipeline, forecast, routing, quote and renewal operations through policies and live signals rather than spreadsheet-driven periodic cycles.
Trust score
0
Touchless
0%
Human review
0%
Override rate
0%
Capacity released
25-45% operational capacity; ±5% forecast variance aspiration
Accountable human
SVP Revenue Operations
CoS agent: RevOps Chief of Staff
How a unit moves: the conductor, the five desks, the agents, and the people
Flow of work
How work actually moves through Revenue Operations
Work enters on the left. RevOps Chief of Staff routes it to one of five desks. A named agent does the work. It leaves as cleared, as evidence posted, or as a hold for a person. Every packet you see below is weighted by the real distribution of 185 live units.
Live units
185
Moving now
86
in flight at a station
Held for a person
25
59 past SLA
Agents on the floor
88
11 sub-functions
Control gates
32
rules a unit cannot pass
Interchanges
14
handoffs out of the function
Flow of work
RevOps Chief of Staff and the desks reporting to it
Each packet is a unit of work. Desk weighting and the outcome mix are taken from the 185 units live in this function.
What starts the work
The triggers that put a unit on a line, ranked by live volume.
- 50
Runs transactional
Runs transactional. Starts when a scheduled window opens.
- 48
Runs transactional
Runs transactional. Starts when a request lands in the queue.
- 38
Runs transactional
Runs transactional. Starts when a threshold is crossed.
- 25
Runs transactional
Runs transactional. Starts when an upstream system posts an event.
- 15
Runs analytical
Runs analytical. Starts when a drift signal breaches tolerance.
Where the work goes next
Shared services that run the transaction, and the functions this one hands to.
- 52070
Order-to-Cash
Repeatable transactions handed to the shared spine
- 21288
Hire-to-Retire
Repeatable transactions handed to the shared spine
- 17390
Record-to-Report
Repeatable transactions handed to the shared spine
- 7285
IT
Repeatable transactions handed to the shared spine
- 6744
DATA-ANALYTICS
Repeatable transactions handed to the shared spine
- 101
P2P
Repeatable transactions handed to the shared spine
- 98
Finance
Interchange: the unit changes owning function here
- 78
Information Technology
Interchange: the unit changes owning function here
- 28
Sales
Interchange: the unit changes owning function here
- 0
Legal
Interchange: the unit changes owning function here
The five desks
What RevOps Chief of Staff is actually conducting
Each desk is a layer of the operating model, not a team. The conductor decides which desk owns a unit, then which agent on that desk picks it up.
Takes a position
Strategy
Agents that take positions, argue them, and get held to the outcome.
Receives
A question the function has to answer with money or people behind it.
Emits
A written position with assumptions, alternatives priced, and break conditions.
tasks 24h
1,835
in flight
192
held
0
gates
0
- Revenue Architecture AgentRevenue AnalyticsA2
- Forecast Integrity Challenger AgentForecast IntegrityA2
- Revenue Analytics Challenger AgentRevenue AnalyticsA2
- Billing Interlock Challenger AgentBilling InterlockA2
- Pricing Strategy AgentPricing & Rate CardsA2
- CRM Data Stewardship Challenger AgentCRM Data StewardshipA2
+ 7 more on this desk
Writes the envelope
Policy
The written rules every other agent is bound by, with version and owner.
Receives
A position that has been accepted, plus every regulator and control change.
Emits
Versioned rules that bind every other desk, with an owner and an effective date.
tasks 24h
875
in flight
108
held
11
gates
32
- Discount Guardrail AgentPricing & Rate CardsA2
- Recognition Policy AgentRevenue Recognition InterlockA2
- Data Policy AgentCRM Data StewardshipA2
- Systems Policy AgentSystems & IntegrationA2
- Comp Ops Policy AgentTerritory & Comp OpsA2
- Order Policy AgentBooking & Order ManagementA2
+ 2 more on this desk
Watches and warns
Observe
Continuous sensing of the outside world and of the agents themselves.
Receives
Outside signals and the behavior of the agents themselves.
Emits
Alerts, drift flags, and the evidence the conductor uses to reroute work.
tasks 24h
1,815
in flight
0
held
0
gates
0
- Data Stewardship OrchestratorCRM Data StewardshipA3
- Territory Ops OrchestratorTerritory & Comp OpsA3
- Retention Analytics AgentRenewals & Churn OpsA4
- Integration Health MonitorSystems & IntegrationA3
- Revenue Analytics OrchestratorRevenue AnalyticsA3
- Renewal Ops OrchestratorRenewals & Churn OpsA3
+ 11 more on this desk
Does the work
Workflow
Doing the work: lines, stations, and live units moving through them.
Receives
Live units of work entering at the first station of a line.
Emits
Cleared work, posted evidence, and holds when a unit leaves the envelope.
tasks 24h
62,475
in flight
1726
held
5
gates
0
- Board Reporting AgentRevenue AnalyticsA3
- Model vs Commit AgentForecast IntegrityA4
- Cancellation AgentRenewals & Churn OpsA4
- Signature Coordination AgentQuote-to-OrderA4
- Provisioning Trigger AgentBooking & Order ManagementA4
- Invoice Accuracy AgentBilling InterlockA4
+ 24 more on this desk
Processes at scale
AI GBS
Repeatable transaction processing run once for the whole enterprise.
Receives
Repeatable transactions handed off from every function on the same spine.
Emits
Settled transactions, a cost per unit, and exceptions back to the owning desk.
tasks 24h
50,271
in flight
1662
held
9
gates
0
- Field Completeness AgentCRM Data StewardshipA4
- Performance Obligation AgentRevenue Recognition InterlockA2
- Renewal Calendar AgentRenewals & Churn OpsA4
- Configuration Validation AgentQuote-to-OrderA4
- Document Generation AgentQuote-to-OrderA4
- Cohort Analysis AgentRevenue AnalyticsA3
+ 14 more on this desk
Human lanes
Where the conductor stops and asks a person
The conductor does not decide everything. Materiality routes a unit to a named human role, and the clock keeps running while it waits.
Function Leader
Critical
Blast radius or value beyond what any agent in this function may commit.
waiting
0
oldest
--
- Nothing waiting in this lane right now.
Process Owner
High
A policy exception inside the function, or a gate the agent is not rated for.
waiting
3
oldest
30h 59m
Approver
Medium
Routine four-eyes on a commitment the agent has already prepared.
waiting
14
oldest
15h 55m
No person required
Low
Inside the envelope. Cleared by the agent and sampled after the fact.
waiting
59
oldest
20h 59m
Walk one unit
Follow the single piece of work with the most at stake
Diagrams argue. A unit proves. Step through the actual route this unit is taking, station by station, and read the evidence written at each action.
Analysis at revenue chief review
Naomi Farouk · raised by Pierre Kaplan · $2.3m at stake · touches 338 downstream things if it goes wrong.
The route
Ingest
clearedCohort Analysis Agent handled this station and released the unit onward. Design dwell here is 7h 34m against an SLA of 8h 55m.
Owned by
Cohort Analysis Agent
Layer
gbs
Dwell vs SLA
7h 34m / 8h 55m
Evidence trail recorded so far
5 entries. Written when an action is taken, not when a station is passed.
- -1859mCohort Analysis Agent Cleared ingestevidence: Spine control pack posted, three-way evidence attached
- -1487mFunnel Diagnostic Agent Cleared model cohortsevidence: Inputs, rule version and output hash written to the evidence log
- -1115mRetention Modeling Agent Cleared diagnose funnelevidence: Inputs, rule version and output hash written to the evidence log
- -744mPipeline Velocity Agent Cleared draft readoutevidence: Inputs, rule version and output hash written to the evidence log
- -372mVP Revenue Analytics Holding at revenue chief reviewevidence: Inputs, rule version and output hash written to the evidence log
Trace a different unit
The walk above always picks the unit in revenue operations with the most at stake right now.
What this view is and is not
Every count, agent, station, gate and unit on this page is read from the live records for Revenue Operations. The moving packets in the diagram are a visual weighting of that same distribution, not a live message bus: they show where volume goes, not individual transactions in real time. The human lanes are the routing rule, not a staffing model. SVP Revenue Operations remains accountable for this function whatever the conductor clears.