ARPA vs ARPU: Why Account-Based SaaS Should Track Revenue Differently

A company with 50 seats on one account and a freelancer on a single-seat plan are both "one customer" by some measures and wildly different by others. Whether you should average revenue per user or per account depends entirely on how your product is sold - and using the wrong one can make a healthy seat-based business look weaker than it is, or a struggling single-seat business look stronger.

This post explains the difference between ARPA and ARPU, when to use each, and why the gap between them is itself a useful signal.

What Is ARPU?

Average Revenue Per User (ARPU) divides total revenue by the number of individual users.

ARPU = Total MRR ÷ Number of Active Users

ARPU treats every individual user as the unit of analysis - useful for products priced and consumed per-person, like most consumer subscriptions and single-seat SaaS tools.

What Is ARPA?

Average Revenue Per Account (ARPA) divides total revenue by the number of paying accounts (companies or organizations), regardless of how many individual users sit inside each one.

ARPA = Total MRR ÷ Number of Active Accounts

🧒 Explained simply Imagine your lemonade stand sells to families instead of individuals. One family buys 5 cups because everyone's thirsty; another family buys 1 cup. If you only count "cups per person," a 5-person family buying 5 cups looks the same as 5 strangers each buying 1 cup - but they're actually one customer relationship, not five. ARPA counts revenue per family (account); ARPU counts it per person. For a business that sells to families, ARPA tells the real story.

ARPA vs ARPU, Side by Side

	ARPU	ARPA
Unit of analysis	Individual user	Account / organization
Best fit for	Consumer apps, single-seat tools, usage-per-person products	Seat-based B2B SaaS, team plans, multi-user accounts
What it reveals	Value generated per individual	Value of a single customer relationship
Risk if misused	Understates account value in seat-based businesses	Hides per-seat pricing dynamics in usage-heavy products

The two metrics aren't interchangeable substitutes - they answer different questions. For a single-seat SaaS tool, ARPU and ARPA are identical, since one account equals one user. The gap only opens up once a product supports multiple users per account.

A Worked Example of the Gap

A B2B SaaS company has 100 paying accounts and $50,000 in MRR. Those 100 accounts have 600 total individual users (because most accounts have multiple seats).

ARPA = $50,000 ÷ 100 accounts = $500/account
ARPU = $50,000 ÷ 600 users = $83.33/user

Neither number is wrong - they're measuring different things. ARPA tells you what a single customer relationship is worth, which is the more useful number for sales targets, CAC sustainability, and account-based growth planning. ARPU tells you the per-seat economics, which matters for pricing decisions and understanding usage intensity within accounts.

Why the Gap Between Them Matters

A widening gap (ARPA growing faster than ARPU) usually means accounts are adding seats. This is a healthy expansion signal - your existing accounts are getting more value and bringing in more of their team, growing ARPA without you having to acquire a single new account.

A narrowing gap can mean average account size is shrinking. If new accounts are signing up with fewer seats than your historical base, ARPA will grow more slowly than ARPU even while individual seat pricing stays flat or improves - worth investigating before assuming everything is fine because ARPU looks healthy.

Tracking only ARPU in a seat-based business hides account health. A seat-based SaaS business that only reports ARPU can completely miss that its average account size is shrinking, since ARPU is blind to how many users are bundled into each paying relationship.

Which One Should You Track?

If your business is...	Track primarily...	Because...
Single-seat, per-person priced	ARPU (equals ARPA)	They're the same number
Seat-based, multi-user accounts	ARPA, with ARPU as a supporting metric	ARPA reflects the actual customer relationship value
Usage-based (per API call, per transaction)	A usage-normalized metric alongside ARPA	Neither ARPA nor ARPU alone captures consumption intensity

Most B2B SaaS companies selling to teams should lead with ARPA in board reporting and use ARPU as a secondary metric to understand seat-level pricing and expansion dynamics within accounts.

How ARPA and ARPU Connect to Other Metrics

ARPA is a key input into CAC payback period and LTV calculations for account-based businesses - using ARPU instead in those formulas would understate the value of a multi-seat account and could lead to under-investing in acquiring it. Conversely, ARPU is more directly useful when evaluating whether per-seat pricing itself needs to change.

How to Track ARPA and ARPU in Chartsy

Chartsy calculates both ARPA and ARPU automatically from your Stripe or Paddle data, so you can see account-level and seat-level revenue side by side. You can ask:

"What is my average ARPA this month?"
"Show ARPA vs ARPU trend for the last 12 months"
"What's the average number of seats per account?"
"Which accounts have grown their seat count the most this quarter?"

Connect Stripe and track ARPA alongside ARPU →

Frequently Asked Questions About ARPA vs ARPU

What is the difference between ARPA and ARPU? ARPU (Average Revenue Per User) divides total revenue by individual users. ARPA (Average Revenue Per Account) divides total revenue by paying accounts, regardless of how many users are inside each one. For single-seat products the two are identical; for multi-seat B2B SaaS they diverge significantly.

Which metric should B2B SaaS companies track? Seat-based B2B SaaS companies should lead with ARPA, since it reflects the value of the actual customer relationship being sold and renewed. ARPU remains useful as a secondary metric for understanding per-seat pricing and usage intensity within those accounts.

Why would ARPA and ARPU move in different directions? If average account size (seats per account) is changing, ARPA and ARPU can diverge even with stable per-seat pricing. Growing accounts that add seats push ARPA up faster than ARPU; shrinking average account size can leave ARPU flat while ARPA declines.

Does ARPA replace LTV or CAC calculations? No, but it's a key input to them for account-based businesses. Using ARPU instead of ARPA in an LTV calculation for a multi-seat product understates the true value of an account, which can lead to setting acquisition spend targets too low for what each account relationship is actually worth.

How do I calculate ARPA from my billing data? Divide total MRR by the number of active paying accounts (not individual users) in the same period. Most billing platforms track accounts/organizations distinctly from individual user seats, but few surface ARPA as a calculated metric automatically - it usually needs to be derived rather than read directly off a dashboard.