Average Revenue Per User (ARPU)
Updated July 21, 2026
Total MRR divided by total paying customers. Tracks whether expansion is outpacing discounting.
Also known as: ARPU, Average Revenue Per Unit
Average Revenue Per User (ARPU) is the average revenue a business generates per user or paying customer over a defined period, almost always a month. In SaaS it is usually calculated as total Monthly Recurring Revenue divided by the number of paying customers. The number matters because it compresses a whole pricing and packaging strategy into a single line: whether expansion, upsells, and price increases are outrunning discounting and downmarket drift. A rising ARPU alongside steady customer growth suggests the business is capturing more value per relationship; a falling ARPU can mean the opposite, even while top-line revenue still climbs.
ARPU originated in the telecom industry in the early 2000s, where carriers needed a way to gauge per-subscriber value against the heavy fixed cost of building and maintaining networks. As subscription and per-user monetization spread, the metric carried into digital media, online gaming, streaming, ISPs, and SaaS. No single inventor or founding paper is documented; sources consistently place its origin in telecom without pinpointing a first use.
Today ARPU is reported in the earnings releases of public telecom and consumer-tech companies and tracked internally by SaaS finance and product teams. It is most useful as a trend over time or benchmarked against direct competitors with similar business models, since absolute values vary enormously by industry, from single-digit dollars per month for consumer apps to thousands per month for enterprise software. There is no universal good number.
How ARPU is calculated in SaaS
The SaaS formula is total Monthly Recurring Revenue divided by the number of paying customers in the same period. If a company books 500,000 dollars of MRR across 2,000 paying accounts, ARPU is 250 dollars per month. Some teams annualize it or compute it per account rather than per individual seat, but the structure is the same: an aggregate revenue figure over a customer count.
Because both inputs move, ARPU is best read as a decomposition rather than a standalone number. It can rise for healthy reasons, such as customers upgrading tiers, adding seats, or adopting paid add-ons. It can also rise for reasons that mask weakness, like churning small accounts while retaining large ones. Reading ARPU next to customer count, retention, and MRR growth separates a genuine move upmarket from a shrinking base that happens to average higher. The metric answers how much each relationship is worth on average, not how many relationships there are or whether they last.
ARPU vs. ARPA, ARPPU, and LTV
Several near-identical metrics differ only in their denominator, and mixing them up distorts comparisons. ARPA (Average Revenue Per Account) divides revenue by paying accounts or companies rather than individual users, and is preferred in B2B SaaS where one account holds many seats, since using per-user ARPU there would understate account-level value. ARPPU (Average Revenue Per Paying User) counts only paying users and excludes the free tier, which matters in freemium models where a large non-paying base would otherwise dilute the average. Gaming and mobile apps often use ARPDAU, revenue per daily active user, to fit microtransaction economics.
LTV (Customer Lifetime Value) is a different animal entirely. ARPU is a single-period snapshot of current per-customer revenue; LTV projects revenue across a customer's full expected lifespan by folding in retention and churn. ARPU feeds LTV as an input, but the two answer different questions: one about the present period, one about the cumulative relationship.
How competitive intelligence teams use ARPU
ARPU is a practical benchmarking lens. Comparing a competitor's disclosed or estimated ARPU against your own reveals how they compete: low ARPU with a high user count points to a price-and-volume play, often freemium or SMB-focused, while high ARPU across fewer accounts points to enterprise depth and value-based pricing. The shape of the number describes the strategy.
The trend line carries even more signal. A rising competitor ARPU may indicate a push upmarket or new upsell and add-on monetization; a falling one may signal discounting to defend share or a deliberate move downmarket. For public companies, these figures come from earnings calls and investor decks. For private competitors, where MRR and CAC are almost never disclosed, ARPU is often one of the few unit-economics proxies that can be approximated externally, inferred from pricing-page changes, plan-tier shifts, and hiring signals. Teams monitoring competitor pricing pages and job postings can watch those inputs move and estimate the direction of travel before any number is published.
Common mistakes and limitations
The most documented pitfall is that ARPU can rise while the underlying business weakens. Landing one large customer can spike the average without reflecting broader growth, because revenue across customers often follows a power-law distribution, where a handful of accounts dominate and the mean says little about the typical customer. This is why ARPU is misleading without customer count, retention, CAC, and LTV alongside it.
ARPU also ignores cost-to-serve. Two companies with identical ARPU can have very different economics if one spends far more to acquire and support each customer, which is what the margin-adjusted variant AMPU (Average Margin Per User) exists to correct. When reading a competitor's ARPU inferred from external signals, the same caution applies with more force: a shifting free-to-paid mix or a single disclosed marquee deal can distort the estimate, so treat it as a directional proxy rather than a precise figure.
Stop looking terms up. Start tracking them.
meertrack watches your competitors' websites, pricing, and hiring, then alerts you when something meaningful changes.
Frequently Asked Questions
How do you calculate ARPU for a SaaS company?
Divide total Monthly Recurring Revenue by the number of paying customers over the same period. For example, 400,000 dollars of MRR across 1,600 accounts gives an ARPU of 250 dollars per month. Some teams annualize the figure or measure per account instead of per seat, but the structure stays the same: an aggregate revenue total divided by a customer count for one period.
What is a good ARPU for SaaS?
No single figure counts as good, because the number swings widely with your pricing tiers, target segment, and region. A budget consumer app might earn only a few dollars each month per user, whereas high-end enterprise software can pull in several thousand. What actually matters is watching the direction it moves and stacking it against rivals that run comparable models, rather than chasing some fixed absolute target.
What is the difference between ARPU and ARPA?
ARPU divides revenue by individual users, while ARPA divides it by paying accounts or companies. In B2B SaaS, where one account can hold many seats, ARPA is usually preferred because ARPU would understate the value of each customer relationship. The choice of denominator is the only real difference, but it changes the number substantially in multi-seat businesses.
Is ARPU the same as MRR?
No. MRR is the aggregate total of monthly recurring revenue across all customers, while ARPU is the per-customer average derived from it. In SaaS, ARPU is typically MRR divided by paying customers. MRR tells you the size of the recurring revenue base; ARPU tells you how much of that base each customer accounts for on average.
How can a company increase its ARPU?
Common levers are upselling and cross-selling existing customers, introducing tiered or bundled pricing, improving retention so loyal customers spend more over time, and demonstrating enough value to justify price increases. A move upmarket toward larger accounts also raises ARPU. Because a single large deal can inflate the average, an ARPU increase is best read alongside customer count and retention to confirm it reflects broad growth.
Related terms
The predictable, normalized monthly revenue from all active subscriptions. The foundational SaaS metric.
Customer Lifetime Value (CLV / LTV)Total revenue a customer is expected to generate over their entire relationship. Typically ARPU / churn rate.
Expansion Revenue (Expansion MRR)Additional revenue from existing customers through upsells, add-ons, or increased usage.
Net Revenue Retention (NRR / NDR)Revenue from existing customers at period end divided by their starting revenue, after expansion, contraction, and churn. Above 100% = customers spend more over time.
Customer Acquisition Cost (CAC)Total cost of acquiring a new customer (marketing + sales spend / new customers).
Pricing IntelligenceThe practice of systematically monitoring competitor and market pricing to inform your own pricing strategy.
Annual Recurring Revenue (ARR)MRR multiplied by 12, used for year-over-year comparisons and company valuation.
Churn Cohort AnalysisGrouping customers by attribute and tracking churn patterns over time to identify when and why attrition spikes.