ARPU Calculator

Use this calculator to measure average revenue per user. A key metric for SaaS, subscription, and consumer app businesses tracking monetisation efficiency, pricing performance, and revenue growth per user over time.

What this calculator does

The ARPU calculator helps you measure how much monthly recurring revenue your business generates on average from each active user.

It uses:

• monthly recurring revenue
• number of active users

This gives you ARPU - average revenue per user - a core metric for understanding how effectively your business monetises its user base.

How to use the ARPU calculator

1. Enter your monthly recurring revenue - the total recurring revenue your business generates each month, excluding one-time charges, setup fees, or non-recurring payments
2. Enter your active users - the total number of active users during the same period, using a consistent definition of what counts as active
3. The calculator instantly shows your ARPU

Consistency matters - define active users clearly and apply the same definition every time you calculate ARPU so your figures are comparable over time.

ARPU Formula

ARPU = Monthly Recurring Revenue / Active Users

Where:

• Monthly Recurring Revenue = total recurring monthly revenue from all active users
• Active Users = total number of active users during the period
• ARPU = average monthly recurring revenue per user

Example calculation

If:

• Monthly recurring revenue = 50,000
• Active users = 2,000

Then:

• ARPU = 50,000 / 2,000
• ARPU = 25 per user per month

Each active user generates an average of 25 in monthly recurring revenue.

What is ARPU?

ARPU - average revenue per user - is a metric that measures the average monthly recurring revenue generated by each active user. It is widely used in SaaS, subscription software, mobile apps, telecoms, and any business where revenue is tied to individual users rather than company accounts.

ARPU helps businesses understand how effectively they are monetising their user base and whether pricing, plan mix, or product changes are increasing or decreasing revenue per user over time.

What is a good ARPU?

ARPU benchmarks vary significantly by business model and market:

• Consumer subscription apps - typically 5 to 20 per month per user
• SMB SaaS - per user pricing - typically 10 to 50 per month per user
• Productivity and collaboration tools - typically 10 to 30 per month per user
• Telecoms and mobile - typically 20 to 60 per month per user

The most important benchmark is your own historical ARPU trend. Rising ARPU over time indicates improving monetisation. Falling ARPU may signal pricing pressure, a shift toward lower-value users, or churn concentrated among higher-paying segments.

Why ARPU matters for subscription and SaaS businesses

Tracking ARPU helps you:

• measure how effectively your business converts users into revenue
• identify whether pricing or plan changes are improving monetisation
• compare revenue efficiency across different user segments or products
• support MRR forecasting based on user growth targets
• benchmark your monetisation performance against industry standards

How to increase ARPU

Three practical levers for growing average revenue per user:

• Raise prices - if your product delivers strong value, increasing subscription prices is the most direct route to higher ARPU
• Encourage upgrades - moving users from lower to higher pricing tiers increases revenue without acquiring new users
• Reduce low-ARPU churn - if lower-paying users churn at higher rates, the remaining mix naturally has higher ARPU over time

Monitoring ARPU alongside net revenue retention gives you a complete picture of whether your monetisation strategy is working.

When to use this calculator

Use this calculator when you want to:

• track changes in user-level monetisation over time
• assess the impact of a price change or new pricing tier on ARPU
• segment ARPU by plan, cohort, or user type to identify your most valuable segments
• support investor reporting or board presentations with user revenue metrics
• compare monetisation efficiency between two products or time periods

Common mistakes when calculating ARPU

Common mistakes include:

• using total registered users instead of active users - inactive users dilute ARPU and make it misleading
• including one-time payments or non-recurring charges in monthly recurring revenue
• confusing users and accounts - in B2B products with multiple seats per account, ARPU and ARPA will give very different results
• comparing ARPU across periods without accounting for changes in the definition of active users

ARPU vs ARPA

These two metrics measure revenue at different levels and suit different business models.

• ARPU measures average revenue per individual user - most useful for B2C, consumer apps, and per-seat SaaS pricing
• ARPA measures average revenue per account - more useful for B2B businesses where buying decisions happen at the company level

For a B2B SaaS business with ten users per account, ARPA will be ten times higher than ARPU. Use the ARPA Calculator if your business model is account-based rather than user-based.

ARPU vs MRR

These metrics are closely connected but measure different dimensions of your revenue.

• ARPU measures the average revenue contribution per user
• MRR measures total recurring revenue across all users

ARPU multiplied by total active users equals MRR. Growing both ARPU and user count are the two core levers that drive MRR growth. Use the SaaS MRR Calculator to track total recurring revenue alongside ARPU.

Related calculations

Once you know your ARPU, you may also want to:

• Use the ARPA Calculator if your business measures revenue at the account level
• Use the SaaS MRR Calculator to track total monthly recurring revenue
• Use the Net Revenue Retention Calculator to measure how effectively you retain and grow revenue from existing users
• Use the LTV Calculator to estimate the total lifetime value of an average user

Useful resources

• Stripe - payment infrastructure for subscription businesses with built-in revenue and user metrics reporting
• ChartMogul - subscription analytics platform for tracking ARPU, MRR, churn, and revenue trends
• Baremetrics - SaaS metrics dashboard with ARPU tracking for Stripe, Braintree, and Recurly
• ProfitWell - subscription revenue optimisation and pricing analysis tools for SaaS and subscription businesses

FAQs

What is ARPU?

ARPU - average revenue per user - measures the average monthly recurring revenue generated by each active user. It is a core metric for SaaS, subscription, and consumer app businesses.

How do you calculate ARPU?

ARPU = Monthly Recurring Revenue / Active Users.

What is the difference between ARPU and ARPA?

ARPU measures revenue at the individual user level. ARPA measures revenue at the account level. For B2B businesses with multiple users per account, ARPA is typically more meaningful. For B2C and consumer apps, ARPU is the standard metric.

Should I use total users or active users to calculate ARPU?

Always use active users. Including inactive or churned users understates ARPU and makes the metric less useful for decision making.

What is a good ARPU for a SaaS product?

It depends on your market and pricing model. Consumer and SMB products typically see ARPU between 5 and 50 per month. The most important signal is whether your ARPU is trending up over time as you optimise pricing and drive upgrades.

How does ARPU relate to LTV?

LTV is directly influenced by ARPU. A higher ARPU means each user generates more revenue over their lifetime, improving the economics of customer acquisition. Use the LTV Calculator to model lifetime value based on ARPU and average customer lifespan.

Can ARPU fall even if revenue is growing?

Yes. If you are adding users at lower price points faster than you are growing revenue from existing users, ARPU can decline even as total MRR increases. This is worth monitoring as it may indicate a shift toward less valuable user segments.

How often should I track ARPU?

Monthly tracking is standard for subscription businesses. Comparing ARPU month over month and year over year gives the clearest picture of monetisation trends over time.

Interpreting your result

Your arpu result should always be interpreted in context:

• compare it against your historical baseline
• review it alongside the main commercial or operational drivers behind the metric
• compare it across products, channels, periods, or segments where relevant
• avoid interpreting the result in isolation without checking the underlying input values

A single period can be noisy, so trend direction over several periods is usually more useful than one standalone result.

Data quality checklist

Before acting on this result, verify:

• the inputs use the same time period and reporting basis
• one-off anomalies are identified separately from steady-state performance
• discounts, refunds, taxes, or fees are handled consistently where relevant
• the underlying values are complete enough to support a meaningful conclusion

Small input inconsistencies can materially change the result.

How to improve this metric

Practical ways to improve this metric depend on the underlying business model, but often include:

• identify the main driver behind the result before making changes
• test one variable at a time so the impact is easier to measure
• compare performance by segment rather than only at an overall level
• review the metric regularly so changes can be caught early

Improvement is most reliable when measurement definitions remain stable over time.

Benchmarks and target setting

A good target depends on your industry, business model, and stage of growth.

When setting targets:

• compare against your own historical trend before relying on outside benchmarks
• define both minimum acceptable and aspirational target ranges
• review targets whenever pricing, cost, demand, or channel mix changes materially
• pair benchmark review with the underlying commercial context, not just the final number

Your own historical performance is usually the most practical benchmark.

Reporting cadence and decision workflow

For most teams, a simple cadence works best:

• Weekly: monitor the metric when trading conditions or campaign activity change quickly
• Monthly: compare the result against target and prior periods
• Quarterly: reassess assumptions, targets, and the main drivers behind the metric

A practical workflow is to calculate the metric, identify the primary driver of change, test one improvement, and then review the next comparable period before scaling.

Common analysis scenarios

You can use this metric in several practical scenarios:

• monthly performance reviews
• pricing, margin, or cost analysis
• planning and forecasting discussions
• investor, lender, or management reporting

In each scenario, pair the result with the underlying business context so decisions are not made on one number alone.

FAQ extensions

Should I compare this metric across channels?

Yes, but only when definitions and attribution rules are consistent.

How many periods should I review before making changes?

At least 3 comparable periods is a good baseline unless there is a clear data issue or one-off event.

What should I do if this metric improves but profit declines?

Check whether costs, discounts, conversion quality, or downstream profitability changed at the same time.