Process Ownership and Revenue Leakage: A Taxonomy and Measurement Protocol
August 1, 2026
ABSTRACT
Process steps without a single accountable owner are a common structural defect in revenue operations, and their cost is largely invisible because nothing fails — work waits, and no event is generated. This paper connects the sales–marketing integration literature to that mechanism, sets out a taxonomy of four ownership states, and provides a measurement protocol an organisation can run against its own data in a week.
Organisations measure what fails. An outage is recorded, a lost deal categorised, a missed target explained. What is not measured is work that simply stops — a step nobody owns, waiting for a person who does not know it is waiting for them.
This paper argues that unowned process is a common structural defect in revenue operations, that its cost is systematically invisible in event-driven reporting, and that it can be measured directly.
1. What the integration literature establishes
Rouziès and colleagues [1] set out a framework for sales and marketing integration, distinguishing the mechanisms through which the two functions are connected — structure, process, culture and shared information among them. The framework's relevance here is that integration is treated as something designed, with identifiable mechanisms, rather than as a quality of relationships between teams.
Kotler, Rackham and Krishnaswamy [2] describe a progression in how sales and marketing relate, from undefined relationships through to fully integrated ones, and characterise the undefined state as one in which the boundary between the two functions has never been articulated. An undefined boundary is precisely the condition in which a step at that boundary has no owner: each function assumes the other holds it.
The core claim
2. Four ownership states
Each state produces a different symptom. Only the first is recoverable through normal escalation.
| State | What happens | Visible as | Detection |
|---|---|---|---|
| Single owner | Work proceeds; delays escalate | A late task with a name on it | Normal reporting |
| No owner | Work waits indefinitely | Nothing — no event is generated | Elapsed-time measurement only |
| Multiple owners | Contradictory action, silent overwrites | A dispute when it breaks | Configuration conflict |
| Nominal owner | Name recorded, no authority or visibility | A map that says the step is covered | Direct questioning |
Source: Taxonomy proposed in this paper
Single owner — one accountable party. Work proceeds; failure is visible and escalable.
No owner — work stops silently. Nobody is late, because nobody was responsible for being on time.
Multiple owners — contradictory action, silent overwrites, and a dispute when it breaks. Operationally equivalent to no owner.
Nominal owner — a name is recorded, but that person has neither the visibility nor the authority to act. The most dangerous state, because the map says the step is covered.
3. Why the cost is invisible
Standard revenue reporting is event-driven: a deal is won or lost, a renewal closes or does not, a ticket is opened and resolved. Unowned work produces no event. A renewal that lapses without ever being worked is recorded as churn with no cause. A lead that sits in a default queue for six days is recorded as a lead that did not convert.
In each case a real number moves and the recorded explanation attributes it elsewhere — product fit, lead quality, market conditions. The organisation then invests against the recorded explanation.
Redman's account of data quality costs [3] describes an analogous dynamic: the costs are real and distributed across operational and strategic decisions, but they are not booked as a line item and are therefore not managed.
4. Where gaps concentrate
Consistent with the integration framework [1], gaps cluster at boundaries — the points where responsibility is assumed rather than assigned.
Handoffs between functions: marketing to sales, sales to onboarding, onboarding to customer success
Steps executed by systems, where automation is assumed to have made ownership unnecessary
Exception paths — what happens when the normal route does not apply, which is where the expensive cases live
Recurring obligations with no trigger, of which renewals are the costliest example
5. Measurement protocol
Runnable by one person in about a week, producing a figure specific to your organisation. It deliberately requires no external benchmark, because a benchmark drawn from another company's operating model is not evidence about yours.
Runnable by one person in about a week against data the organisation already holds.
Enumerate
Map current-state steps for one revenue-critical flow, including workarounds.
Classify
Assign each step one of the four ownership states. Test nominal owners with two questions.
Instrument
Median elapsed time, trigger to completion, for owned versus unowned steps.
Convert
Cycle-time cost and leakage cost, computed from your own opportunity values.
Source: Protocol proposed in this paper
Step 1 — Enumerate the steps
Map the current-state process for one revenue-critical flow: inbound lead to closed opportunity, or signature to renewal. Record what actually happens, including workarounds, at the level where each step has a distinct trigger and completion.
Step 2 — Classify ownership
Assign each step one of the four states. Test nominal ownership with two questions to the named person: how would you know this step was late, and what would you do about it? If either answer is absent, the state is nominal.
Step 3 — Instrument the gaps
For each unowned or nominally owned step, measure median elapsed time from trigger to completion over the last complete quarter. Measure the same for steps with a single owner. The difference is your ownership cost, in time.
Step 4 — Convert to money
Cycle-time cost: additional days multiplied by your own opportunity value and pipeline volume gives deferred revenue.
Leakage cost: obligations that lapsed entirely — unworked renewals, unapplied escalators, unbilled usage — counted directly from your records.
On benchmarks
6. Remediation
Assign a single accountable owner to every step. A person, not a team.
Give every step a failure path: how the owner learns it is late, and to whom it escalates.
Instrument boundaries first — they produce the largest gaps and the least visibility.
Re-measure after one quarter. The elapsed-time difference from Step 3 is the metric that should move.
7. What this does not claim
Ownership is necessary and not sufficient. A well-owned process can still be badly designed or under-resourced. Nor does the cited literature quantify the cost of unowned steps — it establishes that integration is a designed property with identifiable mechanisms [1], that undefined relationships between functions are a recognised state [2], and that distributed, unbooked costs of this kind persist unmanaged [3][4].
The claim defended here is narrower: that a share of losses currently attributed to product, price or market is attributable to steps nobody owned, and that the share is measurable rather than a matter of opinion. An organisation that has not measured it does not know which it has.
Get Process Ownership and Revenue Leakage: A Taxonomy and Measurement Protocol as a print-ready PDF.
Includes the full reference list. One form unlocks every paper and template on the site.
COMMON QUESTIONS
- Why is unowned process expensive if nothing breaks?
- Because the failure mode is waiting rather than erroring. An unowned step generates no exception, no alert and no ticket, so the cost accrues as elapsed time that no system reports.
- What are the four ownership states?
- One owner, no owner, two owners, and a nominal owner who is named but has neither visibility nor authority. Two owners and no owner fail identically in outcome; the nominal owner is the most dangerous because the map says the step is covered.
- How do you measure the cost of an unowned step?
- Instrument elapsed time at the step, compare against steps with clear ownership, and convert the difference to money using the value of the work waiting. The protocol in this paper runs against existing timestamps.
- Where do ownership gaps concentrate?
- At function boundaries — where a step's inputs come from one team and its outputs go to another. That is also where they are hardest to see, because each side reasonably believes the other holds it.
KEY TERMS
Data Governance
The rules determining who may change what, how changes are reviewed, and how they are recorded. The control that stops a designed system from drifting back to whatever it was before.
Escalation
The defined path by which an at-risk account or unresolved issue is raised to people with authority to act.
Handoff
The transfer of an account or opportunity between teams — marketing to sales, sales to onboarding, onboarding to customer success.
Revenue Leakage
Revenue the business had already earned the right to collect but does not, through process gaps rather than lost deals — unbilled usage, missed renewals, unapplied price increases, discounts that outlive their approval.
Revenue Operations (RevOps)
The function that owns the systems, data and process connecting marketing, sales and customer success, so that revenue is produced by a designed system rather than by four teams improvising in parallel.
WHERE THIS HAS BEEN APPLIED
Client work and research from RevOps HQ, our consulting practice.
REFERENCES
- [1]Rouziès, D., Anderson, E., Kohli, A. K., Michaels, R. E., Weitz, B. A. & Zoltners, A. A. (2005) Sales and Marketing Integration: A Proposed Framework Journal of Personal Selling & Sales Management, 25(2), 113–122 link
- [2]Kotler, P., Rackham, N. & Krishnaswamy, S. (2006) Ending the War Between Sales and Marketing Harvard Business Review, July–August 2006 link
- [3]Redman, T. C. (1998) The Impact of Poor Data Quality on the Typical Enterprise Communications of the ACM, 41(2), 79–82 link
- [4]Payne, A. & Frow, P. (2005) A Strategic Framework for Customer Relationship Management Journal of Marketing, 69(4), 167–176 link
Put this into practice: RevOps Audit
The course walks through the same material with the interactive audit tools.
See the course