What revenue operations should own, and what it should hand off
Revenue operations collects work. Anything that touches revenue data and has no obvious owner lands there: a report request, a broken field, a territory dispute, a question about a commission check. Each one is reasonable on its own. Together they turn the team into a help desk for the whole go-to-market org, and the work only RevOps can do gets done last.
The fix is to decide on purpose what the team owns, and to hand the rest to a named owner on the other side. Here is where I’d draw the line.
Own the definitions
Someone has to decide what counts as a qualified opportunity, a booking, an active customer, and churn, and where each stage starts and ends. Those definitions need one owner and one written home, and every report should read from them.
If marketing, sales, and finance each calculate pipeline their own way, the company doesn’t have a pipeline number. It has three opinions. This is the one job RevOps can’t hand off, because no other team sits across all of them.
Own the handoffs between teams
Each team owns its own stage of the funnel. Nobody owns the gap between two stages unless someone is assigned to it. That gap is where leads sit unworked, closed deals reach onboarding without context, and renewals surprise the account manager.
Routing rules, response-time targets, and the fields that carry context from one team to the next belong to RevOps. So does measuring them. A handoff nobody measures slows down quietly.
Own the system design, not every request
The CRM’s structure needs one owner: objects, stages, required fields, validation rules, and who can change them. Routine admin work can be shared. Design decisions can’t, because a field added for one team changes the reports of every other team.
Report requests are different. A team that builds every one-off pull never gets to the analysis that changes a decision. Build a small set of dashboards people trust, make self-serve the default, and spend the time saved on questions nobody else can answer.
Hand off the decisions
Quotas, territories, comp plans, and pricing belong to the leaders accountable for the results, usually with finance in the room. RevOps should build the models behind them: capacity, coverage, funnel math, and the trade-offs between options.
When RevOps makes the call itself, it inherits every argument about it, and its analysis stops looking neutral. Commissions work the same way. RevOps can supply the attainment data, but the payout and the controls around it belong with finance.
Keep the logic, share the plumbing
Where a data engineering team exists, ingestion, the warehouse, and job scheduling belong there. RevOps keeps the business logic: how a booking is defined in SQL, how accounts map across systems, and what counts as a match in a reconciliation. In a smaller company RevOps often runs both, which works as long as the logic is written down well enough to move later.
A simple test helps with each new request: would it break if every team ran its own version? If yes, it’s RevOps work. If it has a natural home somewhere else, hand it over cleanly, with the data and the documentation, and send the next request to its new owner.