Revenue Is Not a Sales Problem

Most companies say they care about growth. Then they hand revenue accountability exclusively to Sales and wonder why the number is always at risk.

Revenue is a company sport. When you treat it like a department sport, you get a company that is structurally unable to grow efficiently.

I've spent years in RevOps sitting at the intersection of Sales, Marketing, Customer Success, Finance, and Product. What I saw from that seat was consistent: the biggest revenue leaks had nothing to do with pipeline. They happened after the contract was signed.

The number that actually tells you if your business works

New ARR gets all the attention. It's the number on the board, the one Sales celebrates, the one investors ask about first. But net revenue retention — NRR — is the number that tells you whether your business model is actually working.

As a refresher: NRR above 100% means your existing customers are expanding faster than they're churning. Below 100%, you're running a leaky bucket. You can keep pouring new ARR in, but you will never outrun the drain.

The problem is that NRR doesn't belong to any single team, it belongs to everyone. In most companies, that means it belongs to no one. Customer Success gets measured on renewals and GRR. Product gets measured on releases. Finance gets measured on forecast accuracy and managing the budget. Nobody wakes up in the morning owning the gap between what customers contracted and whether they actually get value.

That gap is where companies quietly bleed.

What RevOps taught me that leadership often misses

When you sit in RevOps, you see things the org chart hides. You see that the deal that closed at the wrong discount becomes the churn risk six months later. You see that the handoff from Sales to CS is where customer expectations get lost. You see that the renewal conversation happens too late because nobody owns the early warning signal.

You also see that these are not people problems. They are system problems. They happen at the seams — the places where accountability ends on one team and doesn't clearly start on another.

Leaders often mistake seam problems for communication problems. They schedule more cross-functional meetings, they create shared Slack channels, and they run alignment offsites. None of it works as expected, because the underlying incentive structures haven't changed. If CS isn't measured on expansion, expansion won't happen consistently, regardless of how aligned the kickoff meeting felt.

What it looks like when it works

The companies I've seen do this well have a few things in common.

Revenue accountability is explicit and shared. That doesn't mean everyone has the same quota. It means Finance owns the financial model, CS owns the relationship risk, Product owns the adoption signals, and all of them have a shared view of NRR with actual consequence attached to it. The COO's job — or whoever is running the operating model — is to make that accountability real, not theoretical.

The handoffs are designed, not assumed. Who owns the customer from contract through onboarding through first renewal? In most companies, that answer changes two or three times, and each transition is an opportunity to drop the thread and expose the seams. The companies that retain well have mapped every handoff with explicit owners and escalation paths.

And the leading indicators are tracked upstream. By the time a customer churns, the warning signs were there months earlier — low adoption, no expansion conversation, support tickets piling up. Companies that grow efficiently have built systems to catch those signals before they become losses.

Why it doesn't get fixed

The reason most companies don't fix this isn't ignorance. It's that changing revenue accountability means changing how people are measured and compensated, and that is a deeply political conversation. Nobody wants to tell CS they now co-own a number, or tell Sales that their quota doesn't tell the whole story. The COO who can have that conversation — and build the model that makes it real — is the one who actually moves the business.

Why this is a COO problem

It's why I'm increasingly drawn to operating model problems, the work that sits at the COO level, where strategy and execution have to meet. And one thing I keep coming back to is this: the COO's job is to make the operating model match the strategy.

If your strategy is efficient growth — and in this environment, it has to be — then your operating model needs to treat revenue as a company-wide discipline, not a department. That means resetting how you measure, how you structure incentives, and where you draw the lines of accountability. If this creates discomfort in your organization, that's the accountability gap making itself known.

It is not a Sales problem. It is not a CS problem. It is a leadership problem.

The companies that figure this out stop asking "why is Sales missing the number" and start asking "why does our model require us to win new customers to offset the ones we're losing?"

That is a much more uncomfortable question. It is also the right one.

Revenue retention isn't a metric. It's a mirror.