ARPU (Average Revenue Per User)

ARPU is total recurring revenue divided by total customer count over a given period. ARPA (Average Revenue Per Account) is the same calculation at the account level rather than the user level, which is the version most B2B SaaS companies actually care about. The number on its own is rarely informative. The version that matters is ARPU over time, broken by cohort, segment, or plan tier. A flat ARPU with growing customer count means revenue is scaling but pricing is stagnant. A rising ARPU could be price increases, expansion, or mix shift toward larger customers. A falling ARPU usually signals discounting under pressure or downmarket drift the executive team has not noticed yet.

For funded teams, ARPU becomes useful when it gets segmented. Blended ARPU across the entire customer base hides the story. ARPU by ICP segment reveals where pricing power actually lives. ARPU by acquisition channel reveals which channels bring in higher-value customers. ARPU by cohort over the first 12 months reveals how fast expansion is actually working. A SaaS company that thinks its expansion motion is strong, then segments and discovers expansion is concentrated in 5 percent of accounts, has just identified the real shape of its revenue base. The AI Ops Department builds the segmentation views so these patterns surface continuously rather than annually.

ARPU also drives the math on CAC Payback and unit economics. Doubling ARPU through better packaging or annual contracts cuts payback in half without changing acquisition spend at all. Most funded teams sit on 20 to 40 percent unrealized ARPU expansion because pricing was set early, never revisited, and customer willingness to pay has shifted as the product matured. The fastest path to better unit economics is usually a pricing audit and a tier restructure, not a CAC reduction project. Both matter, but pricing moves faster and the leverage is asymmetric.