sources.md

RevOps Org Chart: Source Reference

1. RevOps Team Roles and Hiring Guide

Type: Internal reference Created: November 2025

Four org chart tiers + role breakdowns:

1-3 people (Foundation): Director of RevOps (first hire, 5+ years, strong generalist), RevOps Analyst (junior, data-comfortable), Systems/CRM Admin (owns GTM tech stack and integrations).

4-6 people (Growth): Triggered at 50-60 CRM end users. Adds: second CRM Admin, RevOps Manager (PM + people manager, runs weekly sprints), additional Analyst, BI/Insights Manager (Looker/Snowflake/Tableau), Revenue Enablement Manager.

7-10 people (Scale): Manager shifts to Program Manager (generalist, manages up to executives). Three analysts (one per funnel segment: Sales, Marketing, CS). Marketing Operations Lead (3+ years RevOps, 2+ years Marketing Ops, Marketo/HubSpot admin). CS Operations Lead (3+ years RevOps, CS experience preferred). These are the proto-Business Partner roles.

10+ people (Mature): All prior roles with deeper specialization. Clear swim lanes across funnel. Requires explicit governance.

2. RevOps Co-op: Evolutionary Org Chart

URL: https://www.revopscoop.com/post/how-should-your-revenue-operations-organization-be-structured Also on: https://revopscoop.substack.com/p/revops-co-op-weekly-18-how-should Format: Four-stage evolution diagram

Stage 1: Siloed: Ops report to department VPs. Gets deprioritized. Systems Architects exist but have no mandate. Stage 2: Departmental: All ops under one manager, but organized by department they support. Cross-team conflicts emerge. Stage 3: Functional Specialization: Reorganized by capability. Systems team (Architects + Admins) and Insights team (Analysts) each get dedicated managers. Manager of Systems team = former Systems Architect. Stage 4: Evolved: Enablement joins. Cross-functional PMs and Analysts. Agile methodologies. Ride-alongs (ops shadows end users quarterly).

Key quote paraphrased: Hiring a manager who has been a systems architect to manage the systems team just makes sense.

3. Revenue Wizards: Hiring Guide (Seven FTE Tiers)

URL: https://newsletter.revenuewizards.com/p/the-hiring-guide-for-you-revops-team

Company FTEs	RevOps Team	Guidance
0-10	0 in-house	Agency for CRM setup
11-25	0 in-house	Freelance consultant for hygiene
26-50	1 generalist	First hire; supplement with agency
51-100	2-3 specialists	Analytics, enablement, process
100-250	4-12 professionals	Analysts, PMs, enablement leads
250-1,000	13-100 professionals	Segmented Sales/Marketing/CS ops
1,000+	2-5 or 100+	Small strategic team OR full function

Three archetypes: Strategic Leader (VP/Director), Generalist Manager (always first hire), Subject Matter Experts (never first hire). Ratio: 1 generalist per 5 experts.

4. Hyperscayle: Maturity Model (5 Levels)

URL: https://hyperscayle.com/insights/revops-framework-team-structure Also: https://hyperscayle.com/insights/revops-maturity-model

Level 1: Ad Hoc: No dedicated ops. Level 2: Functional: 1-2 analysts keeping things running. Level 3: Repeatable: RevOps Director + 3-4 analysts. Minimum cost ~$600K/year. Level 4: Scalable: VP RevOps + multiple Directors (Marketing Ops, Sales Ops, CS Ops, PM). Level 5: Optimized: Full mature organization.

Most common under-investment: RevOps team itself. Most common over-investment: Systems and tools. Key principle: Right-size the team with the complexity of the GTM motion, not ARR.

5. Go Nimbly: Three Structural Models

URL: https://gonimbly.com/blog/revops/revops-org-structure-a-comprehensive-guide/

Departmental Model: Sales Ops, Marketing Ops, CS Ops as separate teams under Head of RevOps. Best for early-stage. Risk: re-siloing.

Functional Model: Strategy, Tools/Data, Enablement, Insights teams; each serve all departments. Best for mature orgs. This is the Center of Excellence approach.

Flat Structure: Minimal hierarchy, empowered ICs. Startups only. Does not scale.

7. Maxio: Team Structures by Size

URL: https://www.maxio.com/blog/revenue-operations-team-structures

Org structures for Small (<50 employees), Medium (50-200), Large (200+). Notable: cites OpenAI as example of mature org splitting RevOps into two branches: Systems (tech stack, integrations, data infrastructure) and Strategic (planning, forecasting, process design, GTM alignment). Architect leads Systems branch. Business Partners sit in Strategic.

8. Stage2 Capital: RevOps Hiring Guide

URL: https://www.stage2.capital/blog/revops-when-how-and-who-to-hire

VC-backed hiring guidance. Endorses RevOps Co-op evolutionary org chart as the gold standard for visual representation. Provides hiring timing by stage and typical reporting structures.

9. Leanlayer: Team Size Calculator

URL: https://www.leanlayer.com/team-size-calculator

Interactive calculator for RevOps team sizing. Provides benchmarks from Insight Partners portfolio data:

$0-10M ARR: 49% of companies have RevOps; revenue:RevOps ratio = 11:1
$10-20M: 89% adoption; ratio = 12.9:1
$50-100M: 98% adoption; ratio = 15:1
AE:RevOps ratio scales from 4:1 (1-10 AEs) to 12.2:1 (100+ AEs)

10. RevPartners: RevOps Architect Job Description

URL: https://inbound.revpartners.io/revops-architect

Requirements include: coding (JavaScript, Node.js, Python), data architecture, executive communication. Key principle: "Business process should always drive the technology; the technology should never dictate the business process." Owns: end-to-end system design, integration layer, data model, automation framework, reference architecture documentation.

11. Lift Enablement: Role of the Solution Architect (Podcast)

URL: https://www.liftenablement.com/podcasts/revops-show/best-of/role-of-revops-solution-architect

Episode 34 of RevOps Show. Key framing: the Architect role is fundamentally about business process, not technology. The technology is the output of understanding how the business runs.

12. Squad4: GTM & RevOps Budget Guide

URL: https://www.squad4.io/blog/stop-guessing-revops-budget-definitive-guide

Mature RevOps teams should spend 5-10% of total GTM budget. At $2-5M ARR, 3% of revenue = only $60K-$150K; insufficient for a $180K+ VP. Advice: "Focus early RevOps budget on architecture over administration."

Sources