The sales operations function in most large B2B organisations has accumulated a scope that bears little resemblance to its original mandate. The textbook definition still describes sales ops as the team responsible for forecasting cadence, territory and quota management, CRM hygiene, and sales-process design. The operational reality in most organisations is that sales ops also owns deal-desk work, pricing approvals, partner operations, sales enablement content production, sales analytics, commission administration, sales technology stack ownership, and a long tail of cross-functional projects that touch revenue but do not clearly belong to any other function.
The accumulation has not been deliberate. It has happened because sales ops is structurally the team that gets handed work when no other team is positioned to take it on, and the function has rarely had the leadership cover to push back. The result is a chronically overloaded function that hides a set of organisational gaps the company is not addressing directly.
Where the scope creep actually comes from
The pattern of accumulation is consistent enough across organisations to be diagnostic. Work tends to land in sales ops when it has three characteristics: it crosses functional boundaries in ways that make no single function the obvious owner, it requires operational discipline that the originating function lacks, and it has visible commercial implications that make somebody senior care about the outcome.
Pricing approvals are a recurring example. Pricing strategy formally belongs somewhere between finance, product, and marketing in most organisations, but the operational process of approving deal-specific pricing on individual opportunities crosses too many functional boundaries for any of those teams to own cleanly. It usually lands in sales ops, often initially as a temporary arrangement, and then permanently because no other function has the operational infrastructure to take it back.
Deal desk follows a similar trajectory. The work of reviewing non-standard contract terms, coordinating internal stakeholders, and supporting the rep through the deal-construction process is genuinely cross-functional and requires operational discipline. Sales ops gets it because the alternative would be to build a dedicated deal-desk function, which most organisations are not willing to fund as a standalone investment.
Partner operations is a third example that has grown rapidly in scope as channel programmes have become more complex. The work of managing partner contracts, registrations, deal protection, and co-sell mechanics requires operational infrastructure that is similar to the infrastructure sales ops already maintains for direct sales. The path of least resistance is to extend sales ops to cover it, even when the work would more logically sit inside the channel function.
Why nobody else takes the work
The structural reasons why the work keeps landing in sales ops are worth understanding because they explain why the pattern is hard to reverse.
Other functions that might logically own pieces of this work are typically structured for activities that are conceptually their core mandate rather than for operational support to revenue execution. Finance owns financial planning and reporting, but typically does not have the operational infrastructure to run deal-by-deal approval workflows at the cadence sales requires. Product owns the product, but typically does not have the customer-facing operational discipline to run pricing decisions on individual deals. Marketing owns programmes and content, but typically does not have the operational link to specific deals that the enablement work requires.
These are not failings of the other functions. They are reasonable consequences of how those functions are organised and what they are optimised for. Sales ops fills the operational gap because the alternative would be to expand the operational footprint of the other functions, which is more expensive and harder to justify than letting sales ops absorb the work incrementally.
The incremental nature of the absorption is what makes the problem hard to see. No single decision creates the overload. Each individual scope expansion is reasonable in isolation, often presented as a small additional responsibility that sales ops is well-positioned to handle. The cumulative effect, however, is a function whose actual scope is several times larger than its formal mandate and whose capacity is structurally insufficient to deliver everything it is responsible for.
What gets compromised
The overload produces predictable compromises in what sales ops actually delivers. The work that is most time-sensitive and most visible to senior leadership, including forecasting, deal desk, and pricing approvals, gets done at the required cadence because the consequences of failure are immediate. The work that is more strategic and less time-bound, including territory planning, compensation design, sales analytics, and process improvement, gets done less consistently and at lower quality because the urgent work consistently displaces it.
This means that the parts of the sales ops mandate that have the highest long-term leverage are typically the parts that get the least attention. Strong territory and quota design pays back over years. Disciplined compensation design influences sales behaviour across an entire fiscal year. Genuine investment in sales analytics produces insights that compound over time. The day-to-day operational work pays back over hours and days, which is why it wins the competition for capacity.
The senior sales ops practitioners who have spent careers in the function are usually well aware of this pattern. The frustration of watching the strategic work get displaced by the operational work, year after year, is one of the most common themes in conversations with sales ops leaders who have moved on from the role.
Where the operating model could change
The functions that have managed this better have generally done one of two things. Some have built dedicated capability around the work that was previously absorbed by sales ops, with a separate deal desk function, a dedicated partner operations team, or a sales enablement function that is structured as its own discipline rather than as a sales ops sub-team. These split-out functions free sales ops to focus on its core mandate, but they require explicit investment that most organisations do not make until the sales ops overload has produced visible business consequences.
Others have moved sales ops inside a broader revenue operations function that explicitly owns the cross-functional operational work for the revenue side of the business. The RevOps construct, which has been on the rise for several years, is partly a recognition that the work sales ops has been absorbing is genuinely cross-functional and benefits from being managed as a discipline rather than as scope creep. RevOps does not solve the underlying problem of work landing in operational functions that other teams are not structured to own, but it provides a more coherent organisational home for the work and clearer leadership accountability for the operational quality of revenue execution.
The honest assessment is that most organisations have done neither of these things substantively. They have allowed sales ops to absorb the work and underfunded it relative to the resulting scope, with the operational gaps showing up as forecast misses, pricing inconsistency, deal-desk delays, and enablement content that does not get produced at the required pace.
What sales ops leaders should consider doing
The practical move for sales ops leadership who are trying to manage this is twofold. The first is to make the actual scope of the function visible, with documented inventory of every piece of work the team is currently responsible for, every cross-functional process it owns, and every operational dependency that other functions are quietly relying on it for. This makes the overload concrete in a way that the more abstract conversation about sales ops scope rarely achieves.
The second is to use the visible inventory to have an explicit conversation with senior leadership about where the work should sit going forward. The conversation is rarely comfortable, because it tends to surface that other functions have been relying on sales ops to absorb work that they should arguably be doing themselves. The conversation is also necessary, because the alternative is that the overload continues to compromise the strategic work that sales ops is supposed to be doing.
The broader observation is that the sales ops overload is a symptom of organisational design gaps that companies have not solved. The function's willingness to absorb cross-functional work has been a useful operational lubricant, but it has also allowed those gaps to persist longer than they would have if the work had been allowed to fall through. Closing the gaps requires explicit organisational choices that most companies have not yet been willing to make, and until they do, the function will continue to absorb work that does not belong to it and pay the cost in the strategic work that does not get done.
