Skip to content
RevenueMetric 3 of 35

ARPUAverage Revenue Per User

Average monthly revenue per active customer.

Abderrahim Ben Jazia, PhDBy · Founder of FlowMRR, previously built and sold AIS (Avance Immédiate Services), French tax-credit softwareUpdated:

Put this metric to work: explore FlowMRR's recurring revenue analytics to track revenue movements, retention and forecasts from your Stripe account, or see how FlowMRR compares as a Baremetrics alternative for Stripe.

Here, and in FlowMRR, ARPU means monthly revenue per paying customer: MRR divided by the distinct customers paying that month, not by subscriptions or seats. A person is counted once across products and Stripe customer records (matched by email, Stripe customer ID as fallback). Customers paying nothing (free plan, 100% coupon, paused subscription) and customers who churned during the month are in neither MRR nor the count. Rising ARPU can reflect upsells or smaller customers churning; falling ARPU can reflect discounts or a shift toward smaller accounts.

Formula

ARPU = MRR ÷ paying customers (each person counted once)

Worked example

MRR $50,000 with 250 active customers → ARPU = $200/mo.

Other definitions you will see

Some tools divide MRR by Stripe customer records or by active subscriptions, which gives a lower ARPU when one person holds several subscriptions or records. Many B2B teams use ARPU for revenue per seat or user and ARPA for revenue per account. Consumer businesses often divide by all users, free ones included, which measures how the whole audience is monetised rather than what payers pay.

Illustrative comparisons

By segment

These unsourced ranges are illustrative scenarios, not measured industry benchmarks, percentiles or recommended targets. Their qualitative labels are editorial interpretations. Compare your own cohorts using the same segment, period, currency and measurement basis.

SMB
$50–$500
Mid-market
$500–$5,000
Enterprise
$5,000+

Why it matters

ARPU determines your go-to-market motion. Low ARPU (<$50) demands self-serve and product-led growth — you can't afford salespeople. Mid ARPU ($500+) opens inside sales. ARPU also caps your acceptable CAC: a $20 ARPU product can't sustain a $1,000 CAC.

Common mistakes

  • Calculating ARPU on revenue including one-off charges — inflates the number deceptively.
  • Not segmenting ARPU by plan — hides which tier is actually working.
  • Comparing your ARPU to a different ICP without adjusting expectations.

Calculating it from Stripe data

ARPU is MRR divided by paying customers, so both parts come from Stripe subscriptions. The numerator is monthly-normalised MRR: annual plans ÷ 12, permanent discounts deducted, trialing, incomplete, incomplete_expired and paused subscriptions left out, one-off charges and taxes excluded. The denominator is the number of distinct customers paying in that month: not subscriptions, not seats, and not every customer record in your Stripe account.

Two details change the result. First, a customer with two subscriptions, or the same buyer under two Stripe customer records, should count once: grouping by email or company gives revenue per person or per account rather than per record. Second, customers paying nothing (a free plan, a 100% discount, a paused subscription) belong in neither the numerator nor the denominator; counting them drags ARPU down without saying anything about pricing. Customers who churned during the month are out of both as well.

Compute in the smallest currency unit, such as cents, and round once at the end. Convert multi-currency revenue into one reporting currency before dividing, otherwise exchange-rate moves show up as ARPU changes. FlowMRR calculates ARPU from Stripe as MRR per distinct paying customer, counted once across products.

Reading the result

ARPU is an average, so it moves for two different reasons: customers paying more (upgrades, price increases, seat growth) or a change in mix (small customers leaving, larger ones arriving). Before celebrating a rise, check whether the customer count fell at the same time; if it did, the increase may be the bottom of the base leaving rather than anyone paying more.

Look beyond the mean. A few large accounts can pull ARPU well above what a typical customer pays, so compare it with the median and break it down by plan and by signup cohort. Comparing the ARPU of new customers with that of the whole base shows whether your pricing is drifting up or down over time, and comparing it with CAC shows how much acquisition each customer can support.

Frequently asked questions

How do you calculate ARPU for a subscription business?

Divide MRR by the number of paying customers in the same month. With $30,000 MRR and 150 paying customers, ARPU is $200 per month.

What is the difference between ARPU and ARPA?

ARPU divides revenue by users and ARPA by accounts. When one account holds many users or seats the two differ widely; when each customer is one account, as in many self-serve SaaS products, they are the same figure. Always state the denominator.

Should free users be included in ARPU?

For SaaS revenue metrics, usually not: ARPU is measured on paying customers. Some consumer businesses report ARPU across all users, free ones included, which answers a different question about monetising the whole audience.

Why did ARPU go up while MRR went down?

Because customers left faster than revenue did: when smaller customers churn, total MRR falls but those who remain pay more on average. Check the customer count and churned MRR before reading the rise as a pricing success.

Contact us
FlowMRR

Let's talk

A question, a technical issue or an idea for a partnership? Write to the FlowMRR team.