← Back to articles

Revenue Projections: Bottom-Up vs Top-Down Forecasting for Startups

Key Takeaways

Master two approaches to revenue forecasting: bottom-up (from customer acquisition plans) and top-down (from market sizing). Learn when to use each and how to reconcile them for credible investor projections.

Diverging paths showing bottom-up versus top-down forecasting approaches

Two Approaches to Revenue Forecasting

Revenue projections are the foundation of startup financial models, yet they're often surprisingly inaccurate. Two approaches dominate: bottom-up forecasting (building from customer acquisition plans) and top-down forecasting (deriving from market size). Each has strengths and weaknesses; sophisticated companies use both and reconcile the differences.

Investors expect founders to articulate both approaches and show alignment. A bottom-up projection that exceeds market size is absurd; a top-down projection with no credible go-to-market plan is fantasy. The intersection of both approaches yields credible forecasts.

Bottom-Up Forecasting: Building from Customer Acquisition

Bottom-up forecasting starts with sales execution: How many sales reps can we hire? What's their productivity ramp? How long does it take them to close deals? This approach is deeply rooted in operational reality—it's based on execution capability, not market potential.

Build your bottom-up model in stages: (1) Baseline metrics—what CAC and ACV (Annual Contract Value) are we achieving today? (2) Scaling plan—how many sales reps do we hire and when? (3) Productivity curves—when does a new rep become productive and what's their annual output? (4) Revenue impact—multiply rep count by rep productivity to get total sales.

Most enterprises have 1-2 reps per $1M annual revenue; high-transaction SaaS might require 1 rep per $2-3M. If you're projecting $10M revenue with a $100M market, you can justify the approach. If you're projecting $100M with 10 sales reps, that requires unrealistic productivity assumptions.

Account for ramp time. A new sales rep is 0% productive month 1, 40% productive month 3, 80% productive month 6, and fully productive month 9-12. Hiring 100 reps on day 1 doesn't instantly generate revenue; there's a 6-12 month productivity lag. Many founders ignore this and overestimate revenue.

Top-Down Forecasting: Starting with Market Size

Top-down forecasting starts with market opportunity: What's the total addressable market (TAM)? If TAM is $1B and we capture 1% market share, that's $10M revenue. This approach reveals growth ceiling—you can't exceed market size, no matter how efficient you become.

Define your market carefully. SAM (serviceable addressable market) is the subset of TAM you can realistically address. An HR software company can't address all $100B HR software TAM; it might address $2B of mid-market compliance software. Your SAM is the relevant ceiling for growth projections.

Apply market share assumptions: what percentage of SAM can you realistically capture? In early stages, assume conservative capture: 0.5-1% of SAM. Mature companies might capture 5-10%. If your SAM is $2B and you assume 3% capture, your revenue ceiling is $60M. Project revenues hitting that ceiling by year 5-7, not year 3.

Account for market growth. Some markets grow 20-30% annually; others are flat. If your TAM is growing 15% yearly, your revenue forecasts should also assume market growth benefits. A startup in a declining market faces headwinds; a startup in a growing market has tailwinds.

Building a Bottom-Up Model: Cohort-Based Sales

Create a sales hiring schedule: when do you hire each rep, and what's their productivity curve? Most companies hire sales reps quarterly or semi-annually as revenue scales. A rep hired in Q1 is productive by Q2/Q3. A rep hired in Q4 is productive in Q1 next year.

Track rep productivity in ARR generated per rep per year. Enterprise SaaS reps might generate $1-2M ARR; mid-market might generate $500K; self-serve SaaS might be $100K+ per marketing hire (marketing is the "rep" for self-serve). Use your current productivity data to project forward.

Account for retention and turnover. Sales reps don't stay forever; average tenure is 2-3 years. If you have 10 reps and 30% annual turnover, you need to hire 3 new reps yearly just to maintain headcount. Hiring and training new reps creates temporary productivity drag.

Model different sales channels separately if applicable. Direct sales by reps, channel partners, self-serve through app store, and marketplace have different dynamics. Direct sales scales with headcount. Self-serve scales with marketing efficiency. Channel scales with partner recruitment and enablement. Sum across channels for total revenue.

Building a Top-Down Model: Market Sizing and Capture

Start with TAM research. Use analyst reports (Gartner, Forrester), regulatory data (if available), or industry reports. If researching HR software TAM, you might find "$100B global HR software market growing 8% annually." Don't make up TAM; cite sources.

Define SAM by geography, customer size, and use case. Not all HR software is relevant to your product. Maybe you focus on "mid-market HR compliance software in North America." That's your SAM—perhaps $2B. This is defensible in investor meetings because you've narrowed from total market to addressable market.

Estimate market share: in year 5, what percentage of SAM do you realistically capture? Be conservative. A startup claiming 10% market share by year 5 is claiming $200M revenue in a $2B market—plausible but aggressive. Most startups land 1-5% market share. Only best-in-class winners capture 10%+.

Project the path: year 1 is 0.1% market share, year 2 is 0.2%, year 3 is 0.5%, year 4 is 1%, year 5 is 2%. This S-curve captures the reality that market share grows slowly early (building credibility), accelerates in middle (market leadership), then plateaus (market saturation). This is more credible than linear growth assumptions.

Reconciling Bottom-Up and Top-Down: Finding the Truth

Most startups find that bottom-up and top-down projections diverge. Bottom-up might forecast $15M revenue; top-down might forecast $8M. This gap reveals something: either your go-to-market assumptions are too aggressive, or your market sizing is too conservative.

If bottom-up exceeds top-down, challenge your sales assumptions. Can you really hire and productively utilize 20 sales reps? Is rep productivity realistic? Would the market actually buy that much from you? Reign in the bottom-up model to plausible levels.

If top-down exceeds bottom-up, challenge your market sizing. Is your SAM estimate too high? Are you underestimating market share capture? Or are you being too conservative in sales hiring? Many founders are overly conservative initially—push yourself to justify more ambitious sales hiring if market opportunity is large.

The reconciliation process is valuable. It forces you to defend each assumption: Why 8 sales reps? Why 0.5% market share? Why $100K CAC? This discipline improves your projections and impresses investors who will ask these exact questions.

Incorporating Churn and Retention into Projections

Both approaches need churn assumptions. If you're acquiring customers at rate X but losing them at rate Y, revenue projection is X minus Y in steady state. Monthly churn rates of 2-5% are typical; 10% is concerning. Years 1-2 often have higher churn (finding product-market fit); years 3+ have lower churn (product maturity).

Model churn by cohort. Early customers might churn 5% monthly because product immaturity. Later customers might churn 2% because product is proven. Your overall churn is a blend of cohort churn rates. As you improve product and mature, overall churn should decline 0.5% annually.

Expansion revenue (existing customers buying more) partially offsets churn. If you acquire customers at $50K ACV and 2% monthly churn but 8% monthly expansion, net revenue grows 6% monthly (expansion minus churn). Track these separately to show how expansion helps offset churn.

Adjusting Projections for Market Maturity and Competition

New markets have different dynamics than mature markets. In emerging markets, educating customers is part of sales; CAC is high, sales cycle is long, but capture opportunity is enormous. In mature markets, customers understand the problem; CAC is lower, sales cycles shorter, but capture opportunity is constrained by market size and competition.

Competition also changes forecasting. If you're entering a market with entrenched competitors, your market share assumptions should be conservative. If you're creating a new market, assumptions can be more aggressive (but markets can also evaporate). Most founders underestimate competitive response; be realistic about losing deals to competitors.

Product superiority matters but doesn't guarantee market dominance. Even best-in-class products fail if go-to-market is weak. Conversely, mediocre products with strong go-to-market can win. Your revenue projection should reflect realistic go-to-market execution, not product wishcasting.

Handling Uncertainty in Projections

Revenue projections are inherently uncertain. Most startups miss initial projections by 30-50%. Instead of pretending you know the future, model scenarios: (1) Aggressive (capturing more market share, faster sales reps, lower churn), (2) Realistic (based on current traction), (3) Conservative (slower growth, higher churn, slower hiring).

Show all three scenarios to investors. They'll respect your intellectual honesty. Explain the levers: what would need to happen for conservative to become realistic? What execution risks are there? This scenario analysis is more valuable than a single "accurate" projection that turns out wrong.

Update projections quarterly based on actual performance. If actuals exceed projections, increase projections. If actuals lag, decrease them. Most startups become more accurate at forecasting over time as they accumulate data.

Common Mistakes in Revenue Projections

Many founders use hockey-stick curves: flat revenue initially, then sudden vertical growth. Reality is more gradual S-curves with plateaus and sometimes declines. Hockey sticks are red flags to investors; S-curves are credible.

Another mistake: ignoring sales ramp time. You hire 5 sales reps in January, but they're not productive until April/May. Most projections assume immediate productivity, inflating revenue. Account for 6-month average ramp time.

Founders also often confuse CAC with sales expense. If you spend $1M on sales and marketing and acquire 100 customers, CAC is $10K. But that $1M is in addition to overhead salaries, systems, etc. Your total go-to-market expense is higher than direct CAC implies.

Presenting Projections to Investors

Lead with bottom-up: "We're hiring 5 sales reps in year 1. Based on our current data, reps generate $300K ARR when fully productive. Five reps generating $1.5M ARR is our conservative assumption." This grounds projections in execution capability.

Then add top-down validation: "Our SAM is $2B. We're assuming we capture 0.1% in year 1, 0.3% in year 2, 0.5% in year 3. This is conservative; our direct competitors are at 1-2% market share." This shows the market is large enough to support growth.

Show reconciliation: "Both approaches yield $500K-$1M revenue by year 3. Here's why the range: bottom-up depends on sales hiring pace; top-down depends on market share capture rate. We control both levers." This demonstrates sophisticated thinking.

Key Takeaways

FAQ

How conservative should we be with revenue projections?

Show multiple scenarios. Most venture investors expect you to miss aggressive projections by 30-50%. Better to show conservative projections and beat them than aggressive projections and miss them. The pattern of beating projections is more valuable than the absolute numbers.

Should we project to profitability in year 3 or later?

Most well-funded startups are cash-flow negative for 36-48 months. If your projections show profitability by year 3, investors will assume you're being too aggressive with growth or too conservative with expenses. Show a path to profitability but don't force it into year 3 if you're hiring for growth.

How do we account for seasonality in projections?

Many businesses have seasonal patterns: HR software sees hiring spikes in Q1, payroll software sees year-end peaks. Model seasonality explicitly: some quarters might be 20-30% higher revenue than others. This is especially important for cash flow forecasting.

Should we include channel partner revenue in projections?

Yes, but separately. Track direct sales versus channel revenue separately. Channel has longer sales cycles and lower margin (partners take a cut) but reaches customers you couldn't sell directly to. Assume 60-70% of direct rep productivity for channel reps; they're less incentivized and more distributed.

How do we project international expansion impact?

International expansion adds complexity: different pricing, competition, regulatory requirements, and language. Most teams should focus domestically first. If modeling international in year 3-4, assume 6-month delayed ramp compared to domestic. International is harder than it looks.

Get the complete guide with all 16 chapters, exercises, and model templates.

Get Raise Ready - $9.99
YP
Yanni Papoutsi

VP Finance & Strategy. Author of Raise Ready. Has supported fundraising across multiple rounds backed by Creandum, Profounders, B2Ventures, and Boost Capital. Experience spanning UK, US, and Dubai markets.

The Raise Ready Weekly

Every Friday: the best startup finance insights. Fundraising, modeling, unit economics. No spam.