Revenue Operations (RevOps) is the function that owns the systems, data, and process behind every revenue-generating team. In a B2B company that means the operational layer underneath sales, marketing, and customer success. RevOps owns the CRM, the data flowing through it, the automation logic that connects it to adjacent tools, and the metrics the GTM org uses to make decisions.
What a RevOps team actually does
The day-to-day breaks into four buckets:
- Systems. Choosing, configuring, and maintaining the GTM tool stack: CRM (HubSpot, Salesforce), sequencer (Outreach, Salesloft, Apollo), data enrichment (Clay, ZoomInfo), conversation intelligence (Gong), automation (n8n, Zapier), AI orchestration (Claude + MCP).
- Data. Making sure the right data flows between systems, that records are clean, that fields mean what reps think they mean, and that reporting reflects reality.
- Process. Designing how leads get routed, how deals progress, how renewals get tracked, how handoffs between teams happen, and how exceptions get handled.
- Insight. Building reports and forecasts the CRO trusts. Pipeline velocity, conversion rates by segment, forecast vs actual, churn drivers.
RevOps vs Sales Ops
Sales Ops is the predecessor function — same idea but scoped only to the sales team. RevOps emerged in 2018-2020 as B2B SaaS companies realized that sales, marketing, and customer success were all operating against the same buyer journey but on disconnected systems. Treating those teams as separate ops domains created data drift, attribution wars, and forecast disagreements the CRO couldn’t resolve.
The RevOps consolidation puts one team in charge of the full revenue lifecycle — lead → opportunity → customer → renewal/expansion — with a single data model and a unified set of metrics.
When does a company need RevOps?
The trigger usually isn’t size; it’s complexity. A 30-person B2B SaaS with one motion (inbound demo, AE close) doesn’t need RevOps yet. A 30-person B2B SaaS with three motions (inbound + outbound + product-led) and three personas absolutely does, because the data model and the tooling have to handle the variations.
By $10M ARR most B2B SaaS companies have a dedicated RevOps function. By $25M ARR it’s typically a team of 2-5 with a Head of RevOps or VP RevOps reporting to the CRO.
What changed with AI
Before 2024, RevOps was largely about plumbing — how data moves, how systems connect, how dashboards reflect reality. After 2024, AI-native tools (Clay’s AI columns, Gong’s conversation intelligence, Claude + MCP for agentic workflows) shifted the question. Now the leverage isn’t “how do we move data,” it’s “what AI workflow can we run on the data we have.”
A modern RevOps team writes Claude Skills, builds n8n agents that triage inbound, deploys Cursor rules for the data-engineer types, and treats the AI tool stack as a first-class domain — not a side experiment.
Adjacent functions
- Marketing Ops — same idea, scoped to marketing’s tools (HubSpot Marketing Hub, Marketo, Pardot, Customer.io)
- Sales Ops — sales-only, the predecessor of RevOps
- CS Ops / Customer Success Ops — customer success-only, focused on Gainsight, Catalyst, Vitally
- GTM Engineering — emerging title for the technical end of RevOps (writes code, builds agents, owns infrastructure)
In a small company these are all the same person. In a large company they’re distinct functions reporting up through the same operations leader.