One of the most common questions I get from founders and sales leaders who are starting to take RevOps seriously: who should we hire, where should they report, and when? The question sounds tactical but it's actually strategic — the wrong RevOps structure creates political problems that are harder to fix than the data problems you hired RevOps to solve.
This post covers RevOps team design at each stage of growth: what you need, what you don't need yet, and how the function should evolve as you scale.
The Core Principle: RevOps Serves the Revenue Org, Not a Single Team
Before we talk about headcount and reporting lines, the principle: RevOps is a cross-functional function. It serves marketing, sales, and customer success equally. The moment it becomes "Sales Ops with a different name" — or worse, a subteam of Marketing — it loses the neutrality that makes it effective.
Who does your RevOps lead report to? The answer shapes everything. Reporting to the CRO or CEO is ideal. Reporting to the CMO means marketing needs will dominate. Reporting to the VP of Sales means sales needs will dominate. Reporting to the CFO often means it becomes a finance function rather than an operational one.
Stage 1: Pre-$5M ARR — One Person or Fractional
At this stage, you don't need a RevOps team. You need RevOps outcomes: a working CRM, a documented sales process, basic reporting, and clean handoffs between marketing and sales. One strong generalist RevOps operator can deliver all of that.
Whether that person is a full-time hire or a fractional consultant depends on your budget and how much ongoing system maintenance you need. For most companies under $5M, fractional is the better choice — you get senior-level expertise without the cost of a full-time hire, and you're not building a department before you've figured out what the department needs to do.
The RevOps before your first hire guide covers how to build the infrastructure before bringing someone full-time.
Stage 2: $5M–$30M ARR — First Full-Time RevOps Hire
This is typically when companies make their first dedicated RevOps hire. The role at this stage is a generalist: someone who can own the CRM, build reports, design and maintain workflows, and be the operational backbone of the revenue org.
What to look for in this hire: systems thinking, SQL or data skills, HubSpot or Salesforce admin experience, and enough business judgment to say "that's not an ops problem, that's a process problem" when a sales leader asks them to fix something in the CRM that shouldn't be fixed in the CRM.
This person should report to the CRO or VP of Sales — whichever role has the most cross-functional revenue accountability. Not to a manager of marketing or sales operations specifically.
Stage 3: $30M–$75M ARR — Specialization Begins
At this stage, a single RevOps generalist is usually hitting capacity. You're adding headcount across sales and marketing. The CRM has more complexity. Reporting requests are coming from more directions. You have a real CS team that needs its own operational support.
The right structure here is usually: a RevOps lead (manager or senior individual contributor) plus one or two specialists. The specialization can go two directions: functional (a Sales Ops specialist + a Marketing Ops specialist) or technical (a systems admin + a data/analytics person).
The functional split maps to where the operational pain is. If marketing automation is a mess, hire marketing ops. If sales quota, territory, and compensation are dragging, hire sales ops. If your data quality is the bottleneck on everything, hire an analyst or data engineer.
Stage 4: $75M+ ARR — A Real RevOps Function
At scale, RevOps typically becomes a proper department with a head of RevOps or VP of RevOps leading three distinct teams: Sales Ops, Marketing Ops, and CS Ops. Each has dedicated headcount. The RevOps leader coordinates strategy, system architecture, and reporting standards across all three.
At this stage, the most important design decision is centralization vs. embedding. Do your sales ops people sit with the sales team or with RevOps? Do your marketing ops people report up through marketing or through RevOps? There's no universal answer — it depends on your culture and how much cross-functional coordination your system complexity requires.
What doesn't work at scale: a fully decentralized model where sales ops reports to sales, marketing ops reports to marketing, and CS ops reports to CS with no central coordination. You end up with three separate systems and no shared truth.
When Fractional Makes Sense at Any Stage
Fractional RevOps isn't just for early-stage companies. There are legitimate use cases at any size: filling a gap during a hire process, handling a specific project (CRM migration, stack rationalization, new GTM motion design) that requires more bandwidth than your internal team has, or bringing in an outside perspective for a RevOps strategy reset.
The test: Is this work ongoing and requires someone who knows your systems deeply? That's a full-time hire. Is it time-bounded and requires a specific skill set you don't have internally? That's fractional or project-based.
Building your RevOps function and not sure where to start?
I help growth-stage and mid-market teams design the RevOps structure that fits where they are — and build the infrastructure that makes a future hire successful from day one.
Talk to Gage →