×

Request a free diagnostic

Share your website, the marketing or revenue challenge you want to address, and the decision you need to make next. Scale Orbit will review your context and reply with a practical next step.

← Back

Thank you for your response. ✨

ARPU vs. ARPA: Choose the Right SaaS Revenue Metric

so-editorial-261-revenue-review-desk

Average revenue per user (ARPU) and average revenue per account (ARPA) both describe revenue relative to a customer base, but their denominators differ. ARPU divides revenue by users; ARPA divides it by accounts or customer organizations. That distinction can materially change a SaaS metric.

A revenue review workspace representing analysis by user and by account

Define the revenue numerator first

A common formula is revenue for a period divided by the average number of eligible users or accounts during that period. Some teams use period-end counts; others use average counts. Either method can work if it is documented and applied consistently.

Decide whether the numerator is recognized revenue, recurring revenue, or another defined measure. Do not compare ARPU calculated from monthly recurring revenue with ARPA calculated from recognized revenue without labeling the difference. Exclude taxes and one-time items according to a consistent policy.

Use ARPU for user-level economics

ARPU can help when individual users are the paying or monetized unit, such as self-serve subscriptions or usage plans billed per seat. It can show how plan mix, seat expansion, or monetization changes affect average value per active user.

User definitions matter. A registered user, paid seat, monthly active user, and billable user are different populations. Choose the denominator that matches the question and report it by cohort or plan when a blended average hides meaningful differences.

Use ARPA for account-level economics

ARPA is often useful in B2B SaaS where contracts, buying decisions, and renewals occur at the company account level. A single customer organization may contain many users, so account-based revenue can support comparisons across customer segments and contract portfolios.

Clarify what constitutes an account, especially when subsidiaries, parent organizations, and duplicate CRM records exist. If one legal customer is split across multiple CRM accounts, the denominator may inflate and the metric may appear lower than it is.

Interpret trends with context

A rising average does not necessarily mean monetization improved: lower-value customers may have churned, or the customer mix may have shifted. Pair the metric with retention, expansion, customer counts, and segment-level views to separate mix effects from within-customer change.

ARPU answers a per-user question; ARPA answers a per-account question. Choose the denominator based on how the product is used, sold, and billed.

Your reaction

How did this article land?

Choose one reaction. You can change it anytime.

Email verification required

Write for Scale Orbit

Turn practical experience into a public body of work

Share useful lessons about revenue, marketing, analytics, CRM, conversion, and growth. Build a visible author profile and learn what resonates with practitioners.

  • Public author profile and publication archive
  • Editorial support for your first article
  • Views, reactions, followers, and topic discovery
  • Free publishing with clear moderation rules

Email verification is required. Every first article is reviewed. Publication, rankings, traffic, leads, and revenue are not guaranteed.

THE NEXT STEP

Need to connect acquisition with revenue?

Share what you are trying to improve across acquisition, CRM, or measurement.

✎ Write

Discover more from Scale Orbit | Revenue Systems for B2B Growth Teams

Subscribe now to keep reading and get access to the full archive.

Continue reading