Revenue Operations
Revenue Operations is the function that owns the revenue-generating stack end-to-end: analytics, attribution, pipelines, and the alignment between marketing, sales, and finance.
Revenue Operations
The org function that owns the end-to-end revenue stack — data, tooling, attribution, and cross-team alignment.
Revenue Operations (RevOps) is the centralised function responsible for the systems, data, and processes that generate revenue. It owns the analytics layer (GA4, warehouse, BI), the attribution model, the martech and salestech stack, and the operating cadence that keeps marketing, sales, customer success, and finance pointed at the same number.
Think of RevOps as the connective tissue between the teams that spend money to acquire customers and the teams that count what those customers are worth. Where FP&A reports on the past, RevOps instruments the present and makes the next quarter operationally possible.
RevOps emerged because the old split — marketing ops, sales ops, customer success ops — produced three teams with three definitions of a qualified lead, three attribution models, and three dashboards that never reconciled. Consolidating them under one function gives the business a single source of truth for pipeline, conversion, and retention.
In an online retail context, the scope is narrower but the principle is identical: one team owns the tracking plan, the GA4 build, the warehouse models, the paid-media attribution, and the experimentation programme. When your performance manager and your finance lead disagree about what CAC was last month, RevOps is the function that makes them agree — or explains why they shouldn't.
Revenue = Traffic × Conversion Rate × AOV × (1 + Repeat Rate)
Traffic
Sessions
Sessions across all channels in the period.
Conversion Rate
CVR
Share of sessions that result in a paid order.
AOV
Average Order Value
Net revenue per order after discounts, before tax and shipping.
Repeat Rate
Repeat-purchase uplift
Additional orders per first order from the same customer in the period.
A Shopify apparel store reviewing Q3 performance with its RevOps lead.
Sessions: 1200000
Conversion rate: 2.1%
AOV: €78
Repeat-purchase uplift: 0.35
→ €2.65M quarterly revenue
RevOps owns each of these four levers as data: it instruments traffic quality, audits the CVR funnel, segments AOV by SKU mix, and models repeat behaviour from cohort exports. The job isn't to move the levers — that's marketing, merch, and CRM — it's to make sure everyone sees the same numbers when they try.
RevOps is the operational layer beneath Revenue Intelligence — the broader discipline of turning customer and pipeline data into decisions. Intelligence is the output; operations is the plumbing that makes the output trustworthy. Without RevOps, your intelligence is just a dashboard nobody believes.
Typical RevOps scope and staffing by online-retail revenue band
| Revenue band | RevOps headcount | Primary scope | Reporting line |
|---|---|---|---|
| €1-3M | 0.5 FTE (shared) | Tracking plan, GA4, weekly KPI report | Head of E-commerce |
| €3-8M | 1 FTE | Attribution, warehouse, experimentation ops | Head of E-commerce / COO |
| €8-15M | 2-3 FTE | Data pipelines, BI, forecasting, martech admin | VP Growth or CFO |
| €15M+ | 4+ FTE team | Full revenue stack, finance integration, M&A data | Dedicated VP RevOps |
The inflection point for most online retailers sits around €5M revenue: that's when a fractional or shared analyst stops being enough, and an unowned tracking plan starts costing real money in mis-attributed spend. Hiring earlier is rarely wasted; hiring later usually means a six-month clean-up project before the new hire can produce a number anyone trusts.
Revenue Operations FAQ
Revenue Intelligence is the analytical output — the insights, forecasts, and recommendations derived from revenue data. Revenue Operations is the function that builds and maintains the systems producing that data. Intelligence is what you read; operations is what makes the reading possible.
Sales Ops is a subset focused on the sales team — CRM hygiene, quotas, territory design, commission plans. RevOps spans the whole revenue funnel: marketing, sales, customer success, and the data layer underneath all three. Most modern orgs have folded sales ops into RevOps.
It's relevant for any business with more than one revenue-touching team and more than one data source. In e-commerce the scope leans heavier on web analytics, attribution, and CRM than on pipeline management, but the consolidation problem is the same — three teams, three definitions of CAC, one P&L.
Most online retailers feel the pain around €3-5M revenue, when GA4, the ad platforms, Klaviyo, and the Shopify back office all tell different stories about the same week. The first hire is usually a senior analyst who owns the tracking plan and the weekly KPI pack.
Usually yes — at minimum the analytics, attribution, tag management, and experimentation tools. Email and ad platforms are typically administered by the team that uses them daily, with RevOps owning the data contract: what events fire, how identifiers flow, and how the warehouse reconciles it.
A warehouse (BigQuery, Snowflake), a BI layer (Looker, Metabase), a tag manager (GTM), an analytics platform (GA4 or a privacy-first alternative), an experimentation tool, and a CDP or reverse-ETL. The exact stack matters less than having one team accountable for it.
Reporting line varies by company stage. Below €10M it usually sits under the Head of E-commerce or COO. Above that it commonly reports to a VP Growth, CFO, or a dedicated VP RevOps. The key is that it doesn't sit inside marketing — that compromises the function's independence on attribution.
Indirect metrics: data freshness and accuracy, time-to-answer on ad-hoc questions, forecast variance vs actuals, experiment velocity, and stack cost as a percentage of revenue. RevOps doesn't own a revenue number directly — it owns the infrastructure that lets other teams hit theirs.
FP&A owns the financial planning view; RevOps owns the operational data feeding it. The two work closely on forecasting — RevOps provides the leading indicators (sessions, CVR, pipeline) and FP&A models the financial outcome. In smaller orgs the roles can blur, but separating them above €10M revenue is best practice.
Partially. Implementation work — GA4 builds, warehouse setup, attribution modelling — is regularly handled by specialist agencies. The ongoing operating cadence (weekly KPI reviews, ad-hoc analysis, stakeholder alignment) is hard to outsource well because it requires constant context on what the business is trying to do this quarter.
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.