Monthly Recurring Revenue (MRR) Calculator
Calculate monthly recurring revenue from your number of subscribers and average revenue per user. The heartbeat metric of any subscription business.
Last updated: May 2026
Compare with similar
About this calculator
Monthly recurring revenue (MRR) is the predictable, normalized revenue a subscription business expects to receive every month, and it is the single most important metric for SaaS and other recurring-revenue companies. The simplest calculation is MRR = number of subscribers × average revenue per user (ARPU), where ARPU is the average monthly amount each customer pays. Normalizing to a monthly figure is the key idea: annual plans are divided by 12 and quarterly plans by 3 before being included, so MRR reflects a consistent monthly run rate regardless of billing frequency. MRR matters because it turns lumpy, unpredictable sales into a smooth, forecastable trend that reveals the true health and trajectory of the business — multiplying MRR by 12 gives the annual run rate (ARR). Investors and operators watch the components of MRR closely: new MRR from new customers, expansion MRR from upgrades, contraction MRR from downgrades, and churned MRR from cancellations, which together produce net new MRR. Edge cases and refinements: this calculator uses the headline formula, which assumes a single average price; real businesses with multiple tiers compute MRR by summing each plan's subscribers times its monthly price. One-time fees, setup charges, and usage-based overages should be excluded because they are not recurring. ARPU itself can be deceptive if a few large accounts skew the average, so segmenting by plan often tells a clearer story. MRR is a run-rate snapshot, not cash collected, and it does not account for the timing of payments or refunds.
How to use
Example 1 — 500 subscribers paying an average of $30 per month. Enter Number of Subscribers = 500, Average Revenue per User = 30. MRR = 500 × 30 = $15,000. Verify: this implies an annual run rate (ARR) of 15,000 × 12 = $180,000, a useful headline figure for the year. Example 2 — 1,200 subscribers at an average of $49 per month. Enter 1200, 49. MRR = 1200 × 49 = $58,800. Verify: the larger base and higher ARPU give an MRR that annualizes to about $705,600 — showing how both subscriber growth and price increases compound into recurring revenue.
Frequently asked questions
How do I handle annual or quarterly plans in MRR?
You normalize every plan to a monthly figure before including it. An annual subscription is divided by 12 and a quarterly plan by 3, so each contributes its true monthly run-rate rather than a lump sum. For example, a $1,200 annual plan counts as $100 of MRR. This normalization is essential — counting the full annual payment in the month it is received would wildly distort MRR and make growth look erratic. The goal of MRR is a smooth, comparable monthly number, so always convert different billing cycles to their monthly equivalent. Cash flow is tracked separately from MRR for exactly this reason.
What is the difference between MRR and ARR?
MRR is monthly recurring revenue, while ARR is annual recurring revenue — and for a pure subscription business ARR is simply MRR × 12. They measure the same recurring revenue stream at different time scales. Early-stage and product-led companies often track MRR because it captures month-to-month movement and reacts quickly to changes, while larger enterprise SaaS companies with annual contracts tend to headline ARR. Neither is 'cash collected' — both are run-rate metrics representing expected revenue if nothing changed. Use MRR for granular operational tracking and ARR for higher-level, annualized reporting and valuation conversations. Just be consistent and never mix the two scales in the same comparison.
What should be excluded from MRR?
MRR should include only genuinely recurring subscription revenue, so exclude one-time charges such as setup fees, implementation or onboarding fees, professional-services revenue, and one-off purchases. Usage-based overages that vary month to month are usually excluded from core MRR or tracked separately, because they are not predictable. Including these inflates MRR and undermines its purpose as a stable, forecastable metric. The acid test is whether the revenue will reliably recur next month under the same subscription — if not, leave it out. Keeping MRR 'clean' ensures it accurately reflects the durable, predictable core of the business.
Why can average revenue per user be misleading?
ARPU is an average, so it can hide important structure in your revenue. If a handful of large enterprise accounts pay far more than the typical customer, the average is pulled upward and may misrepresent the experience of most users. Conversely, many tiny accounts can drag ARPU down even if a few customers drive most revenue. This is why segmenting MRR by plan tier or customer type — rather than relying on a single blended ARPU — often reveals where revenue and growth actually come from. A rising ARPU could reflect either healthy upselling or simply the loss of small customers. Always look beneath the average before drawing conclusions.
When should I NOT rely on this simple MRR formula?
Avoid the single-ARPU formula when you have multiple pricing tiers with very different prices, since one blended average can distort the picture — instead sum each plan's subscriber count times its monthly price. It is also inappropriate for businesses with significant usage-based or one-time revenue, which is not recurring and should be excluded. MRR is a run-rate snapshot, not cash collected, so do not use it for cash-flow planning, which must account for billing timing, failed payments, and refunds. For deep analysis, track the MRR components (new, expansion, contraction, churned) rather than just the total. Use the simple formula for a quick headline figure and a tiered, component-based model for serious financial planning.