ARPU: Revenue Per User, Broken Down

How to calculate average revenue per user and use it to compare pricing tiers and customer segments.

February 25, 20263 min read639 words

one-line definition

ARPU is a core operating metric that helps small teams make better product and growth decisions.

formula: ARPU = Total revenue ÷ Number of active users

tl;dr

ARPU measures the average revenue per user per month. It tells you whether you're extracting more value over time or just adding cheap accounts.

Simple definition

ARPU (Average Revenue Per User) is your total revenue divided by your number of active users in a given period. It answers a simple question: on average, how much is each user worth to you right now?

ARPU is different from LTV. LTV is a lifetime projection. ARPU is a snapshot of the current month. If your ARPU is rising, it means users are upgrading, buying add-ons, or your pricing changes are working. If it's falling, you might be attracting lower-value users or losing your power users.

Why this matters

ARPU is a critical metric for bootstrapped founders because it represents the truth about your business. Before product-market fit, this metric may feel abstract. But once you have paying customers and recurring revenue, ignoring this metric becomes dangerous to your growth trajectory.

Most solo founders make the mistake of focusing on the wrong metric at the wrong time. Before $1k MRR, the best metrics are activation and product-market fit. Between $1k-$10k MRR, arpu becomes highly relevant. Beyond $10k MRR, it becomes one of your top three growth levers.

The reason solo founders rarely fail due to lack of brilliant ideas. They fail because they don't systematically measure metrics that matter and don't iterate on improvements.

Common mistakes

1. Calculating too early. If you have 5 customers, this metric is noise, not signal. Wait until you have at least 50 customers and 2-3 months of data before drawing conclusions. Too early and you'll see random variance, not real patterns.

2. Ignoring variations by segment. Your customers acquired via blog may behave differently than those acquired via paid ads. Your enterprise customers may function differently than your small-biz customers. Always segment your metrics to see the true signal.

3. Optimizing without context. Improving this metric by 10% means 10% more revenue? Not necessarily. Understand upstream and downstream impact before optimizing. Focus on the change that will have the biggest impact on revenue.

4. Forgetting causality flows both directions. A low metric may indicate a product issue, a positioning issue, or that you're attracting the wrong customers. Before optimizing, understand why it's low.

How to act on this

Calculate this metric for your last 30 customers right now. Do you have the data? If yes, establish a baseline and write it down. That's your first step toward improvement.

Identify your highest-value customer segment. Is it a specific monthly cohort? An acquisition channel? A customer type? Focus on that segment and try to improve this metric for them.

Run one small experiment to improve this metric by 5-10%. Measure, learn, iterate. The compounding of these small improvements over 12 months creates a huge difference.

How to calculate it

ARPU = Total revenue / Number of active users

Say your SaaS made $7,200 last month and you had 180 active users:

ARPU = $7,200 / 180 = $40

Now segment it. If your Pro plan users (50 people) generate $4,500 and your Basic users (130 people) generate $2,700:

  • Pro ARPU = $4,500 / 50 = $90
  • Basic ARPU = $2,700 / 130 = $20.77

That tells you Pro users are worth 4.3x more. Spend your time building features that get Basic users to upgrade.

Example

You run a scheduling tool with a $19/month Starter plan and a $59/month Growth plan. Your blended ARPU is $31. You ship a team collaboration feature gated to the Growth plan. Over two months, 20% of Starter users upgrade. Your ARPU moves from $31 to $39 -- a 26% increase with zero new signups. ARPU growth from expansion is cheaper than ARPU growth from acquisition because there's no CAC attached.

Related terms

  • MRR
  • CAC
  • LTV

FAQ

Why does ARPU matter?+

It gives a fast signal about whether your product and distribution system is improving or regressing.

previous

ARR: Annualizing Your Recurring Revenue

How to calculate Annual Recurring Revenue and when it matters more than MRR for SaaS businesses.

next

ARPPU: Revenue From Paying Users Only

How ARPPU differs from ARPU and why it gives a clearer picture of monetization.

Put the concept to work

Move from definitions to decisions with guides, comparisons, and calculators built for founders.

Explore the blog

Related terms

newsletter

Weekly builds, experiments, and growth playbooks

No fluff. Just things that actually shipped.