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.
What average revenue per account measures
ARPA is **annual recurring revenue divided by the number of active customers**, expressing what a single account pays in a year. It is one of the plainest statements of how a software business is built, and **the level it sits at dictates the design of everything else.** A business at fifty thousand yen per account and one at five million are different in the acquisition cost they can bear, in how they sell, and in how much support they can afford.
**Raising ARPA is not solely a matter of winning new customers.** Expanding usage among existing ones — upselling and cross-selling — and raising prices do just as much. In a market where acquisition costs keep climbing, expansion from the existing base often shows the better return. Enter the annual recurring revenue and the active customer count, and this tool computes ARPA alongside **a table of typical levels for the small-business, mid-market and enterprise segments.**
How to calculate ARPA
- Enter the annual recurring revenue The figure for the business as a whole. Monthly recurring revenue multiplied by twelve serves just as well.
- Enter the active customer count **The number of accounts currently under contract.** Customers who have cancelled do not belong here.
- Read the ARPA You get the annual revenue attributable to a single account.
- Compare against the segment table Establish which segment your own figure sits closest to.
Tips for getting more out of it
- 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 ACV and CAC Payback to help size how much you can afford to spend on customer acquisition (CAC).
Where this helps
Setting a ceiling on acquisition cost
**Without knowing ARPA, there is no way to decide how much you may spend on advertising or sales.**
Estimating the effect of a price change
Modelling ARPA after an increase shows whether revenue holds up even if some customers leave.
Revisiting a segment strategy
If you sell to small businesses but carry enterprise-level sales costs, the structure does not hold.
Explaining the business to investors
Software valuations lean heavily on ARPA read together with the churn rate.
Software metric terms explained
- ARPA
- Annual recurring revenue divided by the active customer count: the average annual revenue per account.
- Annual recurring revenue
- Revenue received on a continuing basis over a year. **One-off amounts such as setup fees are excluded.**
- Monthly recurring revenue
- Recurring revenue per month. Annual recurring revenue is normally this figure times twelve.
- Upsell
- Moving an existing customer onto a higher plan. **It raises ARPA directly.**
- Cross-sell
- Getting an existing customer to take an additional product.
- Customer acquisition cost
- What it cost to win a single customer. **Its ratio to ARPA is how the soundness of the investment is judged.**
Frequently Asked Questions
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.