ARPA is your portfolio's average deal size, not a proxy for booking quality
ARPA answers one question: what does the average customer in your base pay today? That number sets the baseline for unit-economics modeling, cohort analysis, and capacity planning. A rising ARPA over time signals that your go-to-market motion is landing larger accounts or that expansion is working. A falling ARPA signals a mix shift that deserves investigation.The formula is straightforward:
ARPA = Total ARR / Total Active CustomersRun it monthly or quarterly on a consistent snapshot date so trends are comparable.
Segment ARPA to find the signal
Blended ARPA flattens differences across plan tiers, geographies, and acquisition channels. The useful version is segmented:
| Segment | Why it matters |
|---|---|
| Plan tier (Starter, Pro, Enterprise) | Reveals whether your tier structure is pulling customers upmarket |
| Cohort by contract start quarter | Shows whether newer customers enter at higher or lower values than earlier ones |
| Channel (inbound, outbound, partner) | Identifies which motion produces the most valuable accounts |
| Market segment (SMB, mid-market, enterprise) | Separates mix-shift effects from true pricing movement |
How ARPA connects to capacity and unit economics
ARPA is an input to several downstream calculations. Sales capacity models use it to estimate how many accounts a rep must close to hit quota. Finance teams use it alongside churn assumptions to project ARR trajectories. And cohort-level ARPA feeds expansion rate analysis, because a cohort that started at a higher ARPA will generate more absolute expansion dollars even at the same percentage growth rate.
Watch for ARPA compression when you enter a new segment. Selling down-market to capture volume can accelerate customer count while suppressing ARPA, which changes the economics of support costs, onboarding, and rep payback.
Using ARPA in practice
ARPA is most useful as a trend line, not a point-in-time number. Set a cadence, calculate it consistently, and watch it relative to the segments that matter to your business. Tie it to your annual contract value tracking at the deal level and your net revenue retention at the portfolio level to get a complete picture of deal quality over time. Rising ARPA combined with strong retention is the clearest signal that your customer mix is moving in the right direction.
Frequently Asked Questions
How do you calculate average revenue per account?
Divide your total ARR (or MRR) by the number of active paying customers at that point in time. If you want segment-level insight, apply the same formula within a cohort, such as a specific plan tier or company size band, rather than across the entire base.
What is the difference between ARPA and ACV?
Annual Contract Value (ACV) is a deal-level metric calculated at the time of signing and normalized to one year. ARPA is a portfolio-level metric calculated across your existing customer base. ACV tells you what new business is worth at close; ARPA tells you what your customer base looks like today.
Why does ARPA move in the wrong direction even when new bookings are strong?
ARPA dilutes when a high volume of small new logos joins the base faster than expansion revenue lifts existing accounts. It can also compress when lower-tier plans outpace enterprise growth. Tracking ARPA by cohort separates these effects.
Put these metrics to work
ORM builds custom revenue forecast models that turn concepts like average revenue per account (arpa) into prescriptive action for your team.
Schedule a Demo