ARPA (Average Revenue Per Account) Calculator

Enter your ARR (Annual Recurring Revenue) and active customer count to calculate ARPA, the average revenue per account. Includes an SMB / Mid-Market / Enterprise segment reference table.

ARPA customer segment reference table

Segment Typical ARPA (annual) Typical sales motion
SMB Under $1,000 Self-serve — fully online signup minimizes sales cost
Mid-Market $1,000–$25,000 Inside sales — individual attention via phone/video calls
Enterprise $25,000 and above Field sales and dedicated customer success

* The appropriate level varies widely by industry and product. Use these figures as general guidance only.

Tips

  • If you don't have an exact ARR figure, MRR (Monthly Recurring Revenue) × 12 works as a reasonable approximation.
  • Make sure your active customer count excludes churned customers — including them will understate your true ARPA.
  • If your ARPA is far from your intended target segment, it may be a sign to revisit your pricing or your target customer profile.
  • Combine this result with other SaaS metrics like money.saas.acv and cac_payback to help size how much you can afford to spend on customer acquisition (CAC).

Frequently Asked Questions

ACV (Annual Contract Value) is the annualized value of a single individual contract, while ARPA divides your company's total ARR by your entire customer base (total account count). ACV answers "how much is this one contract worth?" while ARPA answers "what is the average revenue per account across the whole company?"

Not necessarily. The right ARPA level varies enormously by business model, so higher isn't automatically better. A low-ARPA, high-volume SMB model and a high-ARPA, low-volume Enterprise model can both be perfectly healthy businesses when executed well. What matters is whether ARPA is consistent with your target customer segment.

ARPA measures revenue per account (customer company), while ARPU measures revenue per individual user. In B2B SaaS where a single customer account often has many users, ARPA tends to reflect the true revenue scale of each contract more accurately.

Three common approaches are: (1) upselling or cross-selling existing customers (upgrading plans, selling add-on features), (2) revisiting your pricing itself, and (3) shifting your targeting toward customer segments with inherently higher ARPA. Keep in mind the balance with customer count — chasing ARPA alone can come at the cost of growth rate.
ツールくん

Side Note — Why SaaS companies talk about segments in terms of ARPA

A single ARPA figure matters so much because it reflects a SaaS company's core strategic question: who are we selling to? Two companies with identical $10 million in monthly revenue — one with an ARPA of $500/year (many customers) and another with an ARPA of $50,000/year (few customers) — need completely different organizations and go-to-market motions. The former must efficiently acquire large volumes of customers through marketing and product polish; the latter needs a dedicated sales team carefully closing a handful of large deals.

The SMB / Mid-Market / Enterprise split isn't just a company-size classification — it's also a practical line for which sales motion makes economic sense. Deploying costly field sales against a low-ARPA segment causes customer acquisition cost (CAC) to exceed lifetime value (LTV), which breaks the business model. Conversely, trying to sell to high-ARPA enterprise buyers through self-serve alone often fails to address decision-makers' concerns (security, customization requirements, etc.), leading to lost deals.

Many fast-growing SaaS companies follow a staged expansion path: validating the market early on with a low-ARPA, high-volume SMB model, then adding features that matter to Mid-Market and Enterprise buyers (SSO, audit logs, SLAs, etc.) as the business matures, gradually raising ARPA. Tracking ARPA over time is therefore also a useful way to check whether this "move upmarket" strategy is actually working.