How to Write Financial Projections That VCs Will Believe

Financial projections are where founders most often destroy their own credibility. The pattern is predictable: year one is modest, year two grows 3x, year three grows 5x, producing a revenue hockey stick that looks designed to impress rather than to inform. Every investor has seen this template. Most can tell within 30 seconds whether a financial model is built from real assumptions or reverse-engineered from a target number.

Credible financial projections do the opposite: they start from the mechanics of the business — how customers are acquired, at what cost, how long they stay, and what they pay — and let the revenue number emerge from those mechanics. The goal is not to project the largest defensible number. It is to project the most accurate number with the most transparent assumptions.

Why Projections Matter Even When Everyone Knows They Are Wrong

No investor expects a three-year revenue projection to be accurate. The specific numbers will be wrong. What the projection reveals is whether the founder understands the business well enough to articulate the key inputs that drive growth. If the model is built from customer count × ACV × growth rate with a coherent sales hiring plan behind it, the investor knows the founder thinks like an operator. If the model is built from "the market is $5 billion and we will capture 1% per year," the investor knows the founder has not done the work.

The projection also establishes the use of funds logic. If you are raising $5 million, and your financial model shows you reaching $4 million ARR by month 24, the investor can evaluate whether $5 million is the right amount to reach that milestone or whether you have under- or over-raised.

The Inputs That Drive a Credible SaaS Financial Model

For a B2B SaaS company, the five inputs that determine revenue are:

1. Starting ARR. Your current contracted recurring revenue. This is the only number in the model that is not a projection — it is a fact. State it explicitly.

2. New ARR per month. How much new ARR will you add each month? This is driven by your sales and marketing activity. If you have three salespeople each closing two deals per month at an average ACV of $30,000 per year, that is $180,000 in new ARR per month ($2.16M per year). Show the sales headcount assumption behind this number.

3. Churn rate. What percentage of ARR are you losing each month to cancellations? For SaaS, a monthly churn rate below 1% (12% annually) is healthy; below 0.5% is strong. If your churn rate is 3% per month, the math of the business becomes very difficult as revenue scales.

4. Expansion revenue. For products that grow with usage, expansion ARR can offset churn and then some. A net dollar retention above 110% means existing customers expand their spend faster than others churn, which is a powerful driver of efficient growth.

5. Headcount and costs. Revenue growth requires sales and marketing spend and headcount. A model that doubles revenue without showing the accompanying payroll increase is not credible. Build the model with a headcount plan and show COGS, S&M, R&D, and G&A as separate line items.

Building the Model: A Step-by-Step Approach

Step 1: Start from what you know. Current ARR, current monthly new ARR, current monthly burn, and current team size. These are the anchors from which every projection extends.

Step 2: Build a 24-month hiring plan. How many AEs will you hire and when? How long is the ramp period before they are fully productive (typically 3-6 months for mid-market SaaS)? When will you hire a VP of Sales? Each new hire has a cost (salary + benefits + equity) and a revenue contribution after the ramp period.

Step 3: Project CAC and quota capacity. If each AE has an annual quota of $600,000 and you expect them to achieve 70% of quota on average, each AE produces $420,000 in new ARR per year at full ramp. A team of five AEs (all fully ramped) produces $2.1 million in new ARR per year from the sales channel alone.

Step 4: Apply churn. Subtract monthly churn from ARR each month. If you start with $2 million ARR and have 1% monthly churn, you lose $20,000 in ARR in month one. At $5 million ARR, monthly churn at 1% is $50,000 — a real drag that must be offset by new logo acquisition.

Step 5: Add expansion. If you have NDR above 100%, model the expansion as a percentage of existing ARR. If NDR is 115%, existing customers grow their spend by 15% annually on average — model that as 1.25% expansion per month applied to beginning-of-month ARR.

Step 6: Build the cost model. COGS (hosting, customer success, implementation), S&M (salaries, paid acquisition, events), R&D (engineering salaries), and G&A (legal, finance, office). Show monthly burn and cumulative cash burn. The raise should fund at least 18 months of runway.

How to Present Projections in the Deck

For the deck itself, distill the model to a clean summary. A single table showing year-one, year-two, and year-three revenue, gross margin, EBITDA or net income, and headcount is sufficient. Include a monthly burn rate and runway figure.

State your key assumptions explicitly in the speaker notes or in a small text block below the table: "Growth rate assumes: 5 AEs fully ramped by month 12, 15% quota attainment ramp, 0.8% monthly gross churn, 115% NDR." An investor who wants more detail will ask for the full model in due diligence.

Benchmarks by Stage

Seed ($2-5M raise): Year-one projections of $500,000-1.5 million ARR, with a path to $3-5 million ARR by year two if the go-to-market works. Monthly burn of $150,000-300,000. Runway of 18-24 months post-raise.

Series A ($10-20M raise): A company at $2-4M ARR projecting $8-12 million ARR by year two (3x growth) and $20-30 million ARR by year three. Monthly burn of $500,000-900,000. Rule of 40 compliance targeted by year three.

Series B ($25-50M raise): A company demonstrating Rule of 40 compliance currently or within six months. Revenue typically $8-20 million ARR. Burn and growth rate should produce a clear 24-36 month path to EBITDA breakeven.

The Three-Scenario Approach

Presenting projections in three scenarios — base, bull, and bear — signals analytical rigor without requiring you to commit to a single number. The base case is what you actually expect to achieve. The bull case shows what happens if one or two key bets pay off (a new partnership channel, a product expansion). The bear case shows the business is viable even if growth comes in at 50% of plan. This framing is especially useful in economic conditions where investors are concerned about downside risk.

Mistakes That Destroy Credibility

The hockey stick with no explanation. If year three is 10x year one with no explanation of what changes, every investor will see it as reverse-engineered from a desired valuation.

Ignoring burn. A revenue projection without a burn model is incomplete. Show monthly cash burn and cumulative cash consumption.

Assuming 0% churn. Every model should include churn. A model with no churn signals naivety about how SaaS businesses actually work.

Projecting margins that improve without explaining how. If gross margin goes from 55% to 75% over three years, show why — economies of scale in hosting? Reduction in implementation costs? Automation of customer success functions?

Financial projections are not about predicting the future. They are about demonstrating that you understand the mechanics of your own business. That understanding is what investors are buying at any stage of funding.