Series A financial model: what investors expect to see

A Series A financial model is a driver-based forecast that shows how a SaaS company turns new capital into revenue growth, and how long that capital lasts. Investors expect it to run from assumptions through a revenue build, headcount plan, operating expenses, P&L and cash flow to runway, monthly for the first 18 to 24 months, with scenarios and a clear link between the raise and the plan it funds.

This walkthrough is for SaaS founders preparing a first institutional round. Where the model fits in the wider finance setup at each stage is covered in the guide to a fractional CFO for startups; this post stays on the model itself.

The structure, tab by tab

A model an investor can follow flows in one direction. Inputs live in one place, and every output can be traced back to them.

1. Assumptions and drivers. Pipeline or lead volume, conversion rates, average contract value, sales rep ramp and capacity, churn and expansion rates, pricing changes, salary bands, and payment terms. Each driver should be labeled with its source: historical actuals, a signed contract or a stated assumption.
2. Revenue build. New customers or new ARR built from the drivers, then an ARR waterfall: beginning ARR plus new and expansion, less contraction and churn, equals ending ARR. Recognized revenue follows from ARR, and billings and collections follow from contract terms.
3. Headcount plan. One row per role, with start month, fully loaded cost and, for revenue roles, a ramp period before full productivity. The mechanics are in the guide to headcount planning.
4. Operating expenses. Software, rent, marketing programs and professional fees, each tied to a driver such as headcount or revenue where possible.
5. P&L. Revenue, cost of revenue, gross margin, operating expenses by department, and operating income.
6. Cash flow and runway. Net income adjusted for billing timing, payables and capitalized costs, rolled into a monthly ending cash balance and a runway date.
7. Scenarios. A base case and a downside case at minimum, switched from the assumptions tab rather than built as separate copies of the file.

Monthly first, annual later

The first 18 to 24 months should be monthly. That is the period the round is meant to fund, and hiring dates, annual billing cycles and lumpy collections only show up at monthly granularity. Years three onward can be annual. Investors treat them as direction, not commitment, and extra precision there adds work without adding credibility.

What the raise buys: use of funds and runway

The model has to answer the question every investor asks first: how much is being raised, what does it pay for, and how long does it last? Use of funds should come straight from the headcount and expense tabs, not from a pie chart drawn separately.

Runway should come from the monthly burn path, not from dividing cash by today's burn. A Series A plan almost always increases burn as hiring proceeds, so the simple calculation overstates how long the money lasts. The guide to burn rate and runway covers the definitions; the example below shows why the path matters.

Illustrative figures, not client data.

At today's burn of 250 a month, 9,000 of cash looks like 36 months (9,000 / 250). With the hiring plan the round is meant to fund, the same cash lasts 27 months. That nine-month gap is the difference between starting the next raise on time and starting it with too little runway left. A model that shows only the simple figure tends to get discounted once an investor rebuilds it.

Tie the model to actuals and to the deck

A model that starts from a blank month invites doubt. The forecast should begin from the last closed month in the books, with history alongside it, so an investor can see whether the first forecast months look like the recent past. If new ARR jumps in the first forecast month, the model needs a reason: a signed contract, a pricing change or new sales capacity already in seat.

The model and the pitch deck also have to agree. ARR, net new ARR, burn, headcount and retention figures in the deck should come from the model, on the same definitions used in the SaaS metrics investors ask for. An analyst who finds ARR of one figure on slide four and another in the model will question every other number.

After the round, the same model should keep running. Updating it monthly as a rolling forecast means the next raise starts from a model with a track record rather than one built for the occasion.

Mistakes investors spot quickly

• Top-down revenue. A market size multiplied by a share assumption, or a growth rate applied to ARR, with no pipeline, conversion or capacity underneath. Investors want to see how many reps, closing how many deals, at what contract value.
• Hiring with no ramp. A new sales rep producing full quota in the first month, or engineering hires with no recruiting lag. The cost arrives on the start date; the output arrives later.
• Cash that does not tie. Ending cash should equal beginning cash plus the cash flow for the month, and it should match the balance sheet. A model where cash is a separate plug cannot answer runway questions.
• Scenarios that are just percentages. A downside case that cuts revenue by a flat amount but keeps every hire on schedule is not a downside plan. The downside should show which hires slow and how runway changes.
• Hardcoded numbers in formulas. A growth rate typed into a cell in the P&L instead of the assumptions tab breaks the scenario switch and hides the assumption.

How an investor reads your model

Decipher's founder spent nearly a decade running FP&A inside private equity backed software companies, building and reviewing the models investors use to judge a business. An investor's analyst rarely reads the summary first.

• The assumptions tab. Are the drivers grounded in history, and does each one have a stated source?
• The first six forecast months against the last six actual months. A sudden change in trend needs an explanation.
• Revenue per sales rep and hiring ramp. Does the plan expect more from new reps than existing reps deliver today?
• The cash line. Does it tie every month, and does runway use the burn path rather than current burn?
• The downside case. Does the company still reach its next milestone before cash runs short?
• The deck. Do the figures match, on the same definitions?

A model that answers those questions on first pass shortens diligence and keeps partner meetings on the business instead of the spreadsheet.