# Revenue Per User (RPU)

> The average revenue each active user or account brings in over a period.

- Type: Calculator: Average dollars each user brings in
- Tags: Metrics, Pricing
- Growth levers: Revenue (primary)
- ~996 words

---

**RPU Calculator.** Average revenue each active user or account brings in. Inputs: Total revenue (period), Active users / accounts. Outputs: Revenue per user.

Revenue per user (RPU), also called average revenue per user (ARPU), is the total revenue you earn in a period divided by the number of active users or accounts in that period. It tells you how much each user is worth to you on average, which is the fastest read on whether your pricing and packaging are pulling their weight. Pick one period and one user count and keep them consistent, or the number stops meaning anything from month to month.

> **Formula:** RPU = total revenue in the period / active users in the period. Keep the numerator and the denominator on the same clock. Monthly revenue over monthly active accounts gives you monthly ARPU, which is the figure the benchmarks below use.

## How RPU is calculated

Worked example: you booked $240,000 in revenue last month and had 2,000 active accounts. RPU = $240,000 / 2,000 = **$120** per user for the month. That is the same number the calculator above returns for those inputs. Swap revenue for monthly recurring revenue if you want a pure subscription read, or keep total revenue if usage and services are part of how you actually get paid.

One decision moves this number more than the math does: who counts as a user. Divide by paying accounts and you get a clean monetisation read. Divide by every signup, free tier included, and you get a blended figure that drops every time a free user lands. Both are valid. Pick the one that answers the question you are asking, label it, and never quietly switch denominators between two reports.

## Revenue Per User (RPU) benchmarks by industry

There is no single "good" ARPU in dollars, because segment and pricing swing it by an order of magnitude. A self-serve tool billing $30 a month and an enterprise platform billing $5,000 a month can both be healthy. KeyBanc Capital Markets' SaaS survey puts the median monthly ARPU for public SaaS near $100, which anchors the SaaS median below. [ChartMogul's analysis of 2,500-plus subscription businesses](https://chartmogul.com/saas-metrics/arpa/?utm_source=productgrowth.blog) and OpenView/Insight Partners put the broader B2B SaaS median higher, past $210, which sets the good band, and the great band sits at the $500-plus level where the account is large enough to pay back an inside-sales motion.

| Industry | Median | Good | Great |
| --- | --- | --- | --- |
| SaaS | $100.00 | $210.00 | $500.00 |
| Fintech | $130.00 | $260.00 | $600.00 |
| Dev Tools | $60.00 | $130.00 | $320.00 |
| AI/ML | $130.00 | $260.00 | $600.00 |
| E-commerce | $25.00 | $60.00 | $150.00 |
| Healthtech | $140.00 | $280.00 | $650.00 |
| Martech | $90.00 | $190.00 | $460.00 |
*Monthly ARPU ($) · KeyBanc Capital Markets SaaS survey puts median monthly ARPU for public SaaS near $100, which anchors the SaaS median; ChartMogul (2,500+ subscription businesses) and OpenView/Insight Partners report the broader B2B SaaS median climbing past $210, and Culta's 2026 ARPU benchmark ($250 median B2B, up from $210 in 2024) sets the good band, with the great band at the $500-plus level where inside sales turns viable. Fintech and AI/ML run roughly 30% above SaaS: ChartMogul's higher-ARPA finance cohort and the 25 to 50% price premium AI tiers commanded in 2024-25 (Culta 2026) push both verticals up. Healthtech sits highest because regulated, compliance-driven buyers are the least price-sensitive. Dev Tools sits below SaaS (per-seat resistance and open-source substitutes hold ARPU down), and E-commerce SaaS lowest because it is cheap to buy and runs self-serve. Martech tracks the SaaS line. All figures are monthly ARPU in USD.*

Read the table by your own segment, not against the headline. Fintech and AI/ML sit roughly 30% above plain SaaS: finance buyers tolerate higher prices for deeper integrations, and AI tiers commanded 25 to 50% premiums in 2024-25, per [Culta's 2026 ARPU benchmark](https://culta.ai/blog/arpu-benchmarks-2026/?utm_source=productgrowth.blog), which also clocks the median B2B SaaS ARPU at $250, up from $210 in 2024. Healthtech runs highest because regulated, compliance-driven buyers are the least price-sensitive. Dev Tools sits lowest among the technical verticals, since developers resist per-seat pricing and open-source alternatives cap what you can charge. E-commerce SaaS lands at the bottom: cheap to buy, self-serve, high volume. Martech tracks the SaaS line.

## How to improve RPU

RPU climbs in one of two ways: each account pays you more, or the low-value accounts in your denominator pay you something. Expansion usually beats new-logo work here, because the customer already costs you nothing more to acquire.

- **Expand the accounts you already have.** Seats, usage, and upgrades raise revenue on users you keep at zero extra acquisition cost. This is the cleanest lift, and it shows up in net revenue retention before it shows up anywhere else.
- **Fix the packaging, not just the price.** Tiers that bundle the features people actually want, a usage component, and a sensible upgrade trigger move RPU more than a blanket price bump that pushes price-sensitive users to churn.
- **Convert or cut dead weight in the denominator.** A free tier full of users who never pay drags blended RPU down. Either move them up a tier with the right in-product nudge, or report paid ARPU separately so the figure stays honest.

## Related calculators

- [Customer lifetime value](https://www.productgrowth.blog/calculators/customer-lifetime-value-ltv): RPU times gross margin times average lifetime is your LTV, so this number feeds straight into it.
- [Monthly recurring revenue](https://www.productgrowth.blog/calculators/monthly-recurring-revenue-mrr): MRR divided by paying accounts is just subscription RPU, the recurring slice of this metric.
- [Expansion revenue](https://www.productgrowth.blog/calculators/expansion-revenue): the upsell and seat growth that lifts RPU on customers you already have.

#### What is a good revenue per user (RPU)?

A good RPU depends on your segment far more than on any single number. For B2B SaaS, KeyBanc's survey puts the median monthly ARPU for public companies near $100, broader datasets like ChartMogul push the median past $210, and a great figure sits at $500 or more, where an account is large enough to pay back an inside-sales motion. Self-serve tools can run healthy at $30 to $50 a month, while enterprise platforms clear $5,000. Judge yours against your own segment and your own trend, not the headline average.

#### How is RPU calculated?

RPU = total revenue in a period divided by active users or accounts in that period. For $240,000 of monthly revenue across 2,000 active accounts, RPU is $240,000 / 2,000 = $120 per user per month. Keep revenue and users on the same period, and keep the user definition fixed so the number stays comparable over time.

#### What is the difference between RPU and ARPU?

They are the same metric. RPU (revenue per user) and ARPU (average revenue per user) both divide revenue by users over a period. Some teams reserve ARPA (average revenue per account) for when the denominator is accounts rather than individual seats, which matters in B2B where one account holds many seats.

#### Should RPU count free users or only paying ones?

Either, as long as you are consistent and you label it. Paid ARPU divides by paying accounts and reads your monetisation cleanly. Blended ARPU divides by every active user including the free tier and tells you the average across your whole base. The blended figure drops every time a free user signs up, so do not compare a blended number in one report against a paid number in the next.

---

All posts: https://www.productgrowth.blog/archive · Site: https://www.productgrowth.blog