In June 2019, Forrester was still describing revenue operations as "an emerging model." By January 2023, LinkedIn's Jobs on the Rise list ranked head of revenue operations as the fastest-growing job title in the US. And in October 2026, Forrester argued that AI is already making RevOps' current mandate obsolete. Few business functions have gone from new idea to C-suite reporting line to AI rewrite in less than a decade.
RevOps grew up in SaaS, where revenue is earned over a customer's whole lifetime rather than in a single sale, and it is now being reshaped by two forces at once: AI agents and partner ecosystems. This guide explains what RevOps is, why SaaS companies created it, what it owns, how it differs from partnerships and how AI is changing the job.
What Is RevOps?
Revenue operations (RevOps) is the function that designs and runs the system a company uses to win, keep and grow revenue. It connects the operations work of marketing, sales, customer success, partnerships and finance under one plan, one set of definitions, one data model and one technology stack, so leaders can see the entire revenue lifecycle from first touch to renewal.
Forrester's SiriusDecisions research defines revenue operations as sales operations, marketing operations and customer success operations teams working together under shared operating principles for planning, processes, technology, data and measurement. Since then, the scope has widened. In most SaaS companies today, RevOps also covers partner operations, quoting and pricing governance and the handoff into billing.
In one sentence: sales, marketing, customer success and partnerships generate revenue; RevOps builds and maintains the engine they all run on.
Why RevOps Is a New Discipline, and Why SaaS Built It
Before RevOps, each revenue team had its own operations function: sales ops owned the CRM and territories, marketing ops owned automation and lead scoring, and customer success ops owned health scores and renewals. Each optimised its own funnel stage. Nobody owned the full path from first touch to renewal, and that is where revenue leaked.
A short history of RevOps
Why SaaS companies needed it first
Three features of the SaaS model made the old structure break faster than in other industries:
- Revenue is earned after the sale. In a subscription business, the first contract is only the start. Renewals and expansion decide whether a customer is profitable, so the handoff from sales to customer success is as important as the handoff from marketing to sales. SaaS Capital's 2025 benchmarks show private SaaS companies with net revenue retention above 130% growing at a median of 44% a year, against 15% for those below 100%.
- SaaS companies run several go-to-market motions at once. Self-serve sign-ups, product-led upgrades, sales-led enterprise deals, marketplace listings and partner-led sales often coexist. Each motion needs its own rules, but they all share customers, data and targets.
- The tool stack grows faster than the team. Every function buys its own software. Without a single owner, data ends up duplicated, definitions drift and nobody trusts the dashboard.
What RevOps Owns in a SaaS Company
RevOps doesn't own the revenue number; the CRO and CEO do. It owns the system that produces the number. The table below shows what that looks like across the SaaS revenue lifecycle.
How big is the team? BCG's 2025 Rule of 40 benchmarks put the median ratio of account executives to RevOps team members at 4.8 across the software companies surveyed, ranging from 4.1 for companies with contracts above $40,000 to 6 for mid-market contract values. In other words, a SaaS company with 25 account executives commonly supports around five people in RevOps roles.
RevOps vs. Sales Ops, Marketing Ops, CS Ops and Partner Ops
The simplest way to understand RevOps is to compare it with the functional operations teams it connects.
In smaller SaaS companies, one RevOps team covers all five. In larger ones, the functional teams remain but report into or follow standards set by RevOps.
RevOps vs. Partnerships: Where They Meet
This is the relationship most RevOps guides skip, and it matters more every year. Canalys, now part of Omdia, estimates that partners deliver just over 70% of global IT spending, and Forrester's 2025 partner ecosystem research found that 67% of B2B partner and channel decision-makers plan for indirect revenue to grow above or significantly above the previous year.
The two functions do different jobs. The partnerships team builds relationships: it recruits partners, agrees commercial terms, co-sells and keeps partners motivated. RevOps builds the system that partner revenue flows through: the CRM fields, the deal registration rules, the attribution model and the forecast. When the two work separately, partner revenue becomes the least trusted number in the business.
Signs that RevOps and partnerships aren't connected:
- Partner deals appear in the CRM late or not at all, so they can't be forecast
- Partner managers keep their own spreadsheet because they don't trust CRM reports
- Reps and partners chase the same account and nobody knows who registered it first
- Commission disputes are settled by email threads rather than system records
Our guides to PRM vs. CRM, building a SaaS partner program and the chief partnership officer role go deeper on the partner side.
How AI and Agents Are Changing RevOps
RevOps was created to manage complexity, and AI is now absorbing much of the coordination work that complexity created. Forrester names forecasting, reporting, lead routing, data enrichment, pipeline management and workflow execution as activities AI can perform or augment, and argues that "RevOps' center of gravity shifts from operating the revenue engine to designing how the revenue engine operates."
The pressure comes from both sides of the deal:
- Buyers are using agents. Gartner predicts that by 2028, 90% of B2B buying will be AI agent intermediated, pushing over $15 trillion of B2B spend through AI agent exchanges. Forrester's 2027 predictions expect two-thirds of providers to lose deals because buyers can't verify their claims.
- Sellers are getting agents. Gartner also predicts that by 2028 AI agents will outnumber sellers ten to one, yet fewer than 40% of sellers will say agents improved their productivity.
- Humans still close the loop. A Gartner survey found that 69% of B2B buyers prefer to validate AI-generated insights with sales reps.
- Not every AI project survives. Gartner expects over 40% of agentic AI projects to be cancelled by the end of 2027 because of escalating costs, unclear business value or inadequate risk controls.
Here is how the job changes in practice:
The partner angle is easy to miss here. If your direct sellers have AI agents but partners still submit deals by email, the partner channel becomes the slowest and least visible part of the revenue engine. Journeybee's AI partner agent gives partners cited answers from your approved content and flags stalled leads, and every Journeybee plan includes a REST API, webhooks and an MCP server so AI clients can read and register partner deals with permissions you control.
Key RevOps Metrics for SaaS
RevOps teams usually report on a small set of company-level metrics that cut across teams:
- Annual recurring revenue (ARR): the yearly value of active subscriptions
- Net revenue retention (NRR): revenue kept and expanded from existing customers, after churn and contraction
- Gross revenue retention (GRR): revenue kept from existing customers before expansion
- Customer acquisition cost (CAC) payback: the months it takes to earn back the cost of winning a customer
- Forecast accuracy: how closely forecast revenue matches actual results
- Pipeline coverage: open pipeline divided by the remaining target for the period
- Partner-sourced revenue share: the percentage of new revenue that originated with a partner
For the practices that move these numbers, see our guide to RevOps best practices.
When Does a SaaS Company Need RevOps?
There's no fixed revenue threshold. The trigger is usually complexity rather than size. Common signals include:
- Marketing, sales and customer success report different numbers for the same metric
- Leadership doesn't trust the forecast
- You run more than one go-to-market motion, such as self-serve, sales-led and partner-led
- Your tool stack has grown, but nobody owns how the tools connect
- Partner revenue is growing but lives outside the CRM
Most SaaS companies start with one RevOps hire who reports to the CEO, CRO or COO, then add specialists as the go-to-market motions multiply.
RevOps in Practice: Three SaaS Partner Programmes
Each of these Journeybee customers had the same core problem: partner revenue sat outside the RevOps system.
- Draftable, a document comparison software company, found that fewer than a quarter of partner deals reached HubSpot early enough to forecast. After building a custom partner engine on Journeybee's API connected to HubSpot, it reported around 30% higher partner programme efficiency, about half as much manual data entry and roughly double the confidence in attributing partner-sourced pipeline, according to the Draftable case study.
- Telnyx, which builds infrastructure for real-time AI and communications, needed to support resellers, referral partners and advisors side by side. Journeybee's CRM integration removed around half of its manual data entry and syncing, and roughly half of partner deals now start in Journeybee, as described in the Telnyx case study.
- Simployer, an HR technology company, reported a 75% increase in partner-sourced leads, 95% better lead attribution accuracy and 20 hours a week saved on manual admin, according to the Simployer success story.
How Journeybee Works With RevOps Leaders
Journeybee is a partner relationship management platform built to fit inside your revenue operations rather than beside them. We work with RevOps leaders on four things:
- Your CRM stays the system of record. Journeybee runs alongside Salesforce, HubSpot, Microsoft Dynamics, Pipedrive, Zoho or Attio with two-way sync, and partner, deal and contact fields are mapped one to one, as set out in how Journeybee works.
- Partner deals follow your rules. Deal registration checks submissions against existing CRM records for conflicts, and partners can register deals via Slack, Teams, email or a form.
- Partner revenue is measurable. Partner analytics map CRM opportunity data back to partner activity, and partner CPQ keeps reseller quotes inside your pricing rules.
- It's built for AI and custom workflows. The API, webhooks and MCP server let your team connect agents and build custom partner workflows, as Draftable did.
Most teams move from setup to a live, branded partner portal in one to five business days. Book a demo to walk through your RevOps setup with our team, or see pricing.
