Revenue Operations and the Ghost State

The Ghost State #

Revenue Operations tends to appear where descriptions of the business stop matching one another: between Sales and Finance, between what the CRM records and what the forecast deck implies. Between the clean narrative on a slide and the hesitation that lingers in the room when someone asks whether the number will actually land.

Depending on when you encounter it, RevOps can look like a reporting line, a tool administrator, a planning function, or simply the default destination for problems that resist categorization. In some companies it reports to the CRO and is treated as an extension of the revenue engine. In others it sits under Finance and inherits suspicion along with rigor. Occasionally it reports nowhere in particular and instead hovers across Slack threads, summoned when something fractures.

That ambiguity isn't a branding failure. It reflects the nature of the work.

RevOps is less a function than the keeper of shared reality, and shared reality inside an organization is never stable for long. Incentives pull at it. Turnover erodes it. Urgency distorts it. The shape the role takes depends on what is breaking, who benefits from the break, and how much distortion the organization can temporarily tolerate.

You don't always know which version of the job you're walking into until the conversation starts.

Three Pipeline Numbers #

I once watched a company prepare for a board meeting where three teams brought three different pipeline numbers, each generated in good faith and each capable of surviving light interrogation.

Sales had its commit, built from rep-level forecasts and a healthy amount of confidence. Marketing had its influenced pipeline, carefully attributed across campaigns. Finance had a third number derived from a model that reconciled bookings, historical conversion rates, and a set of adjustments only one analyst could fully narrate.

The disagreement didn't begin as conflict. It presented as clarification. A question about stage definitions. A note about attribution windows. A quiet recalculation in the corner of a laptop.

Within twenty minutes it became clear that the organization was operating with parallel descriptions of the same quarter. Each internally coherent. None collectively usable.

In that moment, RevOps did not look like process optimization or dashboard hygiene. It looked like arbitration. The work was to reconcile frames, not just numbers, and to bring three defensible versions of reality into one description the business could plan against without splitting itself.

Absent that collapse, the meeting would have proceeded anyway. Decisions would have been made. The fragmentation would simply have migrated downstream, where it would resurface later as surprise, blame, or revision.

Shared reality is not a philosophical luxury. It is a coordination requirement.

The Box That Changes Shape #

At other times, the function resolves into something that feels closer to memory than mediation.

A new leader arrives with a forecasting methodology imported from a previous company, presented with confidence and a few slides. It sounds contemporary. The language feels crisp. Someone pulls up an old dashboard and recognizes the pattern. The company tried this before. It failed quietly, not because the model was irrational, but because it collided with the actual behavior of the sales team at the time.

No one in the room remembers the collision clearly enough to narrate it without artifacts.

Here, RevOps becomes a custodian of context. The job is not to defend the past reflexively, nor to resist change for its own sake, but to ensure that decisions are made with an awareness of what has already been attempted and why it broke. Without that memory, iteration becomes repetition with better slides.

Under end-of-quarter pressure, the same function can feel less archival and more political. Stage criteria soften at the edges. A late-entering opportunity is granted the benefit of the doubt. Historical conversion rates are cited selectively. The math is not fabricated. It is framed.

Correcting the definition is technical. Escalating the framing is relational.^[1]

The person closest to the data can see the distortion forming in real time. Whether they can name it without losing the access that makes their role effective is another question.

The Cat in the Room #

There is a reason the function resists stable definition.

You don't know which version you need until you're inside the room.

Sometimes you walk in expecting to troubleshoot Salesforce fields and leave having mediated a dispute over what "renewal" means. Sometimes you prepare to debate stage progression and end up reconstructing why a churn metric was defined the way it was three years ago. Sometimes you think you're building a dashboard and realize you're rebuilding trust.

RevOps exists in a kind of superposition until observed. It is connective tissue, institutional memory, belief maintenance, invisible infrastructure. Only when pressure is applied does it collapse into one of those states.

That collapse is not abstract. It is political.

Shared reality is always contested. Sales optimizes for optimism. Finance optimizes for defensibility. Marketing optimizes for attribution that proves leverage. Leadership optimizes for coherence and narrative. Each function is rational inside its own frame.

RevOps sits at the boundary between those frames and attempts to maintain a description of the business that everyone can act on at once.^[2]

It does not own the truth. It maintains the conditions under which a shared version of it can survive.

Shadow Fields #

The easiest way to see where shared reality is fracturing is not in formal reports but in shadow systems.

A Salesforce instance with two fields: "Close Date" and "Real Close Date." The second created quietly by a salesperson who updates the official field during pipeline reviews but keeps a private assessment elsewhere. A churn tracker built outside the official dashboard because the official version runs two weeks behind. A spreadsheet maintained by someone in Customer Success that captures renewal risk more accurately than the CRM ever has.

These artifacts are not rebellion. They are measurements.

They capture the distance between what the system requires and what operators believe.

RevOps reads these not as compliance failures but as diagnostic signals. The question is not why the spreadsheet exists. The question is what the official system failed to provide.

Shadow systems proliferate when reporting audiences and operating audiences diverge. The CRM optimizes for management visibility. The frontline optimizes for action. When those incentives separate too far, shared reality begins to fork.

Left unattended, the forks harden.

Invisibility and Drift #

When RevOps succeeds, it disappears.

A deal desk workflow that once generated Slack threads and escalations becomes routine. A forecasting cadence that once required heavy facilitation becomes something the team prepares for without prompting. A territory model that once required arbitration simply works.

The process feels native. New hires inherit it as fact rather than as design.

That absorption is a sign of maturity. It is also a risk.^[3]

Embedded assumptions stop being examined once they stop being named. Approval thresholds set in one pricing era persist into another. Segmentation logic designed for one customer profile becomes default for a different one. Edge cases that were rare at design time become common as the company expands.

Invisibility makes systems durable. It also makes them opaque.

The keeper of shared reality has to notice when reality itself has shifted, even if the dashboard remains technically correct.

Reporting Lines and Asymmetry #

Where the function reports shapes which version of reality tends to win.

Under a CRO, it lives close to the number and risks inheriting commercial bias. Under a CFO, it inherits skepticism and distance from frontline context. Under a CEO, it absorbs cross-functional ambiguity and a steady stream of "quick questions" that are rarely quick.

I have seen companies with "RevOps" on the org chart still arrive at board meetings with three pipeline numbers. The reporting line had quietly decided whose math counted.

When shared reality holds, little is said. Board questions have answers. Handoffs feel procedural rather than adversarial. New hires learn one process instead of three conflicting ones. The system feels stable.

When it fractures, the failure is immediate and visible. Forecasts splinter. Meetings turn into reconciliation exercises. Bright people spend hours debating definitions instead of deciding what to do next.

Infrastructure that prevents visible failure is harder to quantify than visible output. When the system holds, it belongs to everyone. When it breaks, it belongs to whoever is closest to it.^[4]

That distribution of credit and blame isn't accidental. It's structural. And it shapes how much protection the function receives when priorities tighten.

The Keeper #

The constant is not the activity. The constant is coherence across time.

In any given quarter, the organization benefits from a certain amount of distortion. Optimism greases deals. Narrative simplifies complexity. A late-entering opportunity gets the benefit of the doubt. A conversion rate is cited at its best quarter rather than its median. None of this is fabricated. None of it is malicious. It is how institutions metabolize uncertainty while continuing to function, and it is happening in every room, in every company, in every quarter, whether or not anyone is naming it.

Someone, however, has to maintain a stable coordinate. A version of the business that can survive incentive pressure, turnover, and urgency without splitting into parallel truths. Not because distortion is always wrong - sometimes optimism is correct - but because without a reference point, the organization loses the ability to distinguish between a frame that is useful and a frame that has quietly become the thing itself.

You may not know what the role will need to be when you walk into the room. Some days it resolves into mediation. Other days it feels archival, or infrastructural, or quietly diplomatic. The superposition holds until pressure is applied. Only then does it take shape.

What you can know is this: without someone tending the shared description of reality across functions and across time, the system does not stay coherent. It begins to fork.

Three pipeline numbers again.

And at that point, the meeting isn't about growth or strategy. It's about which version of the quarter everyone is willing to stand inside.