About the Tiered Pricing Revenue
The Tiered Subscription Pricing Revenue Calculator adds up monthly recurring revenue (MRR) across a multi-tier SaaS or subscription pricing structure, where different customer segments pay different monthly prices. It multiplies each tier's customer count by its price, sums the three tiers into total MRR, and calculates the blended average revenue per customer across the whole base.
How It Works
Enter the number of customers and the monthly price for each of three pricing tiers. The calculator multiplies customers by price within each tier to get that tier's revenue, adds the three tier revenues together for total MRR, and divides total MRR by the combined customer count across all tiers to produce blended ARPU (average revenue per user). A breakdown table shows each tier's customer count, price, and resulting revenue side by side.
Examples
A typical three-tier SaaS mix
With 400 customers at $19, 150 at $49, and 30 at $149, tier revenues are $7,600, $7,350, and $4,470, for total MRR of $19,420 across 580 customers, giving a blended ARPU of $33.48.
A high-volume, low-price product
With 1,000 customers at $9, 200 at $29, and 20 at $99, total MRR comes to $16,780 across 1,220 customers, giving a blended ARPU of $13.75, notably lower because the customer base is concentrated in the cheapest tier.
Advantages
- Breaks total MRR down by tier, showing exactly which pricing tier is driving the most revenue, not just the combined total.
- Calculates blended ARPU automatically, a useful single figure for tracking whether the customer mix is trending toward higher or lower tiers over time.
- Lets a business quickly model what-if scenarios by adjusting customer counts or prices per tier without recalculating everything by hand.
Common Mistakes
- Comparing blended ARPU across two periods without noticing that a shift in customer mix between tiers, not a price change, is what actually moved the number.
- Forgetting that MRR here is a point-in-time snapshot and does not itself capture churn or new signups happening mid-period.
- Leaving a tier's customer count at zero for a pricing level the company genuinely does not offer, which is fine mathematically but can make a shared result misleading if not labeled clearly.
Edge Cases to Watch For
- If total customers across all three tiers is zero, blended ARPU is set to zero rather than producing a division-by-zero error, since there is no revenue base to average.
- The calculator assumes exactly three pricing tiers; a business with more or fewer tiers, or usage-based add-ons on top of a base tier price, would need to combine or approximate those into the three available slots.
- Revenue here is a snapshot MRR figure based on current customer counts and prices; it does not account for mid-cycle upgrades, downgrades, or churn happening within the period being measured.
- Blended ARPU is a weighted average across tiers, so it is pulled toward whichever tier has the most customers; a large low-price tier can keep blended ARPU low even when the top tier's price is very high.
Common Use Cases
- SaaS finance and RevOps teams calculating current MRR broken out by pricing plan.
- Product and pricing teams modeling how a proposed price change or new tier would affect total revenue.
- Founders reporting blended ARPU trends to investors as a signal of upmarket or downmarket customer movement.