How Much Should a Growing Company Invest in Revenue Operations?

By Victor Hoang · Updated Oct 11, 2026

Ask a CFO where revenue operations sits on the budget and you'll usually hear "G&A." It supports sales, so it's overhead. And overhead is what gets trimmed when the plan tightens, because nobody can point to a deal that closed because of a RevOps hire.

That framing is the mistake. RevOps doesn't close deals. It decides how many of the deals your team works on turn into numbers you can trust, and how much of your reps' week goes to selling instead of repairing records. Cut it, and the bill doesn't arrive as a line item. It arrives as a forecast you can't defend and a sales team that spends its best hours on admin.

So here's the position: fund RevOps as a ratio of your revenue team, and justify it against measurable leakage, not against its own activity. The rest of this piece shows how to do both, and what to do when the budget is under pressure anyway.

Why RevOps Gets Cut First

Three things make RevOps the easy cut.

Its output is invisible when it works. A clean forecast, a lead that routed in four minutes, a dashboard nobody argued about: none of these generate a thank-you. Failure is loud and success is silent, which is a terrible position to defend in a budget meeting. The maturity model describes the same trap from the inside, where reactive work gets praised and structural work gets forgotten.

It's measured by activity. Tickets closed, reports built, fields added. None of that maps to revenue, so when a CFO asks "what do we get for this headcount?" the honest answer sounds like a list of chores.

The cost of cutting is delayed. Lay off a RevOps analyst in January and nothing visible happens in February. The data decays slowly. Routing rules go stale. Required fields get skipped. By the time the forecast misses in Q3, the cause is six months old and nobody connects it to the cut.

That delay is why the cut feels free. It isn't.

What Underinvestment Looks Like

You can recognize an underfunded RevOps function without a single benchmark. Two symptoms show up first.

Forecast misses

When nobody owns pipeline definitions, stage criteria and the forecast process, the number leadership sees is only as good as each manager's gut. Xactly's 2024 survey of 405 finance, sales and revenue operations professionals, reported by CFO.com, found that 43% said their forecasts are usually at least 10% off, and 81% said they're typically at least 5% off. Xactly sells forecasting and compensation software, so read it as a vendor's survey of its own market. But the causes respondents named are all operational: systems that don't integrate, reps not enabled on which deals to include, and poor CRM or pipeline data hygiene.

The same coverage notes that 95% of finance and revenue operations respondents still expressed confidence in planning with those forecasts. A confident team planning against a number that's off by 10% is what an unmeasured leak looks like.

Selling time lost to admin

Salesforce's State of Sales research, announced in February 2026, found the average seller spends 40% of their time selling. It surveyed 4,050 sales professionals in August and September 2025. The same release reports that 74% of sales professionals are focused on data cleansing, and that 79% of high performers prioritize data hygiene versus 54% of underperformers.

Read that last gap carefully. The teams that win treat data work as a priority, which means someone has to own it. In an underfunded company that someone is the rep, and every hour spent fixing a record is an hour not spent in a conversation.

If you want a blunt test, ask three reps what they did last Friday afternoon. If any of the answers is "cleaned up my pipeline before the forecast call," you've found where the missing RevOps budget went. It went into your most expensive people.

Size It Against the Revenue Team, Not the Org Chart

The most useful starting point for budgeting is a ratio, because it scales with the thing RevOps supports.

The Pedowitz Group, a consultancy, publishes its own rules of thumb: roughly one RevOps professional for every 12 to 15 revenue team members across marketing, SDR/BDR, sales and customer success, stretching to about 1:20 for lean, low-complexity teams and tightening to about 1:8 to 1:10 for multi-region or multi-product setups. The page doesn't cite survey data, so treat these as practitioner heuristics, not benchmarks. They're still a useful anchor, because they force the right question: how many people does RevOps support, and how complex is their world?

Here's how those ranges translate into a planning table.

The ratios come from the Pedowitz Group page above; the revenue-team size bands in the second column are a rough orientation, not part of that source. Treat the whole table as a starting hypothesis to test against your own leakage, which is the next step.

For hiring order, the first RevOps hire piece covers who to bring in before the team grows past one person, and centralized versus embedded RevOps covers how to organize it once it does.

Justify It Against Leakage

A ratio tells you what's typical. It doesn't tell you what's worth it for your company. For that you need to measure what the lack of RevOps is costing today. There are three leaks that matter, and each can be priced with numbers you already have.

1. Selling time. Take your number of quota-carrying reps, their fully loaded annual cost, and the share of the week they spend on non-selling work. If you don't have your own number, Salesforce's 40% selling-time average is a reasonable placeholder. Every point you recover is capacity you've already paid for.

Illustrative example, not a benchmark: 40 reps at a loaded cost of $150,000 each is $6 million a year in rep cost. If a RevOps investment moves selling time from 40% to 45%, you've recovered 5% of $6 million, or $300,000 of capacity. A RevOps person in that ratio range costs less than that. The arithmetic only works if the time really moves, which is why you measure it before and after.

2. Forecast error. Price what a wrong number costs you. Hiring plans are committed against the forecast. So are marketing budgets, inventory, and sometimes the board's view of runway. Ask finance for the last two quarters where the forecast missed by more than 10% and what decisions were made on it. You'll usually find one decision that cost more than a year of the function.

3. Leads and deals dropped. Slow routing, duplicate records and stale follow-up tasks all lose revenue quietly. Pull the share of leads untouched after a defined window, and the number of open opportunities with no activity in 30 days. Pipeline hygiene is a cultural problem, but the cost of letting it slide is a plain number you can attach to the pipeline.

Add the three up for your own company, and the question changes. It stops being "can we afford RevOps?" and becomes "can we afford this leak?"

The Funding Model in One Page

Put the two lenses together and you get a budget you can defend.

Two rules keep this honest.

First, tie the budget to the revenue team, not to last year's RevOps budget. If you double the sales team, the supporting function can't stay flat, because complexity grows faster than headcount. More reps means more territories, more routing rules, more forecast roll-ups, more tools.

Second, don't count tooling as a substitute for people. A common mistake is to fund software instead of the function, hoping a platform will do the governance. It rarely does, and each added tool adds its own integration burden. The true cost of software sprawl is a good reality check before you approve another subscription.

What to Do When the Budget Is Under Pressure

Sometimes the cut is coming anyway. You still have choices that protect the function's value.

Cut projects, not ownership. Pause the dashboard rebuild or the attribution experiment. Keep the roles that own definitions, routing and the forecast process, because those are the ones whose absence causes drift.

Don't cut the person who holds the data model. Of everyone in RevOps, the one who understands why fields exist and how objects relate is the hardest to replace and the most expensive to lose. A contractor can build a report. Nobody can quickly reconstruct six years of institutional logic.

Protect the unit economics work. If the board is watching efficiency, the analyses behind CAC payback and attribution are exactly what lets you decide where to cut sales and marketing spend. Cutting the team that makes that visible leaves you cutting blind.

Reframe the ask. Replace "we need two more analysts" with "we're losing X% of selling time and forecasting within Y%; here's what closing half that gap is worth." The first sentence is a cost. The second is an investment with a return.

What Not to Measure

Be careful about the metrics you attach to the budget. Tickets resolved, dashboards shipped and fields created are activity. They'll reward a busy function, not a valuable one.

Choose outcome measures that the revenue team would recognize: forecast accuracy by segment, percentage of reps' week spent selling, lead response time, stage-to-stage conversion consistency, and share of opportunities with complete required data. These move when RevOps does its job well, and they move in a direction a CFO can read without a glossary. For the data side, CRM data hygiene breaks down what "complete and current" should mean in practice.

What to Do Next

If you're the executive who owns the budget, here's a sequence you can start this month.

1. Count your revenue team. Marketing, SDR, sales and customer success. Divide by your current RevOps headcount and compare it to the ranges above.
2. Ask three reps how much of last week went to non-selling work. Average the answers, then check them against a time-in-CRM or activity report.
3. Pull the last two forecast misses. Write down which decisions were made on those numbers and what they cost.
4. List dropped leads. Count leads untouched after your response-time target and open deals with no activity in 30 days.
5. Price the leakage. Add the three leaks into one dollar figure, even a rough one.
6. Set two outcome targets for RevOps, such as a forecast accuracy band and a selling-time goal, and review them in two quarters.

If you can't produce step 5, that's the finding. A company that can't measure its own leakage is underinvested in exactly the function that would measure it.

Key Facts

• Xactly's 2024 survey of 405 finance, sales and revenue operations professionals found 43% say forecasts are usually at least 10% off and 81% say at least 5% off (CFO.com).
• Salesforce's State of Sales research (4,050 respondents, fielded August to September 2025) found the average seller spends 40% of their time selling (Salesforce).
• In the same research, 79% of high performers prioritize data hygiene versus 54% of underperformers.
• A common consultancy rule of thumb is one RevOps professional per 12 to 15 revenue team members, from about 1:8 in complex setups to about 1:20 or more in lean ones (Pedowitz Group).
• Budget RevOps against two things: revenue team size and the dollar value of three leaks (selling time, forecast error, dropped leads).

Learn More

• Forecast governance: the operating rules that turn a forecast into a number leadership can plan on.
• The RevOps Maturity Model: where your function sits today and what the next level requires.
• The True Cost of Software Sprawl: why tooling isn't a substitute for ownership.