ARPU, ARPA & ARPPU Calculator

ARPA is calculated by dividing total revenue for a specific period by the count of active accounts during that same period:

ARPA = (Total Revenue) / (Active Accounts Count)

For example, if your monthly recurring revenue (MRR) is $125,000 across 500 active accounts, the monthly ARPA is:

Monthly ARPA = $125,000 / 500 = $250.00 per account/month

When evaluating growth, separate ARPA for new cohorts from existing cohorts to see if new signups are choosing higher-tier plans.

ARPA (or ARPU) divides revenue by every active account, free ones included. ARPPU divides the same revenue by paying accounts only. Paid conversion is paying accounts divided by active accounts.

Take $50,000 of monthly revenue across 10,000 active accounts, 1,000 of which pay. ARPA is $5, ARPPU is $50 and paid conversion is 10%. ARPPU is always ARPA divided by the conversion rate, so the two figures can move independently: a price rise lifts ARPPU, while a better onboarding flow lifts ARPA without touching ARPPU at all.

That is why quoting one without the other hides which lever moved. A low ARPA next to a high ARPPU says buyers accept the price and most accounts never become buyers, which is a conversion problem rather than a pricing one.

Enter recurring revenue for a period (typically monthly recurring revenue), any add-on or setup revenue you want included, the active accounts in that period and the paying accounts among them. The calculator adds the two revenue lines, divides by active accounts for ARPA and by paying accounts for ARPPU, and multiplies the period total by 12 for an annual run-rate, which is only meaningful when the inputs are monthly.

Run this monthly and watch the trend line rather than a single snapshot: a rising ARPA usually means successful upsells or a price increase sticking, while a falling ARPA alongside rising account counts often means growth is coming from lower-tier plans.

A B2B SaaS company records $125,000 in monthly recurring revenue across 500 active accounts. ARPA = $125,000 / 500 = $250 per account per month.

Annualized, that's roughly $3,000 per account per year (ARPA × 12). If the company's average contribution margin is 70% and typical account lifetime is 24 months, a rough LTV estimate would be $250 × 0.70 × 24 = $4,200 per account, useful context for setting a sustainable CAC ceiling.

ARPA is a mean, and means are unreliable summaries of SaaS revenue because SaaS revenue is rarely symmetric. A book of 500 accounts at $250 average might be 480 accounts paying $80 and 20 enterprise accounts paying $4,300. The average is arithmetically correct and describes almost none of your customers.

That matters the moment you act on it. Pricing decisions, support staffing, and success coverage all get sized wrong if you plan for a typical account that does not exist. Look at the median alongside the mean: when the mean sits well above the median, a small group is carrying your revenue, and your real exposure is concentration risk rather than average monetisation.

Segment before you average. ARPA computed separately for self-serve, mid-market, and enterprise gives three numbers you can actually manage. A blended figure can rise for the uninteresting reason that the enterprise share grew, while every individual segment stood still or declined.

"Active accounts" needs a rule you apply consistently. Free trials, paused subscriptions, $0 legacy plans, and accounts inside their notice period all sit in a grey area, and including or excluding them can move ARPA by double digits. Whatever you decide, write it down, because a definition that quietly changes turns your trend line into noise.

Watch the timing too. Divide a full month of revenue by an account count taken on the last day of the month and a strong signup month will drag ARPA down for a reason that has nothing to do with monetisation. Use the average account count across the period instead of a point-in-time snapshot.

ARPA also says nothing about whether an account is profitable. An enterprise account paying ten times the average can consume twenty times the support, onboarding, and infrastructure. Read ARPA next to gross margin per segment, not on its own, before concluding that the high-paying end of the book is the valuable end.

Feed ARPA into acquisition math with the customer lifetime value calculator and CLV-to-CAC ratio calculator.