What is ARPA?
Average Revenue Per Account (ARPA) is the average monthly revenue generated by each paying customer. It divides your total MRRby 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
| Variable | What it captures |
|---|---|
| Total MRR | Sum of normalized monthly recurring revenue across all active subscriptions |
| Active Paid Subscriptions | Count of subscriptions with effective MRR greater than $0 — free and trial subscriptions excluded |
What's your ARPA?
Connect Stripe and see your ARPA calculated automatically — paid subscribers identified, free trials excluded, MRR normalized.
Benchmark My ARPAWorked example
Current month: Your company has $25,000 in MRR across 500 paying subscriptions.
| Input | Value |
|---|---|
| Total MRR | $25,000 |
| Active paid subscriptions | 500 |
| Free/trial subscriptions (excluded) | 150 |
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:
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.
| Variable | What it captures |
|---|---|
| Total MRR | Sum of normalized MRR across all active subscriptions — annual plans divided by 12, quarterly by 3, coupons applied after normalization |
| Active Paid Subscriptions | Count 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.
| ARPA | ASP | |
|---|---|---|
| Population | All active paying subscriptions | Only new subscriptions this period |
| What it measures | Blended revenue per customer across the entire base | What new customers are paying at signup |
| Includes upgrades/downgrades | Yes — reflects current plan mix including expansions | No — only the initial plan choice |
| Best for | Pricing analysis, CLV calculation, monetization trends | Evaluating sales efficiency, landing price trends |
| Typical relationship | Lags behind pricing changes (large base absorbs slowly) | Leads pricing changes (shows where new deals are landing) |
If ASP is consistently lower than ARPA, new customers are coming in at lower price points. Your base ARPA will eventually decline as the lower-paying cohorts grow.
If ASP is higher than ARPA, new customers are landing at premium tiers. Your ARPA will trend upward as the higher-paying cohorts dilute the legacy base.
The gap is your pricing trajectory. A widening ASP-below-ARPA gap is an early warning of monetization erosion, even if total MRR is still growing.
Common ARPA mistakes
- 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.
- 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.
- 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.
- 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. Early-stage median is $40/mo; growth-stage median reaches $1,000/mo.
| MRR Tier | Range | Bottom 25% | Median | Top 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 |
| ARPA benchmarks from 1,400+ Stripe-verified SaaS companies. | ||||
Where does your ARPA rank?
Benchmark your Average Revenue Per Account against 1,400+ SaaS companies at your MRR stage.
Benchmark My SaaSFrequently 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.
Ready for metric clarity?
Connect Stripe and let AI build your metrics system. No manual setup, no guesswork.
Get Started