Average Revenue Per User condenses pricing strategy, customer mix and packaging into a single number. A Zurich SaaS with CHF 50,000 MRR and 200 customers has CHF 250 ARPU. Doubling ARPU through better packaging is the single most powerful lever in SaaS — it moves valuation 2× without requiring any new customer acquisition.
ARPU is computed monthly or annually. Monthly ARPU = MRR / Customers. Annual ARPU = ARR / Customers. They are interchangeable but the monthly version reacts faster to mix changes. Most European boards review monthly ARPU and annual ARPA (Average Revenue Per Account) side by side, where the account version handles multi-seat enterprise contracts.
ARPU trends matter more than absolute level. A rising ARPU signals successful upmarket motion, packaging changes or pricing power; a falling ARPU usually signals SMB-heavy new acquisition or discounting drift. The direction is the leading indicator; the level is the lagging one.
Monthly ARPU = MRR ÷ Total Customers Annual ARPU = ARR ÷ Total Customers
Example: A Marseille SaaS has EUR 180,000 MRR across 600 customers. Monthly ARPU = 180,000 / 600 = EUR 300. After a packaging change that upsells 100 customers from Pro (EUR 200/mo) to Business (EUR 500/mo), MRR rises to EUR 210,000 with the same 600 customers. New ARPU = EUR 350 — a 17% lift without any new logos.
Average Revenue Per User: The Complete Definition
ARPU divides recurring revenue by the customer count for a single period. It excludes one-off implementation fees, professional services and usage overages — exactly the same boundary as MRR. The customer count should match the definition used in the rest of the metrics stack (active paying customers as of the period end).
Two important variants exist. ARPU (per user/customer/account) divides by logo count. ARPPU (per paying user) is more relevant for freemium and consumer products where the user base is much larger than the paying base. For B2B SaaS, ARPU and ARPPU are usually equivalent because there is no free tier.
How to Calculate ARPU: Formula and Example
Period boundaries matter. Take MRR and customer count at the same point in time (typically the last day of the month). Avoid averaging customer count over the period — it produces a smoother but less interpretable number.
Worked example for an enterprise-mix SaaS: a Vienna company has 300 SMB customers paying EUR 99/mo (EUR 29,700 MRR), 50 mid-market customers at EUR 800/mo (EUR 40,000 MRR) and 5 enterprise at EUR 5,000/mo (EUR 25,000 MRR). Total MRR = EUR 94,700; total customers = 355; ARPU = EUR 267. The blended ARPU hides that enterprise drives 26% of revenue from 1.4% of customers — always segment ARPU by tier.
ARPU in Switzerland, Germany, France and Italy
ARPU benchmarks reflect pricing tolerance more than country. Swiss B2B SaaS typically commands 20–40% higher ARPU than French peers for the same product because Swiss buyer willingness-to-pay is higher and CHF prices stick. German SaaS sits between Swiss and French; Italian tends to the lower end except in regulated verticals (legal, accounting) where price tolerance is high.
Sales-led motions deliver higher ARPU than product-led across all four countries — typically 3–5× higher because sales teams can capture value-based pricing and packaging optimisation that self-serve buyers won't pay for. The choice of motion is therefore as much an ARPU decision as a CAC decision.
Why ARPU Matters
ARPU is the most direct lever on unit economics. A 20% lift in ARPU (achievable through packaging changes in 2–4 quarters) translates 1:1 into a 20% lift in CLV and a 20% reduction in CAC payback — without touching the sales engine. No other single metric has the same compounding effect.
Strategically, ARPU trajectory reveals the company's positioning. Rising ARPU = moving upmarket, capturing more value, healthier mix. Flat ARPU = stable positioning. Falling ARPU = discounting drift or SMB acquisition outpacing enterprise. Use the MyEuroCalculator MRR Calculator to project ARPU lift scenarios on the 12-month plan.
ARPU vs ARPA: Key Differences
ARPU (Average Revenue Per User) divides by individual users; ARPA (Average Revenue Per Account) divides by accounts. For multi-seat B2B SaaS where one account has many users, ARPA is usually 2–10× ARPU. Public European SaaS reports both because investors want to see seat-level and account-level efficiency separately.
Typical ARPU by segment (European SaaS, 2026)
| Segment | Monthly ARPU | Annual ARPU | Typical packaging |
|---|---|---|---|
| SMB self-serve | EUR 30–250 | EUR 360–3,000 | Per-user tiered |
| Mid-market | EUR 500–2,500 | EUR 6,000–30,000 | Seat-based with usage |
| Enterprise | EUR 4,000–15,000 | EUR 48,000–180,000 | Custom + modules |
Common mistakes
Including one-off implementation fees in MRR-based ARPU produces a misleading spike on contract signing.
A blended ARPU hides whether enterprise or SMB is driving the average. Always split by tier in board reporting.
Use point-in-time MRR and customer count, not period averages — the latter is smoother but harder to reconcile to the MRR walk.
Deal size is the upfront contract value (often annual); ARPU is the monthly normalised value. The ratio between them tells you about billing cadence.