Skip to main content
New: 9 PM Courses with hands-on exercises and certificates
← Back to Glossary
MetricsA

Average Revenue Per Account (ARPA)

Definition

Average Revenue Per Account (ARPA) measures the average revenue generated by each customer account over a specific period, typically calculated monthly. The formula is simple: Total Revenue / Total Number of Accounts. In B2B SaaS, where pricing and contracts are structured at the account (company) level rather than the individual user level, ARPA is the standard monetization metric.

ARPA is closely related to MRR and net revenue retention (NRR). If your MRR is growing but your account count is growing faster, ARPA is declining, which usually means you are acquiring smaller customers. If your MRR is growing faster than your account count, ARPA is rising, indicating successful expansion revenue or a shift toward higher-value segments.

Investors and board members pay close attention to ARPA trends because they signal the health of the go-to-market motion. Rising ARPA suggests the company is moving upmarket or successfully expanding within existing accounts. Falling ARPA might indicate pricing pressure, increased competition, or a strategic shift toward volume over value.

Why It Matters for Product Managers

ARPA directly connects product decisions to revenue outcomes. When you launch a new feature or pricing tier, ARPA tells you whether it moved the needle on monetization. If you add a premium analytics module and ARPA rises 15% among accounts that adopt it, you have evidence that the investment was worthwhile.

PMs should segment ARPA by customer cohort, plan tier, industry, and company size. These segments reveal where your product delivers the most value (and where customers are willing to pay the most for it). If enterprise accounts have 5x the ARPA of SMB accounts but only 2x the support cost, that informs where to invest product development resources. Use the LTV/CAC calculator to model how ARPA changes cascade through your unit economics.

How to Apply It

  • ☐ Calculate monthly ARPA and track the trend alongside account growth
  • ☐ Segment by customer size (SMB, mid-market, enterprise), acquisition channel, and plan tier
  • ☐ Track new customer ARPA separately from overall ARPA to detect segment shifts
  • ☐ Set ARPA expansion targets for existing accounts (e.g., 10% ARPA growth year-over-year)
  • ☐ Analyze which product features correlate with higher ARPA accounts
  • ☐ Use ARPA as the numerator in LTV calculations for B2B (LTV = ARPA / monthly account churn rate)

For related financial metrics, see the annual contract value (ACV) term, which measures the annualized value of individual contracts rather than the average across all accounts. The product-led growth entry covers how PLG motions affect ARPA through bottom-up adoption patterns.

Related Terms

ARR / MRR (Annual Recurring Revenue / Monthly Recurring Revenue)LTV (Customer Lifetime Value)Expansion RevenueNet Revenue Retention (NRR)Churn Rate

Frequently Asked Questions

How is ARPA different from ARPU?+
ARPA divides revenue by accounts (companies or organizations). ARPU divides revenue by individual users. In B2B SaaS, one account often has many users. A company paying $5,000/month with 25 seats has an ARPA of $5,000 but an ARPU of $200. ARPA is the standard metric for B2B SaaS because sales, pricing, and expansion decisions happen at the account level. ARPU is more relevant for B2C or prosumer products where each user has an individual subscription. When board decks reference 'average revenue per customer,' they almost always mean ARPA in a B2B context.
How do you increase ARPA over time?+
There are five primary levers. First, seat expansion: as the customer's team grows, they add more licenses. Second, upselling: customers upgrade from a lower tier to a higher tier (e.g., Pro to Enterprise). Third, cross-selling: customers adopt additional products or modules. Fourth, usage-based pricing: as customers use the product more, their bill increases naturally. Fifth, pricing optimization: periodic price increases for new customers (grandfathering existing customers for a period). The most sustainable ARPA growth comes from customers genuinely getting more value over time, not from aggressive price hikes.
What ARPA benchmarks should B2B SaaS PMs target?+
ARPA benchmarks vary by market segment. SMB-focused SaaS: $100-500/month ARPA is typical. Mid-market SaaS (50-500 employees): $1,000-5,000/month is common. Enterprise SaaS: $5,000-50,000+/month. More important than the absolute number is the ARPA growth rate. Top-performing SaaS companies grow ARPA 10-20% year-over-year through expansion revenue. If your ARPA is flat or declining, your expansion and upsell motions need attention. Track ARPA for new customers separately from existing customers to understand whether you are attracting higher-value accounts or just expanding existing ones.
← PreviousAssociate Product Manager (APM)Next →Average Revenue Per User (ARPU)

Explore More PM Terms

Browse our complete glossary of 100+ product management terms.

Full GlossaryExplore Frameworks