Contents

What are the main revenue forecasting models for SaaS?

A SaaS company does not have one revenue stream, so it should not have one forecasting model. New business, expansion and renewals behave differently, and the right model for each follows from how that revenue is produced.

Four models cover most teams:

ModelWhat it readsBest fit
Pipeline model (weighted or decomposed)Open deals, stages, close datesNew business already in the CRM
Driver-based model (regression)Pipeline created, win rate, deal size, cycle length, headcountNew business and expansion
Time series modelThe history of revenue itself: level, trend, seasonalityRenewals, the subscription base, MRR trend
Bottom-up roll-upRep and manager calls by dealA judgment check on the current quarter
For short definitions of each type, see the glossary entry on revenue forecasting models. For the head-to-head between the two statistical methods, see regression vs time series forecasting. This guide is about the practical question: which model to run on which part of the number.
Put this to work on your numbers
Run your own numbers with the free Forecast Accuracy Scorecard, then see how ORM builds it into a custom model.

Which model fits which revenue stream?

Match the model to how the revenue behaves. New business is driven, renewals repeat, and expansion sits in between.
Revenue streamHow it behavesPrimary modelCheck against
New businessProduced by pipeline creation and conversionDriver-based modelDecomposition of the quarter
ExpansionDriven by usage, seats and account plans, with some pipelineDriver-based model on account signalsRenewal and usage history
Renewals and the recurring baseRepeats on a contract calendarTime series or a renewal schedule with cohort ratesAccount health and risk flags
Blending all three streams into one model gives you a forecast that is wrong about each of them. A renewal base that barely moves hides a new business miss, and a strong new business quarter hides churn building in the base.

New business: driver-based models

A driver-based model tells you which lever to pull. It takes pipeline created, win rate, average deal size, cycle length and headcount, fits the relationship between those inputs and revenue, and projects forward from where the inputs sit today.

The coefficients are the point. When a model says each dollar of pipeline created in a segment returns a set share of revenue two quarters later, you have a pipeline target, a marketing budget argument and an early warning indicator in one output.

It also reacts to change early, because the inputs move before the output does. Say pipeline creation falls sharply in March (illustrative). A driver-based model shows the damage in the forward number right away. A time series model keeps projecting the old trend until the revenue miss shows up in the series, one or two quarters too late to fix.

The trade is fragility. The inputs have to be measured the same way every period, and they have to exist for the forecast period. Feed the model many correlated features on a few dozen rows and it will fit noise.

Renewals and the recurring base: time series models

Time series is built for seasonality, because seasonality is exactly the pattern it is designed to extract.

SaaS revenue is rarely spread evenly. At many SaaS companies some quarters run stronger than others, and bookings often bunch into the last month of a quarter. A team that spreads an annual target evenly across twelve months has built a plan that looks behind for most of the year and then appears to recover in weeks that were always going to be heavy.

A seasonal decomposition separates the underlying trend from the repeating shape, so a soft January reads as a normal January rather than a crisis. That single correction removes a lot of noise from monthly variance conversations.

The catch is that it takes complete cycles to learn a cycle. With eighteen months of data, a model cannot tell a real seasonal dip from a one-time miss, so it treats a bad quarter as a permanent feature of the calendar. For contract-level renewal forecasting, lay out renewal dates and the ARR attached to each, then apply cohort rates by segment; the ARR forecast model guide walks through it.

How the models compare

DimensionTime seriesDriver-based (regression)
InputsPast revenue onlyPipeline, win rate, deal size, headcount
Answers whyNoYes, through coefficients
SeasonalityNative strengthMust be added as a term
Reacts to a pipeline dropOnly after revenue fallsImmediately
Data neededTwo to three years monthlyEnough rows for the feature count
Main failure modeProjects the past into a changed marketOverfits, or inherits bad driver data

Why do all revenue forecasting models miss when conditions shift?

Because a fitted model is a snapshot of assumptions, and the most common reason a forecast fails is that the business or the market changed while the model kept using the old ones.

The shifts that break models are not exotic. A new competitor enters and creates pricing pressure, so average deal size falls. Interest rates rise, private equity firms slow capital deployment, portfolio companies cut costs to protect earnings, and win rates drop. Broad uncertainty pushes buying committees to delay, so the time from qualified to closed stretches out. You redraw territories and execution suffers while the pipeline chart looks normal.

Each of those changes one of the parameters a model treats as fixed. Deal size, win rate and cycle length are the three numbers most forecasts quietly assume are stable, and they are the three that move first when the market turns.

A model that refits often on recent data picks that up. One retrained once a year will not. This is why forecast accuracy should be tracked as a running series rather than reported once at quarter end. Accuracy decaying over consecutive periods is the signal that your assumptions expired.

How should a RevOps team combine the models?

Run a driver-based model on new business, run time series on the recurring base, and reconcile both against a decomposed view of the quarter.

The reconciliation step is where most of the value sits. A statistical model produces a total, and a total cannot be managed. Break the quarter into what closes from existing pipeline, what has to be created and closed inside the quarter, and what might get pulled forward from later periods. Then check whether the statistical number and the decomposed number agree. When they disagree by more than a few points, one of them is carrying a broken assumption, and you have a specific thing to go look at.

No model removes the need for pipeline discipline. A time series model does not know whether next quarter's coverage exists, and a driver-based model does not know that a third of the pipeline it counted has not been touched in months. Both need a clean sales forecasting foundation underneath them. Start with how to forecast revenue, get the decomposition right, then add the models on top.

Frequently Asked Questions

What are the main revenue forecasting models for SaaS?

Four cover most SaaS teams: a pipeline model that weights or decomposes open deals, a driver-based model that fits revenue to inputs like pipeline created and win rate, a time series model that extends the history of revenue itself, and a bottom-up roll-up of rep and manager calls. Each one fits a different revenue stream, so most teams run more than one.

Which revenue forecasting model is best for new business?

A driver-based model, checked against a decomposition of the quarter. New business is produced by pipeline and conversion, so a model built on those inputs reacts as soon as they move and tells you which lever to pull. A time series model only sees the drop after revenue has already fallen.

Which model fits renewals and the recurring base?

Time series, or a contract-by-contract renewal schedule with cohort rates. Renewal revenue repeats on a known calendar and depends little on this quarter's selling, which is the pattern a time series model is built to extract, seasonality included.

How much history does each model need?

Time series needs enough complete cycles to separate seasonality from trend, which in practice means two to three years of monthly data. A driver-based model can work at the deal or weekly level, so eighteen months of clean opportunity records can give it more usable rows than a seasonal time series model gets from the same period.

Why do revenue forecasting models miss when the market changes?

Because every model learns from history and assumes the relationships hold. A new competitor lowers average deal size, higher interest rates slow buyer decisions and reduce win rates, and a territory change hurts execution while pipeline looks unchanged. A model fitted before those shifts keeps forecasting the old world until it is refit on data that includes the new one.

ORM Technologies
Pete has built custom revenue forecast models for B2B SaaS companies for over a decade.

See how ORM turns these insights into action

ORM builds custom revenue forecast models for B2B SaaS companies. Not dashboards. Prescriptive analytics that tell you what to do next.

Schedule a Demo