How to Forecast Revenue

Revenue forecasting has two failure modes. The amateur mistake is extrapolating a trend line and calling it a forecast. The sophisticated mistake is building a model detailed enough to look rigorous but anchored on a growth assumption that is fundamentally a guess. Both produce point estimates that collapse under any real variance.

This guide walks through a forecast that survives scrutiny: method choice, pipeline- or cohort-based build, range publication, and monthly calibration. The approach draws on the standard forecasting textbook^[1] and public founder-survey data^[3].

1. Choose a forecast method that matches your data

The method should match the data available, not the other way around:

• Time-series extrapolation (ARIMA, exponential smoothing). Appropriate for businesses with 24+ months of stable revenue history and no structural changes. Works for stable retail, mature subscriptions, cyclical B2C^[1].
• Pipeline-coverage forecasting. For B2B with a defined sales cycle. Forecast = weighted pipeline × close rate, by stage.
• Cohort-based retention forecasting. For subscription businesses. Forecast = sum of cohort MRR projected forward with measured retention curves.
• Unit economics × acquisition rollup. For transactional e-commerce or marketplaces. Forecast = projected new acquisitions × repeat rate × AOV.

Do not build a forecast that mixes methods unless you can clearly separate what each component is forecasting. Mixing top-down market-share assumptions with bottom-up pipeline math is where numbers start diverging from reality.

2. For B2B, build from pipeline coverage

A defensible B2B forecast starts with the current pipeline, stage by stage. For each stage, multiply value by historical conversion rate to the next stage. The conversion rates come from your CRM, not industry benchmarks.

Example, monthly forecast:

• Stage 1 (SQL): $800k in pipeline × 25% conversion to Stage 2 = $200k.
• Stage 2 (Evaluation): $200k + existing $300k = $500k × 45% = $225k.
• Stage 3 (Proposal): $225k + existing $250k = $475k × 65% = $309k.
• Stage 4 (Closing): $309k + existing $100k = $409k × 85% = $347k.

That $347k is a P50 estimate of closed revenue. Apply the sales cycle distribution (not every stage-4 deal closes this month) to get the month's booked revenue, then the booking-to-revenue timing gives recognised revenue. For businesses with a typical 45-day sales cycle, expect 60–70% of stage-4 pipeline to close in-month; the rest slips.

Roughly 3x pipeline coverage of the revenue target is the floor for credible forecasting in typical B2B^[3]. Below 3x, the forecast is aspiration.

3. For SaaS, build from cohort retention

For subscription revenue, the forecast is a sum over cohorts:

Projected MRR(t) = Σ [Cohort(c) × Retention(c, t − c)] + New Cohort Acquisition(t)

Three inputs. Cohort starting MRR from your billing system. Retention curves from cohort analysis (build the table, do not trust aggregate churn). New acquisition from your demand-generation model — which is itself a pipeline forecast, recursively.

The retention curve is the piece most founders undercount. Early cohorts churn differently from mature cohorts; early-stage products often have an initial retention cliff at 30–90 days that persists for that cohort forever. If you use a single aggregate churn number, you understate the retention of older customers and overstate the retention of new ones. Use the actual cohort table.

4. Publish a range, not a point

A point forecast hides the uncertainty that actually matters for planning. Publish three numbers:

• P50 (median). The equally-likely-over-or-under estimate.
• P75. 75% chance the actual number comes in at or below this. Plan hiring and vendor commitments against P75 if you want margin of safety.
• P90. 90% chance of hitting or underperforming. Useful for communicating to lenders or investors what the realistic downside looks like.

Constructing the range: for pipeline-based forecasts, vary close rates by ±20% and sales-cycle slippage by ±15% around historical medians. For cohort forecasts, vary churn rates by ±1 percentage point monthly for each cohort stage. Run both together and the range usually widens to ±25–35% for early-stage SaaS^[4].

A narrow range is not a sign of rigor; it often signals that the model lacks enough variance inputs.

5. Calibrate monthly

A forecast you do not review is a number, not a forecast. Every month, compute the error of last month's P50 estimate versus actual. Track the rolling three-month MAPE (mean absolute percentage error). If MAPE is consistently above 25% in a SaaS business, the model needs rebuilding, not tuning.

The useful calibration question is not "were we right?" It is "when we were wrong, were we systematically high or low, and in which cohort?" Systematic bias in one direction reveals a structural flaw in the model — the early-stage acquisition assumption is too optimistic, or a specific cohort's retention is materially worse than projected.

Based on the published methodology across the major forecasting texts, the two disciplines that separate credible forecasts from theatre are: (a) updating assumptions when they are wrong, not defending them; and (b) publishing error bands that match actual observed variance, not the variance the founder wishes existed^[1].

6. Account for external conditions

Models that ignore external conditions miss the structural shifts that matter most. Consider:

• Macroeconomic cycles. Fed interest-rate decisions affect buyer purchasing patterns, especially for B2B software sold to venture-backed buyers. A rate-hiking cycle typically extends sales cycles 20–30% and compresses deal sizes.
• Industry-specific trends. If your buyer segment is under pressure (e.g., retail during a downturn, healthcare during reform cycles), their pipeline behaviour changes before your forecast reflects it.
• Competitive shifts. A major competitor launching, raising, or changing pricing can materially affect your close rates. The forecast model should anticipate this, not respond to it after the fact.
• Regulatory changes. GDPR, CCPA, sector-specific regulation can open or close market segments. Relevant for data-intensive or healthcare/finance-adjacent products.

Build one macro-assumption review into the forecast cadence quarterly. If nothing has changed, skip; if something structural has shifted, adjust both P50 and P75 scenarios to reflect it. Fed SBCS 2024 data shows small businesses reporting macro concerns accurately predicted slowdowns in their own revenue 1–2 quarters ahead^[4] — the signal is usually visible before the hit.

7. Forecasts for different audiences

The same underlying numbers need different presentations for different audiences:

• Internal operational plan. P75 (conservative) with full driver detail. This is what hiring, vendor commitments, and sales capacity gets planned against.
• Board and investor updates. P50 (realistic) with clearly stated assumptions and error bands. Showing the range signals rigor; hiding it signals overconfidence.
• Lender or debt-covenant discussions. Often contractually specified — lenders typically require the conservative case against certain ratios. Know what your covenants demand.
• Sales team goals. Stretch of P50, published as quota. Not the model's central estimate, by design — sales teams are expected to hit harder numbers than the business is planned against.

The common mistake is using the same number across all audiences. What works for an investor update (show range, discuss assumptions) actively harms a sales team (too much ambiguity) and lenders (they want one specific conservative number they can tie to covenant math).

8. Numeric worked example — pipeline forecast with ranges

A $1.5M ARR B2B SaaS runs a 60-day sales cycle, 28% average close rate from qualified opportunity, and has $1.1M in stage-2+ pipeline. The CRO projects $380k of Q4 bookings in a single point estimate. Build the honest range instead.

Pipeline stage   Value    Close rate   Expected bookings
─────────────────────────────────────────────────────────
Stage 2          $420k    32%          $134k
Stage 3          $380k    55%          $209k
Stage 4          $300k    82%          $246k
                                       $589k gross pipeline-expected

Slippage (historical 35% of stage-4 slips month-end)       −$86k
In-quarter bookings (P50 central estimate)                  $503k

P75 (close rates −20%, slippage +15%)                       $410k
P90 (close rates −30%, slippage +25%)                       $335k

The single-point $380k looked conservative; the honest range shows P50 meaningfully higher and P90 still roughly at the committed number. Hiring and cash-reserve decisions plan against P75 ($410k); lender covenant conversations cite P90 ($335k); the board deck shows P50 with the range^[1]. Same underlying model, three different audience-appropriate numbers.

9. Failure modes worth naming

• Forecast built from target, not data. "We need to hit $X so the plan shows $X." The reverse direction of honest forecasting. The math has to run from pipeline or cohort data up to an emergent number; if the model is tuned until it matches the desired headline, it stops being a forecast.
• Ignoring sales-cycle lengthening. Fed SBCS 2024 and First Round State of Startups 2024 both document meaningful sales-cycle lengthening in 2023–2024 versus 2021 baselines^[3][4]. Models still running on pre-2022 close-rate and slip assumptions overstate near-term bookings by 15–30%.
• Retention curve flattened prematurely. Six months of SaaS data doesn't reveal year-two churn. Projecting forward at month-12 retention assumes the curve stops dropping, which almost never happens below enterprise-ACV segments. Apply a conservative floor until you have at least 18 months of cohort data.

As of 2026-Q2, public founder-survey data continues to show that forecasts published with an explicit uncertainty band have meaningfully higher trust from boards and lenders than point estimates^[3]. The credibility is in the range, not in the precision.