SaaS Pricing Calculator — MRR, ARR & Blended ARPU in 60 Seconds

Every recurring-revenue business eventually lives or dies by three numbers: monthly recurring revenue (MRR), annual recurring revenue (ARR), and blended average revenue per user (ARPU). This calculator computes all three live as you edit your tiers, so you can see exactly how a price change, a new plan, or a shift in your customer mix moves the topline. If the term itself is new to you, our glossary entry on what SaaS means is a good two-minute primer.

The math is intentionally transparent. Each tier contributes its normalized monthly price multiplied by its customer count to total MRR. Annual-billed tiers are divided by twelve first, so a plan billed at $1,990/year is counted as roughly $165.83/month of MRR — the same way every serious SaaS metrics dashboard normalizes it. ARR is MRR times twelve. Blended ARPU is total MRR divided by your total customer count across every tier, which is the cleanest single signal of whether your base is drifting toward low-touch self-serve accounts or higher-value customers.

Why blended ARPU is the number to watch

Founders obsess over MRR growth and under-watch ARPU. That is a mistake. You can grow MRR while quietly destroying unit economics if every new customer lands on your cheapest plan. A blended ARPU that trends down as you scale means each new account brings less revenue but roughly the same support burden, the same infrastructure cost, and the same billing complexity. Watching ARPU alongside MRR is how you catch that drift before it shows up as a margin problem in a board meeting.

What churn really costs you

The churn line is the one most pricing spreadsheets skip. We apply your monthly revenue-churn percentage to current MRR, annualize it, and surface the net-new MRR you must add every single month just to stay flat. At 5% monthly churn you are effectively re-acquiring more than half your revenue base every year before you grow a dollar. That is why reducing churn is almost always cheaper than acquiring your way around it — and why the billing experience (failed-payment recovery, clean upgrade paths, proactive renewals) is one of the highest-leverage things an early SaaS team can invest in.

Assumptions and what this calculator deliberately leaves out

This is a topline model, not a full cohort engine. It does not model expansion revenue, cohort decay curves, seasonality, discounting, or the cash-flow timing benefit of annual prepay beyond the MRR normalization. It assumes the customer counts you enter are steady-state. Those simplifications are exactly what make it useful for a quick gut-check — and exactly why a fundraise- or board-grade model layers them back in. When your pricing surface gets genuinely complex (usage-based tiers, seat-based plus metered hybrids, grandfathered legacy plans), the modeling and the underlying billing logic both become real engineering. That is the work we do, and the multi-tenant SaaS architecture guide covers the data-model side of getting it right from day one.

When pricing becomes an engineering problem

There is a predictable moment when pricing stops being a spreadsheet exercise and becomes a build. It is the point where you have multiple tiers with real upgrade and downgrade flows, proration on mid-cycle changes, metered overages, and dunning for failed payments. At that stage, gluing it together with ad-hoc Stripe webhooks creates reconciliation debt that eventually lands on someone's desk. Our Next.js and Stripe integration guide walks through doing it cleanly, and our SaaS platform development practice exists precisely to own that layer for you.