How do you build a RevOps team from scratch?

TL;DR

• First hire at $3M ARR is a hands-on Salesforce admin or RevOps generalist, not a strategist.
• Comp benchmarks: generalist $95K–$130K base, manager $140K–$170K, director $180K–$220K, VP $250K–$320K OTE.
• Hire in this order through $30M ARR: Generalist → Analyst → Marketing Ops → Manager → CS Ops → Director/VP.
• The #1 failure is hiring a strategist before a systems person; the #2 is burying RevOps under a CRO who only cares about quota.
• At Series C, the mature org has five pods (Systems, Analytics, Sales Ops, Marketing Ops, CS Ops) reporting to a VP RevOps who reports to the CFO or COO — not the CRO.

The First Hire (and the trap)

Almost every founder I have watched build this function makes the same wrong move: they read a Pavilion thread, get excited about "revenue strategy," and hire a Director-level RevOps person from a Series D company for $190K. Six months later that person is furious because they cannot pull a clean pipeline report — the stage definitions are mush, opportunity owners are wrong, and three reps are still working in HubSpot while the rest moved to Salesforce a year ago. The director quits, the founder concludes RevOps was a waste, and the function gets dismantled.

The first hire is a builder, not a thinker. You want a senior Salesforce administrator — ideally someone who has been a #2 on a real RevOps team at a Series B or C company and is ready to own one — or a RevOps generalist with three to six years of operating experience in B2B SaaS. They should be able to write a SOQL query, build a flow without breaking validation rules, run a forecast call without a deck, configure a CPQ rule, and tell the CRO "no, that field already exists, here it is." Comp in the U.S. for this role in 2026 is $95K–$130K base, $110K–$155K OTE, with a small variable tied to system uptime and forecast accuracy.

Give them ninety days with a single deliverable: a trustworthy pipeline. Stage definitions documented, required fields enforced, owner hygiene above 98%, dashboards that match what the CRO says in the QBR. Until that exists, no one on the team can do anything useful, including the strategist you were about to hire.

The Sequence Through $30M ARR

Here is the actual ladder, built around revenue milestones rather than headcount targets, because RevOps complexity scales with deal volume and tech-stack sprawl, not seat count.

$3M ARR — Hire 1: RevOps Generalist. Profile above. They report to the CRO or, ideally, to the COO/CFO. If you can get them reporting outside of sales, do it; it preserves their ability to push back on bad pipeline calls. Base $95K–$130K.

$10M ARR — Hires 2 and 3: Sales Ops Analyst + Marketing Ops Specialist. The Sales Ops Analyst owns forecasting, territory design, comp plan calc, and weekly pipeline inspection ($85K–$115K base). The Marketing Ops Specialist owns the MAP (Marketo, HubSpot, Pardot), lead routing, attribution, and the MQL-to-SQL handoff ($90K–$120K base). Without this hire, demand-gen spend is unaccountable; ICONIQ's 2025 GTM benchmarks show companies without dedicated MOps have CAC payback periods 30–40% worse than peers.

$20M ARR — Hires 4 and 5: RevOps Manager + CS Ops Analyst. Promote the original generalist into the Manager seat ($140K–$170K base, $170K–$210K OTE) or hire externally if they are not ready. Add a CS Ops Analyst ($85K–$110K) the moment your NRR matters to investors — usually right around Series B. They own health scoring, renewal forecasting, expansion playbooks, and the Gainsight or Catalyst instance.

$30M ARR — Hire 6: VP RevOps. OTE $250K–$320K, equity 0.15–0.4%. This is the person who runs annual planning, owns the GTM tech stack budget ($1M–$3M at this stage), partners with Finance on the revenue plan, and sits in the executive staff meeting. Hire from a $100M+ ARR company where they were a Director, not from a $30M company where they were already the VP — you want someone who has seen the next stage.

A note on geography: comp ranges above are SF/NYC. Subtract 15–20% for Austin/Denver, 25–30% for second-tier U.S. metros, 40–55% for LATAM/EMEA remote. Pavilion's 2025 RevOps comp report and Bowery Capital's operator benchmarks both confirm these spreads.

Common Failure Modes

1. Strategist before systems person. Covered above. Symptom: senior hire churns inside a year, founder loses faith in the function.

2. RevOps reporting into the CRO. This works until it doesn't. The moment the CRO needs to spin a bad quarter, RevOps gets pressure to soften the forecast or hide pipeline rot. Best practice — endorsed by Bessemer's State of the Cloud and most public-company orgs — is RevOps reporting to the CFO, COO, or CEO once the company crosses $20M ARR. Bowery Capital's CMO/CRO study found companies with independent RevOps reporting hit plan 22% more often.

3. Hiring consultants instead of FTEs in year one. Big-four or boutique consultants will happily charge you $300K to "stand up RevOps." You get a deck, a Salesforce reorg that breaks three integrations, and no one left to operate it. Use consultants for one-time migrations only. Build the muscle in-house.

4. No analytics seat until too late. Founders confuse "BI" (Looker, Tableau) with "RevOps analytics." They are different jobs. A dedicated Sales/RevOps Analyst who lives in the CRM data and owns weekly forecast calls is non-negotiable past $10M ARR. Without one, the CRO's forecast is a vibe.

Related on PULSE

• [How do you build a RevOps team from scratch in 2027?](/knowledge/q12251)
• [How do you build a 2027 RevOps tech stack from scratch on a $50K annual budget?](/knowledge/q12104)
• [How do you build a sales operations stack from scratch in 2027?](/knowledge/q12261)
• [How do I build a federal / public-sector motion from scratch?](/knowledge/q95)
• [How do you build a deal-desk function from scratch in a 30-rep org without slowing every deal down?](/knowledge/q208)
• [How should a 2027 partner team design a partner program from scratch?](/knowledge/q12521)

Key Metrics to Track Before and After Your RevOps Hire

Before you make your first RevOps hire, establish a baseline for three critical metrics that will define success. Data quality score — measure the percentage of CRM fields that are complete, consistent, and non-duplicative. Most early-stage companies operate at 40–60% data quality; your first hire should target 85%+ within 90 days. Lead response time — track the average minutes between inbound lead capture and sales follow-up. A clean CRM enables automated routing that cuts this from hours to under 5 minutes. Forecast accuracy — calculate the variance between predicted and actual closed revenue over the last 3 quarters. Companies without dedicated RevOps often see 30–50% variance; a functioning RevOps team should drive this below 15%.

Post-hire, add time-to-value metrics: how quickly can your team generate a pipeline report, build a new lead scoring model, or deploy a sales playbook? A single RevOps generalist should reduce these from weeks to days within their first quarter. Track system adoption rates — the percentage of sales reps logging activities, updating deal stages, and using automation features. If adoption drops below 70% after 6 months, your RevOps hire may be building systems that don't match how your team actually sells. Finally, monitor revenue per RevOps head — a healthy ratio is roughly $3M–$5M ARR per full-time RevOps employee. If you're below $2M per head, you may have over-hired; above $8M suggests you're under-invested.

Common Pitfalls When Scaling from One to a Team

The transition from a single RevOps generalist to a multi-person team is where most companies stumble. Pitfall #1: Keeping the generalist as the only hire too long. Many founders get comfortable with their first hire and delay adding headcount until $15M–$20M ARR. By then, that person is drowning in tickets, has no time for strategic work, and burnout risk is extreme. The rule of thumb: when your RevOps person spends more than 50% of their week on reactive requests (fixing reports, resetting passwords, cleaning imports), you need a second hire immediately — regardless of ARR.

Pitfall #2: Hiring specialists before the foundation is solid. It's tempting to bring in a Marketing Ops lead or a dedicated Salesforce developer when you hit $10M. But if your core data model, lead routing, and reporting infrastructure aren't clean, specialists will spend their time fighting fires rather than building. One founder I worked with hired three specialists at $12M ARR and saw zero improvement in forecast accuracy for 8 months because they were all working from different definitions of "qualified lead." Pitfall #3: Letting the VP RevOps hire happen too late. By the time you're managing 4–6 RevOps people across different functions, someone needs to own prioritization, career development, and cross-functional alignment. If you wait until $40M+ to hire a VP, you'll have siloed teams building redundant tools and conflicting processes. The right window is $25M–$35M ARR, when you have at least 3 RevOps people and clear functional separation emerging.

Integrating RevOps with Existing Sales and Marketing Leadership

A RevOps team built from scratch will fail if it operates in a vacuum. Establish a weekly "triad" meeting from day one — 30 minutes with the Head of Sales, Head of Marketing, and your RevOps lead. The agenda is fixed: review pipeline health (stage movement, aging, conversion rates), discuss system changes needed, and flag any data integrity issues. This meeting prevents RevOps from becoming a "ticket-taking" department and forces cross-functional ownership of revenue data.

Define clear RACI boundaries for every major revenue process — lead handoff, deal progression, renewal management. A common mistake is giving RevOps full ownership of CRM hygiene but no authority to enforce standards. The VP of Sales must visibly back RevOps decisions about data entry requirements, stage definitions, and pipeline reviews. Without this backing, your RevOps team becomes powerless to fix the very problems they were hired to solve. Create a "RevOps council" of one sales leader, one marketing leader, and one customer success leader who meet monthly with the RevOps team to prioritize the next quarter's systems roadmap. This ensures that the tools and automations being built actually solve real revenue team problems, not just technical curiosities. Companies that formalize this council see 40% faster adoption of new RevOps initiatives and significantly lower churn of their RevOps hires — because the team feels heard and impactful rather than like an internal IT help desk.

FAQ

What is the first role I should hire for a RevOps team? Hire a systems person first, not a strategist. A Salesforce admin or RevOps generalist focused on making the CRM trustworthy is the right starting point. This role typically costs $95K–$130K base and should be brought on around $3M ARR.

When should I add a second person to the RevOps team? Around $10M ARR, you should add a Sales Ops analyst and split responsibilities into Systems and Analytics. This creates a two-person team that can handle both CRM management and data analysis.

How does the team scale beyond $30M ARR? At $30M ARR, you build out functional pods — Sales Ops, Marketing Ops, CS Ops, Systems, and Analytics. These pods should report to a VP of RevOps, whose total compensation typically ranges from $250K–$320K OTE.

What is the biggest mistake when building a RevOps team? Hiring a Director of RevOps before anyone has cleaned the data they're supposed to operate on. This reverses the proper order and often leads to frustration and inefficiency.

Do I need a RevOps team if I'm below $3M ARR? Not a full team, but you should have someone responsible for CRM hygiene and basic reporting. This could be a fractional RevOps person or a technically-minded early employee who can keep the CRM clean.

How long does it take to build a mature RevOps function? The timeline varies widely based on company growth rate and resources. Most companies go from a single hire to a full team with pods over 2–4 years, assuming they hit the revenue milestones along the way.

Sources

• Pavilion, "2025 RevOps Compensation Report" — base and OTE benchmarks by level.
• Bowery Capital, "CMO and CRO Operating Benchmarks 2025" — reporting structure data.
• OpenView Partners, "2025 SaaS Benchmarks Report" — RevOps headcount ratios.
• ICONIQ Growth, "Topline Growth and Efficiency 2025" — CAC payback and MOps impact.
• Bessemer Venture Partners, "State of the Cloud 2026" — go-to-market efficiency benchmarks.
• SaaStr, "The First RevOps Hire" by Jason Lemkin — founder-stage guidance.
• RevOps Co-op, "2025 Salary and Hiring Survey" — community comp data by geography.
• Gartner, "Revenue Operations Maturity Model 2025" — pod structure and reporting evolution.

People also search for: build a revops team from scratch · how to build a revops team from scratch · build a revops team from scratch guide