RevenueMetric 4 of 35

ARPAAverage Revenue Per Account

Average monthly revenue per paying account, not per seat.

Put this metric to work: explore FlowMRR's recurring revenue analytics to track revenue movements, retention and forecasts from your own account.

ARPA measures monthly revenue per paying customer account. If ARPU uses seats as its denominator, the two diverge: one account can hold dozens of seats. FlowMRR uses active customers for ARPU instead; it equals ARPA only when a counted customer corresponds to one account.

Formula

ARPA = MRR ÷ Active Accounts

Worked example

MRR $60,000 across 200 accounts → ARPA = $300/account. If those accounts hold 1,500 seats, ARPU (per seat) = $40 — same revenue, very different story.

Illustrative comparisons

By motion

These unsourced ranges are illustrative scenarios, not measured industry benchmarks, percentiles or recommended targets. Their qualitative labels are editorial interpretations. Compare your own cohorts using the same segment, period, currency and measurement basis.

Self-serve

$15–$100

Inside sales

$300–$3,000

Enterprise

$3,000+

Why it matters

ARPA is the number that should trend up as you move up-market or layer in expansion. Rising ARPA with flat customer count means your existing base is paying you more — the cheapest growth there is. Confusing ARPA with per-seat ARPU is how teams misprice multi-seat plans.

Common mistakes

Using ARPU and ARPA interchangeably when your plans are seat-based.
Computing ARPA on total revenue including one-off fees.
Not segmenting ARPA by plan or cohort, which hides where expansion actually happens.

Track ARPA in FlowMRR