RevOps, or revenue operations, is the discipline of making the systems behind your revenue work as one: your CRM, your data, your pipeline, your reporting and the handoffs between sales, marketing and delivery. The goal is revenue that's predictable because the machinery producing it is reliable, rather than dependent on who remembers what. If you're an engineer at heart, think of it as DevOps for the commercial side.
That analogy is the fastest way in, so here's the rest, plainly, without the "align, silos, revenue engine" fog most definitions leave you in.
What does RevOps actually cover?
Four areas. Strategy and alignment: getting sales, marketing and delivery pointed at the same goals with shared definitions, what counts as a lead, when it qualifies, who owns it. Technology: the CRM and surrounding tools set up so data flows instead of sitting in silos. Data and reporting: clean records, a readable pipeline, and reporting that comes straight from the system. Enablement: training and documentation so the team actually uses what's built.
Note the order. The tool comes after the design. A perfectly configured CRM running a badly designed process just makes the wrong thing happen faster.
What does it look like when it's missing?
You notice the absence as irritations, not as a gap on the org chart. The pipeline lives partly in the CRM, partly in the MD's head and partly in a spreadsheet called pipeline_v3_FINAL(2).xlsx. The forecast is an educated guess that gets less educated each quarter. Sales and marketing each hold their own version of the truth. A promising deal goes quiet and nobody notices for six weeks.
None of that means anyone's doing a bad job. It means the company grew past the point where goodwill and memory can hold the commercial side together. Every company hits this point; the only variable is how long they live with it.
Is RevOps just having a CRM?
No, and this is the most common confusion. HubSpot or Salesforce is a tool. RevOps is the design and discipline that makes the tool earn its keep. Buying HubSpot and expecting predictable revenue is like buying a lathe and expecting parts: the machine matters, but the process around it matters more.
That's why "we already have HubSpot" and "we need RevOps help" are usually both true at once.
When does a company need RevOps?
Somewhere between 10 and 100 people, usually announced by a symptom rather than a strategy meeting: a forecast that misses badly, a big deal that slipped through the cracks, or a board asking questions the CRM can't answer. If you sell B2B with a cycle measured in months, the need arrives earlier, because long cycles multiply the cost of losing track.
Below about ten people you probably don't need it; the founder holds the whole pipeline in their head, and that's fine. A rough self-test: if losing one person would take real revenue knowledge out the door, that knowledge is in heads when it should be in systems.
Who does the RevOps work?
Three options, honestly compared. A full-time hire makes sense when there's five days a week of this work, which usually means 100+ people. An agency gives you a team and breadth, best when you need marketing delivery alongside operations. A fractional operator gives you a senior person a few days a month, which fits most companies in the 10 to 100 range.
I've written a full cost breakdown and a fair comparison with agencies if you're weighing this up.
Where should I start?
By measuring, because you can't prioritise what you haven't seen. Run a free commercial systems health check: a few minutes, a score out of 100 across your CRM, pipeline, data and follow-up, and the three fixes worth doing first. Even if you take it no further, you'll have replaced a vague sense that "things are a bit messy" with an actual number.
Frequently asked questions
What's the difference between RevOps and sales ops?
Sales ops supports the sales team specifically. RevOps takes the whole revenue engine, sales, marketing and delivery, and makes their systems and data work as one. RevOps is the broader remit.
Do small businesses need RevOps?
Below about ten people, usually not, the founder can hold the pipeline in their head. The need arrives as you grow past that, especially with long B2B sales cycles where losing track is expensive.
Is RevOps the same as HubSpot?
No. HubSpot is a tool; RevOps is the design and discipline that makes any CRM earn its keep. You can own HubSpot and still need RevOps, and often do.