Skip to content
OperationsMetric 28 of 35

Forecast & Scenario Planning

Three numbers (new, expansion, churn) drive every SaaS forecast.

Abderrahim Ben Jazia, PhDBy · Founder of FlowMRR, previously built and sold AIS (Avance Immédiate Services), French tax-credit softwareUpdated:

Put this metric to work: explore FlowMRR's MRR analytics and forecasts to track revenue movements, retention and forecasts from your Stripe account, or see how FlowMRR compares as a Baremetrics alternative for Stripe.

A forward projection of MRR built from drivers. FlowMRR steps month by month from today's MRR: new MRR is new customers × ARPU, churned MRR is MRR × monthly revenue churn, and expansion or contraction applies to the MRR that survives. Its base scenario is seeded from your history; optimistic and pessimistic scenarios move churn, new customers, acquisition growth and expansion in opposite directions. The best forecasts are scenario-based, with the levers explicit so you can react to whichever shows up.

Formula

Next month's MRR = MRR + New customers × ARPU − MRR × Revenue churn + Surviving MRR × (Expansion − Contraction)

Worked example

Simplified monthly model: base 4.5% new + 1.5% expansion − 2% churn = 4% net growth. After 18 months, MRR is about 2.03× its starting value (1.04¹⁸). Downside: 2.5% new + 1% expansion − 3.5% churn = 0%, so MRR stays flat. Reactivation and contraction are assumed zero in both scenarios.

Other definitions you will see

Many forecasts extrapolate the MRR trend directly, for instance at a compound monthly growth rate, instead of modelling drivers. Sales-led companies often build top-down from pipeline and bookings, and some teams fit a statistical model to past MRR. These can agree over a few months and diverge widely over several years.

Illustrative comparisons

Forecast accuracy (90-day)

These unsourced ranges are illustrative scenarios, not measured industry benchmarks, percentiles or recommended targets. Their qualitative labels are editorial interpretations. Compare your own cohorts using the same segment, period, currency and measurement basis.

Tight
< 5% error
Usable
5–15%
Unreliable
> 25%

Why it matters

Forecasting forces you to write down your beliefs about the business. The forecast is rarely right in the absolute, but the discipline of comparing forecast-vs-actual every month is what separates founders who learn from those who guess. Scenario planning also exposes which variable matters most — usually churn, sometimes pricing.

Common mistakes

  • Single-scenario forecasts (you cannot act on them; you can only be right or wrong).
  • Forecasting in revenue instead of in the underlying drivers (new, expansion, churn).
  • Never going back to compare forecast vs actual — you learn nothing.

Calculating it from Stripe data

A driver-based forecast needs a starting point and a handful of monthly rates, all of which can be read from Stripe history. The starting point is today's MRR on the headline basis (annual plans ÷ 12, forever discounts deducted, trialing, incomplete, incomplete_expired and paused subscriptions excluded) and the number of distinct paying customers. The rates are new paying customers per month, revenue churn, customer churn and net expansion on the surviving base. Take every rate from complete months only: the open month is partial, and a forecast seeded from it starts with too little churn and too little new business.

Count new customers as people, not subscriptions. A second subscription from an existing customer is expansion and already sits in the expansion rate, so counting it as new books it twice. Average acquisition over several recent months rather than one, because a launch or campaign month is not a run rate. FlowMRR seeds its base scenario this way: current MRR and ARPU from the dashboard, churn from your recent churn history, new customers from the recent deduplicated average, and expansion or contraction backed out of your 12-month NRR, converted to a monthly step.

A cash view needs two more inputs, both available in Stripe: the share of MRR billed annually, since those customers pay twelve months at once when they renew, and the effective fee rate, Stripe fees divided by gross receipts over the same period. FlowMRR derives both from your history, falling back to a standard card-processing estimate when there is no fee history, and projects gross and net cash next to MRR.

Scenarios are deliberate changes to these drivers. FlowMRR's optimistic and pessimistic scenarios start from the base and move churn, new customers, acquisition growth and expansion in opposite directions; every input stays editable and you can add your own. Seasonality, learned from past MRR growth, and a survival mode in which churn eases with cohort age are optional rules you can inspect, not fitted statistical models.

Reading the result

The useful output is not the end figure but the gap between scenarios and the input that causes it. Change one driver at a time: if one point of monthly churn moves MRR in two years more than a 20% change in new customers, retention work is worth more than acquisition spend right now. Compounding makes churn dominate over long horizons, so a five-year scenario is mostly a statement about retention.

Each month, compare actual new, expansion, contraction and churned MRR with what the base scenario assumed, not just the totals. A total that matches by accident, extra churn offset by extra new business, hides a worsening driver. When one driver misses in the same direction several months running, update that seed rather than the whole forecast, and keep the earlier version so you can see whether your assumptions are improving.

Frequently asked questions

How do you forecast MRR for a SaaS?

Start from current MRR and project month by month: add new customers × starting MRR per customer, add expansion and subtract contraction on the existing base, then subtract churned MRR. Seed each rate from recent complete months, and build upside and downside versions by changing the rates, never the result.

How far ahead can you forecast SaaS revenue?

As far as you like arithmetically, but uncertainty grows every month because small rate errors compound. The next few months are mostly determined by customers you already have; multi-year projections depend on acquisition and churn assumptions and are best read as scenarios to compare, not predictions.

What is the difference between an MRR forecast and a cash forecast?

An MRR forecast projects the recurring run rate. A cash forecast projects when money arrives: annual plans pay a year upfront at renewal, payment fees and taxes come off, and failed payments delay or remove receipts. Two businesses with the same MRR forecast can have very different cash curves depending on their share of annual billing.

How should I build a downside scenario?

Move the drivers you are least sure of against you at the same time: higher churn, fewer new customers, slower acquisition growth and weaker expansion. Then check that the downside still fits inside your runway. A downside that only trims growth by a point is a sensitivity test, not a downside.

Contact us
FlowMRR

Let's talk

A question, a technical issue or an idea for a partnership? Write to the FlowMRR team.