How to Create Financial Projections

Financial projections are usually a deck artifact — built once for an investor meeting, never opened again. That is the wrong use. A good model is an operational tool: updated monthly, compared against actuals, revised when assumptions fail. The deck version is a byproduct.

This guide walks through building the model for operational use, with the financial-statement discipline that survives investor scrutiny as a side benefit.

1. Three statements, linked

The three financial statements, briefly:

• Income statement: Revenue, costs, and resulting profit over a period. Accrual basis.
• Balance sheet: Assets, liabilities, and equity at a point in time.
• Cash flow statement: Cash movement over the period, categorised as operating, investing, financing^[2].

They link: net income from the income statement flows to retained earnings on the balance sheet. Changes in balance-sheet items (AR, AP, inventory, capex) drive the cash flow reconciliation. Ending cash on the cash flow statement ties to cash on the balance sheet.

Build all three. A single-statement projection (usually just revenue and expenses) hides the working-capital and cash-timing effects that cause most small-business distress. The income statement can show "profit" while the cash flow statement shows you running out of money in month 8 because receivables extended and inventory expanded.

2. Drive from operational inputs, not top-down

A top-down model says: "We'll grow 10% per month." A bottom-up model says: "We'll close 12 new deals at $15k ACV, renewing 85% of our $300k base, resulting in $XX MRR."

Both produce numbers. Only the second produces numbers you can stress-test.

For B2B SaaS, the driver stack:

• Pipeline coverage and historical close rates by stage → new bookings.
• Cohort retention curves → revenue from existing customers.
• Sales ramp time × rep count × quota attainment → new-bookings capacity.
• Headcount plan + loaded cost per role → operating expenses.
• Cash timing: billings vs. revenue, AR collection lag, AP payment timing → cash from operations.

For consumer/transactional businesses, the driver stack centers on acquisition (channel CAC × spend = new users), activation (new users × activation rate = active users), and monetisation (active users × ARPU). Each is its own sub-model.

The useful test: can you explain how a 10% miss in any single driver propagates through to revenue, expense, and cash? If no, the model is not driver-based.

3. Sanity-check against public benchmarks

Projections often drift into impossible ranges because they extrapolate from a small sample of good months. Sanity-check against public data:

• Revenue growth rate. Fed SBCS 2024 median small-business revenue growth was ~3–5% year-over-year^[1]. Projecting 30% annual growth puts you in the top decile; projecting 100% means the model assumes top-1% execution. Possible but rare.
• Gross margin. Varies by category — SaaS 70–80%, ecommerce 30–45%, services 40–60%. Project gross margins well outside the category range, and be prepared to explain why.
• Operating margin at scale. For SaaS: 15–25% is good, 25%+ is excellent, negative is expected in early years. For consumer-products: margins vary wildly. Carta 2024 data shows most early-stage SaaS running 50–100% negative operating margin during growth phase^[4].
• CAC payback. Under 24 months healthy for B2B SaaS. Projecting 6-month payback scaling to thousands of customers is a red flag — the channel economics usually erode at scale.

The model should justify any number materially outside these ranges. "Because our team is great" is not a justification; "because we have a structural cost advantage from X" is.

4. Build P50, P75, and downside scenarios

Three scenarios, each serves a different purpose:

• P50 — realistic. Your genuine best estimate of what will happen. This is the headline number for investors and is what you plan sales and marketing capacity around.
• P75 — conservative operational plan. Assumes close rates 20% lower, sales cycles 20% longer, churn 1 percentage point higher. This is what you plan hiring and vendor commitments against. If you commit to headcount based on P50, you will have to cut when it misses.
• Downside — what if the environment breaks. Revenue declines 20%, a major customer churns, you can't raise the next round on schedule. What do you do, and when?

The downside case is not pessimism; it is preparation. A company with a clear downside plan acts faster when conditions deteriorate, which is often the difference between distress and survival. SBA guidance specifically recommends scenario modeling for this reason^[3].

5. Projections as operational artifacts

The model is useful only if it is updated and compared to actuals regularly. Monthly cadence:

• Pull actuals from accounting and CRM systems into the model.
• Compare actual vs. P50 projection. Document the variance by driver (not just aggregate).
• Identify systematic biases. If new bookings missed by 15% three months running, the driver assumption is wrong — not the arithmetic.
• Revise forward projections where evidence has changed. Do not revise to hide past misses; revise to improve future decisions.

Quarterly, re-run the P75 and downside scenarios with updated inputs. Monthly fluctuations should not move those; structural shifts (new product line, major customer loss, competitive entry) should.

A projection model that stays in sync with reality is worth more than one built to a higher standard and then abandoned. In the typical case, the habit of monthly revision is what distinguishes operationally useful projections from pitch-deck artifacts.

6. Common traps in financial modeling

Four patterns that produce unreliable projections:

• Hockey-stick revenue with no underlying driver. If the model shows exponential growth without explaining where each new customer comes from, the model is aspiration. Investors and experienced operators can spot this instantly, and it damages credibility.
• Static cost assumptions with dynamic revenue. Revenue grows 200% but COGS, support cost, and infrastructure stay flat. Fundamentally implausible. Most scaling costs grow with revenue, often at 60–80% of the revenue scaling rate.
• Double-counted revenue. Booking revenue from the same customer in both new-bookings and renewals buckets. Easy to do unintentionally when the model separates segments by channel; discipline the definitions.
• Ignoring working capital in cash flow. A model showing positive net income while the balance sheet accumulates $2M of receivables is showing non-cash profit. Cash flow from operations corrects this if the model is properly linked.

7. Tools and who should build the model

For most small businesses, Excel or Google Sheets is the right tool for financial projections. Purpose-built modeling software (Causal, Finmark, similar) is useful once complexity grows beyond what a single-sheet model can handle — typically when you have 10+ cost centres or multiple product lines.

Ownership of the model matters:

• Founder-built (pre-seed to Series A). Founders should understand the model deeply enough to explain every assumption. Outsourcing this early is usually a mistake.
• Founder-built, finance-maintained (Series A onward). Part-time fractional CFO or full-time finance hire takes ownership of maintenance and calibration, with founder reviewing quarterly.
• CFO-owned (Series B onward). Full-time CFO or VP Finance owns the model, with monthly board-ready outputs. At this stage, the model is part of standard operating cadence, not a one-off artifact.

The model is a living document. A 12-month-old model without monthly updates is worse than useless — it produces numbers that look plausible but are wrong, which drives worse decisions than having no model at all. Build the habit of monthly update into the calendar, not into someone's good intentions.

8. Numeric worked example — top-down vs bottom-up reconciliation

A pre-Series-A SaaS has $2.1M ARR, 18 reps, and a founder projecting "50% growth to $3.15M in year 1." Rebuild the number bottom-up and see where the assumptions break.

Top-down claim
  Year 1 ARR target        $3.15M   (+$1.05M net-new ARR)
  Implied NRR (if 100% new  148%    (wildly above top-quartile)
     from existing)

Bottom-up rebuild
  Existing base ARR        $2.10M
  Assume NRR 108%          +$168k expansion
  Churn on existing (5%)   −$105k
  Existing contribution     $2.16M

  Net-new ARR needed       $0.99M to hit $3.15M target
  18 reps × 70% attainment × avg quota $85k = $1.07M capacity
  New-logo timing drag (ramp + sales cycle): 75% realised in-yr
  Realistic new-logo ARR   ~$0.80M

  Realistic year-1 ARR     ~$2.96M (41% growth, not 50%)

The top-down 50% is only plausible with rep capacity and attainment both hitting best-in-class simultaneously. The bottom-up number (~41%) is still strong — Fed SBCS 2024 puts median small-business growth at 3–5% year-over-year^[1], and Carta 2024 data shows top-quartile early-stage SaaS growing 60–100%^[4], so 41% sits credibly in the "good-not-peak" band. The gap between $3.15M and $2.96M is where hiring commitments, cash planning, and investor expectations diverge from reality.

9. Failure modes worth naming

• Model built once in Sheets, never re-opened. A projection that isn't reconciled to actuals monthly drifts toward fiction inside a quarter. Put the reconciliation meeting on the calendar; the model earns its keep only if the habit holds.
• Unit economics assumed to hold at 10x scale. CAC at $8k with today's top-of-funnel costs may not hold when you are spending 10x the current paid-acquisition budget. Assume channel economics degrade 20–40% as you exhaust the cheapest audience.
• Balance sheet treated as optional. A model that skips AR/AP/inventory line items will show income but miss the working-capital stress that drives most small-business distress. FASB ASC 230 spells out why the cash-flow reconciliation matters^[2]; skipping it breaks the cash line.

As of 2026-Q2, Carta data continues to show meaningful dispersion in how early-stage companies model growth^[4]; the models that survive board scrutiny are consistently the bottom-up, driver-linked, monthly-reconciled kind — not the polished single-tab "hockey stick" decks.