ARPU & ARPA Calculator

What Is ARPU and Why It Matters

ARPU (average revenue per user) is your total monthly recurring revenue divided by the number of active paying users in the period. In B2B SaaS, the same math run at the account level is called ARPA — average revenue per account — and that is usually the version that matters for unit economics. One number, one question answered: how much is a typical customer worth to you per month?

ARPU is the connective tissue of your model. LTV is built on ARPA, CAC payback is CAC divided by gross-margin-adjusted ARPA, and pricing changes show up in ARPU before they show up anywhere else. If MRR is growing but ARPU is flat, you are growing on volume alone — and your ceiling is whatever your acquisition channel can feed you.

The ARPU Formula, With a Worked Example

ARPU = Total MRR ÷ active accounts. Multiply by 12 for the annual figure.

Say you end the month at $84,000 MRR across 700 active paying accounts. ARPU = 84,000 ÷ 700 = $120/month, or $1,440 annualized. Now split it: if 500 of those accounts sit on a $49 starter plan, the other 200 must average roughly $298 to produce that blend. Same ARPU, two very different businesses — which is why segmenting by plan, cohort, or channel beats staring at one blended figure. For the denominator, use the ending account count, or the average of start and end if your base moves fast within the month.

What's a Good ARPU?

There is no universal benchmark — ARPU is a function of who you sell to, so comparing yours against a different segment is noise. The useful test is whether your ARPU can carry your go-to-market motion. Directional 2026 medians by segment:

The rule of thumb: your fully loaded cost to acquire and serve a customer has to fit inside what that ARPA supports. A $50/month product cannot afford field sales; a $2,000/month product run purely self-serve is leaving expansion revenue on the table. Cross-check the adjacent metrics on our 2026 SaaS benchmarks page.

Common Mistakes

• Free and trial users in the denominator. Fine for consumer apps reporting blended ARPU, but for SaaS unit economics use paying accounts only — and label which basis you are reporting.
• One-time revenue in the numerator. Setup fees, services, and overages are not MRR. Including them inflates ARPU and corrupts everything downstream, LTV especially.
• The mean hiding the distribution. Three whale accounts can prop up a blended ARPU while your median customer pays a third of it. Check median against mean at least quarterly.
• Confusing monthly and annual. ARPU quoted without a period is meaningless — always state it.

Once you have a clean ARPU, feed it into the LTV calculator and check it against your CAC — that pairing is where ARPU stops being trivia and starts being a decision.