Esc
  • Jump to
  • The board
  • All launchesSort and filter by week or category
  • Open statsEvery number, in public
  • Maker storiesApps that stopped hiding
  • Submit a launch
  • AICategory
  • AnalyticsCategory
  • API & BackendCategory
  • Audio & VoiceCategory
  • AutomationCategory
  • CommunityCategory
↑↓ to move↵ to openPress / anywhere
Sign in

What is Average Revenue Per User (ARPU)?

Average Revenue Per User (ARPU) measures the average monthly recurring revenue generated by each active paying customer across all subscription tiers.

Updated · SaaS Metrics

Plain definition

Definition of Average Revenue Per User (ARPU)

Average Revenue Per User (ARPU) measures the average monthly recurring revenue generated by each active paying customer across all subscription tiers.

Formula / syntaxARPU = Total MRR / Active Paying Customers

Worked example

Say a made-up research bookmarking tool called ShelfDock offers a free tier alongside two paid plans. At month-end it has 150 active users on the $0 Free plan, 60 paying customers on the $15/month Solo plan ($900 MRR), and 20 paying customers on the $45/month Team plan ($900 MRR). Total MRR is $900 + $900 = $1,800 across 60 + 20 = 80 paying customers.

Dividing $1,800 by 80 gives a paid ARPU of $22.50/month (often labeled ARPPU, or Average Revenue Per Paying User, to remove ambiguity). Watch what happens if you mistakenly divide by all 230 active users including the 150 free accounts: $1,800 / 230 = $7.83/month, nearly three times lower. ARPU also translates revenue targets into concrete sales volume: reaching $5,000 MRR at $22.50 ARPU requires 223 paying customers ($5,000 / $22.50 = 222.22), whereas shifting more buyers onto a $50 average tier reduces the required customer count to exactly 100 paying accounts, cutting support load in half for the same monthly revenue.

Why it matters when you launch

ARPU immediately signals which distribution channels your pricing can realistically support. A product with a $9 ARPU must rely almost entirely on low-cost organic search, launch directories, or product-led sharing because paid search clicks, newsletter sponsorships, and manual outbound calls quickly cost more than a customer returns over several months.

Watching ARPU move over time also shows whether new features and higher tiers actually pull buyers upmarket. If your subscriber count climbs steadily while ARPU falls month after month, you are likely attracting smaller accounts, pricing your starter tier too generously, or leaning too heavily on permanent launch discounts just to win early signups.

Common mistakes

  • Including free-plan or active trial users in the denominator when calculating paid ARPU, which drags the average downward and corrupts LTV and CAC payback formulas.
  • Mixing up ARPU with ARPA (Average Revenue Per Account) in team software where one paying organization holds multiple seats, creating inconsistent pricing comparisons.
  • Tracking only one blended company-wide average when two distinct customer segments, such as solo hobbyists and 10-seat agencies, pull the average in opposite directions.
  • Including one-time setup, migration, or consulting payments inside monthly ARPU, which creates artificial spikes that disappear in the next billing period.

Tools and guides that use it

Official sources

Pritam Ghosh runs Hauntboard and maintains this glossary.

Published · Updated

Building something real? Launch it in public.

A person reviews every launch on Hauntboard, and every view and visit it sends your site is published on your launch page. Free to submit.

Launch free →

On the board

All →

Still hiding your app?

Put it on the board. Reviewed by a person, free to launch.

Launch free
Submit a launch