Average Revenue Per Account (ARPA)

Average Revenue Per Account (ARPA, or ARPU when measured per user rather than per company account) is the average recurring revenue a SaaS business collects from each active customer, calculated simply as total MRR divided by the number of active paying accounts (or the ARR equivalent divided by accounts for an annualized figure). If a company has $100,000 MRR across 500 paying accounts, ARPA = $200/month. ARPA is a foundational input to several other core SaaS metrics: it's one of the two variables (alongside churn rate) in the standard LTV formula, and tracking its trend over time is one of the clearest signals of whether a company's expansion motion and pricing strategy are working — a rising ARPA within a stable or growing customer base usually means expansion revenue (upsells, add-ons, seat growth) is outpacing any downward pricing pressure from discounting or increased mix of smaller customers. ARPA is also the metric most directly shaped by go-to-market segment: a self-serve SMB-focused SaaS product typically runs ARPA in the tens to low hundreds of dollars per month, while an enterprise-focused SaaS selling annual contracts to Fortune 500 companies can run ARPA in the tens or hundreds of thousands of dollars per year — meaning ARPA by itself is meaningless without context on which customer segment and pricing tier it's being measured across, which is why mature SaaS reporting almost always segments ARPA by plan tier or customer size band rather than reporting one blended company-wide number. Concrete worked example: a project management SaaS reports blended ARPA of $85/month across its full customer base — but a segmented breakdown shows Starter-tier customers average $19/month, Pro-tier customers average $79/month, and Enterprise customers average $850/month. When the company's sales team shifts pipeline focus toward Enterprise deals over the following two quarters, blended ARPA climbs to $110/month even with total customer count flat — a segmented ARPA view is what lets the finance team correctly attribute that revenue-per-account growth to mix-shift toward Enterprise rather than mistakenly crediting broad-based pricing power across the whole base. Tracking ARPA trend alongside customer count is also an early-warning system: a company whose customer count is growing but whose blended ARPA is steadily declining may be winning increasingly price-sensitive, lower-value customers over time — a mix-shift worth catching well before it shows up as a broader growth or retention problem in the topline numbers. ARPU (Average Revenue Per User) is the closely related sibling metric used when a business's natural billing unit is the individual user rather than the company account — more common in consumer and prosumer SaaS — and the choice between reporting ARPA versus ARPU should reflect whichever unit actually drives the underlying pricing model, since conflating the two can misrepresent unit economics when a single account contains many users.