ARPU looks simple but hides sharp edges. Pick users or accounts, pick monthly or annual, and apply it the same way every time. A number that changes shape between slides stops meaning anything to the people reading it.
ARPU, or average revenue per user, is total revenue for a period divided by the number of users or accounts during that same period. Teams use ARPU to track pricing power, compare segments, and gauge whether expansion revenue is actually working. The variant ARPA, average revenue per account, swaps users for accounts and is the number most B2B subscription businesses actually track.
The six things to know about ARPU before you quote it in a pricing review, board deck, or growth plan.
ARPU is total revenue for a period divided by the count of users or accounts that produced it. Monthly ARPU uses monthly revenue and the monthly user count. Annual ARPU uses annual revenue and the annual count. Mixing the two periods is the fastest way to produce a number nobody can defend.
The straight calculation is total revenue in the period, divided by the number of paying users (or accounts, for ARPA) across the same period. Some teams use the average of the starting and ending counts, others use the ending count. Pick one definition, label it, and keep it consistent across every report.
ARPU tells you whether the price your product can command is going up, down, or sideways. A rising ARPU signals pricing power, expansion revenue, or a mix-shift toward larger customers. A falling ARPU signals discounting pressure, a shift toward smaller plans, or a product that is picking up users faster than revenue.
Consumer and freemium products usually track ARPU because the user is the paying unit. B2B subscription products usually track ARPA because the account is the paying unit and seats inside it can vary. Reporting ARPU on a seat-based product understates the number by whatever the average seat count is.
ARPU trends tend to lead ARR trends by a quarter or two. Rising ARPU without new logo growth still produces ARR growth. Falling ARPU with strong top-of-funnel still eats ARR eventually. Teams that watch ARPU catch pricing and mix problems before they show up in the annual run rate.
ARPU is calculated from billing data (what everyone pays) and CRM data (which accounts those payers belong to, what plan they are on, which segment they are in). A CRM like Strkr joins the two so ARPU breaks out by plan, by segment, and by cohort instead of landing in the deck as a single blended number.
There is no single ARPU calculation. There are a handful of variants that are all honest, and the only wrong move is using more than one in the same report. The paragraphs below walk through monthly ARPU, annual ARPU, the ARPA variant for account-level businesses, and the two user-counting conventions that most finance teams quietly disagree on. Pick a variant for your business, document it, and use it everywhere.
Monthly recurring revenue divided by the number of paying users at the end of the month, or divided by the average of the starting and ending counts. Common in consumer subscription, mobile, media, and freemium products. The month is short enough to catch pricing moves quickly and long enough to smooth over daily noise.
Annual recurring revenue divided by paying users across the year, usually the ending count or a weighted average. Common in B2B subscription where contracts are annual and monthly fluctuation is noise. The annual view is also the one that lines up with LTV calculations and most benchmark reports.
Revenue divided by the number of paying accounts rather than paying users. The right variant for B2B subscription, where one account can contain anywhere from a handful of seats to several thousand. ARPA is the number that moves when expansion inside existing accounts is working.
Freemium products must decide whether the denominator is paying users only or all active users. ARPU on paying users measures pricing. ARPU on total users measures free-to-paid conversion. Report both, label both.
A single blended ARPU is useful for trend lines and almost nothing else. ARPU broken out by plan, segment, channel, and vertical is where the real insight lives. Track blended ARPU for the board and segmented ARPU for the operating meeting.
ARPU does not have a universal benchmark the way the LTV-to-CAC ratio does. The right number depends on who you sell to, how you sell, and what you charge for. The paragraphs below describe the shape of ARPU across the common segments and go-to-market motions, so a founder or operator can judge whether their own number is in the right neighborhood without pretending there is one target the whole industry hits.
Consumer subscription businesses typically run the lowest ARPU of any segment, with the number paid for by very large user counts. Streaming, mobile apps, and consumer tools all sit here. The growth lever is user count and conversion from free to paid, not price.
Small-business SaaS tends to land in the middle, with pricing anchored to seats, usage, or small-scale plans. The growth lever is a mix of acquisition and expansion. Product-led motions can run a lower ARPU and make it up on self-serve volume, while inside-sales motions tend to run higher.
Mid-market B2B subscription almost always reports ARPA rather than ARPU, with the number materially higher than SMB because deals bundle more seats, modules, and services. The growth lever is deal size and expansion inside the install base, which is why net revenue retention becomes a load-bearing metric at this stage.
Enterprise ARPA is the highest of any segment and the most variable, driven by negotiated contracts, long sales cycles, and multi-year commitments. Benchmarks are less useful than peer comps. The right question for an enterprise team is whether ARPA is growing cohort over cohort, not whether it hits an industry median.
Usage-based pricing (API calls, compute, messages, storage) decouples ARPU from seat count entirely. ARPU rises as customers consume more, which can look like expansion revenue without any sales motion attached. The flip side is that ARPU falls just as fast when consumption drops, which makes forecasting harder.
ARPU is a famously easy metric to compute wrong. The formula is one line, the inputs are everywhere, and the error only shows up two quarters later when a pricing change gets credited to the wrong lever. The paragraphs below cover the five mistakes that show up on nearly every first-pass ARPU calculation, and what to do about each one before quoting the result to leadership.
A seat-based B2B product that reports ARPU per account one month and ARPU per seat the next month is reporting two different metrics and labeling them the same. Decide whether the unit is the user, the seat, or the account, document it, and use that same unit every time the number appears.
Including free users in the denominator produces a technically correct number that is operationally useless for pricing. Report ARPU on paying users for pricing analysis and free-to-paid conversion separately. Blending the two produces an ARPU that falls every time the top of funnel grows.
Monthly recurring revenue divided by annual user counts, or annual revenue divided by monthly users, both produce numbers that are off by a factor of twelve. Pick a period, use it everywhere in the calculation, and label the result with the period. Monthly ARPU is a different number from annual ARPU.
ARPU can rise because prices went up, because expansion worked, or because the business sold more to larger segments. The three stories have very different implications. Decomposing ARPU change into price, expansion, and mix is the step that turns the metric from a trend line into a diagnosis.
ARPU sits at the intersection of two systems: billing and CRM. Billing says what every customer pays. CRM says which account that customer belongs to, what plan they are on, which segment they are in, and how they came in. A revenue operations team that cannot join those two cannot calculate ARPU at the segment level, which is the only level where the number actually drives decisions. The cards below describe what each system contributes and how a modern CRM like Strkr pulls them together without a data warehouse project.
Invoices, plan upgrades and downgrades, add-ons, usage overages, discounts, and refunds. Billing data is the source of truth for the numerator of the ARPU calculation. Pulled into the CRM through a Stripe, Chargebee, or Zuora integration, it hangs off the account record and feeds the ARPU report directly.
The account identity, the plan tier, the segment, the acquisition channel, the sales motion, and the owner. Without this context, ARPU is a flat average. With it, ARPU becomes a per-plan, per-segment, per-channel number that acquisition, pricing, and retention teams can actually use.
The point of a modern CRM is that the account record is the join key. Billing events and CRM relationship data hang off the same object. ARPU becomes a report that reads from one place instead of a quarterly spreadsheet reconciliation, which is where most ARPU reports go to die.
Mature revenue teams track ARPA not just across the install base but also over time inside individual accounts. The number for a cohort of accounts six months in versus eighteen months in tells the expansion story in a single line. Net revenue retention is the roll-up. Cohort ARPA is where the detail lives.
Once billing and CRM are joined, ARPU becomes a dashboard metric with the same refresh cadence as pipeline and ARR. Rolled up by plan, by channel, by vertical, and by cohort. The quarterly spreadsheet reconciliation is replaced by a report the leadership team can actually trust between reviews.
Strkr pulls billing events into the account record alongside pipeline, segment, and acquisition data, so ARPU and ARPA break out by plan, channel, and cohort instead of landing as a single blended number. Marketing, pipeline, and documents live in the same tool, which is why the metric stays honest between reviews.
ARPU stands for average revenue per user. It is the total revenue a product or company generates in a period, divided by the number of paying users during that period. In B2B subscription businesses the related variant ARPA, or average revenue per account, is usually the more useful number because the account rather than the individual user is the paying unit.
The formula is total revenue for the period divided by the number of paying users (or accounts, for ARPA) during that same period. Monthly ARPU uses monthly recurring revenue and the monthly user count. Annual ARPU uses annual recurring revenue and the annual user count. The two periods are not interchangeable, and mixing them in the same calculation produces a result that is off by a factor of twelve.
ARPU uses the paying user as the denominator. ARPA, average revenue per account, uses the paying account. The two numbers can be identical in a product where every account has exactly one user, and wildly different in a seat-based B2B product where one account can contain hundreds of users. Consumer and freemium products usually track ARPU. B2B subscription products usually track ARPA.
There is no single benchmark that applies across SaaS, because ARPU depends heavily on segment, pricing model, and go-to-market motion. SMB SaaS typically runs a lower ARPU than mid-market, which runs lower than enterprise. Product-led motions tend to produce lower ARPU than sales-led motions in the same segment. The useful question is whether the ARPU is growing cohort over cohort, not whether it hits an industry median.
ARPU is a per-period revenue number. LTV, or customer lifetime value, is the total gross profit a customer is expected to generate across the full relationship, which is a function of ARPU, gross margin, and churn. ARPU is one input to the LTV calculation. The two metrics answer different questions and should be reported separately.
Monthly for most companies, with a cohort or segment-level view refreshed quarterly. ARPU moves in response to pricing changes, plan mix shifts, discount programs, and expansion revenue. Teams that trust ARPU the most are the teams that watch it the most often, because the trend line is often a leading indicator of ARR changes a quarter or two later.
Revenue is rising faster than the user count would predict only if ARPU is growing. Revenue going up while ARPU falls means the user count is growing faster than revenue, which usually points to a mix shift toward smaller plans, a discount program that is working harder than planned, or a successful push into a lower-ARPU segment. The direction of ARPU is often more informative than the direction of total revenue.
A modern CRM like Strkr pulls billing events through a Stripe or similar integration, hangs them off the account record, and joins them to the plan, segment, and acquisition data already on that record. ARPU and ARPA then become dashboard reports rather than quarterly spreadsheets. The calculation itself is simple arithmetic. The hard part is the data join, and that is what the CRM provides.
No sales call, no migration consultant, no four-month implementation. Enter your card, get 14 days of the full Pro tier, cancel any time before day 14 with zero charge. Spin up a workspace, import your CSV, and have something useful before lunch.
