You pull average revenue per user (ARPU) for the monthly investor update and the number has climbed from $180 to $340 since last month. One enterprise account landed in that window, and the other 200 accounts on the books spent exactly what they spent before. An average that moves like this is worth explaining before anyone else has to ask.

This guide covers the ARPU formula, the calculation choices that change the number, what counts as a good ARPU and how investors read it during investor due diligence.

What is ARPU

Average revenue per user is total revenue divided by the number of users over a set period, usually a month or a year. Digital media companies and consumer communications businesses report it most often, and subscription software borrowed the measure as almost every product moved to a recurring bill. In software as a service (SaaS), the purpose is the same: revenue measured against a defined user base. Whether that base counts seats, accounts or active users is a decision each company makes for itself.

ARPU tells a founder whether pricing and packaging convert into revenue per account. A flat ARPU through a tier change usually means the new packaging isn't lifting monetization, once you account for customer mix and any change in the denominator. Founders also use it with gross margin and retention to check whether customer acquisition cost (CAC) supports the payback period the business needs. Investors look at the same number to size up monetization before they ask about growth.

How to Calculate ARPU

The calculation takes seconds. The harder part is keeping the inputs consistent: the revenue base, the denominator, and the measurement period. Change any one of those between updates, and ARPU stops being comparable over time.

Formula and Worked Example

ARPU = Total revenue in a period / Number of users in that period

$180,000 / 1,200 users = $150 ARPU

ARPU equals total revenue in a period divided by the number of users in that period. A company with $180,000 in recurring revenue and 1,200 active users in a month posts an ARPU of $150. That $150 means something only if next month's figure uses the same inputs and the same period length. Everything below concerns what belongs on each side of the division.

Denominator Choice

Signups, active users and paying accounts each produce a different number from identical revenue. Dividing by paying accounts gives you average revenue per account (ARPA), a separate metric covered below. Active users work as a default for most software and consumer subscriptions. Dividing by registered signups pulls dormant accounts into the average and pushes the figure down without explaining anything. Companies also define an active user differently from one another, so a founder who changes that definition between periods hands investors a series nobody can interpret.

Revenue Base

The numerator is recurring revenue only, which for most software companies means monthly recurring revenue (MRR). Implementation fees and one-time setup charges inflate the number in the month they land, then disappear the month after. Every period-to-period comparison breaks with them. A setup fee that spikes ARPU in month one and vanishes in month two says nothing about pricing power. Professional services, hardware sales and non-recurring consulting belong in the same excluded bucket.

Measurement Period

Monthly and annual ARPU produce different pictures, and founders who mix the two walk into the annual-contract trap. For a $1,200 annual subscription delivered evenly across 12 months, the revenue recognition standard IFRS 15 puts monthly recognized revenue at roughly $100. Booking the whole $1,200 in the month it arrived spikes that month and understates the following 11. Usage-based revenue produces the mirror image, where one customer bills $20 one month and $400 the next and an accurate monthly ARPU swings with them. A trailing multi-month window dampens both distortions.

ARPU vs. ARPA, ARPPU and LTV

Founders routinely report one of ARPU's neighbors and label it ARPU. The differences come down to who lands in the denominator and how far out the time horizon runs:

• Average revenue per account (ARPA): Divides revenue by accounts instead of individual seats, which is the more useful cut for most business to business (B2B) companies even when the slide says ARPU. One enterprise account can hold dozens of seats, and a single large deal lifts revenue per account at the same time revenue per individual user falls.
• Average revenue per paying user (ARPPU): Strips free users out of the denominator, the right number for any product with a free tier. Free users add to the denominator and nothing to the numerator, and by definition ARPPU lands at or above ARPU.
• Customer lifetime value (LTV): Extends ARPU across the whole customer relationship and folds customer churn into the calculation. ARPU covers a finished period; LTV is an estimate of the whole relationship.

Whichever version you use, labeling the slide saves an investor from recomputing it.

What Counts as a Good ARPU

A good ARPU is one that covers what it costs to acquire and serve each customer, with enough margin left over for the business to work. Cross-company benchmarks travel poorly, because ARPU is an absolute number and the business models underneath it rarely line up. Reddit reported $6.18 per user globally in the second quarter of 2026. Among private B2B software companies, the ones that outgrew their peers ran closer to $564 in ARPA at $1 million in annual recurring revenue (ARR). Neither figure sets a bar for the other.

For an internal comparison that survives scrutiny, group ARPU by sales motion, not by industry. Self-serve and prosumer products depend on volume. Small and medium-sized business (SMB) pricing supports inside sales, and mid-market and enterprise contracts fund a field team. ARPU has to support a CAC payback period the company can survive, whichever motion you run.

How to Increase ARPU

ARPU rises when existing customers spend more or the customer mix shifts upward. Packaging is the least expensive place to start, and the levers run roughly in order of effort from there:

• Packaging and tier design: A flat plan structure gives growing customers no path to spend more, and better tier design lifts ARPU without a price increase. Plans buyers find confusing or too rigid on contract terms are packaging problems as much as pricing ones.
• Expansion inside existing accounts: Seats, add-ons and usage above a threshold raise ARPU without another acquisition cycle. Expansion supplies about 40 percent of net new ARR at the median.
• Plan mix and annual commitments: Moving customers toward premium plans lifts the average with no product change. Annual commitments do the same and shift retention dynamics at the same time.
• Better-fit acquisition: Customers who match the product move into higher tiers faster and expand more predictably. What looks like a retention problem often begins at the point of sale.
• Retention among high-value accounts: Losing one large account drags the average down harder than losing 10 small ones. Aiming a save motion at your largest accounts does more for ARPU than any pricing tweak.

These levers work on the numerator and the customer mix, and none of them adds accounts. Packaging and expansion tend to move fastest of the group.

An ARPU increase can also come from the denominator shrinking. If smaller customers leave, the remaining base spends more on average while total revenue and account count both fall. Founders should check whether customer count moved before treating a higher ARPU as progress.

How Usage and Outcome Pricing Change ARPU

Artificial intelligence (AI) products that do work previously done by headcount break the link between seats and value. Seat-based licensing is starting to give way to hybrid pricing models that blend consumption and outcome billing. Two customers on the same plan often consume amounts that differ by an order of magnitude, and automation raises output without adding a single human user. Seat count becomes a weak proxy for delivered value. The ARPU line then moves for reasons unconnected to how the business is performing.

Founders on usage or outcome pricing get more from a revenue-per-account figure normalized over a trailing window, reported with a note on usage volatility. A single monthly ARPU swings with consumption and invites the wrong conclusion. Hybrid models with a subscription floor plus usage keep the figure partly interpretable. CRV-backed Vercel sells developer infrastructure on a plan fee with usage charges layered on top, the shape most infrastructure companies have settled into.

How Investors Read ARPU at Seed and Series A

What a founder can show underneath the ARPU number shapes how a lead investor treats it. At seed stage funding, most companies don't have enough revenue history for ARPU to mean much on its own, and the number functions as a pricing hypothesis. By Series A, with a real base of paying customers and meaningful ARR behind it, the expectation shifts to trend and segment detail alongside retention.

ARPU Over Time

A single month's ARPU is close to meaningless on its own, because revenue and customer count move at once and either one can produce the change. Across six or 12 months on a fixed denominator, the trend separates improving monetization from pure volume growth. A trend only becomes legible when definitions and periods stay constant across updates. Restating the series with a footnote beats leaving it quietly redefined halfway through.

ARPU by Segment

Revenue per customer usually concentrates among a minority of accounts, and a blended average will not show that. An ARPU that jumped is the first thing an investor asks a founder to break out by plan, segment and cohort. Monthly and annual plans pushed into a single average describe neither group, and SMB and enterprise accounts blended together produce the same problem. That is the opening scenario in miniature. Tolerance for account concentration also tightens between seed and Series A, where what passed as an early bet starts to look like risk.

ARPU Next to Retention

A high ARPU says little about whether those customers stay. Net revenue retention and gross retention belong right next to it. Losing 20 percent of logos a year makes a $400 ARPU a weaker business than a $150 ARPU on a cohort that expands. LTV formulas fold ARPU and churn together, and errors in either one multiply instead of adding. CAC payback divides acquisition cost by monthly revenue per customer times gross margin, and it is where ARPU does visible work.

What ARPU Should Tell You Before Your Next Raise

A working ARPU definition comes down to one denominator, recurring revenue only, a period long enough for a trend to appear, and CAC and retention in view alongside it. Picking a denominator and keeping it for a full quarter is where most founders start. A three-month series on one definition is worth more than a 12-month series that changed underneath them twice. The $180 to $340 jump from the opening turns into a segment question once you can show the 200 accounts that didn't move and the one that did.

A defensible ARPU definition costs nothing to adopt and takes a quarter to prove out. If you're an early stage founder looking for an investor who will work through your pricing and unit economics at the board level, reach out to us to see if we'd be a good fit.

Frequently Asked Questions About ARPU

What's the difference between ARPU and MRR?

MRR is the total recurring revenue a company recognizes or normalizes for a month, and ARPU is that revenue divided by the number of users. The first gives you the size of the business, and the second breaks that size down per user. Two companies can post identical MRR with one serving 10,000 users at $18 and another serving 300 users at $600, and only ARPU separates them.

How often should you calculate ARPU?

Monthly works for subscription software, anchored to MRR so the figure stays consistent with the rest of your metrics. Consumer apps and games often track a daily version alongside the monthly figure, and businesses with sporadic usage such as travel and rideshare use longer reporting periods. A multi-month trend supports a conclusion. One large deal can move a single month on its own.

Do consumer apps and marketplaces measure ARPU differently?

Yes. Consumer apps and mobile games often use variants such as average revenue per daily active user (ARPDAU) for ad-driven products. ARPPU fits products where only a small share of users ever pay. Marketplaces earn revenue through a take rate on gross merchandise value and not through a subscription, so revenue per active buyer reflects transaction volume multiplied by that take rate.

Should free users count in your ARPU?

Free users belong in the denominator only when you're modeling free-to-paid conversion economics. For pricing decisions and investor reporting, leaving them out and reporting ARPPU isolates what paying customers generate. Whichever choice you make, label the denominator and keep it constant across every update.