North Metric

    What is Average Revenue Per Account (ARPA)?

    The average monthly revenue generated by each paying customer — your monetization depth gauge.

    SAAS METRIC · UNIT ECONOMICSBy Riyad Yahya
    IN SHORT

    In North Metric's 2026 benchmarks, the median Average Revenue Per Account is $40 for SaaS companies under $10K MRR and $1,000 at $500K+ MRR. The top quartile reaches $100 and $5,000 at those stages, so compare your own figure with your MRR band, not one SaaS-wide average.

    BY RIYAD YAHYA, CO-FOUNDER & CTO · UPDATED NOV 14, 2026

    What is ARPA?

    Average Revenue Per Account (ARPA) is the average monthly revenue generated by each paying customer. It divides your total MRR by the number of active paid subscriptions, excluding free and trial users. ARPA gauges monetization depth — whether you’re moving customers to higher-value plans or losing pricing power.

    ARPA rising over time means customers are upgrading, adopting add-ons, or responding to price increases. Declining ARPA may signal discounting pressure, a shift toward smaller customers, or free-to-paid conversions that bring in lower-tier plans.

    ARPA is the numerator in Customer Lifetime Value. A $50 ARPA with 2% monthly churn gives a $2,500 CLV. Increasing ARPA directly increases the revenue you extract from every customer relationship.

    The ARPA formula

    Average Revenue Per AccountARPA = Total MRR ÷ Active Paid Subscriptions
    VARIABLEWHAT IT IS
    Total MRRSum of normalized monthly recurring revenue across all active subscriptions
    Active Paid SubscriptionsCount of subscriptions with effective MRR greater than $0 — free and trial subscriptions excluded
    Find money lost to old pricesMoney lost to old prices and endless discounts.See revenue leakage →

    Worked example

    Current month: Your company has $25,000 in MRR across 500 paying subscriptions.

    InputValue
    Total MRR$25,000
    Active paid subscriptions500
    Free/trial subscriptions (excluded)150
    ExampleARPA = $25,000 ÷ 500 = $50/month

    Each paying customer contributes $50 per month on average. The 150 free and trial users are excluded — including them would drop ARPA to $38.46, underrepresenting what your paying customers actually generate.

    What the plan mix tells you

    If 300 customers are on a $29/mo plan and 200 are on an $89/mo plan:

    ExampleTotal MRR = (300 × $29) + (200 × $89) = $8,700 + $17,800 = $26,500

    ARPA of $53 tells you the blended rate. If new signups consistently choose the $29 plan, ARPA will trend down over time even as MRR grows — a signal to revisit your pricing or upgrade path.

    How it’s computed

    ARPA is a Tier 1 metric — it depends directly on MRR and the paid subscriber count, both of which are computed from raw Stripe subscription data.

    VARIABLEWHAT IT IS
    Total MRRSum of normalized MRR across all active subscriptions — annual plans divided by 12, quarterly by 3, coupons applied after normalization
    Active Paid SubscriptionsCount of subscriptions generating effective revenue (MRR > $0) — a subscription with a 100% coupon is excluded

    Why “effective MRR” matters for the denominator

    A subscription on a $100/mo plan with a 100% coupon generates $0 in revenue. Should it count as a “paid” subscriber? North Metric says no — the denominator filters on effective MRR, not list price. This prevents coupon-heavy accounts from inflating the subscriber count and deflating ARPA.

    ARPA as a pricing power indicator

    Track ARPA over time to measure pricing effectiveness. Rising ARPA without proportional new customer growth means existing customers are upgrading or accepting price increases — strong pricing power. Falling ARPA despite growing MRR means you’re adding customers at lower price points — growth via volume, not monetization.

    Cross-validation

    ARPA has been cross-validated against ChartMogul. Results: within $0.01 on matched months (e.g., $13.17 vs $13.16), with 8 of 13 months matching exactly. Differences in the remaining months trace to how each tool reconstructs historical plan amounts — a common divergence between snapshot-based and event-sourced architectures.

    How ARPA feeds into CLV

    CLV = ARPA ÷ monthly customer churn rate. When ARPA is $50 and monthly churn is 5%, CLV is $1,000. Doubling ARPA to $100 doubles CLV to $2,000. ARPA is the most direct lever on customer lifetime value — every dollar of ARPA improvement multiplies across the entire customer lifetime.

    ARPA vs ASP

    ARPA and ASP both measure revenue per customer, but over different populations. ARPA reflects your entire paying base — the blended rate across all active subscriptions. ASP reflects only new signups — the average revenue from customers acquired this period.

    ARPAASP
    PopulationAll active paying subscriptionsOnly new subscriptions this period
    What it measuresBlended revenue per customer across the entire baseWhat new customers are paying at signup
    Includes upgrades/downgradesYes — reflects current plan mix including expansionsNo — only the initial plan choice
    Best forPricing analysis, CLV calculation, monetization trendsEvaluating sales efficiency, landing price trends
    Typical relationshipLags behind pricing changes (large base absorbs slowly)Leads pricing changes (shows where new deals are landing)

    Common ARPA mistakes

    1. Including free users in the denominator. Dividing MRR by all users (free + paid) produces ARPU, not ARPA. Including 200 free users alongside 500 paying customers drops the average from $50 to $36 — a 28% deflation that misrepresents your paying customer value.
    2. Using list price instead of effective revenue. A subscription on a $100 plan with a 50% coupon contributes $50 to MRR, not $100. If your denominator counts it at list price, ARPA and MRR tell different stories.
    3. Confusing ARPA with ASP. ARPA measures the entire base; ASP measures new signups only. Reporting ASP as “average revenue per customer” misses the impact of upgrades, downgrades, and pricing changes on your existing customers.
    4. Ignoring ARPA trend direction. A flat or declining ARPA alongside growing MRR means you’re adding volume, not monetization. Growth via volume is harder to sustain — you need more customers to hit the same revenue targets.

    SaaS ARPA benchmarks

    ARPA benchmarks are segmented by MRR tier. Higher is better. ARPA naturally increases with company maturity as products add features, pricing tiers expand, and the customer base shifts toward enterprise. The Seed median is $40/mo; the Enterprise median reaches $1,000/mo.

    Stage · MRRBottom 25%MedianTop 25%
    Seed · < $10K$15$40$100
    Early · $10K – $50K$40$100$300
    Growth · $50K – $100K$75$200$500
    Scale · $100K – $500K$150$400$1,500
    Enterprise · $500K+$300$1,000$5,000
    Higher is better. Benchmarks by revenue stage, compiled from published SaaS studies and North Metric’s own analysis.

    Frequently asked questions

    What is a good ARPA for a SaaS company?

    It depends on your market segment. SMB products typically range from $15–$100/mo, mid-market from $75–$500/mo, and enterprise from $300–$5,000/mo. The median across all stages is $40–$1,000/mo depending on MRR tier. More important than the absolute number is the trend — rising ARPA signals pricing power.

    What is the difference between ARPA and ARPU?

    ARPA (Average Revenue Per Account) uses only paying customers in the denominator. ARPU (Average Revenue Per User) typically includes all users — free, trial, and paid. ARPU produces a lower number because the denominator is larger. North Metric reports ARPA. Some tools label the same paid-only metric as ARPU, so always check which users are included.

    How does ARPA relate to CLV?

    ARPA is the numerator in the CLV formula: CLV = ARPA ÷ monthly churn rate. Every dollar of ARPA improvement multiplies across the entire customer lifetime. A $10 ARPA increase with 2% monthly churn adds $500 to CLV. Improving ARPA is one of the two ways to raise CLV (the other is reducing churn).

    Why is my ARPA different from other analytics tools?

    The most common difference is the denominator. North Metric and ChartMogul use paid subscriptions only. Some tools use all active customers (including free), producing a lower ARPA. Another source of difference is coupon handling — North Metric excludes subscriptions with 100% coupons from the paid count, while some tools include them.

    Should I track ARPA monthly or annually?

    Monthly. ARPA is derived from MRR (monthly recurring revenue), so the natural cadence is monthly. An annual version (ACV — Annual Contract Value) divides ARR by customers and is common in enterprise sales. For SaaS analytics, monthly ARPA is the standard because it aligns with churn rate, CLV, and retention metrics.

    From metric to action

    North Metric estimates the money leaking to old prices and discounts on your Stripe account. See revenue leakage.

    Further reading

    Related metrics

    All metrics →
    SAAS METRIC

    Customer lifetime value (CLV)

    CLV = ARPA ÷ Monthly Customer Churn RateTotal expected revenue per customer — CLV uses ARPA as its numerator.Open metric →
    SAAS METRIC

    Monthly recurring revenue (MRR)

    MRR = sum of each active subscription's normalized monthly amount, net of discountsMonthly Recurring Revenue — the total revenue base that ARPA divides across customers.Open metric →
    SAAS METRIC

    Average sale price (ASP)

    ASP = New Business MRR ÷ New Paid SubscriptionsAverage MRR of new subscriptions — tracks how deal size trends compare to your existing ARPA.Open metric →
    USAGE METRIC

    Metered ARPU

    Metered ARPU = Usage Revenue ÷ Metered customers with usageARPA's counterpart for usage-based revenue.Open metric →
    See the customers behind your ARPA.Actions off until you turn them onGet your free churn report →