A CEO of a 60-person Series B company called me last quarter. Their sales team had grown from 4 reps to 18 in fourteen months. The CRO was spending two days a week in HubSpot fixing dashboards. The marketing director was building lead routing rules at midnight. The VP of CS was running renewal forecasts on a Google Sheet she did not want anyone to see. Their question was not whether to hire RevOps. It was who to hire, what title, and how to write the job description without describing a unicorn.
This is the most common question I get from founders between $3M and $15M ARR, and the wrong answer wastes 9 to 12 months. Hire too late and the operations debt compounds into broken forecasts. Hire too early and you are paying $140K a year for someone with no system to run. Hire the wrong level and you either get a Salesforce admin who cannot think strategically or a Director who refuses to touch a workflow.
This post is the structured way I think about RevOps hiring for B2B teams, based on the audits we run at Ziel Lab and what I have seen across maybe 40 build-outs in the last four years. The signals, the first hire profile, the next three hires, and the compensation reality in 2026.
When you actually need your first RevOps hire
There is a comfortable myth that you need RevOps from day one. You do not. Founders should run RevOps themselves until somewhere between $2M and $8M ARR. The reason is that RevOps decisions before product-market fit are guesses about a business that does not exist yet, and any system you build will be wrong in interesting ways.
The trigger is not a revenue number. It is a set of operational signals that all show up around the same time, usually when you cross 10 to 15 quota-carrying reps or roughly $4M to $5M ARR.
The signals look like this. Your CRO is spending more than 4 hours a week in spreadsheets fixing forecast inputs. Pipeline reviews take twice as long as they used to because nobody trusts the data. Reps are quietly tracking deals outside the CRM. Marketing and sales are arguing about MQL definitions in Slack threads that never resolve. You have 3 or 4 GTM tools that all write to HubSpot or Salesforce, and the duplicate rate is climbing. Your latest board deck had three different ARR numbers depending on which dashboard you pulled from.
If two or three of those are true, you are late, not early. The cost of operating without RevOps is already higher than the cost of the hire. A recent Landbase analysis put the average operations debt at a Series B at around $300K in wasted comp and bad attribution. That is more than a year of base salary for the person you should already have hired.
What to do before that first hire
Between Seed and Series A, the right answer is almost always fractional or agency RevOps, not a full-time person. The work is too lumpy. You need 60 hours one month to set up the CRM properly, then 8 hours a week to keep the wheels on. A full-time hire at this stage gets bored, builds elaborate dashboards nobody asked for, and leaves in 14 months.
We run this engagement pattern for Series A clients all the time. A 4 to 6 week build out where we design the data model, deploy lead routing, set up forecasting, and document the operating cadence. Then 1 to 2 days a month of optimization for the next 6 months. Total cost is roughly $50K over the year, versus $140K plus benefits for an in-house hire who would not have enough work.
The bigger reason fractional works better at this stage is that early-stage RevOps requires breadth. You need someone who has seen 10 different CRM setups, knows what works in HubSpot Sales Hub versus Salesforce, and can borrow patterns across clients. A single in-house person learns by getting things wrong on your data.
Hire RevOps when the cost of not having it is greater than the salary, not before.
Use fractional or agency support to bridge the gap. The work is too lumpy for a full-time role until 10 to 15 reps.
The profile that actually works for a first hire
Once you cross the threshold, the question is what to hire. Most founders default to one of three wrong answers. They post for a "Salesforce admin" because that is the visible pain. They post for a "VP of RevOps" because their CRO read a LinkedIn post. They post for a "Marketing Operations Manager" because the demand gen lead has been complaining loudest.
All three are wrong for the first hire. The first in-house RevOps person should be a Director-level generalist who can do four things at once.
They should design the revenue system, meaning data model, lifecycle stages, lead routing, forecasting logic, and reporting architecture. They should also build it themselves in HubSpot or Salesforce, no team underneath. They should run cross-functional meetings with sales, marketing, and CS without needing the CRO to be in the room. And they should know data work cold, because 40% of their first six months will be cleaning up the dirty database you inherited from the founder era.
The closest analogy is hiring a senior product manager who can also code. The combination is rare, and the people who can do both command a premium. But it is the only profile that works at this stage. A pure strategist sits in meetings and produces decks while nothing actually changes in the CRM. A pure admin builds workflows but never asks whether the workflow should exist.
The interview signal I trust most is asking them to walk me through a CRM setup they shipped end to end. If the answer is mostly about dashboards they built, pass. If the answer is about a business problem they fixed, where the dashboard was just the last 5%, that is the right person.
The next three hires, in order
Once your first hire has been in seat for 6 to 9 months and the foundations are stable, the question is what comes next. The order matters more than people realize. Sequence wrong and you end up with three people who all want to own the lead lifecycle.
Sales ops before marketing ops is the part most teams get wrong. The intuition is that marketing has more tools and therefore more pain. The reality is that sales ops keeps your CRO out of HubSpot, and a happy CRO buys you 18 months to fix everything else.
Marketing ops is the right second hire only if you are running paid spend above $1M a year and your demand gen lead is making attribution decisions that affect the budget. Below that, the Director RevOps can cover marketing ops adequately for another year.
A note on the analyst hire. Founders often want to make this the second hire because data and dashboards feel concrete. Resist. A standalone analyst before you have a Sales Ops Manager produces beautiful slides that nobody operates on. The order should always be operator first, then operator, then analyst.
What this costs you in 2026
Compensation is where most founders flinch. The numbers are real, and underpaying gets you the wrong person who leaves in a year. Here are the 2026 bands from the RevOps Co-op salary report and our own hiring data with clients.
A Director of RevOps at a Series B will run you $170K to $220K base, plus 15% to 25% bonus, plus equity. Total cash comp lands between $195K and $275K. Add 10% to 15% if they are AI-fluent, which in 2026 means they can build agents in n8n or write prompts that produce real workflows in Clay. AI-skilled RevOps directors are commanding a $60K premium over generalists according to several 2026 reports.
Fully loaded median cost of a Director of RevOps at a Series B in 2026, including base, bonus, and benefits. Underpay and you will rehire inside 14 months.
A Sales Ops Manager runs $110K to $145K base, total $130K to $170K. A Marketing Ops Manager runs slightly less, $100K to $135K base. A RevOps Analyst comes in at $85K to $115K. These are SF and NYC numbers. Reduce by 10% to 20% for second-tier markets, more for fully remote roles outside the US.
VP of RevOps roles, which you should not be hiring until $25M to $40M ARR, run $250K to $310K base, total comp $330K to $420K. Most teams overpay here because they hire the title too early. A Director who scales into a VP role over 18 months is almost always better than a VP hired in cold.
In-house versus agency: the honest version
I run an agency, so my bias is obvious. Here is the honest framing anyway.
In-house wins on three things. Institutional knowledge, because your person learns your data, your customers, and your edge cases over time. Cross-functional relationships, because they are in your Slack and your standups. Cost at scale, because past a certain volume of work, in-house is cheaper per hour than agency.
Agency wins on three different things. Speed to value, because we have done your setup 30 times before and have templates that work. Breadth, because a 5-person agency team has seen 100 CRM setups versus your hire who has seen 3. And specialization on demand, meaning you get a Clay expert for two weeks instead of hiring one permanently.
The realistic answer for most Series A and early B teams is a hybrid. One in-house Director who owns the strategy and the long-term roadmap, plus an agency or specialist contractors for spike work. Migration projects, enrichment build-outs, AI automation deployments. These are the things where a 4-week sprint with experts beats a 9-month internal project.
Past $20M ARR, most teams should be majority in-house with selective agency support. Below $10M ARR, most should be the inverse.
The remit problem nobody talks about
The single most common failure mode in RevOps hiring is unclear remit. The new hire walks in and three people think they own them. The CRO thinks RevOps reports to sales and should fix forecasting first. The CMO thinks RevOps owns attribution. The COO thinks RevOps owns the tech stack budget.
If you do not solve this in the first two weeks, the hire spends six months in meetings about meetings and quits.
The reporting line that works best in 2026 is RevOps reporting to the CRO at Series A and early B, then breaking out to report to the COO or CEO at Series C and beyond. At Series A, most of the work is sales-adjacent, so the CRO line makes sense. At scale, the work spans sales, marketing, CS, and finance, and the CRO line creates territorial fights.
The remit document should be written before you post the job. Three sections. What RevOps owns end to end, like CRM architecture, forecasting model, lead routing rules. What RevOps influences but does not own, like sales comp design and MQL definitions. What RevOps explicitly does not own, like quota setting, hiring decisions for sales, marketing channel mix. This last list is the most important. Without it the hire becomes a complaint desk for every operational problem in the company.
What good looks like 12 months in
After a year, a competent first RevOps hire should have shipped something concrete in each of these areas. CRM data model and required fields locked down with under 5% missing values on key fields. Lead routing automated with SLA tracking, with no inbound lead waiting more than 5 minutes. A forecasting cadence with stage probabilities calibrated to actual close rates, not made up numbers. A reporting layer where the CEO, CRO, and CMO all look at the same source of truth. A documented operating cadence with weekly pipeline review, monthly forecast call, quarterly territory review.
If 12 months in, your RevOps person has built 30 dashboards but the CRO still cannot trust the forecast, you have hired wrong. The output is operational reality, not analytical artifact.
Trying to figure out the first hire?
We run RevOps audits and fractional support for B2B teams between Seed and Series C. Book a 30-minute call and we will tell you whether to hire, when, and what to write in the job description.
Book a call →FAQ
When should a B2B SaaS company make its first RevOps hire?
The trigger is operational, not financial. Most teams should hire their first full-time RevOps person between $4M and $8M ARR, or when they cross 10 to 15 quota-carrying reps. Before that, fractional or agency support is more cost-effective. The clearest signal is when the CRO spends more than 4 hours a week in spreadsheets or when pipeline reviews take twice as long as they used to.
Should the first RevOps hire be a Director or a Manager?
Director-level, even if it feels heavy for the company size. The first hire has to design the system and build it themselves, which means they need strategic judgment plus hands-on CRM skill. A Manager-level hire will execute what you tell them to but will not push back on bad architecture decisions. The price difference is $40K to $60K a year and pays for itself in avoided rework.
Does the first RevOps hire report to the CRO or the CEO?
CRO at Series A and early B, because most of the early work is sales-adjacent. COO or CEO at Series C and beyond, because the remit grows to include marketing, CS, and finance. Reporting to a CMO is the worst option at any stage, because it biases the hire toward attribution work and away from sales infrastructure.
What is the right title for a first RevOps hire?
Director of Revenue Operations. Not Head of RevOps, which has unclear seniority. Not VP, which is too senior. Not Sales Operations Manager, which signals you only care about sales. The title matters for hiring because candidates with the right experience filter their search by Director-level RevOps roles.
Can you outsource RevOps entirely instead of hiring?
Up to about $5M ARR, yes, and many teams do. Past that point you need someone in-house who lives in your Slack and your standups. The hybrid model works best in the $5M to $20M range, where one in-house Director handles strategy and an agency partner handles build-out projects and specialist work. Fully outsourced RevOps past Series B usually produces good dashboards and poor adoption.