Revenue Operations (RevOps) is the function accountable for aligning the systems, data, and processes across sales, marketing, and customer success so a company can measure and grow revenue as one connected motion instead of three departments reporting three different numbers. Sales Ops optimizes how reps sell inside the CRM (customer relationship management platform). Marketing Ops optimizes how campaigns run inside the marketing automation platform. RevOps sits above both, owns the handoff between them, and gets stuck with the metrics nobody else wants to claim, like how many marketing-qualified leads (MQLs) actually turn into closed revenue instead of disappearing somewhere between two systems.
GNW has been doing this long enough to know that handoff problem isn’t theoretical. According to the 2026 B2B State of Martech and Revenue Operations Report from LXA and LeanData, based on a survey of 201 senior B2B leaders at enterprise companies fielded in April 2026, 42% cite poor sales and marketing alignment on lead qualification as a significant operational gap, and 29% say they have no visibility into what happens after the marketing-to-sales handoff. It goes back further than most people think: a 2021 Forrester Consulting study commissioned by Salesforce found that only 32% of surveyed organizations had a single role accountable for revenue growth across every channel at the time, which is part of why RevOps got created in the first place, and why so many companies still get the role wrong.
Key Takeaways
- RevOps is not Sales Ops with a new title. Sales Ops optimizes the sales motion inside the CRM; Marketing Ops optimizes campaigns inside the marketing automation platform; RevOps owns the connective tissue and the metrics between them, including revenue recognition and cross-functional reporting.
- According to the 2026 B2B State of Martech and Revenue Operations Report (LXA and LeanData, 201 respondents), 42% of enterprise B2B leaders cite poor sales and marketing alignment on lead qualification as a significant gap, and 29% have no visibility into the marketing-to-sales handoff.
- GNW Consulting’s published position, argued by Chief Strategy Officer Andrea Lechner-Becker in “RevOps Is Rarely About RevOps”, is that the function should report to the CFO (chief financial officer), not a CRO (chief revenue officer), CMO (chief marketing officer), or CSO (chief sales officer).
- Companies under roughly $5M in annual recurring revenue (ARR) rarely need a dedicated RevOps hire. Somewhere between $5M and $20M ARR is where the first dedicated RevOps role typically earns its keep.
- The single clearest sign a RevOps function is broken is that a lead, deal, or renewal can go missing between systems and nobody can say whose job it was to catch it.
- RevOps should own a specific, named set of metrics, not “alignment” as a vague concept. Pipeline coverage, lead-to-account match rate, and net revenue retention (NRR) belong to RevOps whether or not anyone assigned them.
What is RevOps, and why did it emerge as a separate function?
RevOps emerged because Sales Ops and Marketing Ops were each doing their jobs well on their own, which sounds fine until you notice that the revenue was leaking out through the exact seam nobody was watching: the moment a lead crossed from marketing’s system into sales’s, back when a company just had a Sales Ops person keeping the CRM clean and a Marketing Ops person running nurture programs in the marketing automation platform, and neither of them had ever been asked to own that handoff. That’s where deals actually got lost and numbers actually stopped matching, quietly enough that it took years before anyone gave the problem a name, let alone a job description.
RevOps was built to close it. In practice, that means one function (a person, a small team, or eventually its own department) is accountable for the full revenue lifecycle: how a prospect is scored and routed, how that handoff is measured, how renewals and expansion revenue get tracked, and how the company reports on all of it consistently. GNW Consulting’s own Revenue Operations Framework maps this out as a layered system, connecting board-level growth goals down through marketing support, sales support, and customer support, rather than treating RevOps as a single department bolted onto sales.
The catch, and the reason this hub page exists, is that most companies who create a “RevOps” title still hand it a Sales Ops or Marketing Ops job description. That difference between the name and the actual scope of the role is most of what goes wrong with RevOps in practice, and it is the subject of the skepticism section below.
RevOps vs Sales Ops vs Marketing Ops: who owns what
Sales Ops, Marketing Ops, and RevOps are not three names for the same job. Each one optimizes a different part of the revenue lifecycle, and the overlap between them is exactly where handoffs break if nobody owns the seam.
The overlap that causes the most confusion sits in the middle two rows. Sales Ops and Marketing Ops both touch lead handoff, but each only sees their half of it. RevOps is the only function with visibility into both halves at once, which is also why, per the LXA and LeanData 2026 report cited above, 32% of enterprise B2B leaders report duplicate or mismatched lead-to-account records: a problem that lives squarely in the seam between Sales Ops and Marketing Ops systems, and one neither team is positioned to fully own.
Do you actually need a RevOps function, or is better Sales Ops enough?
You need dedicated RevOps once your handoff problems cost more than a hire would, which for most B2B companies shows up somewhere between $5M and $20M in annual recurring revenue (ARR). Below that, a strong Sales Ops or Marketing Ops generalist covering both sides usually suffices. Above that range, the coordination tax of not having RevOps starts exceeding the cost of hiring for it.
Use this checklist as a directional guide, not a hard rule:
Signs you don’t need RevOps yet:
- Under roughly $5M ARR, with a sales team small enough that the founder or a single ops hire can track every deal by memory
- Marketing and sales are effectively the same 3-5 person team, or sit in the same weekly meeting
- You have one CRM, one marketing tool, and nobody’s job depends on reconciling data between them
Signs you’re in the gray zone (RevOps as a fractional or part-time function):
- $5M-$20M ARR, with a sales team of roughly 5-15 reps
- Marketing has started generating enough volume that lead quality, not lead quantity, is now the debate in pipeline meetings
- You’ve hired a Sales Ops or Marketing Ops person, and they’re already doing work that belongs to the other side of the house
Signs you need a dedicated RevOps hire or team now:
- $20M+ ARR, or a shorter sales cycle with high enough velocity that a broken handoff compounds weekly instead of monthly
- Sales and marketing leadership disagree on basic numbers, like how many qualified leads were generated last quarter, and there’s no neutral system of record to settle it
- Customer success, renewals, or expansion revenue is tracked in a spreadsheet instead of a system, and finance doesn’t trust the number
Signs you’re already past due:
- You have Sales Ops and Marketing Ops as separate teams, each with their own dashboards, and the two dashboards disagree
- Deals or renewals have gone missing between systems and it took weeks to figure out whose responsibility it was
- Leadership is having the “is this just a rebrand” conversation covered later in this piece, which is usually a sign the role was created without the authority or scope to do its job
A day in the life of RevOps at GNW
RevOps work is less about strategy decks and more about tracing a single broken process to its root cause and fixing the system, not just the symptom. When GNW Consulting stepped into Tavoron (formerly JHFOSTER), a manufacturing company selling automation and compressed air solutions, the RevOps-style problem was inherited process debt. As Christie Koester, Director of Marketing & Communications at Tavoron, put it in GNW’s Tavoron case study: “Our Marketing Operations were very cumbersome and messy. There were a lot of inherited processes that we had to audit and then flip to ensure we could find all of the errors across data inconsistencies and to increase our target audience.” The actual day-to-day work was absolutely granular: auditing existing Marketo tokens and program architecture, rebuilding the campaign workflow so it could scale, and tying every KPI back to real conversion data so marketing’s reported wins matched what sales and finance saw on their end. The result, tracked and reported rather than estimated, was a 1,150% increase in conversions across Q1-Q3 and more than 20 additional marketing campaigns run year over year.
At Drift, the day-to-day problem looked different but sat in the same seam. Drift’s internal team needed to spend more time on high-value, revenue-generating work and less time firefighting operational tasks inside a complex MarTech stack. GNW’s engagement started with a full audit of the marketing automation platform and CRM database together, not separately, because a fix on one side that isn’t checked against the other side just moves the breakage. Monique Lemieux, Head of Marketing Operations at Drift, described the outcome this way in GNW’s Drift case study: “They understand all of our systems, our processes, and they’re in our project management tool. They’re interfacing directly with our marketers and our demand gen team. And it really feels like they just are part of the operations of our organization.” That embedded, cross-system involvement, sitting inside both the marketing stack and the sales-facing systems at once, is what RevOps work actually looks like day to day. It produced a documented 40% improvement in MOps (marketing operations) productivity.
Neither engagement started with a reorg or a new job title. Both started with an audit of where data and process broke down between two systems that were each individually working fine. That is the day-to-day reality of RevOps: less “strategy,” and more forensic reconciliation of what each department’s system says happened against what actually happened.
The core metrics RevOps should actually own
RevOps should own the metrics that need visibility across more than one department’s system, because no single department can be held accountable for a number it can only see half of. That’s the filter, and everything on the list below passes it. Attribution scores, campaign engagement, MQL volume, all the numbers people obsess over in QBRs, don’t make the cut, because any one team can already see those on its own.
Most RevOps functions quietly stop measuring anything real. Raja calls it exactly what it is on Signal & Stakes: “You have to kill all of these vanity dashboards, vanity metrics, and shift into doing what’s working right now.” Same logic applies to revenue analytics, which people keep trying to buy off a shelf as a platform when it actually works like a lens, one RevOps is the only function required to look through across every department at once, not just the one it happens to sit inside.
- Pipeline coverage ratio. The ratio of total pipeline value to the revenue target it’s meant to cover, tracked against one shared pipeline definition that sales and marketing both actually agree to, not two competing versions.
- MQL-to-SQL and SQL-to-closed-won conversion rates. The rate at which marketing-qualified leads (MQLs) become sales-qualified leads (SQLs) and eventually closed revenue, which is the exact handoff most companies can’t measure without RevOps in the room.
- Lead-to-account match rate. How often inbound leads correctly match to the right account instead of spawning a duplicate, a problem 32% of enterprise B2B leaders reported in the LXA and LeanData 2026 report cited earlier in this piece.
- Sales cycle length by segment. How long deals take to close, broken out by customer segment or deal size, since this number gets skewed the moment marketing and sales measure the cycle from different starting points.
- Win rate. The percentage of qualified opportunities that close, which only tells you something useful if the qualification criteria behind it stay consistent across reps and time. This is also the metric Raja points to when he’s asked what should replace vanity numbers like clicks and impressions: “Clicks without attribution to an opportunity are just as meaningless as impressions. Let’s start measuring: did it increase deal velocity? Are we tying it to revenue? What are the win rates on those target accounts? Those are the things we have to be looking out for as a RevOps leader.”
- Customer acquisition cost (CAC) and CAC payback period. The fully loaded cost to acquire a customer and how long it takes to earn that cost back, which means pulling spend data from marketing and revenue data from finance into one model instead of two.
- Net revenue retention (NRR). Revenue retained and expanded from existing customers, net of churn and downgrades, sitting right at the intersection of customer success, finance, and sales.
- Forecast accuracy. How closely predicted revenue matches what actually closes each period. As Raja put it on the same episode, this is the one the whole C-suite actually cares about, and you can’t get there off attribution data alone: “You can’t forecast unless you’re doing the exact same thing, or something similar to it, over and over again.” RevOps is positioned to own this because it’s the only function holding the data feeding the forecast in the first place, not just one slice of it.
- Data quality and completeness rate. The percentage of records in the CRM and marketing automation platform that are complete, deduplicated, and correctly routed. Unglamorous, and the metric everything else on this list quietly depends on.
One way to sanity-check this list: if a number only ever lives in the CRM, or only ever lives in the marketing platform, it doesn’t belong on your RevOps scorecard, no matter how often it comes up in a QBR. It has to cross two systems that don’t talk to each other by default. That’s what makes it RevOps’ problem instead of someone else’s.
Is RevOps just Sales Ops with a rebrand?
No, but the skepticism is earned, and even our own founder admits it. Raja Walia said this on Signal & Stakes (formerly Call It RevOps): “When I first heard the term RevOps, I didn’t agree with it. It didn’t make sense to me, and honestly, to a point, it still doesn’t make sense to me to this day. Isn’t that just the job of senior leadership? Do we really need a middle manager to make sure senior leadership is also focused on revenue?”
In most companies, the rebrand is exactly what happened. Forrester found this back in 2021, and put it more bluntly than I would have: “a distinct gulf between those that have fully embraced RevOps and those that have simply rebranded existing sales or finance teams.” Nothing about that has changed. What actually separates the two, real cross-functional alignment and one shared source of truth for customer data, isn’t cosmetic either: those companies were roughly twice as likely to see the results RevOps is supposed to deliver, while everyone else just changed a title and hoped it would work.
Look back at the table above: if a “RevOps” role’s actual responsibilities map entirely to the Sales Ops or Marketing Ops columns, no ownership of the handoff, no cross-functional metrics, it’s a rebrand. A real RevOps role owns something neither Sales Ops nor Marketing Ops can claim alone: the metrics above, and the reporting line below. If a company can’t name one metric its RevOps hire owns that didn’t already belong to someone else, the title changed and the job didn’t.
There’s an attitude test here too. A RevOps hire who says yes to every request from sales or marketing without ever pushing back isn’t really running the function, no matter what the org chart says. Walia gets at this later in the same episode: “You earn influence by executing well, not by rebranding your job every time a new title comes into fashion… Ops exists to support, scale, and streamline the business initiatives that are already coming. We don’t redefine them.
Who should RevOps report to?
GNW Consulting’s position, argued directly by Chief Strategy Officer Andrea Lechner-Becker, is that RevOps should report to the CFO (chief financial officer), not a CRO, CMO, or CSO. The reasoning: RevOps is fundamentally a financial operations function, responsible for how revenue is recognized, classified, invoiced, and collected across every system, not just how deals move through the CRM. When RevOps reports into a go-to-market leader, whether that’s a CRO, CMO, or head of sales, the function tends to inherit that leader’s go-to-market priorities instead of maintaining the financial accountability that gives it real authority. GNW’s full argument, including real (anonymized) job description examples showing how this goes wrong, is laid out in “RevOps Is Rarely About RevOps: Why the Role Is Ineffective and How to Fix It.”
Most companies don’t follow this model yet, and that’s fine in practice as long as whoever RevOps reports to, usually a CRO, CMO, or COO, is disciplined about giving the function real cross-functional authority instead of treating it like an extension of their own department. The warning sign is a RevOps leader who only ever gets pulled into sales conversations, or only ever gets pulled into marketing conversations. If you can predict which department’s problems get solved first just from the reporting line, that’s the tell something’s off.
Who RevOps reports to is a different question from who should actually run it day to day. The strongest RevOps leaders tend to come out of marketing operations, not sales ops or IT, because MOps is usually the only seat that touches the entire tech stack, sits with customer success on onboarding, and works sales enablement across the whole lead lifecycle, seeing a lead long before sales ever does. That full-lifecycle view is what the role actually needs, and it’s hard to build anywhere else.
Signs your RevOps setup is broken
Process and Operations is the weakest pillar in enterprise revenue operations maturity for the third year running, and that’s exactly where most broken RevOps setups actually live: good people, decent tools, and a process nobody ever got around to building properly. The LXA and LeanData 2026 report puts a number on it, scoring Process and Operations at 3.66 out of 5.0, behind both People and Teams (3.82) and Platform and Technology (3.81). Here’s what that actually looks like on the ground:
- A lead, deal, or renewal has gone missing between systems, and it took real investigation to figure out whose job it was to catch it.
- Sales and marketing report different numbers for the same metric, most commonly pipeline value or lead volume, and there’s no shared system of record either side trusts.
- Only 26% of organizations in the same 2026 report have enforcement mechanisms in place for routing, qualification, and lead-to-account matching, meaning most companies are relying on manual vigilance instead of systems that catch errors automatically.
- RevOps spends most of its time on reporting and dashboards instead of fixing the processes that make the underlying data unreliable in the first place.
- Nobody outside of RevOps can explain what RevOps is actually accountable for, beyond a vague sense that they’re “supposed to align sales and marketing.”
- New tools keep getting added to fix problems that are actually process gaps, not technology gaps, which is how stack sprawl happens without solving anything.
What tools does a RevOps function typically use?
RevOps typically works across five tool categories, not a single platform, because its job is to connect systems that were each bought for a different department.
- CRM (customer relationship management). The sales team’s system of record for accounts, contacts, and opportunities.
- Marketing automation platform. The marketing team’s system of record for campaigns, lead scoring, and nurture programs.
- Lead routing and orchestration tools. Software that governs how leads and buying signals move between the CRM and marketing automation platform, enforcing the rules that prevent duplicate or misrouted records.
- Revenue intelligence and forecasting tools. Tools that pull pipeline and deal data to support forecast accuracy and pipeline coverage reporting.
- Data warehouse or reverse ETL layer. The infrastructure that consolidates data from the CRM, marketing platform, and finance systems into a single reportable source of truth.
Deliberately excluded from this list are specific vendor names. Which CRM or marketing automation platform a company uses matters less for this hub page than understanding that RevOps’ job is to make these categories work as one system rather than five disconnected ones.
Frequently Asked Questions
What’s a healthy ratio of RevOps staff to sales reps?
There’s no fixed industry ratio, because the right RevOps headcount depends more on data complexity and number of systems than on rep count alone. As a directional guide, companies in the $5M-$20M ARR range typically start with one RevOps generalist supporting the full go-to-market team, and add specialized roles (like a dedicated data or systems analyst) once the company crosses roughly $20M-$50M ARR and the tooling and reporting load outgrows one person.
Can a fractional or outsourced RevOps function work instead of a full-time hire?
Yes, and for companies in the gray zone described earlier in this piece, a fractional model is often the more disciplined choice, since it avoids hiring for a role before the company has enough handoff volume to justify a full-time headcount. The risk with fractional RevOps is the same risk as an internal hire: if the engagement is scoped as Sales Ops or Marketing Ops work relabeled, it won’t solve the cross-functional problem RevOps exists to fix.
Does RevOps replace the need for a dedicated CRM administrator?
No. A CRM administrator manages the day-to-day configuration, permissions, and maintenance of the CRM itself. RevOps sits a level above that, deciding what the CRM should be configured to do in the first place based on cross-functional process and reporting needs, then working with the administrator (whether that’s a dedicated hire or a shared resource) to implement it.
How is RevOps different from a Chief Revenue Officer (CRO)?
A Chief Revenue Officer (CRO) is a go-to-market leadership role, typically accountable for hitting the revenue number itself across sales and sometimes marketing. RevOps is an operational function that supports whoever is accountable for that number, whether that’s a CRO, CFO, or CEO, by building the systems, data, and process that make the number measurable and repeatable. A company can have a CRO without RevOps, and vice versa, though the two roles work best in tandem.
How long does it take to stand up a RevOps function from scratch?
That same 2021 research found most companies, regardless of how mature their eventual RevOps function became, took six months to two years to stand up the function initially. That range still holds up as a practical planning benchmark: a narrow systems fix can happen in weeks, but a fully staffed, cross-functionally trusted RevOps function realistically takes several quarters to earn the authority described throughout this piece.
Should RevOps own the martech and sales tech budget?
RevOps should influence the budget heavily, even where it doesn’t formally own it, because RevOps is the function with visibility into which tools are actually being used, which ones overlap, and which ones are being kept alive by habit rather than necessity. Per the LXA and LeanData 2026 report cited throughout this piece, average enterprise stack sizes dropped from 62 tools in 2025 to 37 in 2026, a consolidation trend that RevOps functions are typically the ones driving.
Ready to find out where your own RevOps setup is breaking? Speed-date a GNW consultant.
