hiring revops
RevOps or another AE: the maths behind the decision
Whether to hire RevOps or another AE, with a fully loaded cost model, the break-even uplift at four, eight and fifteen reps, and how to tell which you need.
Hire the AE if your existing reps are at or near quota, because you have a capacity problem and capacity is what an AE adds. Hire RevOps if reps are missing quota while the company argues about which number is correct, because another AE will miss quota too. Below six reps the maths favours the AE. Above ten it favours ops.
The short answers
- The test is whether your current reps are hitting quota. If they are, the system works and you are short of capacity. If they are not, adding capacity to a broken system buys you a second person missing the same number.
- Team size decides this more than conviction does. A RevOps hire pays back by releasing productivity across everyone else, so the arithmetic improves with every rep you already employ. At four reps the ops hire has to lift each rep by 19 per cent. At fifteen reps it has to lift each rep by 5 per cent.
- The published quota data is worse than most boards assume. The Bridge Group’s 2026 study of 158 B2B companies found 48 per cent of reps at quota, down from 51 per cent in 2024. RepVue’s index of 246 companies put Q2 2025 at 42.7 per cent.
- Ramp is now 6.2 months at median, the longest in the Bridge Group’s study history, which means a new AE hired in January is a cost centre until July and a partial contributor until the following year.
- A fully loaded AE costs far more than the OTE line. On the model below, a $200,000 OTE AE costs $329,100 in year one once commission, on-costs, recruiting, tooling, management time and patch support are counted.
- Neither hire is measurable in revenue for two quarters. Judge the ops hire on forecast accuracy, time to answer a commercial question, pipeline hygiene and rep selling time, and baseline all four before the person starts.
- The worst version of this decision is hiring ops to avoid a conversation about a sales leader who cannot forecast or a product that does not retain. That is an expensive way to postpone something.
Capacity problem or system problem
There are two reasons a sales team misses its number and they take opposite fixes.
A capacity problem looks like this. Reps are at or above quota. Inbound leads sit unworked. Response times slip because there is nobody free. Accounts in a named segment have no owner. Deals are lost because nobody got back to the buyer in time. The system produces revenue reliably and there is more demand than there are hours. Buy more hours.
A system problem looks like this. Reps miss quota. The forecast is wrong in both directions and nobody can say why. Two people produce two different win rates from the same CRM. A deal is at stage 4 on Monday and stage 2 on Thursday and nobody logged the reason. The weekly pipeline call spends its first fifteen minutes establishing which number is correct. Reps keep a private spreadsheet because they do not trust the one in the CRM. Adding a rep to this adds a seventh person to the argument.
The distinction matters because the two diagnoses have almost the same symptom at board level. Both present as “we are behind on bookings”. The difference is whether the reps you already pay are converting the demand they already have.
One caveat before the maths. If reps are missing quota because there is genuinely not enough demand, neither hire is the answer, and a RevOps manager will spend two quarters producing beautifully accurate reports about a pipeline that is too small. Check pipeline coverage against quota first. If coverage is under 3x and the gap is at the top of the funnel, this decision is a marketing decision wearing a sales costume.
What another AE actually costs
Most companies budget this decision on OTE against salary, which understates the AE by 65 per cent and the RevOps hire by 63 per cent. Both figures need to be fully loaded before they can be compared.
The model below uses the Bridge Group’s 2026 medians as the sourced spine: $200,000 median OTE, $960,000 median quota, 6.2 month ramp, with the 53:47 base to variable split from the 2024 edition and the 10.3 per cent commission rate on ACV from the 2023 edition. Everything else is an input you should replace with your own number, and each line says which is which.
| Cost line | Year one | Source or assumption |
|---|---|---|
| Base salary | $106,000 | 53 per cent of $200,000 median OTE (Bridge Group) |
| Commission earned on year one bookings | $47,100 | 10.3 per cent of ACV closed (Bridge Group 2023) |
| Ramp guarantee, 3 months at half target variable | $11,800 | Common practice, your number |
| Employer on-costs at 20 per cent of cash comp | $33,000 | Payroll taxes, pension, benefits, your number |
| Recruiting cost at 20 per cent of base | $21,200 | Contingency norm, see what a search costs |
| Tooling and data seat | $6,000 | CRM, engagement, dialler, enrichment, your number |
| Management overhead | $36,000 | $250,000 loaded manager across a span of 7, your number |
| Onboarding and enablement time | $8,000 | First 90 days of manager and enablement hours |
| Patch and demand generation support | $60,000 | The most company-specific line, see below |
| Fully loaded year one cost | $329,100 |
The patch line is where this model most often goes wrong in real budgets. A quota of $960,000 at 3x coverage needs $2.88m of pipeline created for that patch. If you add a rep without adding the demand generation to feed them, you have not added capacity. You have divided the existing patch by one more person and diluted everyone’s attainment, which is the single most common way a headcount decision produces a worse quarter than doing nothing. Take your demand generation spend, divide it by the number of quota-carrying patches it currently feeds, and use that as the marginal patch cost. For scale, sales and marketing runs at 37 per cent of revenue at the median in the Benchmarkit and Pavilion 2025 benchmark set, rising to 47 per cent for VC-backed companies. Rep compensation is a minority of that. The rest is the machinery that makes a patch sellable, and it does not appear on a headcount requisition.
Against that cost, what does the AE produce in year one?
Three discounts apply and they compound.
Ramp. At the median 6.2 months, a reasonable production profile is nothing in months one and two, a third of run rate in months three and four, two thirds in months five and six, and full run rate from month seven. That is 8.0 months of full capacity inside a 12 month year, a ramp factor of 0.667. SaaStr’s guidance is segment-dependent: SMB reps should be at quota by the second sales cycle, enterprise reps need six to nine months. That is practitioner opinion with no sample behind it, and it happens to bracket the Bridge Group median.
Attainment. Neither the Bridge Group nor RepVue publishes mean attainment as a fraction of quota. Both publish the share of reps at or above quota, which is a different statistic. The model uses 85 per cent as a team-average attainment expectation and tests 70 per cent and 100 per cent below. Treat it as an assumption, because it is one.
Attrition. The Bridge Group’s 2023 edition reported 32 per cent annual AE turnover and 2.2 years average tenure, split 20 per cent voluntary and 12 per cent involuntary. Salesforce’s survey of 7,775 sales professionals put average sales team turnover at 25 per cent. With departures spread through the year, a 32 per cent annual rate gives an expected survival factor of 0.84 for a 12 month window. New hires depart earlier than average, and their departure lands inside the ramp, so the revenue loss is worse than the headline rate implies. Be careful with the cost-of-turnover figures that circulate alongside these. The widely quoted claims about what a departing rep costs, aggregated on pages like Xactly’s, trace back to HubSpot, SiriusDecisions and an unnamed Forbes study, none of which resolves to a dated primary source with a stated sample. The model above uses attrition to discount expected output and does not attempt to price the replacement cost, because that number is not reliably knowable.
Expected year one new ARR is therefore $960,000 x 0.667 x 0.85 x 0.84, which is $456,960.
At a 75 per cent gross margin that is $342,720 of gross profit against $329,100 of cost. The AE roughly washes its face in year one and makes money from year two. That is a normal and acceptable answer. It is also a much thinner year one than the OTE line suggests.
What a RevOps hire actually costs
A RevOps manager has no commission, no quota and no ramp revenue. It also has no patch cost and a lower management overhead, because the role usually reports to a CRO, COO or founder directly.
| Cost line | Year one | Source or assumption |
|---|---|---|
| Base salary | $150,000 | Illustrative mid-level US figure, see what each role pays |
| Bonus at 10 per cent | $15,000 | Company performance bonus, your number |
| Employer on-costs at 20 per cent | $33,000 | Same basis as the AE |
| Recruiting cost at 20 per cent of base | $30,000 | Same basis as the AE |
| Tooling and seat | $4,000 | Their own licences. The team’s stack is budgeted separately |
| Management overhead | $12,000 | Lighter span, direct report to a revenue leader |
| Fully loaded year one cost | $244,000 |
The gap is $85,100. That is the number people quote when they say ops is cheaper, and on its own it is meaningless, because the AE brings $456,960 of expected bookings and the RevOps hire brings none of its own.
The RevOps hire earns its place entirely through what it releases across the people already selling. That is the whole argument, and it is testable.
The other cost line worth naming: a RevOps hire also has a ramp, and it is not zero. Nothing lands in the first six to eight weeks beyond an audit. A realistic year one impact factor is 0.6, meaning the work is live for about seven months of the first twelve. Companies that expect quarter-one impact from an ops hire are the ones who conclude in month five that it did not work. If you want the detail on why that judgement is usually premature, ops hires fail in the first 90 days for reasons that have little to do with the person.
The break-even formula
Set the two net contributions equal and solve for the productivity uplift the ops hire has to release.
u = (A - C_ae + C_ops) / (N x Q x a x i)
| Term | Meaning | Value in the worked example |
|---|---|---|
u | Sustained percentage uplift in each existing rep’s output | The answer |
A | AE expected year one new ARR, equal to Q x r x a x s | $456,960 |
C_ae | Fully loaded year one cost of the AE | $329,100 |
C_ops | Fully loaded year one cost of the RevOps hire | $244,000 |
N | Existing quota-carrying reps the ops hire can affect | 4, 8 or 15 |
Q | Median annual quota per rep | $960,000 |
a | Expected attainment as a fraction of quota | 0.85 |
i | Ops impact ramp factor in year one | 0.6 |
r | AE ramp factor in year one | 0.667 |
s | AE survival factor given attrition | 0.84 |
Put your own numbers in. The numerator is fixed by the AE side of the comparison and the cost gap, so it does not move with team size. The denominator scales linearly with N. That is why the answer flips as the team grows, and it is the only part of this that behaves like a law rather than an opinion.
With the values above, the numerator is $456,960 minus $329,100 plus $244,000, which is $371,860. That is the total incremental ARR the RevOps hire must release across the existing team in year one to match hiring the AE.
The break-even at four, eight and fifteen reps
Existing reps (N) | Total year one uplift required | Uplift required per rep | Uplift as a percentage of that rep’s output | Is that a defensible claim? |
|---|---|---|---|---|
| 2 | $371,860 | $185,930 | 38.0 per cent | No |
| 3 | $371,860 | $123,953 | 25.3 per cent | No |
| 4 | $371,860 | $92,965 | 19.0 per cent | Hard to defend |
| 6 | $371,860 | $61,977 | 12.7 per cent | Arguable |
| 8 | $371,860 | $46,483 | 9.5 per cent | Defensible |
| 10 | $371,860 | $37,186 | 7.6 per cent | Comfortable |
| 12 | $371,860 | $30,988 | 6.3 per cent | Comfortable |
| 15 | $371,860 | $24,791 | 5.1 per cent | Close to a rounding error |
| 20 | $371,860 | $18,593 | 3.8 per cent | The AE case has to be exceptional to win |
The flip sits between six and ten reps. That is the finding.
Below four reps, the ops hire has to make every one of your salespeople sell a fifth more than they do today, and hold that. Nobody should promise that in an interview and nobody should believe it if they do. At four reps the AE is almost always the right call, and the honest version of the ops pitch at that size is that it is a strategic bet on the next twelve months rather than a return in this one.
At fifteen reps, the ops hire needs to release five per cent per head. Salesforce’s survey found reps spend 28 per cent of their week actually selling, which is 11.2 hours in a 40 hour week. A five per cent lift in output, if output moved with selling hours, would need 34 minutes a week back per rep. Getting 34 minutes a week back from a rep who spends 28.8 hours on deal admin, data entry and internal reporting is not an ambitious target. It is what a competent ops person does with a routing rule and three fields deleted.
Output does not move linearly with selling hours, and that caveat matters. An hour returned to a rep who is bad at discovery produces an hour of bad discovery. The selling-time arithmetic sets a plausibility floor for the ops case, and it does not prove it.
How sensitive the answer is to the assumptions
The obvious objection to any model like this is that the assumptions do the work. Here they do not, and that is worth showing instead of asserting.
| Assumption changed | 4 reps | 8 reps | 15 reps |
|---|---|---|---|
| Base case, attainment 85 per cent | 19.0 per cent | 9.5 per cent | 5.1 per cent |
| Pessimistic, attainment 70 per cent | 18.7 per cent | 9.3 per cent | 5.0 per cent |
| Optimistic, attainment 100 per cent | 19.2 per cent | 9.6 per cent | 5.1 per cent |
| Year two steady state, no ramp on either side | 19.3 per cent | 9.6 per cent | 5.1 per cent |
Attainment expectations move the answer by less than half a percentage point. Removing ramp from both sides moves it by less than half a percentage point. The break-even is governed almost entirely by N, because N is the only term in the denominator that is not also in the numerator.
The model is currency-agnostic for the same reason. u is a ratio, so a UK company running the same comparison in sterling with a lower AE OTE and a proportionally lower RevOps base gets the same break-even percentages. What does change the answer is the ratio of ops pay to AE OTE. If your market pays RevOps close to AE OTE, the cost gap narrows, the numerator rises and the break-even gets harder at every team size.
Two things genuinely move it. The first is the patch cost. If adding an AE requires no incremental demand generation because you have unworked inbound, drop that $60,000 line and the AE gets cheaper, the numerator rises to $431,860, and the bar for the ops hire goes up: 22.1 per cent at four reps, 11.0 per cent at eight, 5.9 per cent at fifteen. That is the mathematical form of “if you have unworked demand, hire the AE”.
The second is N itself, and it is easy to get wrong. Count only the quota carriers whose work the ops hire will actually touch in year one. A US team of eight and an EMEA team of four running a different CRM instance is N = 8, not 12.
The four signs it is the system and not the pipeline
Each of these is verifiable in under a week and none of them requires a consultant.
| Signal | What it looks like | How to verify it | What it rules out |
|---|---|---|---|
| Two sources, two answers | The CRO’s win rate and finance’s win rate differ for the same quarter | Ask both, separately, in writing, for last quarter’s win rate and average deal size. Do not tell them why | If the numbers match, your reporting is fine and the problem is elsewhere |
| Forecast error with no direction | The forecast misses by 20 per cent up one quarter and 18 per cent down the next | Pull the last six commit submissions against actuals. Compute absolute percentage error each time | Consistent optimism in one direction is a coaching or a leadership problem, not a data problem |
| Selling time displaced by admin | Reps are in the CRM, in Slack and in internal calls during buyer hours | Two week time diary on three reps, cross-checked against calendar and CRM audit logs. Compare against the 28 per cent selling time benchmark | If reps are at 40 per cent selling time and still missing, the problem is skill or demand |
| Pipeline that moves backwards | Deals regress stages, close dates roll repeatedly, stage definitions are argued about | Count deals that moved backwards a stage last quarter, and deals whose close date moved three or more times | Clean forward-only movement with honest slippage means the stage model works |
Gartner’s State of Sales Operations survey found that only 47 per cent of sales leaders and sellers believed their organisation had high quality data and 45 per cent had high confidence in forecast accuracy. That release does not disclose a sample size, which is a limitation worth stating when you quote it in a board paper.
Three or four of these signals present together is a system problem and the ops hire is the right call. One signal on its own usually has a cheaper fix than a headcount.
The honest case for hiring the AE
The AE case is often written as a straw man in ops content and it deserves better, because it is frequently correct.
Your reps are at quota and there is demand they cannot reach. This is the clean case and it needs no further analysis. Capacity constraints are solved by capacity. If lead response time is slipping and inbound is ageing in a queue, an ops hire will document the queue and the queue will still be there.
An unowned segment or territory. Unowned revenue is the cheapest revenue in the business. An AE with an unworked patch has a ramp curve that starts higher than the median, because there is no competition for their attention and no dilution of an existing rep’s accounts.
Is your sales cycle under 45 days? Ramp cost scales with cycle length. An SMB team with a 30 day cycle can have a rep at quota inside two cycles, which changes the ramp factor from 0.667 to something closer to 0.85 and materially improves the AE side of the model. The break-even at four reps rises from 19.0 per cent to 24.6 per cent under that assumption, and at eight reps from 9.5 per cent to 12.3 per cent.
The runway is shorter than the ops payback. A RevOps hire is measurable in ops metrics at 90 days and in revenue at nine to twelve months. If you have four quarters of cash and a bookings target that determines whether you raise, the AE is the correct risk decision even if the ops case is intellectually stronger. Say that out loud in the meeting instead of pretending the ops case is weak.
Your existing ops coverage is adequate for the team size. A capable sales leader with a strong systems-minded ops analyst can hold a six rep team together. Adding a RevOps manager on top of that is a duplication before it is an upgrade.
Buy shots on goal while the motion is still moving. If you are still finding the repeatable motion, more attempts at more account types produce learning that no amount of dashboarding will. Efficiency work on a motion you are about to change is waste.
Where the AE case is genuinely weak is when it is chosen because it is legible. Quota-carrying headcount fits on a board slide and an ops hire does not. That is a reporting convenience masquerading as a strategy.
What the quota attainment data actually says
The published figures matter here because the AE side of the model is built on them, and they are consistently lower than the numbers used in internal plans.
| Source | Metric | Figure | Sample | Date |
|---|---|---|---|---|
| Bridge Group, AE Models, Motions & Metrics | Share of reps at or above quota | 48 per cent, down from 51 per cent in 2024 | 158 B2B companies | June 2026 |
| RepVue Cloud Sales Index, via QuotaPath | Share of reps at or above quota | 42.7 per cent | 246 companies, about 47,000 quota carriers | Q2 2025 |
| RepVue Cloud Sales Index, via The Quota | Share of reps at or above quota | 43.2 per cent, 48.3 per cent in the $200k+ ACV segment | 249 companies, 49,000+ quota carriers | Q3 2025 |
| Salesforce State of Sales | Sellers expecting their team to hit full quota | 17 per cent | 7,775 sales professionals, 38 countries | Fieldwork Aug to Sep 2022 |
The two continuous datasets disagree by five to six percentage points and they are measuring slightly different populations. The Bridge Group surveys companies and reports a company-weighted figure. RepVue aggregates ratings submitted by individual reps, which skews towards reps motivated to rate their employer and towards larger, better-known companies. Neither is wrong. The employer-reported number being the higher of the two is what you would expect from both selection effects.
A third figure circulates widely and does not reconcile. Summaries of the Bridge Group’s 2023 edition report 66 per cent of reps achieving quota, which cannot be squared with the publisher’s own statement that the 2024 baseline was 51 per cent. Either the question changed between editions or the summary restated a different cut. Rareix could not resolve it against the primary reports, both of which sit behind a download, so treat the 66 per cent figure as unverified and use 48 per cent.
The practical consequence for this decision: if fewer than half of reps hit quota in a normal market, then a plan built on the assumption that your next AE will hit theirs is a plan built on the tail of the distribution. The model above already discounts for that. Most internal business cases do not.
Ramp is moving in the same direction. The 2026 median of 6.2 months is the longest the Bridge Group has recorded, and required experience at hire has risen from 2.7 years in 2022 to 3.7 years. Companies are hiring more experienced reps and getting slower ramps, which is the shape of a market where the constraint has moved from selling skill to everything around it.
Sequencing the first ten commercial hires
Under about 50 people the order is: commercial hires first, then ops, then more commercial hires. Skipping the middle step is the mistake, and doing the middle step first is a different mistake.
The first four or five commercial hires come first. At N = 1 or 2, the break-even in the table above is 76 per cent and 38 per cent. There is nothing for an ops hire to multiply across. A founder or a first sales leader can hold every definition in their head, and the CRM has few enough records that one person can read all of them. Ops at this stage systematises a motion you are about to change.
Ops goes in at five or six reps, one hire ahead of where the maths says it breaks even. At five reps the required uplift is 15.2 per cent and at six it is 12.7 per cent, so you are buying slightly ahead of year one payback and you should say so when you propose it. Two things justify going early. The founder has stopped being able to answer commercial questions from memory, and the reporting has started to disagree with itself. If this is your first operations person of any kind, the requirements differ from a fifth or tenth ops hire, and what to look for in a first ops hire covers the specific profile.
Reps seven through twelve are the payback. They ramp faster than reps one through five did, and that speed is the return on the middle step. The territory model exists, the stage definitions exist, onboarding has a document, and the new rep does not spend their first month reverse-engineering the pipeline from Slack. Each of those hires also pushes N up, so the ops hire you funded at 12.7 per cent is defending 7.6 per cent by the time you reach ten reps.
The middle step gets skipped because it costs a quarter of bookings capacity at exactly the moment a board is asking about bookings. Skipping it means hiring reps six through twelve into a system nobody has written down, which is how a company arrives at twelve reps, 43 per cent attainment and a forecast nobody believes.
One decision sits upstream of all of this: which ops role you are actually buying. A RevOps manager, a sales ops analyst and a GTM engineer solve different problems at different prices, and the comparison across the ops roles is worth ten minutes before you write a job description.
What to do when you cannot afford both
The full-time RevOps manager is not the only shape of the work. Three of these options cost less than a quarter of the permanent hire and two of them will tell you whether the permanent hire is warranted.
Rareix does not publish a sampled day rate dataset, so the figures below are derived arithmetic and market observation rather than measurement. The derivation: a $150,000 base at 20 per cent on-costs is $180,000 loaded, which across 220 working days is $818 a day. Contract rates typically sit above that.
| Option | Indicative year one cost | What it gets you | What it does not get you | When it is right |
|---|---|---|---|---|
| Fractional RevOps, two days a week | $78,000 to $118,000 | Continuous ownership of forecast, reporting and hygiene at 40 per cent of the capacity | Deep institutional knowledge, availability in a crisis, anyone to build anything large | You have 6 to 10 reps and cannot justify a full-time head yet |
| Scoped contractor build, 10 weeks | $41,000 to $61,000 | One defined deliverable: a rebuilt stage model, a working forecast, a CRM migration | Anything after the contract ends, unless someone owns it | You know exactly what is broken and fixing it is a build with an end date |
| Diagnostic engagement, 10 to 15 days | $8,000 to $18,000 | A written answer to the capacity-or-system question, with evidence | The fix | You genuinely cannot tell which problem you have |
| Systems-literate analyst instead of a manager | $90,000 to $110,000 loaded | Execution capacity and clean data | Judgement on commercial trade-offs, the ability to challenge a sales leader | Your sales leader is strong on process and short on hands |
| Hire the AE, defer ops one quarter | Nil incremental now | Bookings capacity now, ops decision made with one more quarter of evidence | Nothing, if you actually revisit it. Everything, if you do not | Runway is under five quarters and the bookings number is existential |
The diagnostic option is underused. Ten days of a good operator’s time will tell you whether the forecast error is a data problem or a leadership problem, and that answer changes which of the two roles you should be recruiting for. It costs less than one month of either hire.
The trap in the fractional route is treating it as a permanent solution when the load has outgrown it. A fractional operator at two days a week can hold a system steady. They cannot rebuild one while holding it steady, and the moment you ask them to, you get neither. Track the backlog of ops requests that have waited more than three weeks. When that backlog stops shrinking for two consecutive months, you have outgrown the arrangement.
How to measure whether the RevOps hire worked
Revenue is a bad first-two-quarters metric for an ops hire, because the ops hire does not produce revenue and because the revenue signal is buried under seasonality, the pipeline they inherited and the performance of the reps they support. Companies that measure ops on revenue in month five conclude it failed, which is one of the reasons ops roles churn.
Measure four things instead, and baseline every one of them before the person starts. A baseline collected after the hire begins is contaminated, because the act of measuring changes what gets logged.
| Metric | How to baseline before the hire starts | Data you need | First honest read | What good looks like at 180 days |
|---|---|---|---|---|
| Forecast accuracy | Compute absolute percentage error of the commit against actual for the last 6 quarters | Historic commit submissions and closed actuals | Day 90, one full quarter under the new process | Absolute error inside 10 per cent, and error that is stable rather than alternating |
| Time to answer a commercial question | Log 5 real questions before the hire and time them to a defensible answer. Use questions like “what is win rate by lead source for the last two quarters” | A stopwatch and honesty about how long it took last time | Day 60 | Days become hours. Anything still measured in days is not fixed |
| Pipeline hygiene | Count open deals with a close date in the past, open deals with no next step, and deals that moved backwards a stage last quarter | A CRM export, three saved reports | Day 45 | Past-dated close dates under 5 per cent of open pipeline, stage reversals falling |
| Rep selling time | Two week time diary on three reps, plus calendar audit. Benchmark against 28 per cent | Calendars, CRM audit logs, rep cooperation | Day 120, and repeat the same two week diary | A measurable shift towards buyer-facing hours, with the same measurement method |
| Definition disputes per forecast call | Count, for four consecutive weeks, how many times the call stops to establish which number is correct | A tally on a notepad | Day 90 | Zero to one. This is the fastest-moving of the five and the best early signal |
The fifth row is the one to start with. It costs nothing, it takes four weeks, and a team that stops arguing about which number is correct has already recovered more time than most dashboards do.
Two rules make this work. Publish the baseline to the hiring manager and the new hire in week one, in writing, so nobody relitigates what the starting point was. And do not change the measurement method mid-way, because a rep selling-time figure collected by a different method is not comparable and will be used by whoever wants to argue the hire failed.
If this is an offer you are about to make, the full hiring process puts the same baselines into the scorecard, which is where they belong. Searches for this profile take six to eight weeks to an accepted offer, so the baseline work fits comfortably inside the search.
Hiring ops to avoid a difficult conversation
There is a version of this decision that is not a decision at all. It is a substitution, and it is expensive.
The pattern runs like this. The forecast has been wrong for three quarters. The sales leader is well-liked, was right about a lot of things in the early days, and is now out of their depth on process. Nobody wants to say so. Somebody proposes a RevOps hire. The proposal cites Gartner’s forecast that 75 per cent of the highest growth companies would deploy a RevOps model by 2025, which is an analyst prediction from 2021 with no published follow-up measurement of whether it came true. The proposal is well-received, because it is a plan, and because it means the conversation about the sales leader can be deferred for two more quarters while the new person builds.
The new person arrives, finds that the forecast is wrong because the sales leader overrides the pipeline on instinct and calls it judgement, and discovers they have no authority to change that. They build good reporting. The reporting is ignored. At month eight, the RevOps hire leaves or is managed out, and the original problem is now eleven months older and has a failed hire attached to it.
The same substitution happens with product. Reps miss quota because the product loses to a competitor on two features that come up in every deal. Ops is hired to fix conversion. Ops cannot fix conversion, because conversion is not a process defect.
Three questions catch this before you spend the money.
Ask who has the authority to overrule the forecast, and what happens when the data and that person disagree. If the answer is that the person wins and always has, the ops hire has no mandate and will not acquire one.
Ask why the last two quarters were missed, and require the answer to name a mechanism. “Execution” is not a mechanism. “Deals slipped” is not a mechanism. “We could not tell which deals were real because stage definitions were interpreted differently by three managers” is a mechanism, and it is one an ops hire can fix.
Ask what would have to be true for you to conclude in six months that the problem was never operational. If nobody can answer, the hire is being used as a way of not answering.
None of this means the ops hire is wrong in these situations. Sometimes the honest sequence is to have the difficult conversation and then hire ops, in that order, because the ops hire only works once someone has the authority to make the data binding. Rareix has withdrawn from searches where the first stakeholder conversation made it clear the role existed to absorb blame for a decision the leadership team had not made. Those searches fill and then fail, and the failure is visible on the new hire’s CV rather than on the company’s.
Rep count, not conviction, decides this
The qualitative arguments on both sides are strong and they cancel out. Everyone can tell a persuasive story about the AE who transformed a territory and about the ops hire who found $400,000 of misrouted pipeline in week three. Those stories are true and they are not evidence.
What survives the arithmetic is that the ops hire’s return is divided by nothing and multiplied by N, while the AE’s return is a fixed quantity discounted by ramp, attainment and attrition. That structure means the answer is a function of how many people you already employ to sell. Four reps: hire the AE. Fifteen reps: hire the ops person, and the fact that you are still asking suggests you should have done it two hires ago. Between six and ten: run the model with your own patch cost, because that is the line that decides it.
Where this method is weak, and it is worth saying: the model assumes the ops hire is competent and correctly scoped, which is an assumption a spreadsheet cannot verify. A break-even of 5.1 per cent is easy for a good operator with a clear mandate and impossible for a good operator with no authority. The arithmetic tells you whether the role is worth funding. It does not tell you whether you will hire well, and a 5.1 per cent break-even against a failed hire is still a failed hire.
Related reading
- What to look for in a first ops hire, if you have not hired any operations person yet and are deciding whether the stage is right.
- GTM engineer versus RevOps manager, for which of the operations roles solves the problem you actually have.
- RevOps salary benchmarks, for the UK and US bands behind the cost model on this page.
- How to hire a RevOps manager, for the process end to end once the decision is made.
- Why ops hires fail in the first 90 days, for the onboarding that protects the investment you just modelled.
- What is a GTM engineer, for the role definition behind the third option in this comparison.
- Recruitment fees explained, for the recruiting line in both cost tables.
- How long a RevOps search takes, for fitting the baseline work inside the search window.
Questions
What people ask about this.
- At what headcount does a company need RevOps?
- Between six and ten quota-carrying reps, in most B2B companies. At five reps or fewer the ops hire has to release more than 15 per cent per rep to match the marginal AE, which is difficult to defend. Above ten reps the required uplift falls under 8 per cent per rep and the case gets easy. Headcount is a proxy for the real trigger, which is the number of people whose work an ops hire can affect. A 20 person company with three reps needs ops less than a 20 person company with nine.
- Should I hire another AE or a RevOps manager?
- Hire the AE if your existing reps are hitting quota, because that is a capacity constraint and capacity is what an AE adds. Hire RevOps if reps are missing quota while the business argues about which numbers are correct. Then check the arithmetic: below six reps the maths favours the AE almost regardless of the qualitative case, and above ten it favours ops.
- Can a sales leader do RevOps alongside the day job?
- Up to about five or six reps, yes, if they are genuinely systems-minded and the CRM is simple. Past that it fails predictably, and it fails in a specific way. Ops work is interruptible and coaching is not, so the ops work gets pushed to evenings and then dropped. The tell is that the sales leader's calendar shows more internal meetings than customer calls, and that the reporting they produce is built the night before the board meeting. A sales leader doing ops part-time is also the person least able to audit their own forecast, because they are the source of it.
- Is a RevOps hire measurable?
- Yes, but not in revenue for the first two quarters. Forecast accuracy, time to answer a commercial question, pipeline hygiene and rep selling time are all measurable inside 90 days, and all four have to be baselined before the person starts. The measurement problem with ops hires is almost never that the work is unmeasurable. It is that nobody recorded the starting point, so every improvement becomes a matter of opinion.
- What if we cannot afford both?
- Take the cheapest option that answers the question: a 10 to 15 day diagnostic engagement, which costs less than a month of either hire and tells you which problem you actually have. If you already know it is a system problem, a fractional RevOps operator at two days a week costs roughly 40 per cent of a full-time hire before the recruiting fee you do not pay. If you already know it is a capacity problem, hire the AE and revisit ops in one quarter with a date in the calendar, because the version of this that goes wrong is deferring indefinitely.
- How long before a RevOps hire pays for itself?
- On the model above, the payback is the point at which the released productivity across the team exceeds $244,000 of loaded cost. At eight reps that needs a 9.5 per cent sustained uplift per rep, and the uplift is not live until roughly month five. In practice that means nine to twelve months to cash payback and 45 to 90 days to the first honest ops signal. Anyone promising a quarter is selling something.
- Does the answer change if reps are missing quota because of the product?
- It changes it completely, and neither hire is the fix. A product gap shows up as consistent losses to the same competitor on the same two or three points, and as deals that die at the same stage across different reps. An ops hire can prove that pattern exists inside three weeks, which is genuinely useful, and can do nothing about it. If you already know the pattern, spend the money on product and keep the sales team the size it is.
- Should the RevOps hire report to sales or to finance?
- To whoever can make the data binding. That is usually a CRO or a COO, occasionally a CFO, and rarely a VP Sales who is also the source of the forecast being measured. Reporting into the function whose numbers you are auditing creates the exact conflict that made the numbers unreliable. If the only available line is into sales, the compensating control is that the ops hire presents the forecast to the board directly and unedited.
- What is the cheapest way to test whether we have a system problem?
- Ask two people, separately and in writing, for last quarter's win rate and average deal size. It costs one email. If the answers differ by more than a rounding error, you have a system problem and you found it for nothing. Follow it with the four week tally of how many times the pipeline call stops to establish which number is correct.
- Do we need a GTM engineer instead of a RevOps manager?
- Different problem, different hire. A RevOps manager owns the process, the definitions, the forecast and the reporting. A GTM engineer builds the automated systems that execute the motion, and they command a different price. Most companies making this AE-versus-ops decision need the RevOps manager first, because a GTM engineer automating an undefined process produces faster chaos.
- Does hiring RevOps mean we hire fewer AEs later?
- Usually the opposite. The reason to sequence ops in at rep four or five is that reps six through ten ramp faster and attain higher, which strengthens the AE business case. The ops hire displaces one AE now and improves the return on every AE afterwards. If your growth plan calls for doubling the sales team in eighteen months, that is an argument for bringing ops forward.
- What if the board only counts quota-carrying headcount?
- Then present the ops hire in the board's currency. The break-even formula converts an ops hire into an equivalent number of AEs: at eight reps, a 9.5 per cent uplift per rep is worth $371,860 of year one ARR, which is 81 per cent of what the marginal AE was expected to deliver, at 74 per cent of the cost. Board members who resist ops headcount in the abstract tend to accept it when it is expressed as AE-equivalents with the assumptions on the slide.
Tell us the role. We will tell you honestly whether we can fill it.
Nothing owed until someone starts.
Book a call