What is RevOps (Revenue Operations) and why do you need it?

RevOps (Revenue Operations) is the function that looks after the system your company uses to generate revenue: the data model, the sales process, the tools and the reporting that marketing, sales and customer success share. It exists so that the three teams work from a single version of reality, and so that the number leadership sees is one you can defend.

The problem it solves

RevOps solves the situation where every team that touches revenue works with its own definition, its own reporting and its own tool, and nobody can show where the number is slipping.

In many B2B companies nobody decides this: it builds up. Marketing calls someone a "qualified lead" if they downloaded a resource and fit by sector. Sales calls someone a "qualified lead" if they accepted a meeting. Finance counts someone as a customer once they've paid the first invoice. Each definition makes sense on its own terms. The result: two people pull the report for the same month and get two different numbers.

It shows most in meetings, which get spent reconciling figures instead of making decisions. Sales says there aren't enough leads, marketing says the ones that come in don't get worked, and leadership says the forecast keeps being missed: the same problem told from three sides, and no data to settle which side is right.

RevOps doesn't solve it by getting people to agree in a room, but by writing the definitions down and making the system the only place a number comes from.

It's more than "someone who manages the CRM"

Managing the CRM is a task. RevOps is the function that decides what the CRM should hold, which process feeds it and which decisions get made with what comes out of it.

Someone who only manages the tool answers requests: add a field, build a report, set up a user. Over time the CRM grows with no logic behind it, piles up mandatory fields that get filled with any value just to be able to save, and stops being useful for the actual work.

RevOps works in the opposite direction. Before touching the tool, it asks which decision each data point has to support. If a field isn't used in any decision, it goes. If a pipeline stage describes what the seller does ("proposal sent") instead of what the buyer has done, it gets rewritten. If the real forecast lives in a parallel spreadsheet, the question that spreadsheet answers is brought into the system.

It isn't a new department that sits between sales and marketing asking for reports, either. It's what lets both teams stop chasing reports.

The four pieces of RevOps

RevOps looks after four pieces that depend on one another: the data model, the process, the tools and the reporting.

The data model

The foundation of everything else: what an account is, what a contact is, what counts as an opportunity and when it's created, when someone becomes a customer and how expansions are handled. It includes unglamorous things, such as a unique key per company so that the same account doesn't appear several times in the CRM. A one-page data dictionary, with an owner per definition, usually solves more than any dashboard.

The process

It's the path a deal takes from the moment someone decides who to contact to the moment the customer renews. RevOps writes it as buyer states, each with exit criteria that can be verified by something the customer has done: brought in the person who decides, provided a piece of information, put a date in their own calendar. That way an opportunity stops moving forward because the rep says so, and handoffs between teams stop happening verbally.

The tools

The CRM, the sequencer, enrichment, integrations and, increasingly, AI. The tool is built on top of the process, not the other way round: switching CRMs to fix a broken process produces the same problem in a more expensive tool, because the new one inherits the old process.

The reporting

The metrics you make decisions with: stage-to-stage conversion, sales cycle length, loss reasons by category, forecast. It's the most visible piece, which is why it's the one people try to fix first. That doesn't work: you can't measure a pipeline whose stages mean nothing. The order matters, and RevOps is largely the discipline of sticking to it.

When not having it starts to hurt

You start needing RevOps when the sales process that worked informally with a few people stops scaling as the team grows.

While the founder sells with one or two other people, almost everything works from memory. With the next hires, what was a shared habit turns into as many versions of the process as there are people selling. That's when you start seeing this:

• The ICP is only partly defined and isn't written down, so each new person interprets it their own way.
• Onboarding someone means having them shadow the founder, because there's nothing written to read.
• Some opportunities have sat in the same stage for months and nobody has marked them closed-lost.
• The real forecast lives in a parallel spreadsheet that only the person who built it understands.
• When an opportunity is lost, the reason is written as free text, if it's written at all, and nobody analyses it afterwards.

If you recognise several of these, the problem usually isn't effort or talent. It's that the system doesn't exist as a system. It exists as the habits of specific people. For how this shows up in the CRM, see the five signs that your CRM needs an audit.

In-house, fractional or project-based RevOps

There are three ways to have RevOps: hire someone, outsource the function on a fractional basis, or commission fixed-scope projects that build the missing pieces.

Hiring a RevOps manager makes sense when the volume justifies it and there's already a system to run. Hiring someone to build it from scratch and operate it at the same time, without knowing what comes first, usually ends in firefighting.

Fractional RevOps is the whole function without the hire. In our case it's Fractional Revenue Operations, the most embedded level of Always On: governance of the CRM and the data model, weekly pipeline review, forecast, targets, commissions and reporting to leadership. It costs from €3,500/month plus VAT, licences and tokens, with a minimum of three months. Business decisions stay with you, and when the volume justifies a hire, we help define the role and handle the handover.

Project-based, when what's missing is a specific piece and not someone to operate it every week: the ICP, data hygiene, handoffs, forecasting or CRM implementation. These are the RevOps & GTM Projects, each with a scope fixed in writing, a deliverable that works inside your stack, and an end.

All three need you to know first what's broken and in what order to fix it.

Where to start

Start by diagnosing where your process and your CRM stand today, not with a tool or a hire.

You have two ways to do it. The free one is the online self-assessment (in Spanish): twenty-eight statements about how your company sells. You tick the ones you recognise, and the method tells you where they come from and where to start. It's based on how you see things, and that's its limit: some symptoms can't be seen from the inside.

The paid one is the RevOps & GTM Diagnostic, the entry point we recommend. It applies the same method to your real data: we review the CRM, the data model and the automations, interview the people who sell, prospect and report, and deliver the confirmed symptoms with evidence, where each one comes from, what it breaks, and the priority order, with prices. It takes three weeks at a fixed €1,500 plus VAT, credited in full against the next project. If you'd rather build it in-house, the plan is still yours.

Frequently asked questions

Is RevOps the same as Sales Ops?

No. Sales Ops looks after sales operations. RevOps covers every team that touches revenue (marketing, sales and customer success) and, above all, what happens between them: shared definitions, handoffs and common reporting.

Do I need RevOps if my sales team is small?

You need the discipline before the role. With a small team, it comes down to an ICP written with verifiable criteria, stages defined by what the buyer does, and a one-page metrics dictionary. Writing it down before you grow is cheaper than rebuilding it afterwards.

What role does AI play in RevOps?

AI doesn't fix your data. It amplifies it. On a half-filled CRM it returns fluent, wrong answers that are harder to spot than an ordinary error. It's best to start with uses that don't depend on historical data, such as summarising calls or prepping for meetings, and leave aggregate analysis until the records can support it.