The org chart matters more than the headcount. TPG has seen companies with 12-person RevOps teams that function like a fragmented help desk and 4-person teams that run forecast calls with the board. The difference is structure—specifically, who reports to whom and who owns what decisions.
There are three RevOps models that work. Which one fits depends on where your company is in its growth trajectory.
In a centralized model, one RevOps team serves all three revenue functions—sales, marketing, and customer success. There is no dedicated ops person embedded in each function. The RevOps team sets standards, owns systems, builds reports, and manages process for everyone.
This works under $100M ARR because the volume of requests and the complexity of process doesn't yet require function-specific depth. A skilled RevOps Manager can hold the full picture: marketing attribution, sales forecasting, and CS health scoring without losing resolution on any of them.
What centralized RevOps looks like at $30M ARR:
At this stage, the RevOps Manager reports to the CRO or CEO. That reporting line is not optional—if the RevOps Manager reports to the VP of Sales, marketing ops becomes second priority by default.
The risk of centralized RevOps: As you approach $75M-$100M ARR, the team becomes a bottleneck. Sales wants faster CRM changes. Marketing wants more automated workflows. CS wants a health score model built yesterday. If you do not add headcount and specialize roles before the bottleneck forms, RevOps loses credibility across all three functions simultaneously.
In a federated model, each revenue function has a dedicated ops person—a Marketing Ops Manager, a Sales Ops Manager, a CS Ops Manager. Those three roles report directly to the revenue function they support. A central RevOps layer (VP of RevOps plus a Revenue Analyst) coordinates across them: setting shared data standards, owning the forecasting model, and maintaining the integrated reporting architecture.
This is the model most mid-market companies need and almost none have built correctly. The failure mode is federation without coordination: three ops managers who are functionally independent and rarely in the same meeting. That is not a federated RevOps model. It is three separate ops functions with a shared title.
What federated RevOps looks like at $150M ARR:
The dotted-line reporting to VP RevOps is what makes this model work. Without it, the embedded ops people optimize for their function at the expense of the integrated revenue picture.
The risk of federated RevOps: Integration overhead. More people means more coordination, more competing priorities, and more potential for the central layer to become a governance function rather than an operating one. The VP of RevOps must run the shared standards actively—not just publish a wiki page that no one reads.
At $500M ARR and above, RevOps becomes a full organizational function with sub-teams dedicated to specific domains: a Systems and Data team that owns the tech stack and integrations, a Process and Enablement team that designs and trains on revenue processes, a Revenue Intelligence team that owns forecasting and analytics, and function-specific ops teams that support sales, marketing, and CS.
This model requires a Chief Revenue Officer to make it work. Without a CRO with budget authority over all revenue functions, the sub-teams revert to serving whoever controls their performance reviews.
What full RevOps looks like at $600M ARR:
Total team: 15-25 people depending on sales team size and tech stack complexity.
"The org chart tells you where the power sits. If RevOps reports to sales, it serves sales. If it reports to the CRO, it serves revenue. Those are different jobs."
VP of Revenue Operations: Owns the forecast methodology, shared data standards, and RevOps team performance. Sets the architecture for how all revenue systems connect. Should be able to present the pipeline number to the board and defend every assumption.
RevOps Manager: Executes the architecture the VP defines. Owns day-to-day CRM administration, workflow configuration, and process documentation. In smaller companies, this role is the RevOps function—player-coach who builds and operates simultaneously.
Marketing Ops Analyst: Owns campaign operations in the marketing automation platform, lead routing configuration, and marketing attribution reporting. Should have hands-on HubSpot or Marketo experience, not just familiarity.
Sales Ops Analyst: Owns CRM data quality for the sales pipeline, deal stage governance, quota tracking, and sales forecasting support. Should be able to run a territory analysis and build a custom pipeline report without asking IT.
CS Ops Analyst: Owns the customer health score model, renewal pipeline tracking, and CS team reporting. Should understand churn analysis and be able to identify at-risk accounts from data before the CSM flags them manually.
Revenue Analyst: Owns win/loss analysis, lead source attribution, and pipeline trend reporting. This is not an entry-level role—it requires enough statistical fluency to build a regression model and enough business context to explain what it means.
The single most common RevOps hiring mistake is bringing in a senior VP before the foundational work is done. A VP of RevOps who spends their first 12 months cleaning up a broken CRM is overpaid for the work and undersupported to do it well.
The correct sequence:
RevOps Manager first. This person builds the foundation: lifecycle stage definitions, deal stage criteria, data standards, basic reporting. Budget 6-9 months for this before adding headcount.
Marketing Ops Analyst second. Once the shared architecture is in place, the marketing ops workload—campaign operations, lead routing, attribution—requires dedicated capacity.
Sales Ops Analyst third. Forecast support and CRM governance become the bottleneck as the sales team scales.
Revenue Analyst fourth. When the data is clean enough to analyze, hire someone whose full job is analyzing it.
VP of RevOps when the function needs to scale, not when it needs to be built. A VP can drive 3x more value when they are optimizing a functioning RevOps structure than when they are building from scratch.
The most common failure is creating RevOps by reorganizing existing silos without changing reporting lines.
A company has a Marketing Ops Manager reporting to the CMO, a Sales Ops Manager reporting to the VP of Sales, and a CS Ops Manager reporting to the VP of CS. They rename the group "RevOps" in an all-hands presentation, create a Slack channel, and schedule a weekly sync. Nothing else changes.
Six months later, the Marketing Ops Manager is optimizing for lead volume because that is what the CMO measures. The Sales Ops Manager is running territory analysis because the VP of Sales needs it by Friday. The CS Ops Manager is building health score reports that CS leadership has been requesting for months. The shared work—integrated forecasting, unified data standards, cross-functional process design—is not getting done because no one's performance review depends on it.
Real RevOps requires a single leader with authority over all three operations functions, or a strong VP of RevOps with formal coordination authority over embedded ops managers. Without that, you have three ops functions and one Slack channel.
What to Do Before You Build
Document your current state first. Map every system that touches revenue data, who owns each system, and who has admin access. Inventory all the places where pipeline data lives outside the CRM (spreadsheets, email, regional systems). Count how many definitions of "qualified lead" exist across marketing and sales.
That audit will tell you how much foundation work is required before the RevOps structure can function. Most companies underestimate it by 50%.
Talk to a Revenue Operations Specialist
Should RevOps report to the CRO or the CEO? Under $50M ARR, reporting to the CEO often works better—it gives RevOps authority over sales, marketing, and CS equally without being subordinate to any of them. Above $50M ARR, a CRO with authority over all three revenue functions is the natural home. The wrong answer is reporting to any single revenue function leader, which creates inherent bias in how RevOps allocates its time and political capital.
What is the difference between a RevOps Manager and a VP of RevOps? A RevOps Manager executes: they configure systems, build reports, manage processes, and maintain data standards. A VP of RevOps designs and governs: they set the architecture, manage a team, represent RevOps to the executive team, and own the forecast methodology. At companies under $30M ARR, one strong RevOps Manager can run the function. Above $50M ARR, you need both roles.
How long does it take to build a functioning RevOps team? From first hire to fully functioning RevOps—clean data, reliable forecast, shared process—takes 9-18 months depending on starting-point complexity. The first 3 months are foundation work: cleaning data, defining standards, rebuilding broken workflows. The next 3-6 months are process design: lead handoff SLAs, deal stage governance, CS onboarding workflows. The final phase is optimization: using clean data to improve conversion rates, forecast accuracy, and sales cycle length. Do not judge RevOps ROI at month 6.
Can we outsource RevOps? Outsource the build; hire for the run. External firms like TPG can design the architecture, configure the systems, and establish the processes in 3-6 months. But someone internal needs to own it once it is built. A RevOps function that is entirely outsourced has no institutional authority, no accountability for outcomes, and no continuity when the engagement ends.
The Pedowitz Group | pedowitzgroup.com | Revenue Marketing Experts Since 2007