Last month a Series A founder asked me a question I hear constantly: "We're hiring our first ops person. Should the title be Sales Operations or Revenue Operations?" She had two candidates. One was a former HubSpot admin with five years inside a sales team. The other was a generalist who had run cross-functional projects across sales, marketing, and CS at a Series B SaaS.
She thought the question was about candidates. It was actually about her company. At 14 reps and $4M ARR, she did not need a RevOps leader. She needed someone to clean up her pipeline, fix her routing, and stop her AEs from spending two hours a day in spreadsheets. That is a Sales Ops job, not a RevOps job, and confusing the two costs B2B companies real money.
This post is the explanation I send founders when they ask me to break this down. What each function actually does, how they differ in practice (not in LinkedIn job posts), and which one to hire first based on your stage.
The fast answer
Sales Operations supports the sales team. Revenue Operations aligns sales, marketing, and customer success around shared revenue outcomes. Sales Ops is a function. RevOps is a structure.
If you have fewer than 8 quota carriers, are under $10M ARR, and your marketing team is two people and a spreadsheet, you need Sales Ops. If you are past $25M ARR with separate marketing ops, CS ops, and a finance team that wants weekly forecasts, you need RevOps. Between those points it depends on your GTM motion and how messy your handoffs are.
That is the short version. The rest of this post is the nuance, the trade-offs, and the specific job description for each role.
Sales Ops is who you hire. RevOps is how you organize.
Most founders pick the wrong title because they confuse a role with a strategy. The first hire is almost always Sales Ops, even if you call it something else.
What Sales Operations actually does
I have run Sales Ops at three companies. The job is concrete and the work is daily. A Sales Ops person owns the CRM, the rep workflow, and the sales reports. Their job is to make AEs faster and the VP of Sales smarter.
A typical week looks like this:
- Build a new pipeline stage and update the deal automations in HubSpot
- Fix a routing rule that sent two inbound demos to the same rep
- Pull the forecast for the QBR and reconcile it with finance
- Train two new AEs on the CRM and the sales sequences
- Investigate why deals are dying at the "Discovery" stage and bring the data to the VP
- Deactivate three sales tools nobody is using and consolidate the stack
The center of gravity is the sales team. The KPIs are pipeline coverage, win rate, sales cycle length, quota attainment, ramp time. When the VP of Sales asks "what is my pipeline by stage and how does that compare to last quarter," Sales Ops answers in five minutes, not five days.
Tooling-wise, Sales Ops lives in HubSpot Sales Hub or Salesforce, plus the engagement platform (Outreach, Salesloft, Apollo), plus enrichment (Clay, ZoomInfo), plus whatever dialer the team uses. A good Sales Ops hire knows these tools deeply and can configure them without an engineer.
What Revenue Operations actually does
RevOps owns the revenue engine across functions. Same job at a higher altitude and with more stakeholders. A RevOps leader is responsible for the integrity of the data and the design of the process from the first marketing touch through renewal and expansion.
The work is less about CRM tickets and more about systems thinking. Things like:
- Defining what an MQL is, getting marketing and sales to agree, and putting it in writing
- Designing the lead-to-cash flow so marketing's HubSpot, sales's Salesforce, and CS's Gainsight all reflect the same account state
- Owning the revenue forecast across new business, renewal, and expansion
- Running the QBR for the CEO, not just the VP of Sales
- Standing up an attribution model that does not get torn apart in the next exec meeting
The center of gravity is the executive team. The KPIs are net revenue retention, CAC payback, total revenue, conversion across the full funnel. When the CEO asks "why did our pipeline shrink by 30% even though marketing's lead volume went up," RevOps answers with a real diagnosis, not a guess.
Most RevOps leaders started in Sales Ops, moved to Marketing Ops or Finance, then came back as the head of the whole thing. The work assumes a level of cross-functional fluency that pure Sales Ops people often have not built yet.
Where the difference shows up in real work
The job titles sound similar on paper. The actual day-to-day is very different. Here is the cleanest way to see it.
This is also why salaries are so different. A US-based Sales Ops manager runs $110K to $150K. A RevOps director or VP runs $180K to $280K base, plus equity. If you hire a $250K RevOps leader to do CRM admin for 6 AEs, you are wasting money. If you hire a $120K Sales Ops manager and ask them to redesign your attribution model and align three executives, you are setting them up to fail.
When to hire which: a stage-based view
I have built ops teams at companies ranging from 5 reps to 200. The right hire depends almost entirely on stage and GTM complexity. Here is the rough map I use with clients.
The biggest mistake I see is founders skipping Stage 02 and trying to hire a senior RevOps leader straight from Sales Ops chaos. The candidate gets stuck doing CRM tickets, gets bored in six months, and leaves. Or the founder hires too junior for the RevOps title and the person drowns the first time marketing and sales fight about attribution.
The second biggest mistake is the opposite: companies past $30M ARR with a Sales Ops manager and no marketing or CS ops. Marketing pulls reports out of HubSpot. Finance pulls them out of NetSuite. Customer Success pulls them out of Gainsight. None of the numbers match. The VP of Sales is making decisions on the wrong data. At that scale you have outgrown Sales Ops as a standalone function.
The "RevOps" job that is actually Sales Ops
A lot of B2B companies post a "RevOps Manager" role for the salary of a Sales Ops manager. The job description is usually 80% sales support, 15% marketing data, and 5% "you will own the revenue strategy." This is fine. Just be honest about what you are hiring.
If your real need is:
- A HubSpot or Salesforce admin who can also pull reports
- Pipeline hygiene and deal stage discipline
- Sales tool evaluation and contract management
- Rep enablement and onboarding support
...then write a Sales Ops job description and pay accordingly. Calling it RevOps because the title sounds better is how you lose the candidate three months in when they realize the job is not what was advertised.
If your real need is:
- Designing the GTM data model from scratch
- Owning the forecast that the board reviews
- Aligning sales, marketing, and CS leaders on definitions, SLAs, and incentives
- Building the analytics layer that powers exec decisions
...then yes, that is RevOps and you should pay a RevOps salary. But you also need executive buy-in, because a RevOps leader without authority across the three GTM functions is going to spend their first year political and their second year looking for another job.
What the org chart looks like at each stage
I get asked this often enough that I will draw it explicitly.
At $5M ARR with one Sales Ops hire: that person reports to the VP of Sales. Marketing handles their own HubSpot. CS is small enough that the head of CS does it themselves. The Sales Ops manager helps the marketing team with HubSpot questions when asked.
At $15M ARR: Sales Ops still reports to VP of Sales, but now there is a Marketing Ops contractor or junior hire reporting to the head of Marketing. The two ops people talk weekly. Nothing is consolidated yet.
At $30M ARR: a Head of RevOps reports to the CRO or COO. Sales Ops, Marketing Ops, and CS Ops report into them. All revenue dashboards come from one team. The forecast is one document, not three.
At $75M+ ARR: full RevOps org. Director of Sales Ops, Director of Marketing Ops, Director of CS Ops, plus a dedicated analytics or BI lead. The Head of RevOps is now a VP, often reporting directly to the CRO or CEO.
Why "RevOps owns everything" is the wrong instinct
There is a school of thought that says RevOps should sit on top of all GTM operations from day one, even at 10 reps. I disagree.
At early stages, the value of ops is in execution speed. You need someone who can build a workflow in HubSpot in 30 minutes, fix a Salesforce permission issue before the rep's next call, and have the dashboard ready when the board email goes out. That is heads-down operator work. Senior RevOps leaders, the ones worth their salary, do not want to do this work and are not good at it anymore.
What junior or mid-level Sales Ops people are good at: getting their hands dirty, learning the tools end to end, building relationships with the AEs they sit next to in Slack. This is the foundation everything else gets built on. Skip it and your future RevOps team has no operational muscle to draw on.
The right pattern is: hire Sales Ops first, let them earn the trust of the sales team, and as the company grows either promote that person into RevOps or hire above them with their input. The worst pattern is hiring a senior RevOps person too early and forcing them to do work they hate while the AEs grumble that "ops never ships anything useful."
The tools that go with each role
A Sales Ops manager should be deep in two or three tools and competent in the rest. A RevOps leader should be conceptually fluent in all of them and trust their team to be deep.
If you want to see how this stack fits together at an SMB or Series A company, I wrote a detailed breakdown of the minimal RevOps tech stack that does not require a full ops team. And if your immediate problem is the CRM data itself rather than the org chart, our CRM and RevOps service is where most engagements start.
Hiring questions that separate the two roles
When you interview candidates, ask different questions depending on which role you actually need.
For a Sales Ops hire, ask:
- Walk me through the last HubSpot or Salesforce workflow you built. Why did you build it that way?
- A rep tells you their pipeline view is broken. How do you debug it in the next 20 minutes?
- Show me how you would set up routing for inbound demos across 8 AEs in 3 time zones.
- What is your forecast accuracy method and how do you reconcile rep-level forecasts with the VP's gut?
For a RevOps hire, ask:
- Walk me through how you defined "Marketing Qualified Lead" at your last company. Who pushed back and how did you resolve it?
- The VP of Sales says marketing leads are garbage. The CMO says sales is not following up. What do you do?
- Your CFO wants a quarterly forecast that ties to the financial model. How do you build it?
- What is the worst attribution decision you have shipped and what did you change?
Sales Ops questions are about execution. RevOps questions are about judgment, alignment, and political navigation. If you ask RevOps questions to a Sales Ops candidate, you will get blank stares from a perfectly capable hire. If you ask Sales Ops questions to a RevOps candidate, you will get answers that sound great but tell you nothing about whether they can actually run cross-functional revenue.
Average total cost (salary plus opportunity cost) of a mis-hired RevOps leader at a Series A company, based on the four cases we have audited in the last 18 months.
The fractional middle ground
For companies in the $2M to $15M range that cannot afford a senior RevOps leader but have outgrown a single Sales Ops manager, the fractional model works well. You hire a Sales Ops manager full-time, then bring in a fractional RevOps consultant 10 to 20 hours a month to handle the cross-functional design work.
This is the model we run with most of our clients. The full-time hire keeps the day-to-day operating. The fractional layer designs the data model, sets the attribution approach, and coaches the Sales Ops manager toward eventually owning more of it. It is also dramatically cheaper than a full-time senior hire who would be 40% utilized at this stage.
If this matches where you are, our AI and automation and go-to-market practices both run on this model and we are happy to scope it for you.
Not sure which role you actually need?
Book a free 30-minute audit and we will walk through your stage, your stack, and tell you whether your next hire is Sales Ops, RevOps, or neither.
Book an audit →FAQ
Can one person do both Sales Ops and RevOps?
Yes, but only at small companies. Under about $10M ARR a strong Sales Ops manager can cover the RevOps surface area informally because there are not enough stakeholders to manage. Past $15M ARR the cross-functional load gets too heavy for one person and the Sales Ops work starts slipping.
Should RevOps report to Sales, Marketing, or Finance?
The cleanest answer is the CRO or COO. Reporting to the VP of Sales makes RevOps look like a sales function and starves the marketing and CS work. Reporting to the CFO makes RevOps look like reporting and starves the operational work. Reporting to a CRO or COO with authority across all three GTM functions is the only setup that lets RevOps do its job.
Is Sales Ops a dying role?
No. The headlines about "RevOps replacing Sales Ops" are mostly marketing copy. In every mature B2B org I have seen, Sales Ops still exists as a function inside the RevOps org. The role has not died, it has gotten a manager.
What is the typical title progression?
Sales Operations Analyst (1 to 3 years experience) → Sales Operations Manager (3 to 6 years) → Senior Sales Ops Manager or Director of Sales Ops (5 to 8 years) → Head of RevOps or VP RevOps (8+ years, with marketing or CS ops exposure along the way). About a third of senior RevOps people came in through Marketing Ops or Finance rather than Sales Ops, which is healthy.
How do I know if I am hiring at the wrong level?
Three signs: candidates with the right experience keep turning down your offer, the role has been open for more than 90 days, or you find yourself negotiating the job description down to match the salary. Any of those means the title and the comp are misaligned, and the fix is almost always to reduce the title to Sales Ops and hire someone who is excited to grow into the bigger role.