Ask marketing how the quarter went and they will tell you about leads. Ask sales and you will hear about pipeline. Ask customer success and you will get a churn number. Three teams, three scoreboards, one customer, who is quietly experiencing all three handoffs as a single, slightly broken journey. Revenue operations is the unglamorous fix: stop measuring the relay runners separately and start timing the baton.

The quick version

  • What it is. Revenue operations (RevOps) puts marketing, sales and customer success under one shared funnel, one definition of the numbers, and usually one accountable owner.
  • Why it matters. Revenue rarely leaks inside a team. It leaks at the handoffs, the lead nobody follows up, the deal that oversells, the renewal nobody saw coming.
  • The core move. Agree shared definitions and a single revenue scoreboard before you touch tools or org charts. Alignment is a data problem before it is a people problem.
  • The honest caveat. RevOps is an operating discipline, not a department you can hire your way into. A new title on top of old silos just adds a layer.

The idea in depth

The traditional sales funnel was built for a clean division of labour: marketing fills the top, sales works the middle, and the customer drops out the bottom as a closed deal. That model quietly assumes the relationship ends at the sale. In subscription and renewal-driven businesses, that is exactly backwards, the sale is where the relationship starts, and most of the lifetime value is decided afterwards.

This is the argument HubSpot made when it publicly retired its own funnel. In "How the Flywheel Killed HubSpot's Funnel" (2018), Jon Dick put the structural flaw plainly: "Siloed work and poor handoff between teams are some of the biggest areas of friction in most flywheels." Co-founder Brian Halligan made the same case from the INBOUND 2018 stage, that customers are not an output you discard at the bottom of a funnel, but the very thing that powers the next turn of growth (see the keynote linked below). The reframe matters because it changes what you optimise: not three separate conversion rates, but the friction between the stages.

The practical move: draw your funnel end to end, first touch to renewal and referral, on one page, and mark every point where the customer is handed from one team to another. Those handoff lines are where your revenue is actually won or lost, and they are almost never anyone's job today.

flowchart LR
  M(["Marketing
attract & qualify"]) --> S(["Sales
convert"])
  S --> CS(["Customer success
retain & expand"])
  CS -. "referrals & case studies" .-> M
  M -. "handoff: MQL→SQL" .-> S
  S -. "handoff: closed→onboard" .-> CS
The shared funnel is a loop, not a chute, and the dotted handoff lines are where revenue leaks. Leaders Loop

Why "alignment" keeps failing, and what RevOps adds

"Sales and marketing alignment" has been preached for two decades, mostly as a culture fix: get the teams in a room, build empathy, agree to be friends. It rarely sticks, because the disagreements are usually factual, not emotional. Marketing's "qualified lead" and sales's "qualified lead" are different definitions; the CRM and the marketing platform count the same deal twice; nobody agrees what "pipeline" includes. You cannot hug your way past a data-model conflict.

RevOps treats this as a systems problem first. Stephen Diorio and Chris Hummel, in Revenue Operations (Wiley, 2022), frame it as connecting the people, processes, data and technology across the whole revenue cycle into one operating system, rather than three teams optimising their own slice. The unit of management shifts from the function to the customer's journey across functions.

The market has moved this way fast. Gartner predicted in a May 2021 announcement that 75% of the highest-growth companies in the world would deploy a RevOps model by 2025. Read that carefully: it is a correlation among fast-growing firms and a forecast, not proof that RevOps causes growth. Fast-growing companies adopt a lot of things; you should treat the prediction as a signal of where operating practice is heading, not as a guarantee on your own P&L.

Start with a definitions summit, not a reorg. Get the three team leads in a room and write down one agreed definition for each contested term, qualified lead, opportunity, pipeline, churn, expansion, and where each is measured. As we cover under recurring-revenue metrics, the moment your teams share a vocabulary for the numbers, half the "alignment" arguments dissolve on their own.

One owner, one scoreboard, the part people skip

Shared definitions get you a common language. They do not, by themselves, make anyone accountable for the gaps between teams. That is the structural piece RevOps adds: a single owner, often a RevOps lead reporting to a chief revenue officer, whose job is the end-to-end number, not any one stage of it.

"Siloed work and poor handoff between teams are some of the biggest areas of friction in most flywheels."

The risk, and the honest limitation, is cosmetic adoption. It is easy to rename the sales-ops team "RevOps," draw a new box on the org chart, and change nothing about how the teams actually decide things. If marketing, sales and CS still defend separate budgets against separate targets, a RevOps title is just a more expensive silo. The discipline only does real work when the shared scoreboard is the one that drives planning and pay, when the handoff metrics sit on the same dashboard the leadership team actually looks at.

Here's where to start: make one handoff metric visible and owned this quarter. Pick the leakiest seam, usually the marketing-to-sales lead handoff or the sale-to-onboarding handoff, put a single conversion-and-speed number on it, review it weekly with both teams present, and give one person the job of closing it. You are not building a department; you are proving the loop with one well-chosen metric.

A worked example

Consider a mid-sized B2B software company, call it Northwind. (Illustrative figures throughout; this is a composite, not a real firm.) Marketing reports a strong quarter: 1,000 "qualified" leads, target hit. Sales reports a weak one: pipeline down, blaming lead quality. Customer success is firefighting a wave of cancellations at the 90-day mark. Three scoreboards, three stories, and the board cannot tell which one is true.

A RevOps pass starts with definitions, not blame. It turns out marketing counted anyone who downloaded an ebook as "qualified"; sales only worked leads that had requested a demo. Of the 1,000 leads, perhaps 120 met the definition sales would actually act on, so marketing's "target hit" and sales's "bad leads" were both true, and both meaningless. The teams agree one definition and instrument the single handoff: of leads marketing marks ready, what share does sales accept and act on within 48 hours?

That one number, say it starts at an illustrative 38%, becomes the shared scoreboard. Marketing now optimises for accepted leads, not raw volume. The same lens on the other seam reveals the churn cause: sales had been promising a feature that shipped six months later, so customers churned at renewal. With a shared dashboard, that overselling shows up as a sales-to-CS handoff problem, not a mysterious "product churn." Nobody hired a new team. They agreed definitions, lit up two handoff metrics, and gave each an owner. That is RevOps doing its actual job.

flowchart TB
  A(["Three scoreboards:
leads · pipeline · churn"]) --> B(["Agree shared
definitions"])
  B --> C(["Instrument the
handoff metrics"])
  C --> D(["One owner per seam,
weekly review"])
  D --> E(["One revenue
scoreboard"])
The sequence that works: definitions before dashboards, dashboards before owners. Leaders Loop

Frequently asked questions

Is RevOps just a rebranded sales operations team?

No, though it often grows out of one. Sales ops optimises the sales function. RevOps takes responsibility for the whole revenue cycle, marketing, sales and customer success, and specifically for the handoffs between them. The scope is wider and the unit of accountability is the customer journey, not one team's tooling.

Do we need to reorganise to do this?

Not to start. The highest-value work, agreed definitions and one shared handoff metric, needs no new boxes on the org chart. A formal RevOps function and a CRO make the discipline durable, but proving the loop with one well-chosen metric is a better first step than a reorg that front-runs the evidence.

Is the funnel dead, then?

The linear, ends-at-the-sale funnel is a poor fit for recurring-revenue businesses, which is why the flywheel framing caught on. But "funnel" is still a useful shorthand for stages and conversion. The shift that matters is conceptual: treat retention and referral as part of the same system that feeds acquisition, rather than as someone else's problem after the close.

What's the single most common failure?

Cosmetic adoption, renaming a team "RevOps" while budgets, targets and incentives stay siloed. If the shared scoreboard does not drive planning and compensation, the alignment is theatre. The fix is to make one cross-team metric genuinely consequential before you scale the structure.

How do we know it's working?

Watch the handoff metrics, not the vanity totals. Rising lead-acceptance speed, fewer renewal surprises, and a shrinking gap between what marketing calls a qualified lead and what sales will act on are the early signs. Lagging indicators, net revenue retention, CAC payback, confirm it later.

Related in the Toolkit

Where to go next