Average Revenue Per Account (ARPA)

Average Revenue Per Account (ARPA) is total recurring revenue divided by the number of active accounts in a period. It answers one question: what is a customer worth, on average, right now. A company running $4.8M in ARR across 240 paying accounts has an ARPA of $20,000. The same metric is sometimes labeled ARPU (per user) or ARPC (per customer); the math is identical and only the denominator's name changes.

ARPA is the hinge between top-line growth and unit economics. It tells you whether the business is getting bigger by adding more logos or by selling more to each one — two very different growth stories that look the same on a revenue chart.

How Average Revenue Per Account Is Calculated

The formula is deliberately simple:

ARPA = Total Recurring Revenue ÷ Number of Active Accounts

Pick a period and a revenue base, then stay consistent. Most SaaS teams compute monthly ARPA from MRR and annual ARPA from ARR. The denominator should count only accounts that are actively paying in that period — not trials, not churned logos, not free-tier users. Mixing those in deflates the number and hides the real picture.

The blended number is technically correct and operationally useless. Twelve enterprise accounts at $100k carry the same weight in the blend as 600 SMB accounts. That's why ARPA is most honest when it's segmented.

When Sales Teams Use ARPA

Finance and RevOps watch ARPA to model LTV, since lifetime value is roughly ARPA multiplied by gross margin and divided by churn. A rising ARPA stretches payback math and makes CAC look better without changing a thing about acquisition cost.

VP Sales uses ARPA to set average deal size targets and to decide whether the motion should move upmarket. Founders quote it to investors as evidence the product can command price. Recruiters reading a candidate's resume use ARPA to translate "I closed 40 deals" into something meaningful — 40 deals at $3k ARPA is a transactional motion; 40 deals at $80k ARPA is a different job entirely.

ARPA also drives expansion strategy. When net revenue retention climbs, ARPA climbs with it, because existing accounts are spending more. That linkage makes ARPA a cleaner read on land-and-expand health than raw logo count.

Common ARPA Misconceptions and Gaming Patterns

ARPA is a mean, and means lie when the distribution is skewed. One $2M whale among 200 small accounts can drag blended ARPA up 30% while 199 customers look nothing like the average. Always check the median alongside it; if the two diverge sharply, the blended ARPA is a story about one account, not the book.

The most common manipulation is denominator pruning. Quietly drop dormant-but-paying micro-accounts from the "active" count and ARPA jumps without a single upsell. The reverse trick inflates the denominator with free or near-free seats to make a per-user figure look like broad adoption.

Rising ARPA is not automatically good news, either. It can mean the SMB segment is churning fastest and only large accounts survive — survivorship dressed up as growth. ARPA tells you the average wallet. It says nothing about how many wallets are walking out the door, which is why it should never be read without churn rate next to it.