Home » SaaS Foundations: The Guide for Technical Founders » Monthly Recurring Revenue (MRR): What It Means for SaaS (2026 Guide)

Monthly Recurring Revenue (MRR): What It Means for SaaS

You just closed your fifth paying customer. You’re at $2,400 in monthly recurring revenue, and someone on Indie Hackers already asked when you’re hitting $10k MRR.

If you’ve never thought about MRR before this moment, you’re not alone. Most technical founders ship their product, get their first customers, and only then realize that “how much money are we making” is not the same as “how much money do we predictably expect to make next month.”

MRR is the single most important metric for SaaS businesses. It’s what investors ask about first, what you use to decide whether to hire, and what determines whether your runway is six months or six weeks.

This article explains what MRR actually is — not the sanitized version VCs put in pitch decks — how to calculate it correctly, why your Stripe dashboard is probably misleading you, and how to grow it predictably.

What Monthly Recurring Revenue means and why it’s the north star metric for SaaS
How to calculate MRR using the five-component model (new, expansion, contraction, churned, net)
Monthly recurring payments vs one-time revenue and why the distinction matters
MRR vs ARR vs revenue — and when to use each
How to track MRR accurately when your billing gets complex
Common MRR mistakes that make founders overestimate their business
How pricing model changes cascade into your MRR — and what to watch for

What Is Monthly Recurring Revenue (MRR)?

Monthly Recurring Revenue (MRR) is the predictable, recurring revenue your SaaS business expects to collect from active subscriptions in any given month, normalized to a 30-day period.

The key word is recurring . If you sell a $500 setup fee, a $200 implementation service, or a one-time API key purchase, those are not MRR. MRR only counts revenue that repeats on a predictable cadence — primarily your monthly recurring payments .

MRR normalizes everything to a monthly basis. If a customer pays $1,200 annually, they contribute $100 to your MRR. If another pays $49 monthly, they contribute $49. This lets you compare annual contracts, monthly contracts, and mid-cycle upgrades on a single number.

Why MRR Matters More Than "Revenue"

Total revenue is noisy. MRR is signal.

Total revenue includes one-time charges, usage overages, support fees, and refunds. MRR strips all of that out and shows you what your business is fundamentally worth based on active subscriptions.

When a VC asks “what’s your revenue?”, they actually mean “what’s your MRR?” because MRR is the metric that tells them:

How long your runway lasts (runway = cash ÷ monthly burn; but MRR growth tells them whether burn is a problem)
How predictable your cash flow is
Whether you’ve found product-market fit (growing MRR without proportional increases in CAC)
How quickly you can scale (if MRR growth outpaces cost growth, scaling is profitable)

As a technical founder, you care about MRR because it’s the metric that connects your engineering work to business outcomes. Every feature that reduces churn, every onboarding improvement that reduces time-to-value, every pricing page tweak that improves conversion — it all flows through MRR.

The Five Components of MRR

MRR is not a single number. It’s a system of five moving parts. Understanding the components is what separates founders who manage their business from founders who’re guessing.

New MRR

New MRR is revenue from newly acquired customers during the month. If you onboarded three customers on $99/month plans, your New MRR is $297.

For early-stage founders, New MRR is the number you optimize with everything you do: content marketing, outbound, product-led growth, referral programs, launch platforms. It’s the top of the funnel quantified.

Reduce friction in your signup-to-first-payment flow (every additional click costs conversions)
Offer a free trial or freemium tier with clear upgrade triggers
Publish content that answers the questions your ICP asks before they’re ready to buy
Build in referral loops (e.g., “invite your team” flows that naturally add seats)

Expansion MRR

Expansion MRR (also called “upsell MRR”) is revenue growth from existing customers who upgrade their plan, add seats, or purchase add-ons during the month.

This is where recurring monthly payment amounts go up. A customer moves from $49/month to $99/month — you gained $50 in Expansion MRR. Or a customer adds five seats at $20 each — that’s $100 in Expansion MRR.

Expansion MRR is the highest-leverage growth lever because it costs zero in customer acquisition. You already have the relationship; you’re just extracting more value from it. Companies with strong expansion can maintain flat New MRR and still grow overall — though that’s usually a warning sign about top-of-funnel.

Design pricing tiers with clear value inflection points (the Pro plan should feel worth the jump from Starter when usage hits a threshold)
Build usage dashboards that show customers how close they are to limits — not as a threat, but as evidence their team is getting value
Trigger upgrade prompts at natural moments: when a user hits a usage cap, not via email blast

Contraction MRR

Contraction MRR (also called “downgrade MRR”) is revenue you lose when existing customers downgrade their plan. A customer moves from $199/month to $49/month — you lost $150 in Contraction MRR.

Contraction is not the same as churn. The customer is still with you, but they’ve decided your product is worth less than they thought. This is a product feedback signal you should not ignore.

Your pricing tiers may not align with actual value delivery
A customer’s use case may have shrunk (they left a project, downsized a team, found a cheaper alternative for a specific feature)
Your onboarding may have set expectations the product can’t sustain

Churned MRR

Churned MRR is revenue you lose when customers cancel entirely. If a customer on a $299/month plan cancels, you lost $299 in Churned MRR.

This is the metric that kills SaaS companies. You can build the most feature-rich product in the world, but if Churned MRR exceeds New MRR, you’re on a hamster wheel.

Voluntary churn: The customer actively cancels. This is usually a product-fit or value problem. Fix the product or the positioning.
Involuntary churn: The payment fails and the customer doesn’t fix it. This is usually a billing infrastructure problem. Fix your retry logic, dunning emails, and payment update flows.

Involuntary churn typically accounts for 20-40% of total churn across subscription businesses, according to data from Recurly and Churnkey. That’s revenue you’re leaving on the table with better billing infrastructure — smarter retry schedules, one-click card updates, and proactive payment alerts.

Net MRR

Net MRR (also called Net Revenue Retention when expressed as a ratio) ties all five components together:

Net MRR = Starting MRR + New MRR + Expansion MRR - Contraction MRR - Churned MRR

This is the number that matters. It tells you whether your business is growing organically. If Net MRR growth is positive even with zero new sales, you have a business that compounds.

Net Revenue Retention (NRR) expresses the same concept as a percentage:

NRR = (Starting MRR + Expansion MRR - Contraction MRR - Churned MRR) / Starting MRR

SaaS companies with NRR above 100% grow their existing customer base even without acquiring new customers. Top-tier SaaS companies hit 120-140% NRR. If you’re below 100%, your existing customers are shrinking as a group — you need new customers every month just to stay flat.

How to Calculate MRR Correctly

Here’s where most founders get it wrong.

The Naive Approach (Wrong)

Open Stripe dashboard, look at “Revenue this month,” call it MRR.

This is wrong because it includes:

One-time charges (setup fees, professional services, one-time API credits)
Usage-based overages (variable charges that aren’t recurring)
Refunds and chargebacks (which reduce actual revenue but aren’t always reflected in gross reports)
Proration from mid-cycle plan changes (which distorts the monthly number)
Multi-year annual contracts that haven’t been normalized to a monthly basis

The Correct Approach

MRR should include only the predictable recurring portion of active subscriptions, normalized to a monthly value:

List all active subscriptions at the end of the month
Extract the recurring portion — the base subscription fee, not usage overages or one-time charges
Normalize to monthly — divide annual contracts by 12, biweekly by 2, weekly by 4.33
Sum it up — this is your ending MRR

For the five-component analysis, you also need to track what happened during the month:

Which subscriptions started this month? (New MRR)
Which subscriptions increased in value? (Expansion MRR)
Which subscriptions decreased in value? (Contraction MRR)
Which subscriptions ended? (Churned MRR)

If your billing system doesn’t give you this breakdown natively, you’re either going to build it or you’re flying blind. This is the difference between a payment gateway (Stripe) and a subscription billing platform — the former processes recurring monthly payments , the latter tracks the lifecycle metadata you need to calculate MRR components.

MRR vs ARR vs Revenue

Three metrics, one underlying reality. Here’s when to use each.

Metric

Definition

Best Used When

MRR

Monthly Recurring Revenue, normalized to 30 days

ARR under $1M, weekly/monthly planning, early-stage fundraising

ARR

Annual Recurring Revenue (MRR × 12)

ARR above $1M, annual planning, board reports, Series A+ fundraising

Revenue

Total cash collected, including non-recurring

Cash flow management, tax filing, P&L statements

Never confuse revenue with MRR. Revenue is what you collected. MRR is what you expect to collect next month. Revenue is backward-looking. MRR is forward-looking.

How Pricing Models Affect Your MRR

The way you price your product fundamentally shapes your MRR profile.

Flat-Rate Pricing

Every customer pays the same amount. Simple to calculate: MRR = customer count × price. The problem is that flat-rate pricing leaves money on the table from heavy users and overcharges light users, which drives churn on the high end and weak activation on the low end.

Tiered Pricing

Multiple pricing tiers with different feature sets. MRR calculation requires summing across tiers: (Tier 1 customers × Tier 1 price) + (Tier 2 customers × Tier 2 price) + … Tiered pricing is the most common model for SaaS because it segments customers by willingness to pay. However, tracking MRR by tier is critical for understanding whether your tiers are actually working or whether everyone clusters at the bottom tier.

Per-Seat Pricing

Charge per user per month. MRR = total active seats × per-seat price. This is straightforward but creates a ceiling: customers resist adding seats because each one increases their bill. Watch for contraction when teams shrink or when customers share accounts to avoid adding seats.

Usage-Based Pricing

Charge based on consumption (API calls, tokens, storage, etc.). This complicates MRR because usage varies month to month. Pure usage-based businesses have two choices: (a) define MRR as a trailing 12-month average of usage revenue, or (b) use a hybrid model with a base subscription fee for MRR and usage as expansion/overage. The hybrid approach is what most companies land on because it gives you a stable MRR floor with upside from usage.

Common MRR Mistakes Technical Founders Make

1. Counting Trial Users as MRR

They’re not paying. They’re not MRR. A trial is a pipeline metric, not a revenue metric. Conflate the two and you’ll make hiring and runway decisions based on fiction.

2. Including One-Time Charges

Setup fees, implementation services, custom development — none of this is recurring. Strip it out. Your MRR should reflect what happens if tomorrow you stopped acquiring new customers and did zero professional services.

3. Not Tracking MRR Components

“MRR is $15,000” is not enough. If $8,000 of that is churned MRR, your business is losing more than it’s gaining. Track the five components. If your billing tool doesn’t give you this breakdown, you’re managing blind.

4. Ignoring Involuntary Churn

A card expires, the charge fails, the customer gets locked out, they don’t bother updating it because the dunning emails went to spam — that’s Churned MRR. Research indicates that eMarketer reports a 7-12% revenue loss from failed payments, while Chargebee’s data shows a 28-32% recovery rate with automated dunning. The 11% figure often cited refers to a specific case study’s recovery rate, not a broad statistic on inactive subscriptions. That’s revenue sitting in your billing system, lost to poor retry logic and missing payment update flows.

5. Comparing MRR Without Normalizing for Seasonality

If you sell B2B software, January and July are typically higher months (budget cycles). Comparing February MRR to January MRR without context is noise. Use month-over-month growth for short-term trends and trailing 12-month growth for strategic decisions.

How to Track MRR with Your Billing Infrastructure

Your billing system is your MRR system. If your billing infrastructure is a custom Stripe integration bolted onto your app, you’re probably undercounting or miscounting MRR.

What You Need from a Billing System for Accurate MRR:

Subscription lifecycle tracking. Every subscription needs a clear status: active, canceled, past_due, trial, paused. MRR only counts active subscriptions. If “past_due” subscriptions are still in your MRR count, you’re overcounting.
Proration handling. When a customer upgrades mid-cycle, Stripe prorates the charges. Your MRR calculation needs to understand that the proration credit from the old plan and proration charge for the new plan should resolve to the new plan’s monthly rate at the end of the cycle.
Usage-based revenue separation. If you charge both a base fee and usage overages, your system must separate these. The base fee is MRR. The usage overage is revenue but not MRR.
Webhook reconciliation. If your webhook handler crashes during a batch of subscription updates, you’ll have stale subscription states and your MRR will be wrong. Idempotent webhook processing is non-negotiable.
Historical MRR tracking. You need to calculate MRR for every past month to build trends. If you only track current MRR, you can’t calculate growth rates, which means you can’t forecast.

This is why the distinction between “payment processing” and “subscription billing” matters. Stripe processes payments. A subscription billing platform manages the entire lifecycle — plans, tiers, proration, dunning, webhooks, reporting — and gives you the data to calculate MRR components accurately.

How to Grow MRR: A Technical Founder's Checklist

Reduce time-to-first-value. Every day between signup and the customer experiencing value is a day they might cancel. Optimize onboarding: self-serve setup, pre-built templates, in-app guides.
Build usage dashboards. Show customers how much value they’re getting. When a customer sees they’re using 90% of their API quota, the upgrade feels justified, not upsold.
Implement smart retry logic. Don’t just retry failed charges once. Use exponential backoff with dunning emails: retry at 1 hour, 3 days, 7 days, 14 days. Send email notifications with one-click card update links. This alone can recover 30-70% of lost revenue from failed payments.
Design pricing tiers that guide expansion. Your Starter plan should make success possible but constraining. Your Pro plan should feel worth the jump when the Starter limits become painful. Your Enterprise plan should be a sales conversation for customers who’ve outgrown self-serve.
Track MRR components weekly, not monthly. Monthly MRR is what you report. Weekly MRR component tracking is what lets you catch problems before they become monthly reports. If Churned MRR spikes in week 2, you still have three weeks to respond.
Run pricing experiments. A/B test pricing pages. Test annual vs monthly toggle placement. Test feature visibility between tiers. Every percentage point of conversion improvement on your pricing page flows directly into New MRR.

Internal Links

SaaS Pricing Explained: Models, Strategies, and Best Practices — Understanding pricing models is the foundation for understanding how MRR behaves under different structures
Usage-Based Billing Explained: How It Works for SaaS — How usage-based billing complicates MRR tracking and why hybrid models exist
Recurring Revenue: A Guide for SaaS Founders — The broader category that MRR fits into (includes ARR, NRR, and revenue recognition)
SaaS Subscription Models Explained — How different subscription structures affect MRR predictability
Consumption-Based Pricing Models for SaaS — MRR implications of consumption pricing

External Resources

SaaS Metric Benchmarks by OpenView Partners — Industry benchmarks for churn, NRR, and growth rates by stage
CloudECON Usage-Based Pricing Benchmark — 2024 data on usage-based pricing adoption across cloud companies
Chargebee Subscription Metrics Glossary — Detailed breakdown of MRR components and calculation methods
Stripe Billing Documentation — Reference for subscription lifecycle management in Stripe

Rejected / Unverified Links

(No links were rejected during research. All external resources above were verified as valid and accurate.)

FAQ

What is Monthly Recurring Revenue (MRR)?

Monthly Recurring Revenue is the predictable, recurring revenue your SaaS business expects to collect from active subscriptions in a given month, normalized to a 30-day period. It excludes one-time fees, usage overages, and non-recurring charges. MRR is the north star metric for SaaS because it measures the sustainable revenue your business generates.

The basic calculation: add up all active subscription revenue in a month, normalized to a monthly value. For annual contracts, divide by 12. For the five-component analysis: Net MRR = Starting MRR + New MRR + Expansion MRR – Contraction MRR – Churned MRR.

MRR is Monthly Recurring Revenue. ARR is Annual Recurring Revenue, calculated as MRR × 12. They measure the same thing at different time horizons. Use MRR for businesses under $1M ARR (monthly granularity matters more). Use ARR for businesses above $1M ARR (annual numbers are less noisy).

It depends on your stage. Pre-seed companies should focus on absolute MRR trajectory (e.g., adding $5K-$10K in net new MRR monthly) rather than percentage growth, while Seed companies should target 2-3x annual growth and Series A companies should target 80-120% annual growth. Growth-stage ($5M+ ARR): 3-5% month-over-month is healthy. Year-over-year growth targets vary widely depending on market conditions and company maturity.

Pure usage-based revenue is variable, not recurring — so it technically doesn’t qualify as MRR. Most usage-based companies use a hybrid model: a base subscription fee (which is MRR) plus usage overages (which are revenue but not MRR). Some usage-based companies use a trailing 12-month average of usage as a proxy for MRR, but this is a lagging indicator.

Implement exponential backoff retry logic for failed charges, send dunning emails with one-click card update links, and support multiple payment methods. Involuntary churn typically accounts for 20-40% of total churn across subscription businesses, according to data from Recurly and Churnkey. That’s revenue recoverable with better billing infrastructure. Tools that handle automatic retries, payment method update reminders, and smart dunning can recover 30-70% of lost revenue from failed payments.