Haris OdobasicA RevOps org chart for a mid-sized SaaS company puts a VP of RevOps at the centre, with three heads beneath, namely a Head of RevOps for process and enablement, a Head of Systems for tooling, automation and AI, and a Head of Data. This RevOps team structure fits companies with roughly 20 to 50 full-time staff in sales, marketing and customer success; below that it is too heavy, and above it you add specialists inside each pillar.
"The best structure will not guarantee results and performance. But the wrong structure is a guarantee of failure." Peter Drucker
Fast-forward two years from where I left them in the book. MyGym24, the fictional gym-software company I use to make this stuff tangible, raised a Series A in Berlin-Mitte, and the bet paid off. They raised again. The commercial team went from a handful of people to about thirty-five across sales, marketing and customer success.
And Maria, their Head of RevOps, is drowning.
She is still the entire RevOps function. One person. She is expected to set strategy, clean the data, own the customer relationship management (CRM) system, design the automation, build the dashboards, run enablement and, new this year, figure out the AI roadmap. On a good week she does two of those well. The rest slip.
This is the moment the question changes. Early on, the question is "do we even need RevOps?" Past a certain size, it becomes "how do we structure it?" If you have 20 to 50 full-time equivalents (FTE) in your commercial functions, you are at that moment. So let's build the revenue operations org chart.
Why structuring a RevOps team is harder in 2026
It is harder because of AI, and not in the way most people think.
In our global RevOps survey of 123 practitioners, 73% reported an AI mandate from leadership, and only 38% said they have the data to support it. That gap, a mandate without the foundation underneath it, is not a tooling problem you can buy your way out of. It is an org design problem. Someone has to own the data. Someone has to own the systems and the AI on top of them. Someone has to own the process and the people. And those are not the same someone.
Analysts see the same risk. Gartner expects AI agents to outnumber sellers by ten to one by 2028, and warns that without the right data foundation, workflow integration and seller experience, sales leaders risk "agent sprawl", which means more digital activity but little improvement in seller impact.
Which is the whole point of the revenue operations team structure below.
Build the RevOps org chart around the four pillars
RevOps has four pillars, which are data and insights, processes, systems and enablement. A good org chart is just those pillars with owners' names on them. Get the pillars right and the boxes draw themselves. Get them wrong, with one person holding all four or enablement floating off on its own, and you get Maria.
Here's how I'd distribute the weight.
Head of RevOps for process and enablement
This is your generalist function, and "generalist" is not an insult. The Head of RevOps manages a team of subject-matter experts, one per domain that actually applies to your business. Think sales ops, marketing ops, CS ops or partner ops, and only the ones you need. Their focus is strategy, process and enablement. For companies with an enterprise sales motion, a deal desk that gets contracts signed is often the next process specialist to add.
Enablement, meaning content, training and onboarding, sits here with the generalists. Not as a standalone hire.
I'll say this plainly, because I've watched it fail every single time. Do not hire a pure enablement person with no RevOps skills. They produce decks no one uses and training disconnected from how the process actually runs. Enablement only works when it is attached to someone who understands the system they are enabling people to use.
The key skills for this role are stakeholder management, strategic thinking and communication. This person spends their day with humans, not in the terminal.
Head of Systems for tooling, automation and AI
This head owns the stack, and three roles report into them.
- A tooling and automation expert who keeps the systems running and connected.
- An AI operations role that designs AI use cases and manages the AI stack. This is a real job now, not a side project.
- A software engineer who builds and maintains custom solutions.
That last one is the part people resist, so let me be direct. In 2026 you are going to build, not just buy. The interesting go-to-market (GTM) advantages are not sitting in an off-the-shelf tool anymore. And yes, "vibe coding" will get you a prototype over a weekend. It will not get you something your revenue team can run the business on. A prototype that quietly becomes the production system is a liability with a countdown timer. If you are going to build, let a real engineer do it.
The market calls that engineer the GTM engineer. Bloomberry's analysis of GTM engineering job postings counted GTM engineer and RevOps postings together and found them up 205% in January to September 2025 compared with the same months of 2024. It also found that 9 out of 10 responsibilities in GTM engineer postings appear in RevOps engineer postings too, led by building and automating go-to-market workflows, integrating the stack and owning the CRM. In other words, it is RevOps systems work done with an engineering skill set, and it belongs in this pillar.
This is also where AI in GTM lives. RevOps owns it. Our CRO survey found that without RevOps ownership, AI increases noise instead of impact. AI bolted onto a messy system just produces wrong answers faster.
This person needs to be highly technical, with a strong AI focus.
Head of Data as part of RevOps
Data is part of RevOps. Not a favour you ask the central data team for, not a quarterly export. A Head of Data who manages a data team, inside RevOps, reporting into the function.
Why hold this line so firmly? Because data is what will drive revenue, through pipeline scoring, churn prediction, capacity models and the inputs every AI use case depends on. Remember the survey, where only 38% had the data their AI mandate needs. Those teams did not get there by borrowing data when it was convenient.
The key skills here are a strong data focus and machine learning (ML) engineering.
The VP of RevOps role and reporting line
Three heads pulling in three directions isn't a system. It's three departments that happen to share a name.
The VP (Vice President) of RevOps is the pivot point, the thing the whole revenue operations team structure swings around. They orchestrate the whole thing. Data feeds systems, systems serve process, process is what enablement teaches, and all of it points at revenue. Without the pivot, you have weight with nowhere to transfer. With it, the same force moves something far larger than itself.
The pivot also needs the right line upwards. The VP of RevOps should report to the executive who owns the whole revenue cycle, the CEO or a CRO who runs marketing, sales and customer success, and never to one of the teams RevOps has to align. We cover the options in who RevOps should report to.
When this RevOps structure fits and what it delivers
I recommend this B2B SaaS org chart for companies with 20 to 50 FTE in commercial functions. Below that, it's too heavy, because you don't need three heads to support fifteen salespeople.
In my client work, a structure like this is what lets a company 3-5x its commercial team without adding a single ops hire. The ops function stops scaling linearly with the sales floor. And the commercial team itself gets materially more efficient, somewhere in the 2-10x range, depending on how broken things were when you started. Those are ranges from what I've seen, not guarantees. The rest is execution.
This is also one viable composition. A company with a heavy partner motion, or several geographies at different maturities, will shift the weights around. The principle holds even when the boxes move. Distribute the four pillars, give each a real owner, and put a pivot in the middle.
Structure is the skeleton. The harder question, the one I get asked the moment someone sees this chart, is sequencing. When you can't hire all of this at once, who comes first? That deserves its own post, but the next section gives you the short version.
How the RevOps org chart changes with company size
| Commercial team (sales, marketing, CS) | Structure | Notes |
|---|---|---|
| Under 20 FTE | One senior RevOps generalist covering all four pillars, with admin support or an external partner for specialist work | Three heads would cost more than the problems they solve |
| 20-50 FTE | The structure above, with a VP of RevOps and heads of process and enablement, systems and AI, and data | At the lower end, the VP can double as Head of RevOps, and one person can cover systems and data |
| 50+ FTE | The same three heads, with specialist teams inside each pillar (ops per function and a deal desk; solution architects and integrators; analysts, analytics engineers and data scientists) | Keep one VP as the pivot. More heads without a pivot recreates the silos |
The first boxes to fill are the ones nobody owns today. In our client work, the solo RevOps lead is usually the catch-all for CRM admin, reporting, process design, data clean-up and now the AI roadmap, while the business still calls it one job. That is Maria, and it is the clearest sign the structure needs to change.
The chart describes roles, not headcount. How many people you need at each company size, and how AI is changing those ratios, is covered in how big your RevOps team should be.
If you cannot hire a Head of Systems and an engineer yet, but the automation and AI work cannot wait, talk to us about embedding a GTM engineer in your team. They build the workflows, enrichment and AI use cases inside your own stack while you decide on the permanent structure.
Questions to test your own RevOps structure
- How many people are in your ops function today, measured against your commercial headcount? Is the ratio scaling with the sales floor, or independent of it?
- Of the four pillars, data, systems, process and enablement, is there one that is currently owned by no one?
- If an AI mandate landed on your GTM team tomorrow, who owns the rollout? Do they also own the data it runs on?
- Is your enablement sitting with someone who has actually carried a RevOps domain, or with someone producing training in a vacuum?
- Who is your pivot? And if the honest answer is "no one," what is currently holding your functions together?
If that last answer is "no one", let's talk about where to start.
Frequently asked questions about the RevOps org chart
What does a RevOps org chart look like?
A RevOps org chart for a mid-sized SaaS company has a VP of RevOps at the centre and three heads, for process and enablement, systems and AI, and data. Each head owns one or two of the four RevOps pillars and manages specialists as the company grows.
Who should the VP of RevOps report to?
The VP of RevOps should report to the executive who owns the whole revenue cycle, which is the CEO or a CRO who runs marketing, sales and customer success. Reporting to one of the teams RevOps aligns builds bias into the function.
Where does enablement sit in a RevOps team?
Enablement sits with the Head of RevOps, next to process, because training only works when it is attached to someone who understands the process people are trained on. A standalone enablement hire without RevOps skills tends to produce content nobody uses.
Where do GTM engineers and AI roles sit in the org chart?
They sit under the Head of Systems, next to the tooling and automation expert. The AI operations role designs use cases and manages the AI stack; the GTM or software engineer builds and maintains custom solutions on top of it.
When do you need a separate Head of Data?
You need a separate Head of Data when data starts to drive revenue decisions directly, through pipeline scoring, churn prediction, capacity models and AI use cases. In our experience that happens at around 20 to 50 commercial FTE; below that, a data analyst inside RevOps is usually enough.
