Plan upgrades can look small at first, then they start paying rent. A single move to a higher tier can lift MRR, add expansion revenue, and hint at which customers are outgrowing the product.
When I watch Baremetrics plan upgrades, I am not chasing a vanity chart. I want to know who upgraded, when they moved, and what changed before that move.
If the billing data is clean, the story gets sharp fast. If it is messy, the chart turns into noise, so I start there.
Start with clean billing data
I start with integrating Baremetrics with Stripe, because the upgrade chart only makes sense when billing events line up cleanly. If the plan names are sloppy, the data feels like a shelf with no labels.
That means I keep plan names consistent, and I avoid mixing test accounts with live customers. A plan called “Pro Monthly” should not appear next to “Pro month” as if they are different products.
I also watch for one-time charges, refunds, and odd subscription edits that do not belong in upgrade analysis. Those items can blur the line between real expansion and billing noise.
When I clean the source data first, the rest of the dashboard reads like a ledger instead of a puzzle. That matters, because I want the upgrade trend to reflect customer behavior, not admin habits.
Read the Upgrades metric as revenue movement
Baremetrics tracks upgrades as customers moving to a higher spend plan. I treat that as a direct signal of expansion revenue. The count matters, but the MRR behind the count matters more.
Before I read too much into the trend, I keep Baremetrics’ SaaS metrics guide nearby. I also compare the pattern with subscription movement and upgrade rates, because upgrade counts alone can hide weak revenue impact.
I usually look at four things side by side:
| Signal | What I check in Baremetrics | Why it matters |
|---|---|---|
| Upgrade count | Upgrades by day or week | Shows how often customers move up |
| Expansion MRR | Revenue tied to those upgrades | Shows the dollar value of the move |
| Plan destination | Which plans customers move to | Shows which tiers pull demand |
| Customer segment | Group, size, or cohort | Shows who is upgrading |
That mix tells me whether upgrades are broad, concentrated, or tied to one pricing step. It also keeps me from calling a flat month “good” just because the count went up.
A higher upgrade count is useful. A higher expansion MRR is useful in the right way.
Break upgrades into patterns that reveal behavior
The first chart tells me what changed. The second chart tells me why it changed.
I start by switching between daily and weekly views. Daily data helps when a release, campaign, or pricing edit lands. Weekly data helps when I want the noise to settle and the real pattern to show up.
Then I split the upgrades by plan. If most customers move from one tier to the next, the ladder is working. If they stop right before the next jump, I inspect the jump itself.
That is where tracking net revenue retention in Baremetrics helps me. When upgrades rise but NRR stays weak, expansion is not carrying enough weight. Something else is pulling revenue back down.
I also keep subscription movement and upgrade rates in mind when I look at cohorts. A healthy pattern has shape. It does not look like random confetti on a chart.
If upgrades spike after an onboarding change, I read that as product fit or clearer value. If they spike after a sales push, I ask whether the pitch or the plan design did the work. Different causes need different follow-up.
Plan-level views are especially useful for growth teams. They show which features, limits, or prices create pressure for a move up. That pressure is where expansion revenue starts.
Turn upgrade data into pricing and retention decisions
Upgrade data earns its place when I use it to make decisions. A strong chart without action is only a nice-looking mirror.
If one plan gets most of the movement, I ask whether that tier is too easy to outgrow. It may be acting like a waiting room instead of a home. On the other hand, if no one moves up, the gap between tiers may feel too wide.
I also look at timing. Upgrades that cluster near renewal dates can point to value that takes time to prove. Upgrades that happen right after a feature release can show which product changes matter most.
Retention sits beside all of this. A customer who upgrades and then slips away a month later does not help much. I want the account to stay, grow, and keep growing.
For finance leaders, the cleanest read comes when I line upgrades up with MRR and NRR. For SaaS founders, the same view helps answer a sharper question, which parts of the pricing ladder are doing real work?
If I need a broader frame for that review, I return to tracking net revenue retention in Baremetrics. It keeps expansion revenue in context instead of letting it float alone.
A weekly review that keeps the numbers honest
I review upgrades on a steady rhythm, because one glance is never enough. A short routine keeps me from overreacting to one spike or one slow week.
- I compare the last seven days with the week before it.
- I split upgrades by plan and customer segment.
- I check expansion MRR beside total MRR and NRR.
- I note launches, campaigns, pricing edits, and support events.
- I write one follow-up for product, finance, or customer success.
That routine takes a few minutes, but it gives me a cleaner read on growth. It also makes it easier to explain the trend to people who need the short version.
When I see a rise, I want to know whether it came from product value, pricing structure, or timing. When I see a dip, I want to know whether customers paused, stalled, or found the next tier unclear.
What I take from the upgrade chart
Plan upgrades tell me how customers climb the ladder I built for them. In Baremetrics, the clearest view comes from clean billing data, the Upgrades metric, and segment views that show which customers are moving.
When I pair that with MRR and net revenue retention, I get a sharper picture of growth. I can see when expansion is healthy, when pricing needs work, and when retention is doing the heavy lifting.
A noisy chart can still hide a useful story. I just have to read the movement, not the count, and let the numbers point to the next decision.
