Average revenue per user

Average revenue per user (ARPU) divides total revenue by the number of active users or accounts in a given period. In SaaS, it is typically calculated monthly (monthly ARPU) or annually, and it represents the average monetisation level across the customer base.

ARPU is a bridge metric. It connects volume metrics like total users to revenue metrics like MRR and ARR. If you know your number of customers and your ARPU, you can calculate MRR directly: MRR equals customers multiplied by ARPU. This makes ARPU a powerful lever for growth because even small increases in ARPU, compounded across thousands of customers, create significant revenue impact.

ARPU also serves as a proxy for value delivery. Customers pay based on the value they receive. Rising ARPU suggests customers are finding more value in the product (upgrading, adding seats, using more features). Declining ARPU may signal that new customers are smaller, that existing customers are downgrading, or that pricing has not kept pace with the value delivered. Tracking expansion revenue alongside ARPU helps distinguish between growth and mix effects.

The basic ARPU formula divides total revenue for a period by the number of active users during that period. However, the definition of both "revenue" and "users" requires careful consideration.

For revenue, decide whether to include only recurring subscription revenue or also one-time and usage-based charges. Most SaaS companies calculate ARPU using recurring revenue only to maintain consistency with MRR and ARR definitions.

For users, decide whether to count all active users at month-end, the average number of users during the month, or only paying users (excluding free-tier and trial users). The choice affects the result significantly, especially for freemium businesses where free users can dilute ARPU dramatically.

The most useful approach for SaaS is to calculate paying ARPU: total MRR divided by the number of paying customers. This gives a clean measure of monetisation among converted customers and avoids the distortion caused by large free-user bases.

ARPU decomposes naturally in a metric tree because it sits at the intersection of pricing, packaging, and customer mix. The tree reveals the levers you can pull to increase average revenue without necessarily acquiring more customers.

The first-level decomposition splits ARPU by plan tier or customer segment. This immediately reveals whether ARPU changes are driven by mix shifts (more customers on lower-priced plans) or by actual monetisation changes within a tier (customers adding seats or features). The second level decomposes each segment further into base price, add-on revenue, and usage-based revenue.

This tree structure reveals a common ARPU problem: when a company adds a lower-priced plan to attract smaller customers, blended ARPU may decline even if every individual customer segment is monetising well. The tree shows this clearly: the plan mix branch shifts toward lower tiers while the revenue-per-plan branch remains stable. The diagnosis is not a monetisation problem but a mix effect, and the appropriate response may be to accelerate upgrades from the lower tier rather than abandoning the strategy.

More important than absolute ARPU is the trend. Increasing ARPU over time indicates effective pricing, strong expansion revenue, and movement upmarket. Decreasing ARPU may signal over-discounting, mix shifts toward smaller customers, or pricing that has not kept pace with product value. Track ARPU for new cohorts separately from the overall base to identify whether changes are driven by acquisition patterns or by the behaviour of existing customers.

1. 1

   Introduce value-based pricing tiers

   Design pricing tiers around the value dimension that matters most to customers, whether that is seats, usage volume, features, or outcomes. This creates natural upgrade paths as customers grow and ensures that customers who derive more value pay more.

2. 2

   Build high-value add-ons

   Identify features or capabilities that solve specific problems for a subset of customers and price them as add-ons. Reporting, analytics, integrations, and priority support are common add-ons that increase ARPU without requiring a full plan upgrade.

3. 3

   Implement seat-based expansion

   If your product becomes more valuable with more users, per-seat pricing naturally increases ARPU as teams adopt the product. Make it easy for users to invite colleagues and ensure the product delivers immediate value to new users.

4. 4

   Raise prices for new customers

   Many SaaS companies under-price their product relative to the value it delivers. Test price increases with new customers first to validate willingness to pay without disrupting the existing base.

5. 5

   Focus on higher-value segments

   If mid-market customers generate 5x the ARPU of SMB customers with only 2x the acquisition cost, shifting marketing and sales focus toward mid-market can increase blended ARPU significantly.

1. 1

   Diluting ARPU with free users

   Including free-tier and trial users in the denominator makes ARPU artificially low and hides the true monetisation level of paying customers. Track blended and paying ARPU separately.

2. 2

   Ignoring cohort-level ARPU trends

   Overall ARPU can be stable while new cohorts are monetising at lower levels. Track ARPU by acquisition cohort to catch degrading unit economics early.

3. 3

   Optimising ARPU at the expense of volume

   Aggressively raising prices may increase ARPU but reduce conversion rates or accelerate churn. Total revenue equals customers times ARPU, and maximising one at the expense of the other can reduce total revenue.