Financial projections are forward-looking estimates of revenue, expenses, profitability, and key metrics over a defined period, typically 3-5 years. They're presented as condensed outputs from the underlying financial model, used in fundraising decks to communicate trajectory to investors, board reviews to show planned vs actual performance, and strategic planning to anchor major decisions. Projections are a distinct artifact from the financial model itself: the model is the detailed driver-based spreadsheet; projections are the summarized outputs. It is one of the most-scrutinized elements of fundraising materials.
The relationship between model and projections:
You build the model first; projections fall out of it.
The standard projection summary for fundraising:
Five-year projection table:
Key assumptions documentation:
Sensitivity analysis:
Cash flow projections:
The growth pattern most companies project (and why investors are skeptical):
This "hockey stick" is the standard projection pattern. Investors see hundreds of these per year; most don't materialize. The investor question becomes: what specifically would have to be true for this trajectory? Founders who can answer with specifics (customer counts, deal sizes, sales velocity by segment) are credible. Founders who can't are dismissed.
Common projection mistakes:
Defensible projection practices:
Financial projections are where founders most often hurt their credibility with investors. The pattern: projections show aggressive hockey-stick growth (because that's what investors "want to see") with no underlying detail justifying the trajectory. Investors see this, recognize it as theater, and the projections damage credibility rather than build it. The discipline that works: build defensible projections from bottoms-up drivers. Make every revenue number traceable to specific customer counts and pricing assumptions. Connect projections to hiring plan and operating costs. Present sensitivity analysis showing how outcomes change with assumptions. Be willing to discuss the math in detail; this demonstrates operational rigor. Aspirational projections without underlying detail are worse than conservative projections with rigorous backing.
What founders get wrong: Building optimistic top-down projections to impress investors, only to lose credibility when investors probe the assumptions and find no underlying detail. The right discipline: build projections bottoms-up from driver-based assumptions, ensure internal consistency between revenue, headcount, and operating costs, present sensitivity analysis showing impact of assumption changes, and document the rationale for every key driver. Conservative-but-rigorous beats aggressive-but-vague every time in investor diligence.
Related: Financial Model · Revenue Forecast · Cash Flow · Business Plan · Pitch Deck
What are financial projections?
Forward-looking estimates of revenue, expenses, profitability, and key metrics over a defined period (typically 3-5 years for fundraising contexts). Typically presented as condensed outputs from the underlying financial model. Used in fundraising decks, board reviews, and strategic planning.
What's the difference between financial model and projections?
The financial model is the detailed driver-based spreadsheet with monthly assumptions and full P&L/cash flow detail. Projections are the summarized outputs (annual totals, headline metrics, growth rates). You build the model first; projections fall out of it.
Why do investors discount founder projections?
Because most projected hockey-stick growth doesn't materialize. Investors see hundreds of optimistic projections per year and learn to discount them. Defensible projections (bottoms-up drivers, internal consistency, sensitivity analysis, documented assumptions) build credibility; top-down aspirational projections damage it.
This is just a small sample! Register to unlock our in-depth courses, hundreds of video courses, and a library of playbooks and articles to grow your startup fast. Let us Let us show you!
Submission confirms agreement to our Terms of Service and Privacy Policy.