Revenue operations is about getting marketing, sales and customer success to speak the same language, not about tidying a CRM. The foundation is laid in three layers, in this order: written definitions, reliable data with a single source of truth, then a few metrics followed seriously. Until the layer below is solid, the one above lies with confidence.
Most teams we meet do not steer their growth, they endure it. They have dashboards, pipeline meetings, numbers circulating. But scratch the surface and nobody agrees on what “qualified opportunity” means. The problem is not a lack of tools, it is the absence of a foundation.
RevOps is not a tidy CRM
RevOps is often confused with administering the tool. Tidying the CRM is necessary, but it is not the point. Revenue operations is about getting three functions that otherwise count separately, marketing, sales and customer success, to speak the same language.
Without that foundation, every decision becomes a negotiation of opinions.
- The forecast is fiction. Reps inflate or sandbag, for lack of a shared definition of the stages.
- Attribution is an endless argument. Marketing claims deals that sales believe they closed alone.
- Churn arrives as a surprise. Nobody was watching usage signals, because nobody had decided which ones mattered.
The real cost of this is not the time spent reconciling numbers, considerable though that is. It is that trade-offs get made on intuition, and a company that allocates on intuition ends up funding whatever tells the best story in a meeting.
Three foundations, in this order
A useful foundation is not built by stacking dashboards. It is laid in layers, and the order is not negotiable.
First layer, definitions. What is a lead, a marketing qualified lead, an opportunity, a won deal? At exactly which moment does an opportunity change stage, and on what observable fact? These definitions get written, validated with all three teams, and are not reopened afterwards. It is the cheapest layer and the one most often skipped.
Second layer, reliable data. A single source of truth, named explicitly when several tools claim the title. Mandatory fields at the key moments of the journey, chosen sparingly: every unnecessary mandatory field is a field filled in carelessly. And a data hygiene held over time, which means someone has to be accountable for it.
Third layer, metrics. Few, but followed seriously: conversion rate by stage, cycle length, acquisition cost, net retention, pipeline coverage. Five numbers looked at every week beat thirty available and consulted by nobody.
Until the layer below is solid, the one above lies. A beautiful dashboard sitting on dirty data produces wrong decisions with great confidence, which is the worst of both worlds.
The trap of premature sophistication
We regularly see teams wanting multi-touch attribution, predictive scoring or artificial intelligence on the pipeline before they have properly defined their sales stages. That is fitting a racing engine to a chassis with no wheels.
Sophistication never compensates for a missing foundation: it makes it worse, by giving an illusion of rigour. An attribution model fed inconsistent data produces budget allocation recommendations nobody can challenge, because nobody understands where they came from. The argument of opinions was less dangerous.
Start simple. An accurate table beats a brilliant model fed by doubtful data.
The five questions that decide the rest
Our entry point is never the tool, it is the decision. Ask your leadership team this: what are the five questions we must be able to answer every week, without a preparatory meeting?
The answers usually look like this. Do we have enough pipeline to make the quarter? Where do deals stall? Which channels produce customers who stay, rather than leads that get counted? Which accounts are slipping? And what does acquiring a customer actually cost on each segment?
From those five questions follow the required metrics, then the data to collect, then and only then the tool configuration. In that order, a foundation takes a few weeks. In the reverse order it never finishes, because there is no criterion for stopping.
What the foundation makes possible
The first effect is the most immediate: meetings change in kind. People stop arguing about the numbers and start discussing what to do about them. That is also what lets a pipeline review serve decisions rather than information gathering.
The second effect is on prospecting. Clean data is the precondition for targeting triggered by observable events, the subject of signal-based selling: without accounts correctly linked, an alert is an alert with no recipient.
The third is on pricing. Knowing how your customers actually consume is the raw material of every tariff decision, particularly in models where the invoice follows usage, as we detail in usage-based pricing.
The Arkimoz method
We start from your decisions, not your tools. We work back from the five questions to the required metrics, then to the data to collect, and only then to the configuration. Never the other way round.
We then deal with the one thing that makes a foundation last: accountability. A mandatory field with nobody answering for it empties within three months. That is why revenue operations is an organisational decision as much as a tooling one, and we treat it as such inside the wider framing described in building a go-to-market plan.
The result is not another dashboard. It is an organisation where “we think that” gives way to “we know that”. Only from there does steering become possible.
Frequently asked questions
- What is RevOps?
- Revenue operations is the function that aligns the data, processes and tools of the three teams that touch revenue: marketing, sales and customer success. Its deliverable is not a dashboard, it is the company's ability to answer the same questions with the same numbers, whoever pulls them.
- What is the difference between RevOps and Sales Ops?
- Sales Ops serves one team: it tools, documents and measures the sales function. RevOps covers the whole revenue chain, from first visit to renewal, and its main object is consistency between teams. In practice many companies start with Sales Ops and extend it when disagreements between teams become expensive.
- At what size do you need a RevOps foundation?
- Definitions and a single source of truth are worth having from the first sales team onward, because they cost almost nothing to set up early and a great deal to retrofit later. A dedicated role is justified later, usually when three distinct teams touch the same account and meetings are spent reconciling numbers.
- How many metrics should you track?
- Five are enough in most companies: conversion rate by stage, sales cycle length, customer acquisition cost, net revenue retention, and pipeline coverage against target. Beyond that, attention scatters and nobody really looks at any of them.