If you've been paying attention to ops job postings over the last five years, you've noticed something multiplying. BizOps. RevOps. ProductOps. SalesOps. MarketingOps. And increasingly, Chief of Staff. Each one is a real function. Each one is trying to solve a coordination problem. And if you're a growing company, figuring out which ones you need, in what order, and how they relate to each other is one of the more important organizational design questions you'll face.
Let's try to map it.
The taxonomy of modern Ops
Think of the modern ops landscape as organized around two axes: what domain and what scope.
Scope breaks down into three levels:
- Functional: one specific team (SalesOps, MarketingOps)
- Revenue: the revenue-facing function (RevOps — spans marketing, sales, customer success)
- Company-wide: everything (BizOps, Chief of Staff)
Domain is the second axis: what type of work.
Here's how it typically maps:
SalesOps — functional scope, sales domain. Owns Salesforce hygiene, sales process, quota management, territory planning. Takes non-selling work off sales reps.
MarketingOps — functional scope, marketing domain. Owns the marketing tech stack, campaign infrastructure, lead flow, marketing automation. Enables marketers to market.
ProductOps — functional scope, product domain. Owns the product development process, feedback collection, analytics instrumentation, go-to-market coordination for launches. Reduces friction in the product org.
RevOps — revenue scope. Coordinates across marketing, sales, and customer success with a specific focus on the revenue funnel. Pipeline health, lead handoff quality, win rates, retention. Revenue is the north star; cross-functional alignment is the method.
BizOps — company-wide scope. Coordinates across all functions, owns company-wide planning (OKRs, quarterly reviews), fills gaps where no dedicated ops function exists yet, and maintains the overall operating infrastructure of the company.
Chief of Staff — company-wide scope, person-adjacent. Protects and amplifies a senior executive's bandwidth. The CoS is an extension of one leader's operating system, not a function in the traditional sense.
How they relate
The most important thing to understand is that these functions aren't independent — they're hierarchical and sequential.
Early-stage companies typically have BizOps first. One or two people doing cross-functional coordination, filling gaps wherever they appear, and generally keeping the company from collapsing under its own coordination overhead.
As the revenue function matures, RevOps typically splits off from BizOps. Someone who was doing cross-functional work focused on the revenue funnel specifically becomes the RevOps lead. The BizOps person keeps everything else.
As individual functions grow, they develop their own ops needs. SalesOps emerges when the sales team is large enough that reps can't manage their own pipeline process. MarketingOps emerges when the marketing tech stack becomes too complex for one person. ProductOps emerges when product launches start requiring dedicated coordination.
Chief of Staff usually enters the picture when a senior executive — typically the CEO or a founder — is consistently overwhelmed and needs a dedicated amplifier. The CoS is the most person-dependent of all the ops roles: its shape is defined by the person it serves.
The ordering question
In practice, most companies should build in this order:
- BizOps (Series A/B) — when cross-functional coordination failures start appearing across the whole company
- RevOps (Series B/C) — when marketing, sales, and customer success are large enough to warrant dedicated coordination
- Functional Ops (SalesOps, MarketingOps, ProductOps) — when individual functions are large enough to need dedicated operational support
- Chief of Staff — when a specific executive's bandwidth is the bottleneck to company performance
The common mistake is treating the first visible pain as the whole problem. RevOps optimizes the revenue funnel, but it does not automatically fix company-wide coordination failures. Chief of Staff can unlock an executive, but it does not automatically create operating infrastructure. BizOps is often the foundational layer because it addresses the seams before they harden into separate silos.
What the mature stack looks like
In a well-designed mature organization, the ops functions have clear domains, minimal overlap, and healthy relationships with each other.
BizOps coordinates the company-wide planning process. RevOps owns the revenue funnel and reports into or works closely with the CRO. ProductOps sits inside or adjacent to the product organization. Chief of Staff serves the CEO and has the organizational trust to work across any function when needed.
The signal that this is working: executives know which ops person to call for which type of problem, there are few gaps between ops functions (and the ones that exist are intentional), and cross-functional initiatives don't stall for lack of an owner.
The meta-point
The proliferation of ops functions is itself evidence of a real organizational need. Companies are discovering that cross-functional coordination doesn't happen automatically — it has to be designed, staffed, and maintained. The modern ops stack is the industry response to that discovery.
That's worth remembering when you're deciding whether to hire a BizOps person or a RevOps person or a Chief of Staff. The answer isn't which one — it's what coordination problem you're actually trying to solve.
Sources: Vitaly Matveev / ValueAdd, Costanoa Ventures, Tonkean, RocketBlocks
