Average revenue per user (ARPU) measures how much revenue the business generates per user in a period. It is the basic monetization gauge: whether revenue is growing because there are more users or because each user is worth more.
The formula is:
ARPU = total revenue in the period ÷ active users in the period
Stripe states it the same way: divide total revenue by the number of users. For SaaS, use recurring revenue as the numerator and a documented active-user count as the denominator, averaged over the period rather than taken from the last day. Both choices must stay fixed for the trend to mean anything.
ARPU versus ARPA
ARPU counts individual users. ARPA, average revenue per account, runs the same calculation at the account or customer level. In consumer products the two are nearly identical. In B2B SaaS they diverge hard: one enterprise account can hold two thousand seats, so ARPA describes deal economics while ARPU describes per-seat monetization.
Pick the level that matches the decision. Pricing a seat: ARPU. Sizing segments, quotas, and cost to serve: ARPA. Never let one series silently mix both, and label every chart with the level it uses.
A worked example
A SaaS company ends the month with:
- monthly recurring revenue: $600,000;
- average active users during the month: 12,000;
- billed accounts: 1,500.
The calculations are:
ARPU = $600,000 ÷ 12,000 = $50 per user per month
>
ARPA = $600,000 ÷ 1,500 = $400 per account per month
If next month adds a 3,000-seat enterprise deal at a discounted $40 per seat, MRR rises to $720,000 and users to 15,000. ARPA jumps to about $480 while ARPU falls to $48. Nothing broke. The mix changed, and only the driver breakdown shows that. A leader who watches one ratio without the other will misread the quarter in one direction or the other.
Definition pitfalls
- mixing users and accounts across periods or dashboards;
- putting one-time services and overage revenue into a recurring-revenue
metric;
- counting free-tier users in the denominator without saying so, which is a
legitimate blended view but a different metric from paying-user ARPU;
- taking the user count from the period's last day, so late-month churn or a
signup spike distorts the ratio;
- reading blended ARPU across plans where a mix shift toward a cheaper tier
looks like price erosion;
- treating an ARPU increase from churned low-end users as monetization
progress.
Where ARPU fits
ARPU belongs in the Measurement pillar of the Tenbound Pipeline Architecture Standard: a monetization ratio that only becomes actionable with a driver tree under it.
When ARPU moves, decompose the change into pricing changes, plan mix, seat expansion inside existing accounts, and the ARPU of joiners versus leavers. Then connect it forward: ARPU times retained users is the revenue base that net dollar retention measures in motion. A flat ARPU with strong seat growth and a rising ARPU with shrinking accounts tell opposite stories about the same top line.