Ops counts as a cost center because you don't measure its contribution
In the next budget round, ask out loud what the RevOps role actually delivers. The answer is usually silence, then something about “they keep the CRM running”. Which is exactly why the role gets cut in the first round of savings, and six months later everyone wonders why routing is broken and the forecast lives in Excel again.
The problem is not that ops contributes nothing to revenue. The problem is that nobody calculates the contribution.
Yet the math works, decimal point included. A process fix on lead routing: before, inbound leads sat untouched for an average of 26 hours, after, 40 minutes, and lead-to-meeting conversion rose from 9 to 14 percent. At 400 leads a month and an average deal value of 18,000 euros, the annual impact has six digits. Second example, even simpler: stack cleanup. Four point solutions switched off because the suite covers them natively easily makes 60,000 to 70,000 euros in annual license costs that no longer drain away, at 30 users. Not a model calculation, a number on the credit card statement. And the sales cycle: if a clean quoting path and a working approval process push the cycle from 90 to 75 days, the pipeline turns faster, and that can be quantified in additional closed deals per year.
None of this is exotic. All it demands is that the current state gets measured before every fix, and again after. Baseline, change, delta. You demand the same discipline from marketing on every campaign. Nobody demands it from ops, because ops counts as infrastructure. Power from the wall, it is just there.
The side effect is the truly interesting part. An ops team that documents its deltas has completely different conversations. “We would need budget for data quality” turns into “the dedupe project halved the bounce rate last year and freed up around 120 hours of sales time, the next project has the same structure”. One is begging. The other is a business case.
And yes, not every effect can be cleanly isolated, market and season always interfere. Doesn’t matter. A conservatively calculated number with documented assumptions beats no number, every time, in every budget round.
Cost center is not a fact, cost center is a measurement error. What revenue contribution did your ops team make last year? If you cannot answer that, the problem is not ops.
