Average revenue per user (ARPU) is total revenue divided by the number of active users over a specific period. It measures how much revenue each customer generates on average, and is used to price subscription products, forecast growth, and compare the value of one segment against another.
ARPU is the number every subscription business ends up living by. It tells you whether your pricing works, whether new segments pull their weight, and whether product-led growth is quietly draining revenue per seat. Get it right and you can forecast revenue years out; get it wrong and you build strategy on averages that hide the truth.
What is Average Revenue Per User (ARPU)?
ARPU is a per-customer revenue average. Take the revenue you booked in a period, divide by the number of active users in the same period, and the result is the amount an average user contributed. Telecom operators popularised the metric in the 1990s, and it was adopted by streaming, gaming, and SaaS as recurring-revenue models spread.
The calculation is deceptively simple. The rigor comes from four decisions you make up front:
- Which revenue? Subscription only, or subscription plus usage plus services?
- Which users? All accounts, paying accounts only, or monthly active users?
- Which period? Monthly ARPU differs from annual ARPU by a factor of 12, so consistency matters.
- Which segment? Blended ARPU hides the story that segmented ARPU reveals.
Investors and boards typically look at monthly ARPU for consumer subscription products and annual contract value (ACV) for enterprise SaaS. Both are ARPU under different names — the math is identical, only the denominator and time window change.
Why ARPU matters
ARPU is the pivot metric between acquisition and monetization. Every growth lever you pull eventually shows up here. There are four reasons operators watch it week after week:
- Pricing signal. Rising ARPU means the market accepts your value; flat ARPU with rising churn means you priced past what customers will pay.
- Segment quality. If enterprise ARPU is 40x SMB ARPU but SMB drives 80% of headcount, you know where the go-to-market focus should sit.
- Forecast accuracy. Revenue forecasts break when growth teams pull customers with radically different ARPU into the pipeline without adjusting the model.
- LTV feed. Lifetime value calculations use ARPU as an input. Wrong ARPU, wrong LTV, wrong CAC target — the whole unit economics stack tips over.
How ARPU works
The math is straightforward. The interpretation is not. ARPU only tells you what a user is worth this period; pair it with customer lifetime value to see what they are worth over the whole relationship.
Monthly ARPU = Total Revenue for the Month ÷ Active Users at Month End
# Example: SaaS product
Revenue: $240,000 in June 2026
Active users: 3,200 paying accounts
Monthly ARPU = 240,000 ÷ 3,200 = $75.00
Calculation variations
Different teams reasonably compute ARPU differently. Pick one, document it, and stay consistent:
- Blended ARPU — all revenue over all users, including free and trial accounts. Useful for consumer freemium products.
- Paying ARPU (ARPPU) — revenue divided by paying users only. Cleaner signal for pure subscription products.
- New-customer ARPU — revenue from customers acquired this period divided by their count. Best proxy for current pricing power.
Segmented ARPU
Blended ARPU is often misleading. Segment by plan tier, industry, region, or acquisition channel and you will find one segment is doing almost all the work. For a typical B2B SaaS the top 20% of customers drive 60 to 70% of revenue — and their ARPU dwarfs the average. A cohort view exposes that split faster than any blended chart. Reporting only the blended number hides that concentration.
ARPU expansion levers
Growth teams have four levers to move ARPU without acquiring a single new logo, and each one is undone by churn if retention slips:
- Move users to higher tiers as their usage grows
- Sell usage-based add-ons that expand with customer success
- Cross-sell adjacent products from the same account manager
- Retire discounts and grandfathered pricing as customers renew
Types of ARPU and when to use each
| Metric | Denominator | Best for | Watch out for |
|---|---|---|---|
| Monthly ARPU | All active users, monthly | Most SaaS & subscription businesses | Seasonal skew — smooth with a 3-month average |
| ARPPU | Paying users only | Freemium and trial-heavy products | Hides free-to-paid conversion problems |
| ARPU (annual) | Active users, annual | Enterprise SaaS with annual contracts | Comparable to ACV; keep the labelling clear |
| Segment ARPU | Users inside one plan/region | Prioritizing GTM investment | Small sample sizes for niche segments |
| Cohort ARPU | Users acquired in a single period | Judging pricing changes over time | Takes months of data to be meaningful |
Real ARPU examples
Three worked examples across product categories:
1. Consumer streaming service
Paying subscribers: 15M
Quarterly ARPU = 180M ÷ 15M = $12.00
# Monthly ARPU equivalent = $4.00
2. B2B SaaS with two plan tiers
Pro plan: 400 accounts × $249 = $99,600
Blended monthly ARPU = 157,600 ÷ 2,400 = $65.67
# Starter ARPU: $29 · Pro ARPU: $249 — segment view tells the story
3. Freemium mobile app
Revenue: $800,000 in June 2026
Blended ARPU = 800,000 ÷ 2,000,000 = $0.40
ARPPU = 800,000 ÷ 100,000 paying users = $8.00
ARPU vs ARPPU — which to use
Both measure revenue per user, but they answer different questions.
Use ARPU when
- The whole user base is monetizable (paid-only product)
- You want a single number board-ready
- You are forecasting total revenue from user growth
- You need consistency with LTV models
- The product has no free tier
Use ARPPU when
- You run a freemium or trial-heavy product
- You are pricing an upgrade or new tier
- You are comparing paid-user quality across cohorts
- You want the free-to-paid conversion rate to move separately
- Consumer or mobile apps with big free tiers
6 best practices for tracking ARPU
- Document the formula. Write down which revenue lines go in the numerator and which users go in the denominator. Every finance team has a story about ARPU shifting by 20% when the definition quietly changed.
- Report blended and segmented. The blended number is easy to socialise; the segmented view is where decisions happen. Show both on the dashboard.
- Tie ARPU to CAC and churn. ARPU alone is a vanity metric. Pair it with CAC and gross churn to get true unit economics.
- Track ARPU on new cohorts. New-customer ARPU is the fastest signal that pricing power is rising or falling.
- Watch for mix shifts. If ARPU drops, check whether pricing changed or whether the mix of new customers changed toward a cheaper segment.
- Grow ARPU before you raise prices. Expansion revenue is cheaper to earn than a price hike is to defend.
Blended ARPU can look flat while every underlying segment is growing. That happens when the mix shifts toward cheaper plans. Always check ARPU by segment before declaring pricing is broken; the average may be lying.
Common ARPU mistakes to avoid
- Mixing revenue types. One-off implementation fees and recurring subscription revenue produce different ARPU numbers if you blend them.
- Comparing across companies. A $12 consumer ARPU and a $12,000 enterprise ARPU are both healthy — the number only means something relative to your own history.
- Ignoring cohort effects. Legacy grandfathered pricing can drag ARPU down for years even as new-cohort ARPU climbs.
- Confusing ARPU and LTV. ARPU is a single-period metric; LTV is ARPU multiplied by expected customer lifetime and margin.
- Reporting weekly ARPU. The signal is too noisy for weekly reads; monthly is the minimum useful cadence.
Frequently asked questions
It depends on segment. SMB SaaS typically sees $10 to $50 ARPU per month, mid-market lands at $200 to $1,500, and enterprise SaaS often exceeds $2,500. Compare against your segment cohort, not a global benchmark.
Focus on expansion revenue: package usage-based add-ons, upsell to higher tiers when usage crosses a threshold, and cross-sell adjacent products. Improving the mix of paid seats vs free seats often moves ARPU faster than a price hike.
Early-stage teams should chase user growth to validate demand. Once retention is proven, shift toward ARPU expansion because it compounds without the acquisition cost of new logos.
ARPU divides revenue by all users, including free ones. ARPPU divides revenue by paying users only. ARPPU is more useful when a freemium or trial funnel dilutes the ARPU number.
Monthly for subscription products, quarterly for enterprise. Weekly ARPU is noisy for most businesses because it does not reflect the billing cycle.
Related glossary terms
Sources
- [01]Investopedia — Average Revenue Per User (ARPU) definition
- [02]Klipfolio — ARPU as a SaaS KPI
- [03]ProfitWell — What is ARPU and how to calculate it
- [04]Chargebee — ARPU glossary and expansion strategies
- [05]Internal benchmark: 40+ SaaS ARPU audits across seed to Series C, 2024–2026
