Average revenue per user (arpu)

Average Revenue Per User (ARPU) measures the average revenue generated per user or customer over a specific time period. It's calculated by dividing total revenue by the number of users, typically on a monthly or annual basis. ARPU is fundamental for understanding unit economics, evaluating pricing strategies, and comparing customer segments.

Why it matters

ARPU tells you how much value you extract per customer. Combined with customer acquisition cost, it reveals whether your business model works. If it costs $100 to acquire a customer who generates $10 monthly ARPU, you need customers to stay at least 10 months just to break even.

The metric also enables comparison across segments, time periods, and products. Is ARPU increasing as you add features and increase prices? Do enterprise customers generate higher ARPU than small business customers? These comparisons inform strategic decisions.

For product teams, ARPU connects product decisions to revenue impact. A feature that increases ARPU by $5 across 10,000 users generates $50,000 in monthly revenue. This perspective helps prioritize product work.

Calculating arpu

The basic formula is straightforward:

ARPU = Total Revenue / Number of Users

The challenge is defining terms precisely. What counts as revenue? Which users count?

For revenue, typically include all revenue attributable to users-subscription fees, usage charges, add-on purchases. Exclude one-time non-user revenue like professional services unless that's core to your model.

For users, define what you're measuring. ARPU calculated on paying customers (ARPPU-Average Revenue Per Paying User) differs from ARPU calculated on all users including free accounts. Both are valid; they answer different questions.

Time period matters too. Monthly ARPU is most common for subscription businesses. Annual ARPU works better for products with infrequent purchases.

Arpu variations

ARPU (all users) includes free users in the denominator. For freemium products, this number is lower but shows revenue efficiency across your entire user base.

ARPPU (paying users only) measures revenue from monetized users. This is higher and shows how well you monetize customers who convert to paid.

ARPA (per account) is common in B2B where one account might have many users. A company paying $1,000/month with 10 users shows $1,000 ARPA but $100 ARPU.

Each metric tells a different story. Use the one that matches your question.

Using arpu

For pricing decisions, ARPU reveals how pricing changes affect revenue. If you raise prices 20% and ARPU increases 15%, some customers downgraded or churned. If ARPU increases 25%, customers are selecting higher tiers.

For segment analysis, comparing ARPU across segments reveals where value concentrates. If enterprise customers have 5x the ARPU of SMB customers, that informs acquisition focus and feature prioritization.

For product decisions, features that increase ARPU deserve attention. Usage-based pricing, add-ons, and premium features can all lift ARPU when designed well.

For growth modeling, ARPU multiplied by users gives revenue. ARPU multiplied by projected users gives revenue projections. Understanding ARPU dynamics improves forecast accuracy.

Arpu trends

Tracking ARPU over time reveals important patterns:

Increasing ARPU suggests successful upselling, effective pricing, or shifting customer mix toward higher-value segments. This is generally healthy.

Decreasing ARPU might indicate competitive pressure, customer mix shifting to lower-value segments, or pricing problems. Investigate the cause.

Stable ARPU isn't inherently good or bad-it depends on your growth stage and strategy. Early-stage companies might accept stable ARPU while growing users. Mature companies might focus on increasing ARPU.

Cohort analysis adds nuance. How does ARPU change for customers over their lifetime? If ARPU increases as customers stay longer (they upgrade, buy add-ons), you have healthy expansion dynamics.

Arpu by business model

Different business models show different ARPU patterns:

SaaS subscriptions typically have stable per-user ARPU defined by pricing tiers. Growth comes from more users or moving customers to higher tiers.

Freemium shows low overall ARPU (many free users) but potentially high ARPPU if paying users are engaged.

Usage-based pricing creates variable ARPU that increases as customers use more. Good for aligning price with value but harder to predict.

Marketplace ARPU depends on transaction volume and take rate. More transactions or higher-value transactions increase ARPU.

Common mistakes

Mixing user definitions across calculations makes trends meaningless. If you count all users one month and only active users the next, ARPU changes don't reflect business changes.

Ignoring segment variation hides important dynamics. Average ARPU of $100 might combine $200 enterprise ARPU and $50 SMB ARPU. Changes in segment mix affect overall ARPU without any real pricing change.

Chasing ARPU at all costs can backfire. Raising prices increases ARPU but might increase churn. Adding expensive features increases ARPU but might not serve customers. Balance ARPU with retention and satisfaction.

Comparing incomparable ARPU across companies with different models creates false conclusions. A freemium company with $5 ARPU and a sales-led enterprise company with $500 ARPU aren't comparable.

Arpu and product strategy

Product decisions affect ARPU through multiple mechanisms:

Packaging determines how much value different customers access at different price points.

Usage-based elements let price scale with customer value received.

Premium features create upgrade incentives that increase ARPU when customers adopt them.

Expansion paths make it easy for customers to grow their usage and spending.

Klero helps teams understand what drives ARPU by connecting revenue data to customer feedback. When you can see what high-ARPU customers say, need, and request, you can build features that drive expansion rather than guessing.