# RevOps
RevOps, Revenue Operations, is the function that owns systems, data, and process across the sales, marketing, and customer success organizations. It emerged in the mid-2010s as companies realized that running each go-to-market function as a separate operations group produced data silos at exactly the points where the funnel handoff mattered most. By 2020 most mid-market and enterprise SaaS companies had consolidated under a single RevOps leader. By 2026 it is the default operating model for companies past about 100 employees.
The role spans tooling administration, data quality, process design, forecasting, and increasingly AI-and-agent enablement across the GTM stack. A working RevOps team is invisible to the rest of the organization in the same way good plumbing is invisible, the water arrives, the temperature is right, the pipes do not burst. A failing RevOps team is also invisible, but the downstream symptoms (bad forecasts, broken handoffs, duplicate work, blame) are extremely visible.
Why it matters
The leverage RevOps provides is structural rather than tactical. A good RevOps team is the difference between a sales org where reps spend 30 percent of their time on actual selling and one where they spend 60 percent. The other 30-40 percent in a poorly-operated org goes to manual data entry, list cleanup, tool reconciliation, and chasing down the right contact information that should have been there in the first place.
The data layer is where RevOps creates or destroys the most value. Every other GTM function downstream, segmentation, scoring, ICP definition, forecasting, customer health, depends on the data being right. A RevOps team that gets the data right enables everything else. A RevOps team that lets the data rot caps every other team's ceiling.
The other reason RevOps matters specifically in 2026 is the shift to agent-driven outbound. Agents amplify both the upside and the downside of the underlying operations. A team with clean data and well-defined processes can hand the agent the work and trust the output. A team with messy data and ad-hoc processes will discover the mess at a faster rate than they can clean it up. RevOps becomes the gating function on how much agent leverage the company can capture.
This is a meaningful change in the role. Pre-agent, RevOps could get away with reactive tooling work. Post-agent, RevOps has to think about what the agent will need to do its work, which is a more architectural responsibility.
Common pitfalls
The first is over-indexing on CRM hygiene at the expense of process design. A clean Salesforce instance is necessary but not sufficient. If the underlying process, who hands what off to whom, on what trigger, is unclear, no amount of field-cleanup tooling will fix it.
The second is treating RevOps as a ticketing queue. The function works best when it is forward-looking and embedded in the GTM leadership conversation. Companies that staff RevOps as a back-office support team get exactly that, a support team, and miss the strategic value.
The third is buying tools without designing the integration. Every new tool added to the stack creates new seams. Without a deliberate data flow design, the new tool adds capability and removes coherence. Most stacks get worse before they get better when this happens.
The fourth is failing to invest in dedupe and identity resolution. Bad dedup is the cheapest expensive problem in B2B operations, the cost is hidden in duplicate sends, missed handoffs, and forecast errors, but the fix is structural and pays back across every downstream system.
How it shows up in agent-driven workflows
RevOps is the function that owns the agent's operating environment. The capability manifest, auth scopes, readable data, and actions allowed without approval are RevOps decisions that ripple through every team using the agent.
In Coil specifically, the RevOps-relevant surface includes organization membership, role gates, actor-typed logging on supported mutations, provider connections, and the policy applied to outbound webhook actions. These controls apply to both dashboard users and authenticated machine callers.
The automations layer currently provides explicit webhook actions, not automatic funding, hiring, reply, churn, or calendar triggers. A human organization admin controls the allowed domains and fields and publishes the reviewed automation. A caller then selects leads or a bounded lead scope, admits the run explicitly, and inspects its delivery results and evidence links.
The pattern works because Coil's dashboard and JSON CLI share an authenticated API. A RevOps team can script supported setup, version-control the procedure, and apply it without automating the UI. Machine callers remain subject to the same organization and approval boundaries.
Related concepts
ICP is one of the artifacts RevOps owns or co-owns with sales leadership. The ICP is too important to leave informal and too data-dependent to belong solely to sales.
Dedupe is a core RevOps responsibility. Identity resolution across systems is one of the function's defining problems.
SDR is the role most affected by RevOps quality. A good RevOps team makes SDRs productive. A bad one makes them quit.
Agent-driven outbound is the operating model RevOps now enables, configures, and increasingly defines for the whole GTM org.
For Coil's specific RevOps surface in the platform, see the automations product page and the Coil methodology pillar.
Frequently asked questions
How is RevOps different from Sales Ops?
Sales Ops historically scoped to the sales org alone. RevOps spans sales, marketing, and customer success, with the goal of operating the full revenue funnel as one connected system. The shift was largely driven by the realization that the seams between the three functions were where most leakage happened.
Should a small startup have RevOps?
The function should exist before there is headcount for it. Until then, the founder or the first GTM hire owns it. Companies that wait to hire a dedicated RevOps person until 30-50 employees tend to ship the same systems-and-data debt every time. Better to assign the function early and let the role grow into it.
Does RevOps own outbound?
RevOps owns the systems outbound runs on, CRM, sender, enrichment, the data flowing between them. The campaign strategy and the messaging usually belong to the sales or marketing leader. The split varies by company but the cleanest version is: RevOps owns the rails, sales owns the campaigns.