TL;DR: Revenue Operations (RevOps) is the team that keeps marketing, sales, and customer success working as one revenue engine. In practice, a RevOps team's day comes down to four repeatable jobs: cleaning CRM data, routing leads to the right rep, keeping the forecast honest, and smoothing handoffs between teams. Ballet lets RevOps run those deterministic rules as versioned playbooks instead of fragile zaps and point tools.
Ask five people at a SaaS company what RevOps does and you will get five different answers: "they fix Salesforce," "they build dashboards," "they own territories," or "they manage commissions."
RevOps exists because revenue touches four teams that each buy their own software:
Left alone, every handoff between those systems breaks. Duplicates pile up, leads wait hours for a reply, forecasts slip, and customers get asked the same onboarding questions twice. RevOps owns the system of rules that connects them.
Strip away the org-chart jargon and almost everything RevOps does falls into four concrete workflows.
Three records for "Northwind", "Northwind Ltd", and "northwind.io" enter the CRM from a webinar, an inbound form, and a billing webhook. RevOps deduplicates accounts, standardizes fields (country, industry, employee band), and keeps billing and CRM records in sync so teams are not arguing over whose number is right.
When a new lead arrives, someone has to decide who gets it and how fast. RevOps maintains the territory rules, segment splits (SMB vs. Mid-Market vs. Enterprise), round-robin pools, and capacity caps—and updates them immediately when a rep joins, goes on leave, or changes territory.
Leaders want one reliable number, not a spreadsheet stitched together on Sunday night. RevOps inspects stage definitions, flags stale deals with no activity in 14+ days, tracks slipped close dates, and rolls up weighted pipeline so commit calls are grounded in reality.
When marketing qualifies an account, sales needs the campaign context. When sales closes a deal, customer success needs the contract terms, stakeholders, and implementation notes—without chasing the AE in Slack. RevOps automates those bridges so no deal falls through the cracks.
| Role | Primary focus | Core systems owned | Typical output |
|---|---|---|---|
| RevOps | End-to-end revenue lifecycle across Marketing, Sales, CS, and Finance | CRM architecture, cross-team routing, forecasting, billing sync | Unified pipeline, clean handoffs, predictable revenue |
| Sales Ops | Seller productivity, territories, quotas, and deal desk | CRM sales stages, CPQ, commission & territory tools | Rep capacity plans, quote approvals, forecast prep |
| Marketing Ops | Campaign execution, attribution, lead scoring, and consent | MAP (HubSpot/Marketo), ad platforms, web forms | MQL flow, attribution reports, clean campaign tracking |
| CS Ops | Post-sale retention, onboarding, health scoring, and renewals | Help desk, CS platform, NPS/CSAT surveys | Renewal risk alerts, onboarding SLAs, expansion signals |
In smaller companies (under 100 people), one RevOps generalist or small team wears all four hats. At scale, Sales Ops, Marketing Ops, and CS Ops specialize while RevOps sets the shared data model and cross-team rules.
Most RevOps teams end up owning a ring of point tools around the CRM: a dedupe app, a routing engine, an iPaaS or reverse-ETL sync, and dozens of scheduled scripts or zaps.
In Ballet, you describe the rule in plain English (or build it with Ask Ballet), connect your existing tools, and run it on webhooks or schedules with a full audit log of every field changed.
In modern SaaS teams, RevOps most often reports to the CRO, COO, or CFO so it stays neutral across Marketing, Sales, and Customer Success rather than optimizing for just one department's metrics.
RevOps typically owns pipeline velocity, speed-to-lead, stage-to-stage conversion rates, forecast accuracy, net revenue retention (NRR) visibility, and CRM data completeness.
Use AI to classify, enrich, and draft—never to invent routing rules on the fly. In Ballet, an evaluation step can score lead fit or summarize deal risk, while deterministic playbook steps write the exact CRM fields and trigger approvals.