RevOps Org Chart: What Series B Gets Wrong

You hired your first RevOps person at Series A. They built the CRM, set up Salesforce, connected a few tools. It worked. By Series B, you've 2–3x'd your revenue team, you're opening new regions, and your RevOps person is drowning.

So you hire a second RevOps person. And suddenly you have two people doing the same job, stepping on each other, with no clear handoff. Or worse, you split the work arbitrarily: one owns Sales Ops, one owns Marketing Ops. They barely talk.

I've audited RevOps teams at 20+ Series B companies. The pattern is consistent: they hire based on title and head count, not on the actual functions the business needs.

Here's what actually works.

The Four Functions of RevOps (Not Titles)

RevOps isn't one job. It's four distinct functions that happen to use the same tools:

1. Revenue Systems (CRM, data, integrations)

Owner: "Salesforce Administrator" or "CRM Manager"

Responsibilities:

• Salesforce configuration: custom fields, picklists, workflows, validation rules
• Data architecture: Account and Contact hierarchy, Opportunity structure, custom objects
• System integrations: connecting Outreach, Slack, Hubspot, enrichment tools
• Database maintenance: quarterly audits, deduplication, field mapping

Skills: SQL-adjacent thinking, patience for configuration details, attention to data hygiene

Time allocation: 80% configuration, 20% reporting

2. Pipeline Operations (forecasting, deal flow, risk management)

Owner: "Sales Operations Manager" or "Pipeline Manager"

Responsibilities:

• Forecast accuracy: designing the forecast process, managing forecast calls with sales leadership
• Deal health visibility: building dashboards that show pipeline aging, conversion rates, risk signals
• Sales process design: defining stages, deal qualification criteria, stage exit criteria
• Rep enablement: training on CRM process, proactive coaching on pipeline metrics

Skills: Business acumen, comfort with uncertainty, strong communication with sales leadership

Time allocation: 40% forecasting, 30% analytics, 20% training, 10% optimization

3. Commercial Analytics (unit economics, metrics, growth measurement)

Owner: "Revenue Analyst" or "Analytics Manager"

Responsibilities:

• CAC and LTV measurement: designing cohorts, tracking unit economics by source
• Growth metrics: MRR, ARR, churn, net retention, payback period
• Dashboards and reporting: weekly sales metrics, monthly board metrics
• Root cause analysis: why is conversion down? Why is CAC up this month?

Skills: SQL, comfort with data warehouse, business storytelling

Time allocation: 70% analytics, 20% investigation, 10% strategy

4. Revenue Automation (workflows, playbooks, efficiency)

Owner: "Revenue Operations Engineer" or "Automation Manager"

Responsibilities:

• Outreach workflows: creating email sequences, call cadences, multi-channel playbooks
• CRM automation: workflows, approval processes, field auto-population based on rules
• Tool integration design: planning how tools talk to each other, managing API keys and syncs
• Playbook deployment: onboarding new sales processes into automation

Skills: Systems thinking, workflow design, comfort with APIs and "no-code" platforms

Time allocation: 50% workflow design, 30% troubleshooting, 20% optimization

The Series B Org Chart That Works

If you're Series B with $2–5M ARR and 8–15 AEs:

Minimum viable team: 2–3 people

| Function | Headcount | Owner | Reports To | | --- | --- | --- | --- | | Revenue Systems | 1 | Salesforce Admin | VP Sales or RevOps Director | | Pipeline Operations | 1 | Sales Ops Manager | VP Sales or RevOps Director | | Commercial Analytics | 0.5 FTE | Analyst (shared with Finance) | Finance or RevOps Director | | Revenue Automation | 0.5 FTE | Automation Manager (shared with IT) | RevOps or IT |

Why 2.5 people, not 3?

At Series B scale, Commercial Analytics doesn't require a full-time analyst. Your CFO and finance team are already building board metrics. RevOps can own sales-specific metrics (CAC by source, pipeline conversion) and hand off company-level metrics to finance. Same with Automation: your IT person can maintain integrations and API keys. RevOps designs the workflows.

However, if you're in a high-motion environment (opening new regions, launching new products), you'll scale this to:

| Function | Headcount | Owner | Reports To | | --- | --- | --- | --- | | Revenue Systems | 1 FTE | Salesforce Admin | VP Sales or RevOps Director | | Pipeline Operations | 1 FTE | Sales Ops Manager | VP Sales or RevOps Director | | Commercial Analytics | 1 FTE | Revenue Analyst | Finance or RevOps Director | | Revenue Automation | 0.5 FTE | Automation Manager | RevOps Director |

Key shift: You hire a dedicated analytics person. They're full-time on sales metrics, CAC, LTV, and cohort analysis. That's when you get real insights.

The Mistakes Series B Makes

Mistake 1: "Two people, split by tool"

One person owns Salesforce + HubSpot. The other owns Outreach + Slack.

This is dysfunctional because a data sync problem (Salesforce → Outreach) requires both people. A forecast build requires both. You've introduced dependency and communication overhead with no actual benefit.

Fix: Split by function, not by tool. Person A owns CRM + data. Person B owns forecasting + pipeline visibility. They share tool expertise but own distinct outcomes.

Mistake 2: Hiring a "Director" before you have the team

"We need a RevOps Director to manage the function."

At Series B, you don't have a function yet. You have 2 people doing disconnected work. A Director just adds a layer.

Fix: Hire the individual contributors first. Let them discover their own coordination needs. Promote one to manager/director when headcount hits 4–5 and they're fighting fires together daily.

Mistake 3: Dumping operations tasks outside their core function

"Can RevOps also own account/named account management? They know the data."

"Can RevOps design compensation plans? They understand the pipeline."

RevOps is a systems and operations function. It should not own GTM strategy. It should not own comp design. It should not run account management. When RevOps owns too many things, the core systems break.

Fix: Keep RevOps laser-focused on the four functions above. Everything else is sales leadership's job.

Mistake 4: No clear accountability for data quality

Everyone owns data quality. Which means no one does.

Fix: Revenue Systems owner (your Salesforce Admin) is accountable for data audits, deduplication, and quarterly cleanup. Build it into their job description. Give them 2 hours per month for proactive data work.

Reporting Lines Matter

Where does RevOps report?

Option 1: Reports to VP Sales

• Upside: Direct access to sales leadership. Responsive to sales needs.
• Downside: RevOps priorities skew toward sales convenience, not long-term health. Data quality gets deprioritized when it's inconvenient.

Option 2: Reports to Finance or CEO

• Upside: RevOps can say no to sales when it compromises data integrity. Metrics are defensible and auditable.
• Downside: RevOps feels distant from the sales team. Tool adoption can slow if sales feels like RevOps doesn't understand their workflow.

Option 3: RevOps Director reports to VP Sales, individual contributors report to RevOps Director

• This is the sweet spot at Series B. RevOps has its own leader who advocates for the function while remaining aligned with sales. The director is the tie-breaker.

What to Build First (The Roadmap)

If you're Series B and your RevOps org is a mess, here's what to fix in order:

Months 1–2: Revenue Systems

• Audit your Salesforce setup. Fix data quality. Define your data model.
• This is the foundation. Without clean data, everything else fails.

Months 2–3: Pipeline Operations

• Build a forecast template and cadence. Make pipeline visibility real.
• Sales leadership should see their forecast in the morning, not the afternoon.

Months 3–4: Revenue Automation

• Design email playbooks and workflows. Reduce manual data entry.
• This is where you get time back for your team.

Months 4+: Commercial Analytics

• Start tracking CAC and LTV. Understand your unit economics.
• This is the hardest function to hire for. You can start with your CFO/analyst.

Talk to Your RevOps Team

If you have a RevOps person and they're drowning, they're probably doing 3–4 functions with no clear boundaries.

Ask them: "Which of these four things do you hate the most? Which do you love?"

Their answer will tell you what to hire next. If they hate forecasting but love automation, hire a sales ops person. If they love analytics but hate CRM maintenance, hire a Salesforce admin.

RevOps scales by function, not by title. Build around the actual work, and suddenly you have headcount efficiency and a team that doesn't burn out.

---

Take Action This Week

1. Map your current RevOps team against the four functions. What's covered? What's missing?
2. Ask your RevOps person if they feel like they have clear scope and clear wins.
3. If the answer is no, sketch out a hire for the next 6 months.

That's the start.

---

Related Reading

Building RevOps is systems work. These pieces fit together:

• Your CRM's Dirty Data Problem is a Revenue Leak — Your Revenue Systems owner's first priority.
• The Signals Your Competitors Are Hiring — Watch how competitors structure their revenue teams.

---

ImpactGain helps Series B companies scale their revenue operations team structure. We design org charts, hiring plans, and operational roadmaps. If your RevOps function is opaque or stretched thin, let's talk.

Request a free org chart audit →