Key Takeaways: Revenue operations (RevOps) is the function that aligns your sales, marketing, and customer success teams under one system of data, processes, and technology. For founder-led B2B businesses, it is a worthwhile investment — but only after the underlying commercial model is sound. Building RevOps on top of a broken model does not fix the model. It just makes the broken parts run in an organised way.
Revenue operations is one of those terms that has become ubiquitous in B2B circles without getting any clearer. Founders hear it from their advisors, their investors, and every SaaS vendor trying to sell them a platform. Then they try to pin down what RevOps actually does, who owns it, what problem it solves, and whether a business at £3M to £10M revenue needs it — and the answers get vague fast.
This guide cuts through that. If you run a founder-led B2B business and want to understand revenue operations from a commercial standpoint — not a software vendor’s standpoint — you are in the right place.
Phil Pelucha has worked inside and alongside RevOps functions at businesses ranging from 20-person founder-led firms to PE-backed portfolios with more than £20 billion in assets under management. A pattern Phil identified across multiple diagnostic engagements: founders arrive wanting RevOps when what they actually need first is a working commercial model.
Table of contents
- What is revenue operations?
- What does RevOps actually do?
- Revenue operations vs sales operations
- The three pillars of a RevOps function
- Who actually needs RevOps?
- The problem most founder-led businesses miss
- How to build RevOps the right way
- Frequently asked questions
What is revenue operations?
Revenue operations (RevOps) is the function that aligns a business’s sales, marketing, and customer success teams under a shared system of data, processes, and technology — with the goal of generating predictable, scalable revenue.
Each of those three teams typically runs its own tools, tracks its own metrics, and holds its own version of what a good customer looks like. RevOps creates a single operational layer that connects them. It owns the CRM, the reporting, the pipeline visibility, and the handoff processes that move a prospect from marketing interest to signed contract to expanded account.
According to Salesforce’s State of Sales research, businesses that have aligned their revenue-generating teams under a RevOps model report 19% faster revenue growth and 15% greater profitability than those operating in silos. That gap comes from the 20 to 30 percent of potential revenue that most B2B businesses lose to operational friction — duplicate work, inconsistent lead qualification, poor handoffs between teams, missed expansion revenue.
RevOps exists to close those gaps. Not through heroics. Through structural alignment.
What does RevOps actually do?
A RevOps function has clear ownership across four areas.
Data and reporting. RevOps owns how revenue data is captured, stored, and reported. CRM hygiene. Dashboard design. Ensuring leadership can see an accurate picture of pipeline health without pulling numbers from three different spreadsheets.
Without this ownership, most B2B businesses make commercial decisions on data that is anywhere from 30 to 90 days stale. That is not a technology problem. It is an ownership problem.
Process design. RevOps designs and maintains the processes that govern how leads move through the funnel. Who qualifies a lead? At what stage does marketing hand off to sales? What triggers a renewal conversation? What happens when a deal stalls at the proposal stage?
These handoffs are where most B2B businesses haemorrhage revenue. A deal that goes quiet because no one owns the next step is not a salesperson problem. It is a process problem.
Technology and tools. RevOps owns the revenue technology stack: CRM, sales engagement platforms, marketing automation, AI-assisted coaching, reporting tools. Its job is to ensure those tools are configured correctly, actually used by the team, and delivering genuine performance uplift — not just adding layers of complexity.
HubSpot’s sales technology research found that the average B2B company runs more than a dozen sales tools simultaneously. RevOps exists partly to prevent that number from becoming a distraction.
Forecasting and planning. RevOps builds and maintains the models that project future revenue. Accurate forecasting lets a business make confident hiring decisions, plan capacity correctly, and identify pipeline gaps before they become a crisis. A RevOps function that gets forecasting right means a founder stops managing by feel and starts managing by numbers.
Revenue operations vs sales operations
These two roles get conflated constantly, and hiring for the wrong one is an expensive mistake.
| Revenue operations | Sales operations | |
|---|---|---|
| Scope | Full revenue function: marketing, sales, customer success | Sales team only |
| Data ownership | Full funnel across all teams | Pipeline and sales activity |
| Process ownership | Lead-to-cash end-to-end | Sales process and methodology |
| Technology | Full stack: CRM, marketing automation, CS tools | CRM and sales tools |
| Forecasting | Company revenue model | Sales pipeline only |
| Reports to | CEO or CRO | VP of Sales or CRO |
| Best for | Businesses with 3+ revenue teams needing alignment | Businesses with a sales team needing operational support |
The distinction is scope. Sales operations supports the sales team. Revenue operations connects all three revenue-generating teams and creates one operating layer across them.
For most founder-led businesses under £5M revenue, sales operations capacity — even informal — is often sufficient. RevOps becomes relevant when the misalignment between marketing, sales, and customer success is measurably costing revenue.
The three pillars of a RevOps function
Understanding what RevOps produces is easier when you think in three pillars.
Revenue intelligence. This is the data infrastructure. It tells you where revenue is coming from, where it is stalling, and where it is leaking. Without it, a business cannot diagnose its own commercial model accurately. Decisions that should be based on facts end up based on whoever argues most confidently in the meeting.
Revenue process. This is the operational layer — the defined handoffs, qualification criteria, and stage gates that govern how a deal moves from marketing interest to signed contract to expanded account. A working revenue process eliminates the ambiguity that allows deals to go quiet without anyone taking ownership. It also creates consistency: the same situation gets handled the same way regardless of which salesperson is running it.
Revenue technology. This is the tool layer that makes the first two pillars scalable. CRM configuration, automation, AI-assisted call coaching, pipeline tracking. All of it exists to make the data and the process accessible without requiring the team to manually maintain things that should run automatically.
The pillars work in sequence. Without revenue intelligence, you cannot design the right process. Without the right process, technology automates the wrong things faster.
Who actually needs RevOps?
There is a version of RevOps content that makes it sound like every B2B business should have a dedicated RevOps function immediately. That is not accurate, and believing it leads founders to invest in the wrong thing at the wrong time.
A practical way to think about it:
You probably need RevOps when:
– You have a sales team, a marketing function, and a post-sale customer success team operating in silos
– Your pipeline data is unreliable or inconsistent between teams
– Deals are regularly stalling without clear ownership of the next step
– You cannot forecast next quarter’s revenue with any confidence
– You have a CRM that the sales team does not trust or use consistently
You probably do not need a dedicated RevOps hire yet when:
– The commercial function is still founder-led with no formal team
– Your pipeline is managed informally and it is working
– The bottleneck is not process or data — it is that the underlying commercial model does not work
That last point is the one most founders miss. And it matters enormously.
The problem most founder-led businesses miss
A pattern shows up consistently in founder-led B2B businesses between £3M and £10M. Founders arrive wanting RevOps — or a better CRM setup, or cleaner pipeline processes — and what the commercial diagnostic reveals is that the underlying model is the actual problem.
The CRM is not the issue. The process is not the issue. The issue is that the offer is not differentiated, the ideal customer profile has never been defined precisely, the pricing architecture is leaking margin, or the go-to-market motion has no clear logic connecting the right activity to the right buyer.
Building RevOps on top of that does not fix any of it. It creates a well-organised system for doing the wrong thing consistently.
Phil Pelucha has run commercial diagnostics on businesses in this position many times. The Stealth AI Recruitment engagement is a clear example. Chris Haney came to Phil with a 20-person recruitment firm stuck at $1.2M. The instinct would have been to fix the sales process. Phil’s diagnostic identified adjacent verticals, rebuilt the commercial model around them, and installed a structured intelligence system at the team level. Revenue grew 5x in six months and the business exited at 6x EBITDA — well above the 3 to 5x sector average.
The architecture came before the acceleration.
“Architecture before acceleration” is not a slogan. It is a working principle: before you systemise how your commercial function operates, you need to know whether the model underneath it is sound.
The Revenue Acceleration Diagnostic is the tool BIB uses to answer that question. It is a 45-page PE-grade commercial audit that identifies exactly where revenue is leaking before any process or technology investment is made. Phil runs the same diagnostic framework on a £3M founder-led business that PE firms use before deploying capital on a £54M acquisition target. The questions are identical because the structural problems are identical.
If the diagnostic shows the commercial model is fundamentally sound, RevOps becomes the right next investment. If it surfaces structural problems, fixing those first saves the business from building a RevOps function that will need to rearchitect itself once the model changes.
Many businesses that reach this point also find that a fractional CRO is a faster path to commercial alignment than a standalone RevOps hire — because a fractional CRO owns both the strategy and the operational layer simultaneously, rather than building one without the other.
How to build RevOps the right way
If your commercial model is sound and you are ready to build a RevOps function, here is a practical sequence that avoids over-engineering it for your current stage.
Step 1: Audit your current data state. Before hiring or buying technology, map what data you have, where it lives, and whether the sales team trusts it. An untrusted CRM is a foundational problem. No RevOps investment fixes that until the trust problem is addressed first.
Step 2: Define the revenue handoffs. Map the journey from a marketing-qualified lead to a closed deal to an expanded account. Identify every handoff point. For each one: who owns it, what the qualifying criteria are, and what happens when it stalls. Write it down. The act of writing it down surfaces more problems than any tool will.
Step 3: Consolidate the technology stack. Pick one CRM as the system of record. Consolidate tools that duplicate each other. Fewer tools used consistently will always outperform many tools used inconsistently.
Step 4: Build the minimum reporting layer. Five metrics to get accurate before adding complexity: pipeline value, conversion rate by stage, average deal cycle length, win rate, and revenue from existing accounts. Get these right first.
Step 5: Hire for your current stage. An early-stage RevOps hire is one person: operationally strong, comfortable building in a CRM, capable of writing process documentation without being told to. You do not need a RevOps director at £5M revenue. You need one rigorous person who owns the data and the process.
According to Forrester Research, businesses that mature their RevOps function incrementally — starting with process and data before adding technology — see 36% faster revenue attainment than those who start with technology investment. The sequence matters.
For businesses that want an experienced revenue operations consultant to run this diagnostic and build phase, the approach is the same: a structured audit of the current commercial state, followed by targeted interventions rather than a wholesale rebuild.
Frequently asked questions
What is the difference between revenue operations and sales operations?
Revenue operations covers the entire revenue-generating function, including marketing, sales, and customer success. Sales operations covers only the sales team. RevOps owns end-to-end data, process, and technology across all three teams. Sales operations supports the sales team’s pipeline and methodology. For most founder-led businesses, sales operations capacity comes first. RevOps becomes relevant when team misalignment is measurably costing revenue.
When should a founder-led B2B business invest in RevOps?
A founder-led business should invest in RevOps when it has at least two revenue-generating teams operating in silos, pipeline data is unreliable, or deals are consistently stalling without clear ownership. If the underlying commercial model has structural problems — undefined ICP, pricing leakage, a go-to-market motion that does not convert — addressing those first will produce a better return than any RevOps investment.
What does a revenue operations consultant do?
A revenue operations consultant audits the current data, process, and technology infrastructure in the commercial function, identifies the gaps causing revenue leakage or inefficiency, and designs or implements the fixes. They typically own CRM configuration, define the handoff processes between teams, build the reporting layer, and ensure the technology stack supports accurate forecasting. For a full breakdown of the role, see our guide to what a revenue operations consultant does.
How much does it cost to build a RevOps function?
Building an in-house RevOps function typically costs £65,000 to £120,000 per year for a single experienced hire in the UK market, plus technology stack costs of £8,000 to £35,000 annually. A revenue operations consultant engagement for a founder-led business typically runs £4,000 to £18,000 for a diagnostic and initial implementation phase. Many businesses in the £3M to £10M range start with a fractional or project-based RevOps resource rather than a full-time hire.
Is revenue operations just a CRM?
Revenue operations is a function, not a piece of software. A CRM is one tool a RevOps function uses. RevOps owns the CRM configuration, ensures team adoption, and makes sure the data inside it is accurate. The CRM is the vehicle; RevOps is the driver. Buying a CRM without a function to own it typically results in an expensive system the team does not trust or use — which produces worse commercial visibility than a well-maintained spreadsheet.
Conclusion
Revenue operations aligns your revenue-generating teams, owns the data and processes connecting them, and builds the forecasting layer that makes confident commercial decisions possible. For B2B businesses with multiple teams operating in silos, it is a genuine investment in predictable revenue.
The question worth asking before that investment is whether the commercial model underneath is sound enough to be worth systematising. A well-run RevOps function on top of a broken model surfaces the problems faster — which is useful for diagnosis, but not a substitute for fixing the architecture.
If you want to understand what is actually driving or limiting revenue in your business before investing in any function, process, or technology, the Revenue Acceleration Diagnostic gives you the complete picture. It is the same diagnostic used to assess £50M acquisition targets, applied to a founder-led B2B business. Start there.
