July 5, 2026

Your blended MRR is hiding a problem: visibility per subscription fixes that

Written by Josh @ Gleam

Same total MRR, three different stories

by plan

Team planPro planLegacy plan

Team plan

+18% this quarter

Pro plan

+6% this quarter

Legacy plan

-9% this quarter

A single MRR number is reassuring right up until it isn't useful. "MRR is up 4% this month" sounds fine, until you realize that number is an average of one plan growing 18% and another shrinking 4%, and the blended total just happened to land positive.

Averages erase the thing you need to see

When all you track is total MRR, you can't tell the difference between:

All three can produce the same headline MRR trend for months. The only way to tell them apart is to break MRR down by product or plan tier and watch the lines separately, not just the sum. (For the basics of how MRR itself should be calculated in the first place, see why knowing your real MRR and ARR matters.)

A worked example

Say a SaaS company runs two plans: Starter at $29/mo and Pro at $99/mo. At the start of the month, Starter contributes $8,700 in MRR (300 customers) and Pro contributes $9,900 (100 customers), for a blended total of $18,600.

Over the month:

Blended MRR ends the month at $18,940, up 1.8%. Read as one number, that looks like modest, healthy growth everywhere.

Split by plan, it's a different story. Starter is growing on volume: lots of small new signups outrunning a high churn count. Pro is not growing on new business at all; every dollar of its growth came from expansion within its existing base, while new-customer acquisition for the higher tier has stalled completely. Those are two different problems needing two different responses (Starter's churn rate is high and worth investigating; Pro's top-of-funnel for new customers has gone quiet), and the blended total actively hides both of them.

Why the underperformer matters even when the total looks fine

A subscription tier that's flat or shrinking while everything else grows isn't neutral: it's information. It might mean:

None of these get investigated if the only thing on the dashboard is the blended total. You need the per-plan breakdown to even know there's a question to ask.

What should you actually look at instead of the total?

The useful view isn't just "MRR by plan" as a snapshot. It's the movement breakdown per plan: how much of each plan's MRR is new, expansion, contraction, and churn this month. That's the same new/expansion/contraction/churn split described in why you shouldn't rely solely on the Stripe dashboard, just applied per plan instead of to the business as a whole. A plan can have flat net MRR while actually churning heavily and being masked by expansion from the customers who stayed. That's a very different story than a plan with genuinely low activity in every direction, and the worked example above is exactly that: Pro's net MRR moved in the right direction, but for a reason (upgrades from existing customers) that says nothing good about new customer demand for that tier.

In practice, this means the dashboard you check daily needs a plan-level (or product-level) breakdown as a first-class view, not a drill-down you remember to check occasionally. If checking per-plan movement takes an extra five clicks, most founders won't do it consistently enough to catch a slow-building problem before it's a large one.

How often should you actually check this?

Daily, not monthly. Both of the underperformance patterns above (a high-churn low-priced tier, a stalled top-of-funnel for a premium tier) are easiest to fix in their first few weeks and hardest to fix after a quarter of quietly compounding. A monthly board-deck cadence is fine for ARR; it's too slow for catching the specific plan-level problem before it's baked into next quarter's numbers. The per-plan movement breakdown is only useful if it's part of the thing you glance at every morning, not a report you pull when something already feels wrong.

The takeaway

If your revenue dashboard only shows one line, you're structurally unable to see this. Splitting MRR by product or tier, and watching each one's movement rather than just its total, is what turns "the number is fine" into "the number is fine because of X, despite Y," which is the actual conversation worth having.

This is exactly the view Gleam Revenue's MRR breakdown gives you automatically, split by plan and by movement type. Start your free trial →