The RevOps Land Grab

(Was this newsletter forwarded to you? Sign up here.)

The number that ends your quarter was defined by someone who does not report to you.

Consider what one timestamp can do. Move the point in the CRM where a lead officially becomes an opportunity, push it a single stage later in the funnel, and marketing's lead-to-opportunity conversion rate falls. Same leads, same campaigns, same spend, different math. Nobody records that as a strategy decision, because on the ticket it is data cleanup. It arrives in the pipeline review as a cut to marketing's scoreboard, and marketing tends to find out the way it finds out about most of these changes, once the number is already on the slide.

Ten years ago, the function that made that change did not exist at most companies. Now it owns attribution, funnel stage definitions, lead routing, and forecasting across a large share of B2B. Gartner predicted that 75% of the highest growth companies in the world would run on a revenue operations model by 2025 (Gartner). In LinkedIn's 2023 ranking of the fastest-growing jobs in the United States, Head of Revenue Operations came in first (LinkedIn). That is a power center forming, not a support function scaling up.

Most CMOs waved it through. They treated RevOps as plumbing, a welcome offload of dashboards and CRM tickets nobody wanted to own. They discovered later that they had handed over the one thing that decides whether their team looks like it is winning.

How it happened

Start with where the data lives. The CRM is the system of record, and the CRM sits closer to sales than to marketing at almost every company. Whoever administers those objects controls what counts as a lead, when a lead converts, and which touch gets credit. Marketing ops rarely fought for that ground. It stayed small, stayed tool-focused, spent its headcount tuning the marketing automation platform and building campaign reports, and left the connective tissue between systems unclaimed. RevOps walked into that vacuum and took the connective tissue, which turned out to be the part that matters.

Then the board bought a story. The single source of truth is one of the most seductive pitches in enterprise software, because it sounds like rigor and costs nothing to endorse. One team, one number, no more arguing about whose dashboard is right. CFOs love it. Boards love it. A single source of truth has a single owner, and the owner decides what the truth is.

Add the SDR consolidation. As outbound and inbound development teams got folded under revenue operations for reporting, RevOps picked up the top of the funnel, the exact seam where marketing hands work to sales. Own that seam, and you own the conversion rate that defines marketing's contribution. None of this required a coup. It required marketing to be busy, tactical, and grateful for the help.

The mechanics of the transfer

Power in this arrangement does not move through org charts. It moves through four settings, and each one is a judgment on marketing rendered outside marketing.

Stage definitions. The words "MQL," "SQL," and "opportunity" feel like shared vocabulary. They are configuration. Move the boundary between stages by one field or one timestamp and marketing's numbers move with it, up or down, without a single campaign changing.

The MQL-to-SQL gate. This is the tollbooth between the work marketing pays for and the pipeline sales claims. Whoever sets the passing score sets marketing's yield. Tighten the criteria and marketing generates fewer qualified leads on the same spend. Loosen them, and marketing looks generous while sales complains about junk. Either way, the dial is in someone else's hand.

Attribution model selection. First touch flatters demand gen. Last touch flatters the SDR call and the sales rep. Whoever picks the model picks the winner. Choosing the model is usually a visible fight, though, and a CMO who loses that one at least knows she lost it. The quiet damage sits a layer underneath, in the settings that feed the model you already agreed to. The lookback window. Which touch types get written to the source field at all. Whether an offline conversion arrives stamped with an origin or arrives blank. Change those and the agreed model reports a different answer next quarter, and nobody has to reopen a decision you were part of.

Forecasting. This is the quiet one. When RevOps owns the forecast, marketing's number is an input the CRO's team assembles, adjusts, and presents. Marketing does not walk its own contribution into the board meeting. Someone else carries it, and they carry the version that serves their story.

Whoever writes the definition of a qualified lead writes marketing's performance review.

The three responses

There are only three moves here, and most CMOs make the third one by accident.

Annex. Bring RevOps under the CMO. This is the cleanest fix and the hardest to pull off. It requires a credible operations leader who can hold the CRM, the forecast, and the data model against a CRO who will fight to keep them, and it requires a CEO willing to settle that fight in your favor. Few marketing orgs have that operator on the bench, and hiring one signals to the whole company that you intend to run revenue, not just demand. The cost is political capital spent up front and a rival made permanent. When it works, marketing owns its own scoreboard for the first time. When it fails, you have declared a war you cannot win, and everyone saw you lose it.

Ally. Co-own the definitions through a written charter. This is the realistic play for most companies. You do not need to control RevOps. You need a documented agreement on how stages are defined, which attribution model is used, who can change the MQL-to-SQL gate, and what notice marketing gets before any change ships. Five clauses do the work. Stage definitions move only with sign-off from both the CMO and the CRO. The MQL gate has one named owner and a two-week notice period before any change ships. The attribution model gets reviewed once a year, in planning season, never mid-quarter. Any CRM field change that touches marketing's funnel is flagged to marketing ops before it deploys. And the board forecast carries marketing's contribution as marketing wrote it. Put it in writing, review it every planning cycle, and make sure no field that touches marketing's number moves without marketing in the room. This costs less blood than annexation and gives up the fantasy of full control, which you were not going to get anyway. Its weakness is that a charter is only as strong as the CEO who enforces it. If revenue definitions are treated as neutral operations rather than a shared governance question, the charter becomes a document nobody reads.

Abdicate. Do nothing, which is the default. Let RevOps own the definitions because they are good at it and the dashboards are finally clean. Here is what that looks like two years later. Marketing's conversion rates drift down through a series of hygiene fixes nobody flagged as strategic. The attribution model shifts toward the channels sales controls. The board sees a marketing function that generates volume and questionable quality, and it sees a revenue operations function that turns raw leads into forecast, which sounds a lot more like the thing that makes money. Budget follows that story. The CMO who abdicated did not lose an argument. She was never in the argument. The head of RevOps who set her numbers reported up through the CRO and had never once sat in a marketing planning meeting.

The structural point

This is the same fight I have written about with the CFO, where the person who owns the model owns the budget (Behind the CMO). RevOps is that pattern moved one layer down, into the operational definitions marketing treated as too boring to defend.

The trap is thinking of RevOps as a service. It is a service the way the referee is a service. Technically neutral. Structurally decisive.

You do not have to own the whistle.

You do have to be in the room when they write the rules.