Skip to article
Revenue & retention

How to build a bottom-up SaaS revenue forecast

A bottom-up SaaS revenue forecast starts with customers: how many subscribe, what they pay, when service starts, and whether they renew. Forecast each acquisition cohort, apply its pricing and retention assumptions, and add the cohorts together. Keep recurring revenue, cash collections, and one-time fees separate so each result can be explained.

In this guide

Build the customer assumption before the revenue line

Start with new subscriptions per month. Support that estimate with something observable, such as paid conversions, signed contracts, or a documented sales plan. A market-size percentage alone cannot tell you when someone signs up or pays.

If your sales plan begins with leads and conversion rates, calculate the expected signups separately and enter the resulting acquisition schedule. Startup Model Builder accepts new-customer assumptions and monthly overrides; it does not automatically turn a CRM pipeline into customers.

Use separate products when prices, billing terms, or retention behavior differ enough to affect the decision. Keep the first version small. You should be able to explain why a product needs its own forecast before adding another line.

Trace a simple subscription forecast

Assume a new business starts with zero subscribers, adds 20 each month, and charges $50 per month. For this illustration, 90% of existing subscribers renew at every monthly renewal. New subscribers receive a full month of service. There are no setup fees, discounts, expansion, taxes, or failed collections.

The recurrence is active subscriptions this month = prior month's active subscriptions × monthly renewal retention + new subscriptions. Expected customer counts can be fractional in a forecast; that represents an average outcome, not part of a person.

Illustrative monthly forecast with 90% monthly renewal retention
MonthRetained from prior monthNewActive, expectedMonthly revenue
102020$1,000
2182038$1,900
334.22054.2$2,710

Build this subscription forecast in Startup Model Builder. Set the monthly product price and acquisition assumptions, then use explicit monthly renewal rates for this example.

Match retention to the billing period

The 90% in our example is monthly renewal retention. It is not 90% annual retention. Entering the same number under the wrong period changes the forecast substantially. Label the rate and its interval wherever you record the assumption.

In the builder, explicit first, second, and later renewal rates follow a product's billing cadence. A monthly product renews monthly; an annual product renews annually. After explicit periods, the long-term annual rate is converted to the billing cadence. The cohort retention guide explains the conversion and conditional survival.

To investigate a result, follow one acquisition cohort through its renewals. Then add the cohorts together. This makes it easier to identify whether revenue changes because of acquisition, retention, or pricing.

Read revenue, collections, and ARR as different measures

Under the example's full-month assumptions, month-three recurring revenue is $2,710. Multiplying that monthly recurring amount by 12 gives a $32,520 annualized run rate. That is a snapshot scaled to a year, not a prediction that the following year will earn exactly $32,520.

Setup fees and scheduled other revenue should stay outside that recurring run rate. An annual prepayment also creates a different cash pattern from a monthly subscription, even when the service earns the same amount each month. See the billing comparison before treating collections as revenue.

Define the metric in the report you share. A label such as revenue can otherwise conceal a choice between earned revenue, contracted value, and cash received. Use the builder's separate report rows to keep the explanation consistent.

Challenge growth with a specific alternative

Duplicate the forecast and lower new subscriptions while keeping pricing and retention unchanged. That isolates acquisition risk. Then try a different renewal schedule in another scenario. Changing both without a reason makes it harder to see what drove the result.

Once revenue is traceable, connect its delivery costs and hiring requirements. A forecast that adds customers without the costs needed to serve them gives an incomplete view of the business. Our COGS guide shows how to choose those cost drivers.

Before using the forecast, record what would change your mind about acquisition or retention: a revised sales plan, a signed contract, or another cohort reaching renewal. When that evidence arrives, update the relevant input and compare the result with the previous version.

Related questions

Can I use a growth percentage for new customers?

Yes, if you can explain its basis and timing. Review the implied customer counts, and use monthly overrides for known launches or signed deals. A percentage is a convenient input, not evidence that those customers will arrive.

Why does displayed customer count differ from revenue divided by price?

The builder retains precision in cohort calculations while displaying whole subscription counts. Pricing tiers, discounts, setup fees, and multiple products can also make aggregate revenue divided by one price misleading. Inspect product and cohort detail.

Give every revenue number an explanation.

Model acquisition, subscription prices, billing terms, and renewal assumptions together. Then inspect the cohorts behind the forecast.

Model your subscription revenue