Startups & Business › Metrics & Unit Economics
ARPU
Average revenue per user or account.
Also known as: ARPU, average revenue per user, ARPA
ARPU (average revenue per user/account) is total revenue divided by users: the single number summarizing monetization intensity. Rising ARPU means expansion, upsell and mix shift working; flat ARPU with user growth means adding low-value users; falling ARPU means discounting, downmarket drift or mix decay — each a different strategy conversation.
$100k MRR ÷ 2,000 accounts = $50 ARPU
move it via: mix (more enterprise), expansion (upsell seats/features), pricing (better packaging)
Always segment it: overall ARPU blends enterprise whales with free-tier plankton into meaninglessness. Per-segment ARPU trends reveal which motions monetize and which merely populate — the pricing and product decisions follow those splits, never the average.
The classic mistakes:
- Chasing ARPU by shedding small users. Firing the long tail flatters ARPU while destroying volume, network effects and future expansion base. Grow ARPU per segment; compare segments honestly instead.
- Confusing ARPU with pricing power. Rising ARPU from mix shift (more enterprise deals) differs totally from same-segment price rises. Decompose: price vs mix vs expansion, separately.
- Vanity ARPU on tiny bases. $500 ARPU across eleven design partners predicts nothing. ARPU needs scale to mean anything — report N beside every average.
- Ignoring ARPA vs ARPU. Per-account vs per-user diverge wildly in team products (one account, fifty users). Track the unit matching how value and expansion actually flow.
- Optimizing ARPU over LTV. Price hikes lifting ARPU while accelerating churn destroy lifetime value. Pair ARPU with retention always (LTV).
Trend it per segment monthly, decompose moves into price/mix/expansion, and let it guide packaging — ARPU is the monetization pulse, segmented or meaningless.