What is ARPU?
ARPU — Average Revenue Per User — is the average amount of revenue generated per user or account in a given period. It is one of the most frequently referenced metrics in SaaS finance because it connects two of the most important dimensions of the business: how many customers you have (scale) and how much each one pays (monetization efficiency). Changes in ARPU reflect pricing power, customer mix, upsell success, and competitive dynamics all at once.
ARPU has two common variants depending on what you are measuring. User-level ARPU divides revenue by the total number of individual users or seats. Account-level ARPU (sometimes called ARPA — Average Revenue Per Account) divides revenue by the number of paying accounts or organizations. The distinction matters for multi-seat B2B products: a company with 50 accounts averaging 20 seats each has very different user-level and account-level ARPU. For financial modeling and SaaS benchmarking, account-level ARPU is typically more useful because it reflects the economic unit of the customer relationship.
ARPU sits at the center of the SaaS financial model. It is the key input to MRR (ARPU × number of users), to LTV (ARPU × gross margin / churn rate), and to CAC payback period. A 20% increase in ARPU has the same effect on LTV as a 20% reduction in churn, which is why pricing optimization can be one of the highest-return investments a SaaS company makes. Unlike acquiring more users, raising ARPU improves revenue without increasing the customer base, which means unit economics improve immediately.
The formula
ARPU = Total Revenue / Number of Users- Total revenue — the subscription revenue received or recognized in the period. For most SaaS businesses this means MRR-based recurring revenue. Exclude one-time professional services fees, setup charges, and any non-recurring items that distort the recurring revenue picture. If you want an ARPU that reflects true recurring economics, use MRR as the numerator.
- Number of users — typically the average user count over the period rather than the beginning or ending count. Using a simple average of start-period and end-period users accounts for growth within the period and produces a more representative result.
Monthly vs. annual ARPU: Either works, but most SaaS benchmarking uses monthly ARPU because it aligns with the MRR framework. Annual ARPU (divide annual revenue by average annual user count) is useful for comparing against annual contract value benchmarks. Whatever cadence you use, keep it consistent across comparisons.
Edge case: If the number of users is zero — for example, before launch or after a complete churn event — ARPU is mathematically undefined. The calculator displays ”—” in this case rather than attempting to divide by zero.
Worked example
Default inputs: Total revenue = $50,000, Number of users = 500.
$50,000 / 500 = $100 ARPUAt $100 ARPU, the business has a clearly mid-market pricing position. With 500 users, MRR is $50,000 — or $600,000 in ARR.
What changes if the sales team begins closing larger accounts, shifting the mix from 500 users at $100 ARPU to 400 users at $130 ARPU? Total revenue becomes $52,000 — actually higher — while the user count drops. The revenue-per-user efficiency has improved by 30%, even though absolute user count declined. This is a positive development: higher ARPU with stable or growing revenue is better than lower ARPU with a larger, less valuable base.
What changes if a freemium tier is launched, adding 200 users who pay nothing? If these users are included in the user count, ARPU drops to $50,000 / 700 = $71.43. Whether this is alarming or acceptable depends entirely on the conversion strategy: if 10% of freemium users convert to paid within 90 days, the cohort-level economics may justify the ARPU dilution.
Benchmarks
ARPU benchmarks vary enormously by market segment and product type:
- Consumer subscription apps (streaming, fitness, personal productivity): ARPU of $5–$20 per month. Margins need to be very high to generate acceptable LTV at this level.
- SMB SaaS (project management, accounting, email): ARPU of $20–$200 per month. This range is dominated by self-serve and product-led growth businesses.
- Mid-market SaaS: ARPU of $200–$2,000 per month. Requires some sales assistance and more complex onboarding; common in HR tech, marketing automation, and vertical software.
- Enterprise SaaS: ARPU of $2,000–$20,000+ per month. High-touch sales motion, complex procurement, but very high LTV justifies the investment.
- Marketplace / usage-based: ARPU is highly variable and grows with the customer’s usage. Median ARPU may be low while top-decile accounts drive the majority of revenue.
For companies using usage-based pricing, ARPU is a lagging indicator of expansion; tracking month-over-month ARPU change by cohort reveals whether customers are expanding their usage, which is a leading indicator of net revenue retention.
How to interpret and improve it
ARPU improvement is the highest-leverage pricing action available to a SaaS company because it affects every derived metric simultaneously: MRR, ARR, LTV, and CAC payback period all improve proportionally with ARPU.
The most direct lever is pricing optimization. Most early-stage SaaS companies are underpriced — founders set initial prices based on competitive anchoring or anxiety about churn rather than willingness-to-pay research. Running structured pricing experiments (A/B testing plan prices, testing annual vs. monthly billing, introducing a higher enterprise tier) routinely surfaces 20–50% ARPU upside that was already achievable with the existing customer base.
The second lever is mix shift: moving customers from lower-tier to higher-tier plans through proactive upsell and expansion motions. Tracking ARPU by cohort and by plan tier reveals whether the customer base is expanding or contracting in value, which is a more sensitive signal than aggregate ARPU.
Common mistakes: Including free users in the denominator when calculating paid ARPU will understate the true revenue per paying user. Maintain separate ARPU metrics for paid and total users when a freemium tier exists.
When the metric misleads: A rising ARPU can mask a shrinking user base if higher-value customers are retained while lower-value customers churn. Track ARPU alongside user count and net revenue retention to ensure the trend reflects true business improvement rather than involuntary customer mix change.
Frequently asked questions
What is ARPU? Average Revenue Per User is total revenue in a period divided by the number of users or accounts.
Should ARPU be monthly or annual? Either works as long as you are consistent; monthly ARPU is most common for SaaS.