A healthy monthly MRR growth rate for bootstrappers

From the SoleOS answers series — written about our own product space; grounded in published definitions and documented behavior, never invented numbers.

There's no single healthy MRR growth rate that applies to every bootstrapper, and anyone quoting you "10-20% month over month" is usually describing venture-funded SaaS with paid acquisition budgets, not a solo founder's side project. What matters more is whether your growth rate is improving relative to your own baseline, holding up after you account for refunds and churn, and consistent enough across a few months that it isn't just noise.

The honest answer is: measure your own trailing 3-month trend first, then decide what "healthy" means for that specific product's stage and your time budget.

Why generic MRR growth benchmarks don't fit bootstrappers

Most published MRR benchmarks come from SaaS reports aggregated from VC-backed companies that raised money specifically to buy growth — paid ads, outbound sales, dedicated marketing hires. A 15% MoM target assumes a budget and headcount that a solo founder running one app, let alone ten, simply doesn't have.

There's also a math problem with small numbers. If a product goes from $200 MRR to $280 MRR, that's 40% growth — and it's meaningless as a signal. One annual plan or one refund can swing that percentage by double digits. Percentage growth rates only start to mean something once a product has enough subscribers that a single cancellation doesn't move the needle by more than a point or two. Below roughly $1-2k MRR, track absolute dollars added per month instead of percentages — it's less flattering and more honest.

Finally, benchmarks usually describe a single product's lifecycle. If you're running several apps at different stages — one mature, one just past launch, two in maintenance mode — a blended portfolio growth number hides more than it reveals. A declining mature product can mask a promising new one, or vice versa. This is one of the reasons portfolio reconciliation matters more as you add products: you need per-product trend lines, not just a combined total.

What a realistic growth rate looks like by stage

Rather than a universal percentage, think in terms of stage-appropriate expectations:

• Pre-$1k MRR: Growth is lumpy and driven by individual signups. The goal isn't a percentage, it's consistency — did you add net-new paying customers most months, or did a few bad months net out to flat? Absolute MRR added (in dollars) is the more useful number here.
• $1k-$10k MRR: This is where percentage growth starts to mean something, but double-digit MoM growth without paid acquisition or a viral loop is rare for a bootstrapper. Single-digit MoM growth (3-8%), sustained for several months, is a solid outcome for a product you're working on part-time.
• $10k+ MRR: Growth usually slows in percentage terms even as absolute dollars added per month increase, because the denominator is bigger. A product holding flat-to-slightly-up MRR while you redirect attention to a newer app is not a failure — it's a deliberate trade-off that portfolio founders make constantly.
• Mature / maintenance-mode products: Healthy here often means "net revenue retention near 100%, low effort required." Negative growth that's slow and expected (because you stopped actively marketing it) is different from unexpected churn acceleration, which is a signal worth investigating.

None of these numbers should be taken as a target to hit. They're a sanity check for whether your own result is in a normal range for that stage, so you don't panic over healthy flatness or celebrate unhealthy spikes.

Net new MRR vs. gross MRR vs. what you can actually bank

"Growth rate" also depends on which MRR you're measuring, and this is where reconciliation problems start. Gross new MRR (new subscriptions plus upgrades) looks great in isolation. Net MRR growth — after subtracting churn, downgrades, and refunds — is the number that actually reflects whether the business is getting bigger. A product can show healthy gross growth and flat or negative net growth if churn is quietly eating the gains, which is common in consumer subscription apps with monthly plans.

If you're running Stripe for web and RevenueCat for mobile, this gets more complicated: the two systems define and report churn differently, refunds flow through at different times, and currency conversion can shift dollar totals even with zero subscriber change. That's a big part of why a Stripe MRR number and a RevenueCat MRR number for the same product rarely match exactly — see tracking Stripe and RevenueCat together for the specific gaps to expect. When you're judging "is this growth rate healthy," make sure you're comparing net MRR to net MRR, not net to gross, across time periods.

Set your own baseline instead of chasing a benchmark

The more useful exercise than finding the "right" percentage is building a baseline from your own history:

1. Pull trailing 6-12 months of MRR per product (not blended across your portfolio).
2. Calculate month-over-month net MRR growth for each month.
3. Look at the median, not the average — one good month can skew an average badly for small numbers.
4. Decide what a 20% improvement or decline from that median would mean for your roadmap decisions — more time, less time, or a kill-criteria conversation.

This is slower than quoting a benchmark, but it's the only version of "healthy" that accounts for your actual acquisition channels, your pricing, and how much time you're putting into that specific product this quarter. For a worked example of what this looks like across a real multi-app portfolio, see real numbers from a 10-app portfolio.

Where SoleOS fits (and where it doesn't)

Disclosure: SoleOS is built by the same team writing this post, so take the following as an interested party's view, not a neutral one. SoleOS pulls MRR from Stripe and RevenueCat side by side per project, which makes it easier to see net MRR trend lines per product without manually reconciling two exports every month — useful specifically because the "healthy growth rate" question depends on getting net numbers right across both systems. If you want to see how that reconciliation looks with sample data before connecting anything, the live demo has no sign-up required.

That said, if you're running one product on one billing system, a spreadsheet pulling Stripe's own MRR report is probably enough — you don't need a multi-project tool to calculate a trailing 6-month trend for a single app. See SoleOS vs a spreadsheet for an honest breakdown of when the spreadsheet wins. SoleOS starts to earn its keep when you're reconciling MRR across three or more products and two or more billing systems and doing it manually is eating an afternoon a month. Check SoleOS pricing if that's the stage you're at.

Frequently asked questions

Is 10% MRR growth per month realistic for a bootstrapper?

It's possible early on with small absolute numbers, or later with a specific channel that's compounding (SEO, app store feature, referral loop), but it's not a reasonable baseline expectation for a part-time, ad-free bootstrapped product. Treat any month that hits it as worth investigating for the cause, not as the new normal to budget around.

Should I measure growth rate per product or across my whole portfolio?

Per product, always, at least first. A blended portfolio number can show flat growth while hiding one product declining and another growing — useful for your own overview, but it tells you nothing about which product needs attention. Aggregate only after you've looked at each line individually.

What counts as a warning sign vs. normal fluctuation?

One down month on a small-MRR product is usually noise — a canceled annual plan, a refund, a slow week. Two or three consecutive months of declining net MRR, especially alongside rising churn rate rather than just slower new signups, is worth digging into. The metrics dictionary has exact formulas for churn and net MRR if you want to check you're calculating both consistently.

Does annual-plan revenue distort my MRR growth rate?

Yes, significantly. How you normalize an annual subscription into "monthly" MRR (divide by 12 vs. recognize the cash upfront) changes your growth rate noticeably, and Stripe and RevenueCat don't always normalize it the same way. Pick one method, apply it consistently, and don't compare months where the mix of annual-to-monthly plans shifted a lot without accounting for it.

How much history do I need before a growth rate trend is meaningful?

Three months is a bare minimum to see a direction; six is better for smoothing out one-off events like a refund spike or a seasonal dip. For a newer product, don't over-read growth rates calculated from fewer than 20-30 days of data — the sample is too small for percentages to mean much yet.