SaaS ARPU: formula, worked example and ARPA comparison
Calculate SaaS ARPU from MRR and paying subscribers. Distinguish users, accounts and annual billing to compare recurring revenue consistently.
ARPU means average revenue per user over a defined period. For a subscription SaaS business, a common definition is MRR divided by active paying subscribers. State the unit: a business account with ten seats is not necessarily ten paying customers.
Formula and example
With €24,000 in MRR and 200 paying subscribers, monthly ARPU is €120. Measure revenue and subscribers at the same point in time, with compatible inclusion rules.
| Illustrative plan | Paying accounts | MRR per account | Total MRR |
|---|---|---|---|
| Basic | 150 | €80 | €12,000 |
| Pro | 50 | €240 | €12,000 |
| Total | 200 | €120 average | €24,000 |
A simple average of plan prices would produce €160. That ignores how many customers are on each plan and misrepresents this business.
ARPU versus ARPA
ARPA is average revenue per account. It can be a clearer label for B2B products that bill companies. If the 200 accounts above contain 1,000 users, revenue per user is €24 while revenue per account is €120. Neither denominator is interchangeable with the other.
Normalize annual billing
A €1,200 annual subscription contributes €100 to monthly recurring revenue before the adjustments in your metric policy. Do not put the full annual cash collection into a monthly ARPU numerator. Keep invoicing, recognized revenue, MRR and cash received separate.
Stripe’s ARPU definition uses MRR divided by active subscribers. Check discount and subscription-status rules when reconciling your own calculation to its dashboard.
Read ARPU alongside retention
ARPU can rise because of expansion, price changes or the loss of smaller customers. In the last case, it may rise while total MRR falls. Inspect new business, churn and customer cohorts before concluding that monetization improved.
Segment by plan or acquisition cohort using consistent rules. If there are no eligible subscribers, mark the ratio as undefined rather than treating zero as a comparable observation.
A SaaS metrics view and a recurring report should preserve the numerator, denominator and definition, so the team can explain changes rather than simply read a number.