Average Revenue Per Account (ARPA)

ARPA

Average Revenue Per Account (ARPA) is the mean recurring revenue generated per customer account (company or organization) per period. It is the B2B SaaS equivalent of ARPU, and is more meaningful than per-user metrics when pricing is at the account/company level rather than per individual seat. ARPA directly drives LTV calculations for enterprise-oriented products.

formula.sh

ARPA = Total MRR / Total Active Paying Accounts

> Total MRR — total monthly recurring revenue from all paying accounts
> Total Active Paying Accounts — unique customer organizations or companies currently paying
> Distinct from ARPU when multiple users exist per account
> Calculate at the account (company) level, not the individual user level

example

example.sh

B2B project management SaaS. $500,000 MRR. 1,000 paying companies (accounts).

$500,000 / 1,000

→ $500 ARPA. On average, each company pays $500/month — likely 5–10 seats at $50–100 per seat.

why it matters

ARPA is the right unit of measurement for B2B SaaS because revenue and business decisions happen at the account level, not the individual user level. A company with 50 seats at $10/user/month has a $500/month ARPA. The renewal decision, the expansion opportunity, and the churn risk all exist at the company level.

ARPA expansion is the clearest path to revenue growth without proportional headcount growth. If you can move ARPA from $200 to $300 through seat expansion, tier upgrades, or add-on modules, you have grown revenue by 50% from your existing customer base. That is net revenue retention working at its best.

For market sizing and growth modeling, ARPA defines the revenue potential per ICP company you target. If your ICP has 10,000 potential companies and your ARPA is $500/month, your theoretical ARR ceiling from that ICP is $60M. This frames where product and pricing decisions need to go as you scale.

common mistakes

✗Using ARPU when your pricing model is per-account — this understates the economic unit at which business decisions are made.

✗Not segmenting ARPA by company size or industry — enterprise ARPA and SMB ARPA are often 10–50x different and require separate analysis.

✗Not tracking ARPA expansion within accounts over time — new account ARPA and 12-month account ARPA together reveal your land-and-expand effectiveness.

pro tips

✓Track ARPA at account signup vs ARPA at 12 months — the ratio is your average expansion multiple per account and is a leading indicator of negative churn potential.

✓Set ARPA targets by customer segment: define separate ARPA goals for SMB, mid-market, and enterprise accounts.

✓Build an ARPA cohort analysis: accounts acquired in older vintages often have higher ARPA than newer ones due to expansion — confirm this trend to validate your expansion motion.

the mrrsucks take

ARPA is how much each company actually thinks your product is worth to their business. If it's not growing over time, either your product isn't delivering compounding value or your pricing isn't capturing it.

faq

When should I use ARPA vs ARPU?+

Use ARPA for B2B SaaS where pricing is at the company/account level (flat per-account fee, per-seat with multiple users, usage tiers). Use ARPU for consumer SaaS or B2B tools with individual user pricing where each user is an independent economic unit.

How do I grow ARPA?+

Seat-based expansion (more users per account over time), tier upgrades (move accounts from starter to growth to enterprise plans), add-on modules, usage overage pricing, and account-level upsell motions driven by customer success. ARPA growth from existing accounts is essentially free revenue.

$1K MRR milestone›

related metrics

./install-the-daemon

$9. 365 roasts. one public endpoint of pure shame.