What Is ARPU? Calculation, the Difference from ARPPU, and How to Read It in SaaS

When measuring the profitability of a SaaS or subscription business, how much revenue each user generates is an essential perspective. The representative metric that expresses this is ARPU.

This article explains the meaning and calculation of ARPU, how it differs from the easily confused ARPPU and ARPA, and concrete ways to interpret and improve it in SaaS.

What Is ARPU?

ARPU (Average Revenue Per User) is a metric that indicates the average revenue generated per user over a given period.

Looking at total revenue alone, you cannot tell whether it comes from "a few high-value users" or "many low-value users." By looking at ARPU, you can grasp the revenue's "unit-price structure" and the efficiency of your pricing and monetization. Calculate it over a period that fits the nature of your business—monthly, quarterly, or annually.

How to Calculate ARPU

ARPU = total revenue for the period ÷ number of users for the period

For SaaS, when viewing it monthly, it is common to calculate "MRR (monthly recurring revenue) ÷ number of users." For example, if monthly total revenue is $50,000 and there are 2,500 users, ARPU is 50,000 ÷ 2,500 = $20.

What matters here is who you include in the "number of users." Whether you include free-plan users or calculate using only paying users greatly changes the meaning of the number. In a freemium model, note that including free users significantly dilutes ARPU. This point leads into the difference from ARPPU, explained next.

Differences from ARPPU and ARPA

Two metrics often confused with ARPU are ARPPU and ARPA. Each differs in "who is in the denominator."

• ARPU (per user): divides total revenue by all users, including free users. Represents the monetization efficiency of the entire user base.
• ARPPU (per paying user): Average Revenue Per Paying User. Divides by paying users only. Represents the value of one customer who actually pays.
• ARPA (per account): Average Revenue Per Account. Divides by "contract account" rather than individual user. Effective for B2B SaaS where one account has multiple users.

Let's think through a concrete example. Suppose there is a freemium SaaS with 10,000 free users and 1,000 paying users, generating $100,000 in monthly revenue.

• ARPU: 100,000 ÷ 11,000 ≈ about $9.09
• ARPPU: 100,000 ÷ 1,000 = $100

As you can see, in freemium models free users heavily dilute ARPU, so when you want to see the reality of paying customers, ARPPU is more appropriate. On the other hand, in B2B SaaS where multiple users share one contract, account-based ARPA more accurately reflects the revenue structure.

How to Interpret ARPU in SaaS

ARPU is an "absolute amount" metric, not a ratio. As a result, there is no universal industry benchmark, and it varies greatly by target customer segment, pricing model, and region. Rather than comparing simply with other companies, it is best used for your own internal trend or comparison with similar business models.

Recent research reports large differences by customer segment, such as the following (B2B SaaS, monthly estimates).

• Self-serve (individuals/small teams): around $20–50/month. A model that works through low friction and high-volume acquisition.
• SMB: around $50/month.
• Enterprise: can exceed $5,000/month.

What is important in interpreting it is to combine ARPU with other metrics rather than viewing it alone.

1. Look at the Trend

If ARPU is rising, it is a sign that upselling, cross-selling, or price changes are working, or that the proportion of high-value customers is increasing. Conversely, if it is falling, suspect a skew toward low-price plans or chronic discounting. The direction over time provides more insight than a single month's value.

2. View Alongside Churn and LTV

ARPU is a foundational input for LTV (lifetime value). In general, high-ARPU customers tend to churn less and contribute to revenue stability. By tracking changes in ARPU together with churn rate and LTV, you can verify health—for example, whether raising prices has increased cancellations.

3. Break It Down by Segment

Because overall ARPU is an average, the breakdown is invisible. Breaking it down by plan, customer size, and acquisition channel clarifies which segments drive revenue and where there is room to raise unit price. This becomes the starting point for upsell initiatives and pricing design.

How to Increase ARPU

• Upsell and cross-sell: raise revenue per existing customer by proposing higher-tier plans and additional features or options.
• Review pricing and plan design: design tiered pricing plans (tiering) that match the value delivered.
• Focus on high-ARPU segments: build a path to move customers acquired in SMB up to higher-tier plans as they grow.
• Convert free to paid: in freemium, raising the free-to-paid conversion rate lifts overall ARPU.

Conclusion

ARPU shows the average revenue per user and is a fundamental metric for grasping monetization efficiency and unit-price structure. However, because free users dilute it in freemium models, it is important to use it appropriately alongside ARPPU, which looks at paying customers, and ARPA, which looks at the account level.

Because ARPU is an absolute-amount metric, interpret it not through simple comparison with other companies, but in combination with your own trend, churn, LTV, and the breakdown by segment. By connecting that to improving upsells and pricing design, ARPU becomes a guide for sustainable revenue growth.