Revenue Operations
Revenue Operations is the function that owns the revenue stack — analytics, attribution, pipelines, and the alignment between marketing, sales, and finance. Here's how it works and how it's staffed.
Revenue Operations
The function that owns the end-to-end revenue stack — data, tooling, and alignment between marketing, sales, and finance.
Revenue Operations (RevOps) is the org function responsible for the systems, data, and processes that generate revenue. It owns the analytics layer, attribution models, data pipelines, and the operating cadence that keeps marketing, sales, and finance pointed at the same number.
Think of RevOps as the FP&A of go-to-market: the team that turns siloed activity into a single, auditable view of how revenue is created and where it leaks. It sits underneath the broader discipline of Revenue Intelligence, which is the data and insight layer RevOps operationalises day-to-day.
For online retail brands, RevOps usually starts as one analyst stitching together Shopify, GA4, the ad platforms, and a finance spreadsheet. As the store scales past €1M, that role formalises into a team with clear ownership of the data model, the dashboards leadership trusts, and the experimentation backlog.
The job is less about reporting and more about decisions. A good RevOps function tells you which channels are actually profitable after returns, which segments are worth re-acquiring, and where the funnel is quietly bleeding margin — and it does it without three weeks of cross-team email.
RevOps Efficiency = Net Revenue / Fully-loaded RevOps Cost
Net Revenue
Net revenue
Gross revenue minus refunds, discounts, and returns over the period.
Fully-loaded RevOps Cost
Fully-loaded RevOps cost
Salaries, tooling, and allocated overhead for the RevOps function over the same period.
A Shopify apparel brand doing €6M net revenue runs a two-person RevOps team (salaries + tooling = €240k fully loaded).
Net revenue: €6,000,000
Fully-loaded RevOps cost: €240,000
→ €25 of net revenue per €1 of RevOps spend
A ratio in the €20-€30 range is healthy for a brand at this revenue tier. Below €15 suggests the team is over-built for current scale; above €40 usually means RevOps is under-resourced and decisions are slowing down.
Staffing is the question that comes up most. There's no universal headcount rule, but the ratio of RevOps people to revenue follows a predictable shape across online retail. The table below shows what's typical.
Typical RevOps staffing by revenue tier (online retail)
| Annual revenue | RevOps headcount | Tooling spend / year | Reports to |
|---|---|---|---|
| €1M – €3M | 0.5 – 1 (often shared with finance) | €10k – €25k | Founder / Head of E-comm |
| €3M – €8M | 1 – 2 dedicated | €25k – €60k | Head of E-commerce |
| €8M – €15M | 2 – 4 (analyst + ops lead) | €60k – €120k | VP Growth or CFO |
| €15M+ | 4 – 8 (analytics, ops, systems) | €120k – €300k+ | VP RevOps or COO |
The inflection point is usually €5M. Below it, RevOps is a hat someone wears part-time; above it, the cost of bad data — wrong ad spend, mis-attributed channels, missed restock signals — exceeds the cost of dedicated headcount. That's typically when brands consolidate their GA4 + Hotjar + testing stack into a single source of truth.
Revenue Operations FAQ
Revenue Intelligence is the data and insight layer — the models, signals, and analysis that explain how revenue happens. Revenue Operations is the function that uses that intelligence to run the business: owning the tooling, the pipelines, and the cross-team rhythms.
Usually between €3M and €5M in annual revenue. Before that, a finance-savvy operator or the Head of E-commerce can hold it. After that, the volume of channel data, returns reconciliation, and experimentation backlog typically justifies a dedicated role.
No. Marketing Ops owns the marketing stack (ESP, ad platforms, automation); Sales Ops owns CRM and pipeline. RevOps sits above both and owns the unified revenue picture — including finance reconciliation, which neither traditionally touches.
Analytics (GA4 or a product analytics tool), attribution, the data warehouse if there is one, experimentation tooling, dashboards, and the connectors between Shopify/WooCommerce, the ad platforms, and finance. They're the team that decides what gets consolidated and what gets replaced.
Not as a job title. But the work — clean attribution, accurate margin reporting, a single dashboard leadership trusts — needs an owner from day one. Below €3M that owner is usually the founder or Head of E-commerce wearing the hat part-time.
Typically blended CAC, contribution margin by channel, funnel conversion rate at each step, return rate by segment, and forecast accuracy. The common thread: metrics that span more than one department's tools.
Finance owns the books; RevOps owns the leading indicators that drive them. The healthy pattern is RevOps producing the weekly revenue and channel view, finance reconciling it monthly, and both teams agreeing on the definitions of net revenue, CAC, and contribution margin.
Roughly 0.5%–1% of annual revenue for stores between €1M and €15M. Above that, it tightens to 0.3%–0.6% as fixed-cost tools spread across more volume. Consolidating overlapping tools (separate heatmap, testing, and analytics vendors) is usually the fastest budget win.
Three signals: time-to-answer on a new business question (hours, not weeks), forecast accuracy within ±10% at the monthly level, and zero arguments about which number is right in leadership meetings. If any of those are off, the function isn't operating.
The analytics setup and tooling implementation can be. The ongoing decision-making — what to test next, which channel to cut, how to read a mixed quarter — really shouldn't be. Most brands use agencies to stand RevOps up and then bring it in-house once the systems are stable.
See Metricuno on your data
Bring your stack — Google Analytics, Stripe, a CRM, anything — and we'll walk through the metric tree that turns your funnel into one number.