ARPU Calculator

Live blended ARPU from two segments, with an average-of-averages trap peel so freemium mixes never hide behind a naive midpoint.

SaaS planning literacy. Not GAAP or IFRS revenue recognition. Keep users vs accounts and month vs year labels consistent with your source data.

Author, last update and planning note

By Ahmet C. Toplutaş·Site owner & editor · Business tools

Last updated May 21, 2026 · Reviewed May 21, 2026 · Planning estimates only - not tax, medical, or investment advice

Blended ARPU vs segment ARPUs

Segment ARPUs tell you what each plan or cohort earns per user. Blended ARPU answers a different question: across the whole active base in this period, how much revenue sits on each user (or account)? That blend is total revenue ÷ total count, which automatically weights large segments more heavily.

This page’s framing is blended vs segments, with an average-of-averages trap peel so a freemium mix never pretends the midpoint of two rates is the company number. It is not a countdown rail, not base-notation literacy, and not annual churn’s compound monthly bridge.

Decision framing: “What is the user-weighted company ARPU, and how far is the naive midpoint from that blend?”

The average-of-averages trap

Averaging two segment ARPUs with equal weight ignores headcount. Ten thousand low-ARPU freemium users and five hundred high-ARPU paid users do not meet in the middle. The trap peel shows (A + B) ÷ 2 next to the true blend so pitch decks cannot quietly swap them.

Load Freemium tilt. Segment B looks enormous on its own; the naive midpoint follows it upward; the blended number stays grounded by the freemium mass. That gap is the product beat.

Switch to Dual plan. Watch the trap gap shrink when segment sizes and rates are closer. Same board, different honesty.

Users (ARPU) or accounts (ARPA)

The division is the same. The denominator story is not. Users (or seats) produce ARPU. Accounts (or customers) produce ARPA. Multi-seat B2B deals can look “cheap per seat” and “rich per account” at once. The chips only change labels so you practice staying consistent instead of mixing both on one slide.

Enterprise tilt preset uses accounts on purpose. Keep that label when you share the link.

Same-period honesty

Monthly revenue over monthly active users is a monthly ARPU. Annual revenue over the users you treat as the annual denominator is an annual ARPU. Mixing an annual total with a monthly user snapshot invents a rate nobody can reconcile to the P&L.

Period chips are a labeling contract, not a converter. They do not divide annual by 12 for you. If you need recurring stock, hand off to MRR or ARR.

Mix weights: users vs revenue

When a segment’s share of users diverges from its share of revenue, concentration risk (or opportunity) is hiding in the blend. Mix weights surface that without a separate chart tool. Freemium tilt shows a huge user share in A and a huge revenue share in B.

Optional prior-period ARPU adds a simple period change percentage. It is not a CAGR and not a cohort retention curve.

What the panel actually computes

Two segments, one period, one denominator family. Blended is always total over total.

ARPU_A = revA / usersA (if usersA > 0) ARPU_B = revB / usersB (if usersB > 0) blended = (revA + revB) / (usersA + usersB) naiveAvg = (ARPU_A + ARPU_B) / 2 trapGap = naiveAvg - blended change% = (blended - prior) / prior (optional)

Where this hands off

After intensity-per-user literacy, hand off for recurring stock, retention, or lifetime value.

Monthly recurring stock: MRR calculator
Annualized recurring stock: ARR calculator
Logo loss over a year: annual churn
Lifetime value framing: CLV calculator

Worked scenarios

Scenario A: Freemium tilt. A: $50k / 10,000 users ($5). B: $200k / 500 users ($400). Blended ≈ $23.81. Naive midpoint $202.50. Trap gap dominates the story.

Flip denominator to Accounts without changing numbers only if those counts truly are accounts. Labels lie when the data does not match.

Scenario B: Dual plan. Closer segment sizes. Trap shrinks; mix weights look less extreme. Good board meeting baseline.

Scenario C: Enterprise tilt. Accounts denominator. High ARPA on a small account count next to a broader mid-market segment.

Scenario D: Annual period. Same math, year label. Use only when both revenue and counts are annual-period figures.

Common mistakes

Reporting the average of segment ARPUs as company ARPU.
Mixing users and accounts in the same denominator across slides.
Pairing annual revenue with monthly active users.
Treating ARPU as a substitute for MRR stock.
Ignoring churn while celebrating ARPU (annual churn).
Calling this GAAP recognized revenue per user.

How to use this panel

Load a scene preset or enter two segments’ revenue and counts.
Pick users vs accounts and month vs year labels that match your data.
Read blended vs segments, then the trap peel and mix weights.
Optionally add prior-period ARPU for a simple change %. Share when you want URL state; typing does not rewrite the address bar.

When not to stop at ARPU

Stop here for intensity-per-user (or per-account) literacy. Hand off for recurring stock, retention, or LTV.

Recurring stock: MRR / ARR.
Logo churn: annual churn.
Lifetime value: CLV.

Frequently asked questions

What is blended ARPU?

Total period revenue divided by total users (or accounts) in that same period. It is a user-weighted blend of your segments, not the arithmetic average of each segment’s ARPU.

What is the average-of-averages trap?

Taking (segment A ARPU + segment B ARPU) ÷ 2 ignores how many users sit in each segment. Freemium mixes make that naive average look far richer than the true blend. The panel shows both so the trap stays visible.

ARPU or ARPA?

ARPU uses users (or seats) in the denominator. ARPA uses accounts (or customers). The math is the same division; the storytelling changes. Pick one denominator and keep it consistent across dashboards.

Does period matter?

Yes. Monthly revenue over monthly active users is a monthly ARPU. Annual revenue over average annual users is an annual ARPU. Mixing an annual revenue total with monthly users invents a meaningless rate.

How is this different from MRR or ARR?

MRR/ARR measure recurring revenue stock. ARPU measures revenue intensity per user (or account). You can raise ARPU while MRR falls if the user base shrinks, or the reverse. Hand off recurring totals to the MRR and ARR calculators.

How does this relate to churn?

Churn tracks logo or revenue loss. ARPU tracks how much each remaining (or active) user contributes. A healthy ARPU with rising churn can still shrink the business. Use both lenses.

Is this GAAP revenue?

No. This is SaaS planning literacy. Recognized revenue, deferred revenue, and contract modifications follow accounting rules your finance team owns.

Sources

Loading…

Blended ARPU vs segment ARPUs

The average-of-averages trap

Users (ARPU) or accounts (ARPA)

Same-period honesty

Mix weights: users vs revenue

What the panel actually computes

Where this hands off

Worked scenarios

Common mistakes

How to use this panel

When not to stop at ARPU

Frequently asked questions

What is blended ARPU?

What is the average-of-averages trap?

ARPU or ARPA?

Does period matter?

How is this different from MRR or ARR?

How does this relate to churn?

Is this GAAP revenue?

Sources

Blended ARPU vs segment ARPUs

The average-of-averages trap

Users (ARPU) or accounts (ARPA)

Same-period honesty

Mix weights: users vs revenue

What the panel actually computes

Where this hands off

Worked scenarios

Common mistakes

How to use this panel

When not to stop at ARPU

Frequently asked questions

What is blended ARPU?

What is the average-of-averages trap?

ARPU or ARPA?

Does period matter?

How is this different from MRR or ARR?

How does this relate to churn?

Is this GAAP revenue?

Sources

What this number means

Share your calculation