Unit Economics
ARPU (Average Revenue Per User)
ARPU (Average Revenue Per User) is the average amount of revenue you collect from each active user or account over a set period, usually a month or a year. It is total revenue in that period divided by the number of users, and it tells you how much each customer is actually worth before costs.
Also known as: average revenue per user, ARPA (average revenue per account), revenue per customer
Why it matters
ARPU is the number that decides whether your math can ever work. A founder validating an idea needs to know if the revenue per user is large enough to pay for acquiring and serving that user, and ARPU is the first input to that check. If your ARPU is 5 dollars a month, you cannot afford a paid channel that costs 200 dollars to land a customer, no matter how big the market looks. Watching ARPU over time tells you whether expansion (upsells, higher tiers, add-ons) is actually happening or whether you are stuck selling the cheapest plan to everyone. It also exposes the difference between a product people tolerate and one they pay more for, which is a sharper signal of value than raw signup counts. Low and flat ARPU on a small audience is a common build-or-kill flag: it usually means you are solving a vitamin problem, not a painkiller one. Track it from your very first paying users, because fixing weak ARPU later almost always means repricing or repositioning, both of which are painful after launch.
Formula
ARPU = total revenue in period / number of active users in period
Worked example
Say a project-management tool earns 12,000 dollars in monthly recurring revenue from 400 paying accounts. ARPU is 12,000 / 400 = 30 dollars per account per month. If the founder later launches a 99 dollar team tier and 50 accounts upgrade, monthly revenue rises to 15,450 dollars across the same 400 accounts, pushing ARPU to about 39 dollars. That 9 dollar jump, with no new customers, is direct evidence the upsell found real demand.
Common mistakes
- Counting free or trial users in the denominator drags ARPU toward zero and hides what your paying customers are really worth; for pricing decisions, calculate ARPU on paying users only and track free-to-paid conversion separately.
- Treating one headline ARPU as the truth when a few large accounts skew the average; segment by plan or customer type, and check the median too, or you will price for a customer who does not exist.
- Chasing ARPU growth through discounts and annual prepayments that inflate a single period instead of through durable value; good ARPU rises because customers move up tiers and stay, not because of accounting timing.
Frequently asked questions
What is a good ARPU (Average Revenue Per User)?
There is no universal number; a good ARPU is one that comfortably covers your cost to acquire and serve that user with margin left over. For self-serve SaaS, ARPU often runs 10 to 100 dollars a month, while sales-assisted B2B can be hundreds or thousands. Judge it against your CAC and gross margin, not against other companies in different markets.
How do you calculate ARPU (Average Revenue Per User)?
Divide total revenue for a period by the number of active users in that same period. Pick the period (monthly is standard for subscription products) and be consistent about who counts as a user. For meaningful pricing signals, use only paying users in the denominator rather than blending in free accounts.
ARPU (Average Revenue Per User) vs LTV: what is the difference?
ARPU measures revenue per user in a single period, while LTV (lifetime value) estimates total revenue a user generates across their whole relationship with you. LTV is roughly built from ARPU and how long customers stay, so ARPU is an input and LTV is the output. You watch ARPU to see current revenue health and LTV to judge whether acquisition spend pays back.
ARPU vs ARPA: are they the same thing?
They are nearly identical, but the denominator differs. ARPU divides by individual users, while ARPA (average revenue per account) divides by accounts, which may each contain several seats. For team or B2B products where one company buys many seats, ARPA is usually the more honest number to plan around.
Should I include free users in ARPU?
For pricing and unit-economics decisions, exclude free users and calculate ARPU on paying customers only, since blending free accounts hides what your product can actually charge. Keep a separate blended figure if you want to monitor monetization of your whole base. Mixing the two into one number usually misleads you into thinking your product is cheaper than the market will bear.
How do I increase ARPU for an early-stage product?
The durable levers are tiered pricing, usage-based add-ons, and moving customers from a starter plan to a higher one as they get value. Raising prices on new signups is the fastest test, since it costs nothing to try and immediately shows whether demand holds. Avoid leaning on discounts or one-time charges, which bump a single period without proving customers will pay more long term.
Related terms
More in Unit Economics
Stop reading definitions. Pressure-test your idea.
Knowing the terms is the easy part. Olune runs your actual idea against live Reddit signals, competitor data, and real search demand, then gives you an honest GO / NO-GO verdict in about eight minutes. Free, no card.
Last updated 2026-06-09 · Back to the glossary