Skip to main content
Back to KPI Library
SaaS

What is Average Revenue Per User?

Average revenue generated per user or account.

How to calculate it

Calculate Average Revenue Per User as: Total revenue / Number of users (or accounts). Pull the inputs from your connected data and track the trend over time in your dashboard.

Examples

Example 1

$20,000 MRR / 200 users = $100 ARPU.

Example 2

$30,000 MRR across 250 accounts -> $120 ARPU. After launching a premium tier, ARPU rises to $145 as a fifth of accounts upgrade.

Why it matters

Average revenue per user (ARPU) is the average revenue generated per user or account and tracks monetization and pricing effectiveness over time. Rising ARPU signals successful upsell, better packaging or a shift toward higher-value customers. Mixing user-level and account-level definitions makes the figure inconsistent and hard to trend.

Benchmark context

There is no universal target; watch the trend, expecting ARPU to rise as tier mix improves and upsell motions mature.

Common pitfalls

Mixing user-level and account-level ARPU.

The complete guide

Understanding Average Revenue Per User

Average revenue per user (ARPU) is the average revenue generated per user or account and tracks monetization and pricing effectiveness over time. Rising ARPU signals successful upsell, better packaging or a shift toward higher-value customers. Mixing user-level and account-level definitions makes the figure inconsistent and hard to trend. For context, there is no universal target; watch the trend, expecting ARPU to rise as tier mix improves and upsell motions mature. Treat an external benchmark as a reference point rather than a universal target: company stage, sector, customer mix, pricing model and measurement definitions can materially change what “good” looks like. Read Average Revenue Per User alongside MRR, Expansion MRR and LTV; together these measures provide a more balanced view and reduce the risk of optimizing one number at the expense of the wider outcome.

Make sure the numerator and denominator cover compatible populations and periods, and avoid dividing by a partial or unusually small base. Use a consistent customer and recurring-revenue definition, and separate new, expansion, contraction, reactivation and churn movements. Use customer cohorts and separate new, expansion, contraction and churn movements so that acquisition growth does not obscure the economics of the installed base. A dashboard should show the current value, prior-period comparison and a trend rather than presenting one isolated reading.

Improvement normally comes from a combination of faster activation, stronger adoption, pricing and packaging discipline, expansion motions, and earlier intervention when customer behavior signals churn risk. Common pitfalls: mixing user-level and account-level ARPU. Record the definition beside the dashboard, review it when systems or processes change, and annotate unusual events so future readers can distinguish a genuine performance shift from a data or timing effect.

Sources and further reading

  1. Essential SaaS metrics

    Stripe Accessed

  2. Important SaaS KPIs to track

    Paddle Accessed

Related KPI guides

Turn KPI definitions into governed dashboards

Metricwise helps teams define metrics once, reuse them across dashboards, and ask trusted business questions in plain English.

Get Started