Average Revenue Per User (ARPU)

ARPU

Average Revenue Per User (ARPU) is the mean recurring revenue generated per active user or account in a given period. It is the simplest pricing health metric, showing whether your average customer is paying more or less over time. Rising ARPU indicates successful pricing optimization, upsell motion, or migration to higher tiers. Falling ARPU signals pricing pressure, competitive discounting, or a shift in your customer mix toward lower-value segments.

formula.sh

ARPU = Total MRR / Total Active Users (or Accounts)

> Total MRR — all recurring revenue in the period
> Total Active Users or Accounts — depending on your pricing unit (per user vs per account)
> Calculate monthly for operational use; trend it quarterly to identify pricing dynamics
> Segment by pricing tier and acquisition cohort for actionable analysis

example

example.sh

SaaS platform with $240,000 MRR and 2,000 active paying accounts.

$240,000 / 2,000

→ $120 ARPU per account per month. Track this quarter-over-quarter to see if pricing power is increasing.

why it matters

ARPU is a direct measure of your monetization effectiveness. Increasing ARPU while maintaining or growing customer count is the most efficient path to MRR growth — it requires no additional CAC. Companies that successfully move upmarket, introduce premium tiers, or add usage-based components typically see significant ARPU expansion.

ARPU decline is an early warning signal. If customer count holds steady but MRR stagnates or falls, ARPU is declining — meaning customers are churning from higher tiers, you are discounting heavily to win new business, or your new customer cohorts skew toward lower-priced plans. Each cause has a different remedy.

For LTV calculations, ARPU is the starting point. Even small increases in ARPU compound significantly through the LTV formula: a 20% increase in ARPU produces a 20% increase in LTV, all else being equal. The economics of moving upmarket are almost always favorable when done with pricing power rather than feature bloat.

common mistakes

✗Mixing user-level ARPU with account-level ARPU — for B2B SaaS with per-seat pricing, account ARPU and user ARPU will be very different and tell different stories.

✗Not segmenting ARPU by acquisition cohort — if new cohorts have lower ARPU than established ones, you are moving downmarket without realizing it.

✗Using ARPU as a vanity metric without connecting it to CAC payback — high ARPU with matching high CAC produces the same unit economics as low ARPU with low CAC.

pro tips

✓Plot ARPU trend by acquisition quarter: if newer cohorts have lower ARPU at signup than older cohorts, you have a pricing erosion problem to address before scale.

✓Decompose ARPU change into mix effects (shifting customer composition) vs pure pricing effects (actual rate changes) — the two require different strategic responses.

✓Set an ARPU expansion target: if current ARPU is $120, model what 10% ARPU expansion (to $132) does to your LTV and how much customer success investment to justify it.

the mrrsucks take

ARPU is how much your average customer thinks you're worth. If it's declining while you add customers, you're moving downmarket — congratulations on building a more popular product with worse economics.

faq

What is the difference between ARPU and ARPA?+

ARPU measures revenue per individual user. ARPA measures revenue per account (company). For B2B SaaS with multiple users per account, ARPA is typically the more useful metric. A company with 5 users per account will have an ARPU of $X and an ARPA of $5X.

How do I increase ARPU?+

Raise prices (direct and impactful), create premium tiers with genuine value differentiation, add usage-based components, build upsell paths within the product, and shift acquisition focus toward higher-value segments. Even small ARPU improvements compound dramatically at scale.

$1K MRR milestone›

related metrics

./install-the-daemon

$9. 365 roasts. one public endpoint of pure shame.