ARPA Calculator

Use this calculator to measure average revenue per account. A key SaaS and subscription business metric for understanding account-level monetisation, benchmarking pricing tiers, and tracking revenue expansion over time.

What this calculator does

The ARPA calculator helps you measure how much monthly recurring revenue your business generates on average from each active customer account.

It uses:

• monthly recurring revenue
• number of active accounts

This gives you ARPA - average revenue per account - one of the core metrics for any SaaS, subscription, or recurring revenue business.

How to use the ARPA calculator

1. Enter your monthly recurring revenue - the total recurring revenue your business generates each month, excluding one-time payments, setup fees, or non-recurring charges
2. Enter your active accounts - the total number of active paying customer accounts during the same period
3. The calculator instantly shows your ARPA

Make sure you use active accounts consistently - define what counts as active and apply that definition the same way each time you calculate.

ARPA Formula

ARPA = Monthly Recurring Revenue / Active Accounts

Where:

• Monthly Recurring Revenue = total recurring monthly revenue from all active accounts
• Active Accounts = total number of active paying customer accounts
• ARPA = average monthly recurring revenue per account

Example calculation

If:

• Monthly recurring revenue = 50,000
• Active accounts = 500

Then:

• ARPA = 50,000 / 500
• ARPA = 100 per account per month

Each active account generates an average of 100 in monthly recurring revenue.

What is ARPA?

ARPA - average revenue per account - is a SaaS and subscription business metric that measures the average monthly recurring revenue generated by each active customer account.

It differs from ARPU - average revenue per user - in that it measures at the account or company level rather than the individual user level. For B2B SaaS businesses where a single account may have multiple users or seats, ARPA is typically the more meaningful metric.

ARPA is used to benchmark pricing performance, identify expansion opportunities, and track how effectively a business monetises its customer base over time.

What is a good ARPA for a SaaS business?

ARPA benchmarks vary widely depending on the market segment:

• SMB SaaS - typically 50 to 500 per month per account
• Mid-market SaaS - typically 500 to 5,000 per month per account
• Enterprise SaaS - typically 5,000 or more per month per account

Higher ARPA generally means fewer accounts are needed to reach revenue targets, but it also typically means longer sales cycles and higher customer acquisition costs. Most successful SaaS businesses move ARPA upmarket over time as they add features and expand into larger customer segments.

Why ARPA matters for SaaS and subscription businesses

Tracking ARPA helps you:

• understand the average revenue contribution of each customer account
• benchmark performance across different pricing tiers or customer segments
• identify whether account expansion - upsells and add-ons - is increasing revenue per account over time
• support revenue forecasting based on account growth targets
• compare monetisation efficiency against industry benchmarks

How to increase ARPA

Three main levers for growing average revenue per account:

• Raise prices - if your product delivers strong value, price increases are the most direct way to grow ARPA
• Drive account expansion - upsells, add-ons, and seat expansions increase revenue from existing accounts without acquiring new ones
• Move upmarket - targeting larger businesses with higher willingness to pay naturally increases ARPA over time

Monitoring ARPA alongside net revenue retention helps you see whether expansion revenue is offsetting churn and growing account value over time.

When to use this calculator

Use this calculator when you want to:

• benchmark your average account revenue against target or historical figures
• track whether pricing changes or upsell campaigns are increasing revenue per account
• segment ARPA by pricing tier, industry, or customer size to identify your most valuable segments
• support board reporting or investor updates with account-level revenue metrics
• compare ARPA trends over time as your business grows

Common mistakes when calculating ARPA

Common mistakes include:

• confusing accounts with users - one account may have many users, so the figures are not interchangeable
• including one-time payments or setup fees in monthly recurring revenue, which inflates the figure
• using an inconsistent definition of active accounts across different reporting periods
• comparing ARPA figures without accounting for changes in the mix of pricing tiers or customer segments

ARPA vs ARPU

These two metrics measure revenue at different levels of granularity.

• ARPA measures average revenue per account - most useful for B2B businesses where buying decisions happen at the company level
• ARPU measures average revenue per user - more commonly used in B2C and consumer subscription businesses

For most B2B SaaS businesses, ARPA is the more actionable metric because pricing, contracts, and expansion opportunities are managed at the account level. Use the ARPU Calculator if your business model is user-based rather than account-based.

ARPA vs MRR

These metrics are closely related but measure different things.

• ARPA measures the average revenue contribution per account
• MRR measures the total recurring revenue across all accounts

ARPA multiplied by the number of active accounts equals MRR. Growing ARPA and growing account count are the two levers that drive MRR growth. Use the SaaS MRR Calculator to track total recurring revenue alongside ARPA.

Related calculations

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

• Use the ARPU Calculator if your business measures revenue at the user 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 expand account revenue
• Use the LTV Calculator to estimate the total lifetime value of an average account

Useful resources

• Stripe - payment infrastructure for SaaS and subscription businesses with built-in revenue reporting
• ChartMogul - subscription analytics platform for tracking MRR, ARPA, churn, and revenue retention
• Baremetrics - SaaS metrics dashboard for Stripe, Braintree, and other payment processors
• ProfitWell - subscription financial metrics and pricing optimisation tools for SaaS businesses

FAQs

What is ARPA?

ARPA - average revenue per account - measures the average monthly recurring revenue generated by each active customer account. It is a core metric for SaaS and subscription businesses.

How do you calculate ARPA?

ARPA = Monthly Recurring Revenue / Active Accounts.

What is the difference between ARPA and ARPU?

ARPA measures revenue at the account level. ARPU measures revenue at the individual user level. For B2B businesses with multiple users per account, ARPA is typically the more useful metric.

What is a good ARPA for a SaaS startup?

It depends on your target market. SMB-focused SaaS typically sees ARPA between 50 and 500 per month. Mid-market and enterprise SaaS businesses target significantly higher ARPA. The key is whether your ARPA supports sustainable unit economics relative to your customer acquisition cost.

How does ARPA relate to LTV?

LTV - customer lifetime value - is directly influenced by ARPA. A higher ARPA means each account generates more revenue over its lifetime, improving LTV and the LTV to CAC ratio.

Should I calculate ARPA monthly or annually?

Monthly ARPA is the standard for SaaS businesses using monthly recurring revenue. You can annualise it by multiplying by 12 if you prefer to work in annual figures - this is sometimes called ARPA on an ARR basis.

How do I use ARPA to set revenue targets?

Divide your revenue target by ARPA to get the number of accounts needed. For example, if your target is 1,000,000 MRR and your ARPA is 200, you need 5,000 active accounts to hit that target.

Can ARPA decline even if MRR is growing?

Yes. If you are adding accounts at lower price points faster than you are growing revenue from existing accounts, ARPA can decline even as total MRR increases. This is worth monitoring as it can indicate downward pricing pressure or a shift in customer mix.

Interpreting your result

Your arpa 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.