Growth metric

MRR. The compounding heartbeat — and the easiest metric to lie to yourself with.

Monthly Recurring Revenue is what you'd bill this month if nothing changed — every active subscription, normalized to a monthly value. It's the simplest growth metric in SaaS and the one operators most often report dishonestly, almost always by accident. The mistake isn't usually in the formula. It's in reading the single number in isolation. MRR up 8% looks like a great month. MRR up 8% with churn doubled and expansion flat is a quietly broken business. The honest read isn't MRR. It's MRR movement: new, expansion, contraction, churn — and the net of all four.

What it is

The total recurring revenue you'd bill this month if every current subscription stayed active. Always reported as movement — new MRR, expansion MRR, contraction MRR, churned MRR — not just the aggregate. The single number hides the story.

Measurement period

End of month.

The standard view is MRR as of the last day of the month, with the four movement components broken out for the period. Annual contracts are divided by 12 to normalize. One-time fees never count.

Formula

MRR = Σ monthly subscription value across active customers

Annual contracts divided by 12. One-time fees never count.

When to review

Weekly.

MRR is one of the few metrics worth a true weekly review. If the month starts slow, you can still react before it closes. Monthly is the formal report. Weekly is the operating cadence.

Why it matters

MRR in isolation lies to you. MRR movement is the truth.

The simplest way to mess up MRR is to look at it in isolation. The aggregate number can go up while the business underneath is breaking. New-logo MRR can be flat while expansion masks an accelerating churn problem. Total MRR can grow while net new MRR collapses to zero. Each of those scenarios reports a healthy headline and hides the actual story. The discipline that protects you is reporting MRR as movement — new, expansion, contraction, churned — every single time. The aggregate is the consequence; the movement is the diagnosis.

At PipelineCRM, MRR was our primary internal operating number. ARR run-rate (MRR × 12) was the version we reported in board meetings and to investors. That split mattered: MRR is for operating, ARR is for the boardroom. Pick one as the primary internal metric and stop mixing them in the same conversation. If your team is drifting between MRR and ARR in the same meeting, you're going to make worse decisions than a team that picks one and sticks with it. The numbers are mathematically identical and operationally different.

The thing operators most often miss — and the thing I'd press on harder if I were doing PipelineCRM over — is the weekly cadence. MRR is one of the few metrics where weekly review actually changes the outcome. If you're four days into a month and new MRR is half what it should be, you can act on it. You can push reps, reprioritize deals, escalate champions, accelerate proposals. By month-end the data is just history. By Friday of week one, the data is still actionable. The teams that print better MRR aren't reviewing it monthly with regret. They're reviewing it Monday morning with leverage.

MRR is the simplest growth metric in SaaS. It's also the easiest one to mess up — almost always by reading it in isolation. Report the movement, every time.

Worked example

Three SaaS companies. Same MRR. Very different movement.

Each is a $500K MRR SaaS company that ended last month at exactly $510K — a clean 2% growth month on the headline. The movement underneath tells you which company is actually growing.

Healthy movement

+$10K

New MRR+$18K
Expansion+$6K
Contraction−$4K
Churn−$10K
Net new MRR+$10K

New-logo sales is doing the work, expansion is adding upside, churn is well below new. This is the company you want to be. Every component is contributing.

Hidden churn problem

+$10K

New MRR+$32K
Expansion+$3K
Contraction−$5K
Churn−$20K
Net new MRR+$10K

The headline looks identical. Sales is actually outperforming the healthy example. But churn is double the rate it should be, eating most of the new-logo work. The treadmill is on, the team is just running faster.

Expansion mirage

+$10K

New MRR+$8K
Expansion+$22K
Contraction−$6K
Churn−$14K
Net new MRR+$10K

New-logo sales has stalled. Expansion is carrying the number — which is great until it isn't. Without new logos feeding the base, this company runs out of expansion fuel in two or three quarters. The total looks fine. The motion is broken.

Benchmarks

Net new MRR by ARR stage.

Net new MRR — the four components summed — is the metric that actually matters. Below are typical monthly targets at each ARR stage. Read them as direction, not absolute targets.

Under $1M ARR

Net new MRR of $8K-$15K per month is the band most growing SMB SaaS lands in. Doubling annually at this stage means net new MRR has to keep pace with a doubling base — the bar moves up every quarter.

$1M-$5M ARR

Net new MRR of $20K-$60K per month, depending on growth rate. Most $1M-$10M ARR SaaS companies live here. Churn becomes a meaningful drag — a 2% monthly churn rate on $3M ARR is $5K dragging on every month.

$5M-$10M ARR

Net new MRR of $50K-$150K per month. Expansion MRR becomes increasingly important — at this scale, the cheapest growth dollar is the expansion dollar from an existing customer, not the new-logo dollar.

$10M+ ARR

Net new MRR of $150K+ per month sustained. The compounding base means a flat percentage growth rate requires more absolute MRR every month. Expansion is no longer a nice-to-have — it's the engine.

When MRR is decelerating

Three plays to diagnose what's actually wrong.

If net new MRR is slowing — say, you were printing $40K a month and now you're at $25K — the question isn't "how do we sell more." It's "where is the motion breaking." The three plays below are the sales-efficiency diagnostic we ran at PipelineCRM, in the order we ran them.

— 01 Check pipeline coverage first

If coverage isn't there, MRR won't be.

The first place to look when MRR decelerates is pipeline coverage. New MRR is the consequence of pipeline that existed 60-90 days ago. If coverage was thin two months back, MRR softness today is the predictable result. Coverage is the leading indicator that tells you whether next month's MRR is salvageable or already lost. Diagnose coverage before you diagnose anything else — the answer is often hiding two months upstream in numbers you already had.

— 02 Look at quota attainment by rep

Blended numbers hide which rep is actually broken.

Blended quota attainment is a flattering average. The honest read is rep-by-rep. If three reps are hitting and two reps are missing badly, that's a coaching and ramp problem with a clear fix. If everyone is missing by the same amount, that's a structural problem — the product, the pricing, or the GTM motion isn't working. You can't tell which without breaking it down by rep. At PipelineCRM, the rep-level view was always the one that showed us the actual issue. The blended number was the one that lied to us most.

— 03 Audit leads/MQLs/SQLs by channel

The channel mix changes faster than founders realize.

The third diagnostic is the channel-level top-of-funnel. Leads, MQLs, and SQLs broken out by channel — paid, content, referrals, partnerships, outbound — change shape faster than most founders realize. A channel that was driving 30% of MRR a year ago might be driving 8% today, quietly, without anyone flagging it. If MRR is decelerating, look at where the funnel volume is coming from this month versus the same month last year. The channel that used to work might have stopped, and the channel that's working might be one you haven't invested in.

Common mistakes operators make with MRR.

Reading MRR in isolation, without the movement.

The biggest single mistake. Total MRR can grow while net new MRR is zero or negative — when churn and contraction eat the new-logo work. The aggregate looks healthy, the underlying motion is broken, and nobody catches it until two quarters later when the headline finally collapses. Always report MRR as movement: new, expansion, contraction, churn. The aggregate is what you bill. The movement is what's actually happening.

Mixing MRR and ARR in the same conversation.

MRR and ARR are mathematically identical — ARR is just MRR × 12. But operationally they're different views. MRR is for operating, ARR is for the boardroom. Teams that drift between the two in the same meeting make worse decisions than teams that pick one as the primary number and stick with it. At PipelineCRM, MRR was the primary internal metric and ARR run-rate was the version we reported externally. Same number, different audiences. Don't let them collide.

Including one-time fees in MRR.

Setup fees, implementation fees, professional services, one-time training charges — none of them count. MRR is recurring revenue only. Mixing in one-time charges inflates MRR by a real dollar amount today and produces a phantom drop next month when those charges don't recur. The cleanest discipline: if the customer cancels tomorrow, would this revenue still bill next month? If not, it's not MRR.

Counting annual contracts at full value instead of dividing by 12.

A $24,000 annual contract is $2,000 MRR, not $24,000. This sounds obvious but operators get it wrong constantly, especially when reporting "new MRR" for a big quarter that landed several annual deals. Big annual contracts can make a single month's new MRR look spectacular if you forget to normalize them. The normalized view is the only honest view — and it's the version that lets you compare month-to-month meaningfully.

Not separating expansion MRR from new MRR.

Expansion MRR from existing customers and new MRR from new logos are fundamentally different motions. Expansion is cheaper, faster, and structurally easier — it's the customer success team's work. New MRR is the new-logo sales team's work. Reporting them together makes it impossible to tell whether sales is hitting or whether expansion is masking a sales miss. Always report the four components separately. The combined number is fine for the board deck. The decomposition is what runs the business.

Reviewing MRR monthly instead of weekly.

Most metrics are monthly metrics. MRR isn't. If you only look at MRR after the month closes, you've given up the ability to react inside the period. The teams that print better MRR are reviewing it Monday morning — week one, week two, week three — with enough month left to actually change the outcome. At PipelineCRM, weekly review of MRR was one of the operating disciplines that genuinely moved the number. Monthly is the formal report. Weekly is the cadence that compounds.

How Upbeat helps

MRR belongs on your Monday scorecard, decomposed.

Most teams report aggregate MRR and lose the diagnostic value. Upbeat puts MRR movement — new, expansion, contraction, churn — on your weekly scorecard alongside pipeline coverage and quota attainment by rep, so the diagnostic view is the default view.

See how it works → See pricing

Related metrics

Don't read MRR without the rest of the motion.

MRR is the headline. MRR movement is the story.

Upbeat puts MRR movement, pipeline coverage, and quota attainment together on your Monday scorecard — so the diagnostic view is the default read, every week.

Email Nick directly →