Operations Consulting
Operations consulting, applied to revenue, is the work of fixing how marketing, sales, service, finance, and IT operate as one system instead of as adjacent departments. Each function usually runs well internally. The losses concentrate in the spaces between them: the handoff where a lead waits for follow-up, the queue where a campaign waits for creative, the report that finance and marketing compute differently. None of those losses appear on any single team's dashboard, which is why they persist while every team reports green.
How it actually works
Inside a function, work is managed: it has an owner, a metric, and a deadline. Between functions, work sits in queues nobody owns. A lead generated on Monday and called on Friday costs the same to produce as one called in five minutes and converts at a fraction of the rate. The loss occurs in the handoff, after production.
The standard organizational response compounds this: each function receives targets for its own stage, and each optimizes its stage regardless of the effect on the next one. Marketing reaches a lead-volume target by loosening quality, sales spends its time disqualifying, and both teams hit their numbers while revenue misses the target. Each metric is local, and the failure appears only at the system level.
The operational fix is to design the system end to end: map the path from first touch to revenue, find the queues and the conflicting local targets, and replace them with handoffs that have owners and metrics shared across the boundary. Teams that move fluidly across channel barriers and function as a single system for revenue work inside a structure built to allow it. The treasury argument prices the fix: lead-to-cash days multiplied by daily revenue is the cash tied up in the funnel, which makes queue time working capital. Compressing a handoff releases that cash the same way compressing days sales outstanding does, so a cycle-time reduction belongs in front of the CFO as a working-capital release rather than in front of a single function as a process improvement.
In practice
At Old School Labs, revenue grew 87% in ten months. Part of that came from operational work rather than new spend: shortening the path between insight and action, so research findings changed the ads and offers within days instead of quarters. At 1-800 Contacts, the chat support team was handling two simultaneous conversations plus email, working 50 to 60 hours a week on overtime, and still missing SLAs. The metric everyone watched said capacity; the constraint was cognitive load. Sophie Leroy's research on attention residue (Organizational Behavior and Human Decision Processes, 2009) found that part of attention stays stuck on a task you leave unfinished, and Rubinstein, Meyer, and Evans (Journal of Experimental Psychology: Human Perception and Performance, 2001) found switching costs climb as the rules governing each task get more complex. The fix was specialization. Chat handle time dropped from 7 minutes to 3.5, email handle time from 10 minutes to 1, overtime was eliminated, SLAs were met, and volume decreased because duplicate contacts stopped. Over $250,000 in annual costs came out with no layoffs, no new hires, and no new tools. The case is documented in [the cost of multi-tasking](/insights/why-strategic-initiatives-fail#the-cost-of-multi-tasking).
Where we come in
We help teams move fluidly across channel barriers and operate as a single system for revenue, and we train them to keep finding profitable opportunities after we leave. We have built these systems for businesses from new startups to the Fortune 15, including revenue systems work with Digital Realty and Equinix.
Start a Revenue Health Pre-Assessment →See it in action
Related terms
- Handoff
- The transfer of work between functions: lead to sales, brief to creative, closed deal to service. The point where speed and context are most often lost.
- Queue
- Work waiting between owners. Queue time is invisible in functional metrics because each function's clock only runs while the work is inside it.
- Cycle time
- The elapsed time from start to outcome across the whole system, including waiting time. Queue time appears in this number and in no functional dashboard.
- Shared metrics
- Metrics owned across a boundary instead of inside one function, so neither side can win by exporting cost to the other.
- RevOps
- The function that operates revenue as one system: one data model, one process map, one set of numbers from first touch to renewal.