Revenue Forecast

A revenue forecast is the projection of future revenue over a defined period, typically monthly for 12-24 months and annually for 3-5 years. Ideally built bottoms-up from specific drivers (new customer counts by month, ARPC by segment, retention/churn rates, expansion rates) rather than tops-down from market-share assumptions, the forecast feeds the broader financial model. It is one of the most-scrutinized elements during investor diligence because revenue assumptions drive everything else (hiring plan, burn, runway, valuation). It's the most-important number to get right and the one founders most often build with insufficient rigor.

The components of a defensible revenue forecast:

New customer acquisition (drives new ARR):

• Monthly new customer count by segment.
• Driven by marketing spend, sales capacity, channel partner activity.
• Realistic given current pipeline and historical conversion.

ARPC (Average Revenue Per Customer) by segment:

• Reflects pricing, packaging, customer mix.
• Often varies meaningfully by segment.

Existing customer growth (expansion ARR):

• Net Revenue Retention assumptions.
• Upsell, cross-sell, seat expansion.
• Reflects historical patterns and forward initiatives.

Churn (negative ARR):

• Logo churn (full cancellations) and contraction.
• Should reflect actual cohort data, not optimistic estimates.

Total ARR/MRR trajectory:

• New + Expansion - Churn - Contraction = Net New ARR each period.
• Cumulative trajectory over time.

Revenue recognition timing:

• ARR (or MRR) growth is forward-looking; GAAP revenue follows recognition rules.
• Subscription revenue typically recognized ratably; one-time revenue when delivered.

Common revenue forecast failures:

Tops-down market-share fantasies:

• "1% of $50B market = $500M ARR" without underlying customer math.
• Universally discounted by investors.

Aggressive churn assumptions:

• Assuming 5% annual churn when actual is 15%.
• Optimistic churn dramatically inflates LTV and out-year revenue.

Linear scaling assumptions:

• "We'll grow 100% YoY for 5 years" without specifying what drives it.
• Linear growth at venture scale is unusual; typically S-curve or hockey-stick.

No sensitivity analysis:

• Only the base case shown; no view of how sensitive forecast is to key drivers.

Disconnect from operating plan:

• Revenue grows 10x but headcount grows 3x. The unit economics don't work.

The "bottoms-up first, validate with tops-down" discipline:

• Build revenue forecast from drivers (customer counts, ARPC, churn).
• Sanity-check against market size and competitive context.
• If bottoms-up implies >5-10% market share, question the assumptions.

What founders get wrong: Building tops-down revenue forecasts without underlying driver math, then losing investor credibility when assumptions are probed. The right discipline: bottoms-up from drivers, sensitivity analysis, reconciliation to market context, documented assumptions.

Related: Financial Projections · Revenue Model · Financial Model · Sales Forecasting · Bottoms Up Forecast

FAQ

What is a revenue forecast?
A projection of future revenue over a defined period (monthly for 12-24 months, annually for 3-5 years). Ideally built bottoms-up from specific drivers (new customer counts, ARPC, retention/churn, expansion) rather than tops-down market-share assumptions.

How do I build a defensible revenue forecast?
Bottoms-up from drivers: new customer counts by month and segment, ARPC by segment, expansion ARR from existing customers, churn and contraction. Document assumptions, sensitivity-test key drivers, reconcile to market context. Aggressive but defensible beats aggressive without backing.

What are the most common revenue forecast mistakes?
Tops-down market-share fantasies ("1% of $50B"), optimistic churn assumptions (inflating LTV), linear scaling assumptions (without specifying drivers), no sensitivity analysis, and disconnect from operating plan (revenue grows but headcount doesn't).