Driver-Based Revenue Forecasting (With Template)

What Is Driver-Based Revenue Forecasting?

A revenue forecast is a projection of the money your business will earn over a defined future period. There are two ways to build one:

Top-down forecasting starts with the total addressable market and works down to a market share assumption: “The UK B2B software market is worth £10 billion. If we capture 0.1%, we generate £10 million in revenue.” Useful for sizing the opportunity, useless for operational planning. Investors have heard thousands of 0.1% market share projections and are rightly sceptical.

Bottom-up, driver-based forecasting starts with the specific activities that generate revenue: “We have capacity to run 20 outbound sales conversations per week. Our conversion rate is 10%. Our average contract value is £12,000 per year. That gives us 2 new customers per week, or roughly 100 new customers per year, generating £1.2 million in new ARR.” Every assumption in that chain is testable, improvable, and explainable.

Driver-based forecasting is also the input layer for your 3-statement model — your revenue drivers feed the income statement, which integrates with the balance sheet and cash flow statement.

Why a Revenue Forecast Startup Needs a Different Approach

Established businesses forecast revenue by extrapolating historical data. Startups do not have historical data. The entire forecast must be built on forward-looking assumptions rather than trend lines. A driver-based model built on transparent assumptions is actually more useful to an early-stage investor than a statistical extrapolation, because it makes the business logic explicit and discussable.

The Core Framework: Identify Your Revenue Drivers

SaaS Revenue Drivers

For a subscription software business, the core drivers are:

1. New customers per period — driven by sales/marketing activity.
2. Average revenue per user (ARPU) — driven by pricing tiers and plan mix.
3. Monthly churn rate — driven by product quality and customer success.
4. Expansion revenue rate — upsells and upgrades as a proportion of existing MRR.

From these four drivers, you build a complete MRR waterfall: Opening MRR + New MRR (new customers × ARPU) − Churned MRR (opening MRR × churn rate) + Expansion MRR (opening MRR × expansion rate) = Closing MRR.

Illustrative SaaS Revenue Build

Illustrative example with invented figures. Does not represent any real company.

Assumptions: Month 1 new customers: 5, growing by 3 per month. ARPU: £200/month. Monthly churn: 2.5%. Monthly expansion rate: 1%.

Results: Month 1 — 5 customers, closing MRR £1,000. Month 3 — 24 customers, closing MRR £4,746. Month 6 — 73 customers, closing MRR £15,229. Month 12 — 237 customers, closing MRR £46,507 (approximately £558,000 ARR).

The model is built entirely from four assumptions. Change any one of them and the whole revenue trajectory updates. Note the compounding effect of churn: at 2.5% monthly, annual churn is approximately 26%. OpenView’s SaaS Benchmarks suggest median gross revenue churn for SMB-focused SaaS is 10–15% annually; enterprise-focused SaaS typically sees 5–8%.

E-Commerce Revenue Drivers

For a transactional e-commerce business, the revenue drivers are:

1. Monthly sessions — driven by organic search, paid traffic, email.
2. Conversion rate — driven by product, pricing, UX.
3. Average order value (AOV) — driven by product mix and upsells.
4. Repeat purchase rate — driven by retention, subscription, loyalty.

Revenue = Sessions × Conversion Rate × AOV × (1 + Repeat Purchase Contribution).

Illustrative e-commerce example: 10,000 sessions in Month 1 growing 15% per month, 2.5% conversion, £45 AOV. Month 1 revenue £11,250. Month 6 revenue £27,155. Month 12 revenue £62,904. Adding a repeat purchase uplift from Month 3 onward increases Month 12 revenue to approximately £75,485 in this illustrative scenario.

Marketplace Revenue Drivers

For a marketplace or platform, Revenue = GMV × Take Rate. Your forecasting challenge is building a credible GMV model that accounts for both sides of the marketplace and managing the chicken-and-egg supply/demand dynamic explicitly.

How to Set Defensible Driver Assumptions

1. Use Your Own Early Data

Even five customers worth of data is data. If you have run a pilot, what was your actual conversion rate from demo to close? Early, imperfect data beats benchmarks because it is specific to your product and market.

2. Reference Published Benchmarks (and Cite Them)

For SaaS: Bessemer’s State of the Cloud provides gross margin, ARR growth, and CAC benchmarks by stage. OpenView’s SaaS Benchmarks covers CAC payback, NRR, and churn by ARR cohort. When you use a benchmark, cite it in your model assumptions tab. “Churn assumption: 2.5% monthly, in line with OpenView median for SMB SaaS at sub-£1M ARR” is far more credible than an unexplained figure.

3. Work Backwards from Sales Capacity

A standard benchmark for SaaS AE productivity is 4–6 new logos per month per AE at SMB price points, or 1–2 enterprise deals per quarter per AE at higher ACVs. Use these to sanity-check whether your new customer assumptions are achievable with your planned headcount.

4. Scenario-Test Your Assumptions

Present a base case, a downside case (churn 50% higher, new customer acquisition 30% lower), and an upside case. The downside case is particularly important: it should show that even in a worse-than-expected scenario, the business is fundable and the raise buys meaningful runway.

Connecting Revenue Drivers to the Full Financial Model

Revenue drives COGS. Hosting costs, payment processing fees, and customer support costs all scale with revenue or customer count. If your revenue model shows 5x customer growth over 18 months, your COGS model should reflect the corresponding scaling.

Customer acquisition targets drive Sales & Marketing spend. If your revenue model requires 20 new customers per month and your blended CAC is £2,000, you need £40,000/month in customer acquisition spend. Our unit economics calculator helps you model CAC, LTV, and payback period in detail.

Headcount drives R&D and G&A costs. Your revenue growth assumptions should be consistent with the engineering and success team you plan to build.

Revenue timing affects cash. Annual upfront payments generate cash before revenue is recognised. If your revenue mix includes a meaningful proportion of annual plans, your cash flow statement will look better than your P&L — a feature of SaaS working capital that a driver-based model should make explicit. Our financial model calculator connects your revenue drivers directly to an integrated three-statement model.

Revenue Forecast Startup: Common Mistakes and How to Fix Them

Straight-Line Growth Rates Without a Mechanism

“Revenue grows at 10% per month” is not a driver-based forecast. Identify the mechanism — more sales capacity, higher marketing spend, improved conversion — and model it. The growth rate should be an output rather than an input.

Ignoring Seasonality

Most businesses have seasonal demand patterns. A B2B SaaS business may see longer sales cycles in August and December. If your model shows perfectly smooth monthly growth, investors will notice and question it.

Modelling Revenue Recognition as Cash

Recognised revenue and cash received are not the same thing. If you invoice on net-30 terms, cash arrives a month after revenue is recognised. Your revenue drivers feed the income statement (recognised revenue). Cash timing is a separate modelling step in the cash flow statement.

Not Updating the Model With Actuals

A forecast never compared against actuals is not a planning tool. Build a simple actuals vs. forecast variance analysis into your model. Review it monthly. Update your forward assumptions based on what you are actually observing. This practice — sometimes called rolling forecasting — is the habit that distinguishes founders who understand their business from those who are guessing.

How Investors Evaluate Your Revenue Forecast

Investors evaluate revenue forecasts on three dimensions:

Logic: do the drivers make sense for the business model? Are the mechanics right?

Credibility: are the assumptions grounded in data (your own or benchmarked)? Are they cited?

Sensitivity: does the founder know what happens to their model if the key assumptions are wrong?

The goal is not to be accurate — no early-stage forecast is accurate — but to be defensible, logical, and informed. For further reading on how your revenue model feeds into the broader financial picture, see our guides on startup financial models and the 3-statement model.

Get the Free Revenue Forecasting Template

Download the Raise Ready SaaS financial model template — a pre-built driver-based revenue model for SaaS, with a structured revenue waterfall, cohort analysis tab, and scenario toggle ready to populate with your own assumptions. For the complete founder finance framework, the Raise Ready book covers everything in one place.

Further Reading

• What Is a Startup Financial Model? Founder’s Guide
• The 3-Statement Model Explained for Founders
• Financial Model Calculator
• Unit Economics Calculator
• Cap Table Calculator