Quick answer
Understand the difference between ARPU and ARPA for SaaS, including formulas, examples and when each metric is more useful.
Core formulas
ARPU = MRR / active users
Useful when each user has a similar monetization relationship.ARPA = MRR / active accounts
Useful when accounts can include multiple seats, teams or workspaces.Seats per account = active users / active accounts
Seat density explains why ARPU and ARPA can diverge.Worked example
ARPU and ARPA example
- A SaaS product has $18,600 MRR.
- It has 120 paying accounts.
- Those accounts include 620 active paid users.
The practical difference
ARPU is useful when the user is the economic unit. ARPA is useful when the account is the economic unit. Many SaaS products sell to teams, departments or businesses, so revenue is better understood per account even if many users sit inside that account.
Using the wrong metric can distort pricing. A team product may look cheap on ARPU and healthy on ARPA. A consumer product may not need ARPA at all.
When to use ARPA
Use ARPA when customers buy plans, seats or usage under one billing account. ARPA connects more directly to sales motion, expansion, account health and customer success workload.
- B2B SaaS with teams or workspaces.
- Products with seat expansion or account-level add-ons.
- Revenue forecasts based on customers rather than individual users.
When to use ARPU
Use ARPU when each user pays independently or when user-level monetization is the clearest unit. Consumer subscriptions, media products and creator tools often fit this pattern.
Use the calculators
FAQ
Is ARPA the same as average contract value?
No. ARPA is usually a recurring revenue average per account for a period. Contract value can include contract length, one-time fees and multi-year commitments.
Should free users be included in ARPU?
Only if you are intentionally calculating revenue per total active user. For paid unit economics, use paid users or paid accounts consistently.
Which metric should I put into a SaaS revenue calculator?
Use ARPA when the calculator asks for average revenue per account. Use ARPU when the model is explicitly user-based.