Average revenue per user is one of the most revealing metrics in SaaS. It tells you who your customers are, how you price your product, and where your growth ceiling lives. Two companies with identical MRR can have completely different trajectories depending on whether that MRR comes from 10 customers at $5,000/month or 1,000 customers at $50/month.

B2B SaaS ARPU ranges from $20-50/month for self-serve products to $5,000+/month for enterprise solutions. The 2026 median across all B2B SaaS is approximately $250/month, up from $210/month in 2024, driven by pricing increases and expansion of usage-based models.

This post covers how to calculate ARPU, 2026 benchmarks by segment and vertical, ARPU trends over the past two years, four strategies to increase your number, and the important differences between ARPU, ARPA, and ARPPU.

What ARPU Is and How to Calculate It

ARPU measures the average monthly recurring revenue generated per customer or account. The formula is simple:

ARPU = MRR / Number of Active Customers

Some companies use "accounts" instead of "users" in the denominator, which is an important distinction we will cover later. For now, the standard SaaS convention is to divide total MRR by total paying customers.

Worked Example

Your SaaS product has $500,000 in MRR and 2,000 paying customers.

ARPU = $500,000 / 2,000 = $250/month

Each customer generates an average of $250 per month. This single number tells you a lot: you are likely selling to SMBs or lower mid-market, your sales motion probably involves some outbound but is not pure enterprise, and your product likely has moderate complexity.

It is worth noting that ARPU is an average, and averages can be misleading. If you have 1,900 customers paying $50/month and 100 customers paying $5,000/month, your ARPU is $500K / 2,000 = $250/month. But the reality is that a small number of large accounts are driving half your revenue. Segment your ARPU to see the real picture.

Track your ARPU alongside other key metrics using a SaaS metrics calculator to understand how it relates to your overall revenue health.

2026 Benchmarks by Segment

ARPU varies dramatically based on your target customer segment. Here are the 2026 benchmarks, drawing from KeyBanc's annual SaaS survey and OpenView's product benchmark data.

Self-Serve / PLG ($20-$50/month)

Self-serve products where customers sign up with a credit card and never talk to a salesperson typically see ARPU between $20 and $50 per month. These products compete on ease of use, low friction, and volume. They need thousands of customers to build meaningful revenue.

Examples include project management tools, design collaboration platforms, and developer tools at the individual or small team tier. Companies in this range typically grow through product-led growth, content marketing, and viral loops.

The upside: low CAC, fast sales cycle, predictable cohort behavior. The downside: scaling revenue requires massive customer volume, and churn tends to be higher because switching costs are low.

SMB ($50-$200/month)

Small business SaaS products with some level of onboarding or sales involvement typically land between $50 and $200/month. This segment represents the largest number of B2B SaaS companies by count.

Products in this range usually offer enough complexity to justify a light sales touch, such as a demo or guided setup, but not enough to require a dedicated account manager. Annual contracts are common but not universal.

The SMB segment has been under pricing pressure for years, with many companies successfully raising prices 15-25% between 2024 and 2026 without significant churn increases. If you have not raised prices in the past 18 months, you are likely leaving money on the table.

Mid-Market ($200-$2,000/month)

Mid-market SaaS serves companies with 100 to 1,000 employees and typically involves a proper sales cycle with demos, evaluations, procurement, and implementation. ARPU ranges from $200 to $2,000/month depending on product complexity and seat count.

This is where pricing strategy becomes critical. The difference between $200 and $2,000/month is often not the product itself but how it is packaged: per-seat vs per-account pricing, tier structure, add-on modules, and usage-based components.

Companies in this range benefit from testing their pricing model with a pricing strategy calculator to find the optimal configuration for their market.

Enterprise ($2,000-$10,000+/month)

Enterprise SaaS selling to companies with 1,000+ employees commands ARPU from $2,000 to well above $10,000/month. These deals involve long sales cycles (3-12 months), multiple stakeholders, custom implementations, and dedicated customer success managers.

The top quartile of enterprise SaaS companies report ARPU above $8,000/month, often driven by usage-based components that scale with the customer's business. Enterprise ARPU tends to expand significantly over time as deployment grows within large organizations.

2026 Benchmarks by Vertical

ARPU also varies significantly by vertical. Here are median figures for 2026:

Vertical	Median ARPU	Range
DevTools	$75/mo	$20-$500
HR / People	$150/mo	$50-$800
Marketing Tech	$200/mo	$50-$2,000
Sales / CRM	$250/mo	$75-$3,000
FinTech / Payments	$400/mo	$100-$5,000
HealthTech	$500/mo	$150-$5,000
Security / Compliance	$600/mo	$200-$10,000
Infrastructure	$800/mo	$100-$15,000

DevTools tend to have the lowest ARPU because developers resist high per-seat pricing and many products compete with open-source alternatives. Security and infrastructure have the highest because the buying decision is driven by compliance requirements and risk mitigation, where price sensitivity is lower.

ARPU Trends 2024-2026

Three significant trends have shaped ARPU movement over the past two years.

Pricing power has returned

After the 2022-2023 downturn where many SaaS companies froze pricing to retain customers, 2024-2026 saw a return to regular price increases. KeyBanc's 2024 survey found that 68% of SaaS companies raised prices, with a median increase of 12%. Companies that raised prices saw minimal incremental churn, suggesting that most SaaS was underpriced heading into 2024.

Usage-based pricing is expanding ARPU

Companies that adopted usage-based or hybrid pricing models between 2024 and 2026 saw median ARPU increases of 20-35% compared to flat subscription-only models. Usage-based components naturally expand ARPU as customers grow, creating a built-in expansion mechanism.

OpenView's 2025 benchmarks show that companies with at least 25% usage-based revenue have net dollar retention 15 percentage points higher than pure subscription peers. The MRR and ARR relationship becomes more dynamic with usage-based models, as monthly revenue fluctuates with customer activity.

AI features command premium pricing

SaaS companies that launched AI-powered features in 2024-2025 were able to charge 25-50% premiums for AI tiers. This has been a significant ARPU driver, with companies reporting that 30-40% of their customer base upgrades to AI tiers within six months of launch.

Four Strategies to Increase ARPU

If your ARPU is below the median for your segment, here are four proven strategies to move it upward.

1. Implement Tiered Pricing

If you have a single pricing tier, you are leaving money on the table from customers who would pay more for additional features or capacity. The standard structure is three tiers: a starter tier for price-sensitive customers, a professional tier for your core ICP, and an enterprise tier for larger accounts.

The professional tier should be your default, priced where most of your target customers will land. The starter tier exists to capture customers who might otherwise churn, while the enterprise tier exists to capture the full willingness to pay from your most valuable accounts.

Companies that move from single-tier to three-tier pricing typically see a 15-30% ARPU increase within two quarters as customers sort themselves into appropriate tiers.

2. Add Usage-Based Components

Pure per-seat pricing caps your ARPU at the number of seats a customer buys. Adding a usage-based component, such as API calls, records stored, emails sent, or transactions processed, removes this ceiling.

The key is to tie the usage metric to customer value. If customers get more value as they use more of your product, a usage-based component is natural and fair. If the metric feels arbitrary (e.g., charging per login), it will create resentment.

Hybrid models where you charge a base subscription plus usage above a threshold tend to perform best. The base subscription provides revenue predictability while the usage component enables expansion.

3. Enable Seat Expansion

If your product is seat-based, make adoption easy so that teams naturally expand. This means reducing friction for adding new users, building features that benefit from collaboration, and providing admin tools that make it easy for department leads to onboard their teams.

Companies with strong seat expansion see 5-15% ARPU growth per year purely from existing customers adding seats. This is one of the lowest-effort expansion mechanisms because it requires no sales involvement.

4. Launch Feature Upsells

Identify high-value features that a subset of your customers would pay a premium for. These might include advanced analytics, custom integrations, premium support, or specialized modules for specific use cases.

Package these as add-ons that any tier can purchase. This approach is less disruptive than restructuring your core pricing because it layers on top of your existing model. A $50/month add-on attached to 30% of your customer base increases overall ARPU by $15/month without touching any existing pricing.

ARPU vs ARPA vs ARPPU

These three acronyms are often confused but measure different things.

ARPU (Average Revenue Per User)

Calculated as MRR / total paying users. Each individual user counts separately. If a company has 10 employees using your tool at $50/seat, that is 10 users contributing to the denominator.

ARPA (Average Revenue Per Account)

Calculated as MRR / total paying accounts. Each company or organization counts as one account regardless of how many users they have. The same company with 10 employees counts as one account contributing $500/month.

ARPA is more useful for B2B companies because it reflects how much each customer relationship is worth, which better aligns with sales and success team structures.

ARPPU (Average Revenue Per Paying User)

Calculated as MRR / paying users only, excluding free users. If you have a freemium model with 10,000 free users and 1,000 paying users generating $100K MRR, your ARPU is $9.09/month (dividing by all users) but your ARPPU is $100/month (dividing only by paying users).

ARPPU is more relevant for freemium businesses because ARPU gets diluted by the large free user base and does not reflect the actual monetization of converted customers.

Which Should You Track?

Track ARPA for B2B SaaS to understand account-level economics. Track ARPPU for freemium models to understand monetization efficiency. Track ARPU when communicating with investors who use it as a standard benchmark across companies.

Check where your ARPU sits relative to peers using the SaaS revenue benchmarks for additional context on revenue-per-customer metrics across stages.

Using ARPU in Financial Planning

ARPU is a critical input for revenue forecasting. Multiplying projected customer count by projected ARPU gives you a revenue forecast. But both numbers move independently, which creates forecasting complexity.

When building financial models, project ARPU separately from customer count. Factor in planned price increases, expected expansion revenue, and the mix shift between segments (adding more enterprise customers raises ARPU even without price changes).

If you are projecting ARPU increases, be specific about the mechanism. "ARPU will increase 15% next year" is vague. "ARPU will increase 15% because we are launching a usage-based component in Q2 and raising starter tier pricing 10% in Q3" is actionable and verifiable.

Key Takeaways

ARPU is not just a number. It is a reflection of your market position, pricing strategy, and growth potential. Low ARPU means you need high volume to build revenue. High ARPU means you need fewer customers but longer sales cycles and more support investment.

The 2026 benchmarks are clear: self-serve products land at $20-50/month, SMB at $50-200/month, mid-market at $200-2,000/month, and enterprise at $2,000-10,000+/month. If your ARPU is below the median for your segment, prioritize tiered pricing, usage-based components, seat expansion, and feature upsells.

Track ARPU monthly, segment it by customer tier and cohort, and model it forward in your financial projections. A 10% ARPU increase has the same revenue impact as a 10% increase in customer count, but it is usually far cheaper to achieve.

Sources

KeyBanc — 2024 SaaS Survey. Annual survey of 100+ private SaaS companies providing ARPU, growth, and retention benchmarks by segment and stage.
OpenView — 2025 Product Benchmarks. Comprehensive benchmarks on product-led growth, usage-based pricing, and their impact on ARPU and net dollar retention.

ARPU Benchmarks 2026: What Good Looks Like