What is RevOps, and when does a B2B company need it?

As a company grows, marketing, sales and customer success each build their own tools, reports and ways of working. For a while that is fine. Then the numbers stop matching, handovers get lost and nobody can say with confidence what next quarter’s revenue will be. This is the problem revenue operations, or RevOps, is meant to solve.

Short answer: RevOps is the discipline of running marketing, sales and customer success on one set of processes, one set of data and one set of metrics, so that the whole path from first contact to renewal can be measured and improved. It is less about adding tools and more about removing the gaps between the teams that already exist.

RevOps, sales ops and marketing ops

	Marketing ops	Sales ops	RevOps
Focus	Marketing processes, tools and data	Sales processes, tools and forecasting	The whole revenue process, end to end
Typical owner of	Marketing automation, lead routing from the marketing side	CRM administration, quotas, pipeline reports	The shared funnel, definitions, data model and reporting
Risk when alone	Optimises leads that sales does not want	Optimises deals without seeing where leads come from	Becomes a pure admin role if it has no mandate

The three overlap. The difference is that RevOps takes responsibility for the connections between the teams, which is where most of the friction sits.

What RevOps covers

1. Process. One agreed funnel from lead to customer to renewal, with clear definitions of each stage and handover rules between teams.
2. Data. One reliable source of truth for contacts, companies and deals, with clear ownership of fields and rules for keeping data clean.
3. Systems. The CRM and connected tools set up around the process, not the other way round, with integrations that are documented.
4. Reporting and forecasting. A small set of metrics that both teams trust, and a forecast built on stage definitions and conversion data instead of gut feeling.
5. Enablement and governance. Training, documentation and a way to decide what changes in the system and when.

Signs you need RevOps

• Reports from marketing and sales do not match, and meetings turn into arguments about the numbers.
• Nobody trusts the forecast. It changes late in the quarter and depends on who you ask.
• Handovers fail. Leads sit untouched, or deals lose context when they move to another team.
• The CRM is full of workarounds, spreadsheets and fields nobody understands.
• Every new question needs a new workflow. Each request is built as a one-off instead of fitting the existing model.
• Growth makes everything harder. More people and more tools lead to more complexity, not more output.

If several apply, adding people or tools is unlikely to fix it. The foundation needs attention first.

Two lessons from our own work

Build a model, not a pile of workflows. When a new question arrives, such as “which leads should sales call first?”, the quick answer is another workflow. Over time that creates dozens of workflows nobody can explain. A better habit is to treat the new question as a parameter in a model you already have: a score, a rule or a property that can be adjusted in one place.

Decide where lifecycle lives. In B2B, a company often has several contacts at different stages. Decide whether the lifecycle stage belongs to the person or the company, and how a stage is inherited. Without that rule, reports disagree depending on how you count.

How to start

You do not need a RevOps department to begin. A practical first step:

1. Map the path from first contact to renewal, and write down each stage and each handover.
2. Agree on definitions for lead, qualified lead, opportunity and customer, together with marketing, sales and customer success.
3. Fix the data basics: required fields, duplicates and ownership.
4. Pick five metrics that all teams share, and build one report for them.
5. Name an owner with the mandate to say no to changes that break the model.

This connects directly to marketing and sales alignment and to a lead score you can trust. Treat each improvement as a small experiment so you can see what worked.

Who should own it?

In smaller companies, RevOps can be a shared responsibility with a clear lead, often someone from marketing or sales who has strong CRM and data skills. As the company grows, it becomes a dedicated role or team that reports to someone responsible for revenue, so that it is not seen as belonging to one department. The title matters less than the mandate: the owner must be allowed to set definitions that all teams follow.

When you do not need RevOps yet

• You have no stable sales process. Define the steps first.
• You are very small, with one tool and one team. A clean CRM and a shared definition of a lead go a long way.
• Your real problem is demand or the offer. Better operations will not create pipeline that is not there.

Where to start

Write down three questions your leadership team cannot answer with confidence today, for example “where does our pipeline come from?” or “what will we close next quarter?”. Each question points to a gap in process, data or reporting. If you are unsure where growth is stuck, the bottleneck quiz can help, and the Growth Acceleration trajectory covers RevOps, forecasting and process automation in more depth. For an outside view of your current setup, look at the Growth Audit.

Hear it from the people who do it

• Daan De Wever on getting control of CRM and data
• Steve Declercq on a definition library for data