What Is Revenue Operations, and Does Your Company Need It Yet?

Revenue operations, usually shortened to RevOps, is the business function that aligns sales, marketing and customer success around shared data, processes and goals. In practice it is the team, or the single person, who decides what a lead is, where it goes next, and how the numbers are counted.

The idea exists because each revenue team tends to build its own tools, definitions and reports. Marketing counts form fills, sales counts meetings, customer success counts renewals, and nobody can trace one customer across all three. RevOps takes responsibility for the seams between those teams rather than for any one team's output.

HubSpot describes the function in four parts: operations (standard workflows and automation across the customer lifecycle), enablement (training and materials), insights (KPI definitions, reporting and forecasting) and tools and technology (the CRM, marketing automation and analytics stack). That is a reasonable map, though the weight of each part differs by company.

The practical test of ownership is who gets the call when something breaks. If a lead is routed to the wrong rep, a lifecycle stage changes for no visible reason, or two dashboards disagree on pipeline, RevOps is the team that finds the cause. It owns the system, not the individual deal.

The fully centralised model puts one RevOps team in front of sales, marketing and customer success, with a single head who reports into the revenue leader. A partially centralised model pulls only some work together, such as CRM administration or forecasting, while marketing operations and customer success operations keep some independence. HubSpot's guide says partial centralisation is where most companies start, and suggests beginning with one senior RevOps hire and growing the team as complexity rises.

In our view, for a company under about fifty people, the useful shape is usually one owner of the CRM and reporting with authority to say no to a new field or a new tool. A committee with no owner reproduces the problem it was formed to fix. An outside partner can fill the role for a period, provided the CRM stays in your account and the documentation stays with you.

You need it when the cost of disagreement exceeds the cost of fixing the system. The signs are specific: leadership meetings spend their time debating whose number is right, leads sit untouched between marketing and sales, nobody can say how many opportunities came from a given source, or a reporting question takes a week of spreadsheet work to answer.

You probably do not need a formal function if there is one person selling, a short sales cycle and a CRM you can read in a single screen. The overhead of process would outweigh the benefit. Tidy the CRM, write down your stage definitions, and revisit when a second team or a second tool arrives.

Begin with definitions, because every later project depends on them. Write one sentence each for lead, marketing-qualified lead, sales-qualified lead, opportunity and customer, name an owner for each, and enter them in the CRM as lifecycle stages. Agreement on these terms costs nothing and removes most of the arguments.

Then fix routing and visibility. Every new lead should have an owner and a timestamp for first contact, and one report should show lead source through to closed revenue using the agreed stages. Illustrative example: if a form fill creates a contact with no owner on a Friday evening, the first fix is an assignment rule and an alert, not a new tool. Only after that is it worth cleaning duplicates, consolidating integrations or building forecasting.

Sales operations supports the sales team: quotas, territories, deal desk and forecasting. Marketing operations supports campaigns: email platform, forms, scoring and attribution. Each serves one team's workflow. RevOps sits across them and owns the shared layer, which is the customer record, the lifecycle and the reporting.

The distinction matters when you hire. A person who is excellent at campaign automation is not automatically the right owner of pipeline definitions, and the reverse also holds. Decide first whether your gap is inside a team or between teams. If it is between, that is the RevOps problem.