What does a RevOps team do?

TL;DR

• RevOps owns the GTM tech stack (Salesforce, HubSpot, Gong, Outreach, Clay, LeanData, Default), the data model in Snowflake or BigQuery, and the dashboards leadership uses on Monday mornings.
• The team runs five recurring rituals: weekly forecast, monthly pipeline council, quarterly territory rebalance, annual planning, and continuous deal desk.
• Benchmark headcount is roughly 1 RevOps FTE per $10M–$15M ARR for venture-backed B2B SaaS (per Pavilion's 2025 RevOps Benchmark Report).
• Top-quartile RevOps teams lift win rates 8–12 points and shorten sales cycles 15–20% within four quarters (ICONIQ Growth Topline 2024).
• The function reports to a CRO 62% of the time and to a CFO 18% (Forrester, 2025).

The Five Things a RevOps Team Actually Does All Week

The job is not "Salesforce admin plus reporting." A modern RevOps team operates five concurrent workstreams.

1. Tech stack ownership. They are the DRI for every dollar spent on GTM software. A typical Series C SaaS company runs 18–25 GTM tools at $1,800–$3,400 per rep per year (Bessemer State of the Cloud 2025). RevOps negotiates contracts with Salesforce, HubSpot, Gong, Outreach, Clari, ZoomInfo, Clay, LeanData, Chili Piper, CaptivateIQ, and DocuSign, and builds integrations via native connectors, Workato, or Tray.io. When Marketing wants 6sense and Sales wants Demandbase, RevOps picks one and kills the other.

2. The data model. They define what an "opportunity" is, what each stage means, what counts as an SQL versus MQL, and how ARR is calculated. The canonical stack in 2026: Salesforce or HubSpot feeds Fivetran, lands in Snowflake or BigQuery, gets modeled in dbt, and surfaces in Looker, Mode, or Hex. RevOps owns the dbt models for fct_opportunity, dim_account, and fct_arr_snapshot. Without this, the CEO's board deck and the CRO's forecast won't match — the single most common reason RevOps leaders get fired.

3. Forecast and pipeline. Every Monday or Tuesday, RevOps runs the call: top-down forecast versus rep-submitted forecast versus AI-assisted forecast in Clari or Gong Forecast. They surface pipeline coverage (target: 3.0–3.5x for net-new, 2.0x for renewals per ICONIQ 2024). They flag stalled deals, slipped opportunities, and coverage gaps by segment. The output is a single number the CRO commits to the CFO.

4. Territory, quota, and comp. Annual planning starts in October for a January fiscal. RevOps uses Fullcast or Varicent Territory Planning to model territories, then sets quotas at 4–6x OTE for AEs (Pavilion benchmarks). Commission plans get built in CaptivateIQ, Spiff, or Everstage. A bad comp plan costs companies 2–4% of revenue annually (Alexander Group, 2025).

5. Deal desk and process. RevOps approves non-standard discounts, custom terms, and multi-year structures. They run the CPQ in Salesforce CPQ, DealHub, or HubSpot's native quoting. They build approval workflows so a 40% discount doesn't get signed without VP Sales sign-off.

How RevOps Is Structured at Different Stages

At Seed–Series A ($0–$5M ARR), one Head of RevOps or Sales Ops does everything, reporting to the CEO or first sales leader. At Series B–C ($10M–$50M ARR), the team splits into Sales Ops, Marketing Ops, and Systems/Analytics — typically 3–6 people. At Series D+ and public companies, a VP RevOps or SVP Revenue Strategy & Operations runs four pillars: Strategy & Planning, Systems, Analytics & Insights, and Enablement Operations. HubSpot, Snowflake, and Gong have published their org charts publicly — roughly 1 RevOps FTE per 12 quota-carrying reps.

Notable RevOps leaders worth following: Jeff Ignacio (formerly UpKeep, now advising), Rosalyn Santa Elena (The RevOps Collective), Sean Lane (Drift, now BrainTrust), and Camela Thompson (CaliberMind). Pavilion's RevOps community and the Wizards of Ops Slack are the two main practitioner hubs.

What Separates Great RevOps From Mediocre RevOps

Top-quartile teams obsess over three things. First, data trust — forecast, ARR, and win rate must reconcile across CRM, warehouse, and board deck. Second, rep adoption — they measure opportunities with logged next steps, Gong call recording rate, and Outreach sequence enrollment. Third, cycle time on their own work — they ship a lead-routing change in hours via LeanData or Default, not weeks via a Salesforce admin ticket queue.

Mediocre teams get stuck running reports on demand and rebuilding the same dashboard for every new VP. The fix: productize requests with a Jira intake form, an SLA, and ruthless prioritization against a published OKR set tied to the CRO's number.

Related on PULSE

• [Can a 2027 RevOps team align sales and marketing with only one AI orchestration platform after consolidation?](/knowledge/q16606)
• [Can a 2027 RevOps team survive with only two CRM vendors when the buying committee demands five point solutions?](/knowledge/q16598)
• [How does your RevOps team audit AI predictions that change weekly in 2027?](/knowledge/q16447)
• [Which 2027 data privacy update is blocking your RevOps team from tracking buying committee members?](/knowledge/q16377)
• [Which data points must a 2027 RevOps team extract from AI chat transcripts to score buying committee sentiment?](/knowledge/q16313)
• [Which five vendor relationships should a 2027 RevOps team consolidate first to reduce data latency?](/knowledge/q16306)

Typical RevOps Team Structure & Roles

A fully functioning RevOps team typically includes 4-6 core roles, though early-stage companies may combine several into one person. The most common structure breaks down as:

• RevOps Manager/Director – Owns the overall strategy, stakeholder alignment, and quarterly business reviews. This role spends roughly 40% of time on cross-functional coordination and 60% on execution.
• Systems Administrator – Manages the CRM (Salesforce or HubSpot), handles user permissions, field creation, workflow automation, and integration maintenance. Usually 1 admin per 50-80 CRM users.
• Data Analyst – Builds dashboards, maintains data quality, runs pipeline analysis, and produces weekly forecasts. Often uses SQL, Tableau, or Looker.
• Process/Enablement Specialist – Documents standard operating procedures, designs handoff workflows between teams, and trains new hires on systems usage.
• Compensation & Quota Analyst – Models commission plans, calculates attainment, and manages territory alignment. This role frequently reports into Finance but sits within RevOps.

At smaller companies (under 50 employees), RevOps is often a single person wearing all these hats. At enterprises (500+ employees), teams can grow to 15-30 people with dedicated pods for each function. A common ratio is 1 RevOps FTE per 30-40 revenue team members.

Key Metrics a RevOps Team Owns & Reports

Beyond the obvious pipeline and revenue numbers, a mature RevOps team tracks a set of diagnostic metrics that reveal the health of the revenue engine:

• Data Quality Score – Percentage of records with complete, accurate fields (target: 85%+). Poor data hygiene directly impacts forecasting accuracy and automation reliability.
• Lead-to-Opportunity Conversion Rate – Measures how effectively marketing-qualified leads become sales-accepted opportunities. Industry benchmarks range from 15-30% depending on volume and qualification rigor.
• Sales Cycle Length – Average days from first touch to closed-won. RevOps identifies bottlenecks (e.g., stalled demo-to-proposal stages) and builds automation to compress cycle time.
• CRM Adoption Rate – Percentage of reps logging activities, updating stages, and maintaining pipeline within 24 hours. Below 80% adoption typically triggers retraining or system simplification.
• Forecast Accuracy – Variance between predicted and actual closed revenue. Top-performing teams achieve within 5-10% variance at quarter-end.
• Tech Stack Utilization – Percentage of licensed tools actually used weekly. Many companies discover 30-50% of their SaaS spend goes unused, which RevOps audits quarterly.

These metrics shift emphasis based on company stage: early-stage teams focus on conversion rates and data quality, while mature teams obsess over forecast accuracy and efficiency ratios like CAC payback period.

How RevOps Integrates with Other Departments

RevOps does not operate in isolation — it serves as the connective tissue between traditionally siloed teams. The integration points include:

With Finance: RevOps provides the pipeline data that feeds revenue forecasting, while Finance supplies budget constraints and commission payout limits. Together they build the annual operating plan, aligning quota targets with board-level revenue goals. Weekly or bi-weekly syncs prevent the classic "Finance forecast says $5M, Sales forecast says $7M" disconnect.

With Product: RevOps shares win/loss analysis and feature requests gathered from sales calls. This feedback loop helps Product prioritize roadmap items that directly impact conversion rates. Some RevOps teams also track product usage data (via tools like Pendo or Mixpanel) to identify expansion opportunities in existing accounts.

With Marketing Operations: While Marketing Ops focuses on campaign attribution, lead scoring, and content performance, RevOps ensures those leads flow cleanly into the CRM and align with sales stage definitions. A shared SLA document typically governs response times, lead routing rules, and handoff criteria.

With IT/Security: RevOps owns CRM security permissions, data access controls, and vendor risk assessments for new tools. IT provides infrastructure support (SSO, API gateways) while RevOps defines user roles and field-level security that comply with data privacy regulations.

The most effective RevOps teams schedule monthly cross-functional reviews with each department, plus a quarterly "revenue council" meeting where all GTM leaders align on priorities, resource allocation, and process changes. This cadence prevents the common problem of teams operating with conflicting definitions of "qualified lead" or "closed-won."

FAQ

How many people are typically on a RevOps team? It varies widely by company size. Early-stage startups might have one person wearing the RevOps hat, while mid-market companies often have teams of 3–8 people. Larger enterprises can have 20+ RevOps professionals split across data, systems, and process sub-teams.

Does RevOps replace SalesOps, MarketingOps, and CSOps? Not exactly — it often consolidates or aligns them. Many organizations start with separate ops teams and later merge into a unified RevOps function. Others keep specialized roles but have them report into a single RevOps leader to ensure cross-functional alignment.

What tools does a RevOps team typically manage? They usually own the CRM (Salesforce or HubSpot), data warehouse (Snowflake, BigQuery), and revenue intelligence tools (Gong, Outreach, Clay). The stack can range from 10 to 50+ tools depending on company complexity, with RevOps responsible for integration, governance, and cost optimization.

How does RevOps impact revenue directly? By improving pipeline accuracy, shortening sales cycles, and reducing churn through better data and processes. For example, cleaner data can improve forecast accuracy by 10–20%, and streamlined handoffs between marketing and sales can increase conversion rates. The exact impact depends on the company’s starting point.

Do you need a technical background to work in RevOps? It helps but isn’t always required. Many RevOps professionals come from sales, marketing, or finance and learn the technical side on the job. However, familiarity with SQL, CRM administration, and data modeling is increasingly common for mid-to-senior roles.

How often does a RevOps team update forecasts and reports? Typically weekly for pipeline and revenue forecasts, with monthly or quarterly deep dives for board reporting. Real-time dashboards are common, but the team usually refreshes key metrics at a cadence that matches the sales cycle — often weekly for SaaS, monthly for longer enterprise deals.

Sources

1. Pavilion. *2025 RevOps Benchmark Report.* joinpavilion.com
2. Forrester. *The State Of Revenue Operations, 2025.*
3. ICONIQ Growth. *Topline Growth and Operational Efficiency Report 2024.*
4. Bessemer Venture Partners. *State of the Cloud 2025.*
5. Gartner. *Market Guide for Revenue Operations Platforms, 2025.*
6. MIT Sloan Management Review. "How High-Performing Sales Organizations Use Data," 2024.
7. Alexander Group. *2025 Sales Compensation Trends Survey.*
8. The RevOps Co-op and Wizards of Ops community benchmarking, 2025.