← Back to blog

What Does a VP Operations Actually Do?

A practical breakdown of the VP Operations role at startups and scale-ups — responsibilities, skills, hiring signals, and how the role differs from COO and Head of Ops.

vp operationsoperations leadershipstartup hiringorg designoperator roles

What Does a VP Operations Actually Do?

You've seen the title on LinkedIn. You've seen it on job boards. But when someone says "VP Operations," what does that actually mean — especially at a startup?

The honest answer: it depends on the company. But that's a cop-out. There are clear patterns, and if you're hiring for this role (or considering it as a career move), you need to understand what the VP Ops actually owns, how the role differs from adjacent titles, and when a company genuinely needs one.

Let's break it down.

The Core Job: Making the Machine Work

At its simplest, the VP Operations is the person responsible for making sure the business runs. Not the product. Not the code. Not the sales pitch. The business — the systems, processes, and infrastructure that let everyone else do their jobs.

In a startup context, this typically means owning some combination of:

  • Business process design and optimisation — workflows, SOPs, tooling decisions
  • Cross-functional coordination — making sure eng, sales, product, and support aren't working at cross-purposes
  • Scaling infrastructure — not servers, but the human and process infrastructure that breaks when you go from 20 to 100 people
  • Metrics and reporting — building the dashboards and cadences that give leadership visibility
  • Vendor and partner management — negotiations, contracts, operational partnerships
  • Team management — typically leading a mix of ops analysts, project managers, and specialists

The VP Ops is the person who notices that your onboarding process takes 3 weeks when it should take 3 days, and then actually fixes it. They're the one who builds the QBR template that the entire company ends up using. They're the one who figures out that your support team and your account management team are solving the same problems independently and merges the workflows.

VP Operations vs COO: What's the Difference?

This is the question everyone asks, and the answer is more nuanced than "COO is more senior."

Scope: A COO typically has company-wide remit and sits on the executive team. A VP Ops usually owns a defined operational domain — sometimes company-wide process, sometimes a specific business unit.

Authority: The COO often has P&L responsibility and makes strategic decisions alongside the CEO. The VP Ops executes strategy within their domain and influences company strategy through operational insight.

Reporting: COOs report to the CEO. VP Ops might report to the COO, the CEO, or sometimes the CFO depending on the org structure.

When you see both: In larger scale-ups (200+ people), you might see a COO with one or more VPs of Operations reporting to them, each owning a vertical — e.g., VP Revenue Operations, VP Business Operations, VP People Operations.

The practical test: If the role requires regular board-level interaction, strategic partnership decisions, and cross-functional authority over other VPs, it's probably a COO. If it requires deep operational execution within a defined scope, it's probably a VP Ops.

VP Operations vs Head of Operations

This one's simpler but still worth clarifying.

"Head of Operations" and "VP Operations" are often used interchangeably at startups, particularly before Series B. The distinction, where it exists, is usually:

  • Head of Ops tends to be more hands-on, often the first operations hire, building from scratch
  • VP Ops implies a layer of management underneath — you're leading a team of operators, not just operating yourself

At a 30-person startup, "Head of Ops" and "VP Ops" are the same job. At a 300-person company, they're different roles with different expectations.

Don't get hung up on titles. Focus on scope, authority, and team size.

What Does the Day-to-Day Actually Look Like?

Here's a realistic week in the life of a VP Operations at a Series B startup (150 people, $30M ARR):

Monday: Review weekly metrics dashboard. Flag that customer onboarding time has crept up 40% over the past quarter. Schedule a deep-dive with the CS team.

Tuesday: Lead the cross-functional ops review. Present a proposal to consolidate three overlapping project management tools into one. Get buy-in from eng and product leads.

Wednesday: Interview two candidates for a Senior Operations Analyst role. Spend the afternoon mapping the end-to-end order fulfilment process for a new product line.

Thursday: Work with finance on the Q2 budget. Negotiate a renewal with a key SaaS vendor — save £40K annually by consolidating licences. Draft the ops section of the board deck.

Friday: One-on-ones with direct reports. Review and approve the new employee onboarding workflow. Spend an hour on a process automation that'll save the support team 10 hours per week.

The common thread: every day involves a mix of strategic thinking and hands-on execution. If you're someone who only wants to think big thoughts or only wants to execute tasks, this role isn't for you. The VP Ops lives in the middle.

The Skills That Actually Matter

Forget the generic "strong communicator, analytical thinker" job description language. Here's what separates great VP Ops hires from mediocre ones:

1. Systems Thinking

The ability to see how changing one part of the business affects everything else. When you speed up sales cycles, what happens to implementation capacity? When you automate reporting, what happens to the analyst team's role? Great operators think in systems, not silos.

2. Process Design (Not Just Documentation)

Anyone can write an SOP. The VP Ops needs to design processes — understanding bottlenecks, handoff points, failure modes, and edge cases. This is an engineering mindset applied to business operations.

3. Data Fluency

You don't need to write SQL (though it helps). You need to know what to measure, how to interpret it, and how to present it in a way that drives decisions. The best VP Ops can look at a dashboard and immediately spot the metric that's lying.

4. Stakeholder Management

You're going to tell people their processes are broken and need to change. You need to do this without making enemies. Political awareness, empathy, and the ability to get buy-in are non-negotiable.

5. Prioritisation Under Ambiguity

In operations, everything is urgent and everything is important. The VP Ops needs to be ruthless about prioritisation, often with incomplete information. This means being comfortable saying "no" or "not yet" to senior stakeholders.

6. Tool and Tech Savvy

Modern operations runs on software. You need to evaluate, implement, and optimise tools — CRM, ERP, project management, automation platforms, BI tools. You don't need to code, but you need to understand what technology can and can't do.

Hiring Signals: What to Look For

If you're hiring a VP Operations, here's what to screen for beyond the CV:

Green flags:

  • They can describe a process they built from scratch and explain why they made specific design decisions
  • They've scaled something — a team, a process, a system — through a period of rapid growth
  • They talk about trade-offs, not just wins
  • They ask sharp questions about your current operational pain points during the interview
  • They have examples of cross-functional influence without direct authority

Red flags:

  • They describe their role in purely strategic terms with no operational detail
  • They can't explain how they measure success in their current role
  • They default to "hire more people" as the solution to scaling problems
  • They've only worked in large, structured environments and haven't experienced startup ambiguity
  • They talk about "best practices" without questioning whether those practices apply to your context

Compensation: What VP Ops Roles Pay

Compensation varies significantly by geography, company stage, and scope. Here's a rough guide for UK/US markets in 2026:

| Stage | UK (Base + Equity) | US (Base + Equity) | |-------|-------------------|-------------------| | Seed–Series A | £80K–£110K + 0.3–0.8% | $120K–$160K + 0.3–0.8% | | Series B | £110K–£140K + 0.1–0.4% | $160K–$200K + 0.1–0.4% | | Series C+ | £130K–£170K + 0.05–0.2% | $180K–$240K + 0.05–0.2% |

These are base salary ranges. Total comp including bonuses and equity value can be significantly higher, especially at later stages where equity has more predictable value.

When Does a Startup Need a VP Operations?

Not every startup needs this role, and getting the timing wrong wastes money and creates frustration. Here are the signals that it's time:

  • The CEO is spending >30% of their time on operational issues instead of product, fundraising, or sales
  • Cross-functional coordination is breaking down — teams are duplicating work or blocking each other
  • You're growing headcount faster than you're growing process — things that worked at 20 people are failing at 50
  • You have operational data but nobody is using it to make decisions
  • Customer-facing operations (onboarding, support, fulfilment) are becoming a competitive liability

If fewer than three of these apply, you probably don't need a VP Ops yet. A strong Head of Ops or even a senior ops analyst might be the right first hire.

The Bottom Line

The VP Operations is the person who turns a startup's ambition into repeatable execution. They don't build the product, but they build the machine that delivers it. They don't close deals, but they make sure closed deals turn into happy customers. They don't set the vision, but they make sure the company can actually get there.

It's one of the most impactful roles in a scaling company — and one of the most misunderstood. If you're hiring for it, focus on systems thinking, execution ability, and cultural fit. If you're considering the role, make sure you genuinely enjoy the messy middle ground between strategy and execution.

Because that's where operators live. And it's where the best ones thrive.