Series A Financial Model Template

Investors don’t want a perfect model—they want a model you can operate. Use this driver‑based template to show how revenue compounds, how cash is used, and what changes if assumptions move. It’s structured for partner meetings: ARR bridge, cohorts, CAC payback, unit economics, and a clear hiring plan.

Key takeaways: Build from drivers, not wishful top‑down targets. Prove repeatability with cohorts, CAC payback ≤12–18 months, and a burn multiple ≤1.5–2.0. Tie headcount to milestones; keep a single source of truth for metrics; and version‑control assumptions so diligence is easy.

Operate from drivers and cohorts; show efficient growth with clear cash use.

The short version: what your Series A model must show

A credible path to efficient growth: ARR compounding from realistic pipeline and retention, cash runway 18–24 months post‑raise, and headcount tied to milestones.

Lead with an ARR bridge, cohort retention, margin structure, and CAC payback. Show a clean cash view (burn and runway) and the hiring plan that supports the forecast. Keep definitions consistent with your metrics workbook and annotate any one‑offs.

Template structure (tabs and drivers)

Start with Inputs → Revenue → Costs → Cash → Metrics dashboards. Use drivers for funnel, pricing, retention, and hiring ramp.

Inputs: unit prices, conversion rates, churn/expansion, hiring dates and ramp times. Revenue: new, expansion, contraction, churn by month and cohort. Costs: headcount with salaries/benefits, COGS, marketing programs. Cash: burn, runway, and raise timing. Metrics: GRR/NRR, CAC payback, burn multiple, LTV/CAC.

Definitions tab is non‑negotiable

Document every KPI and calculation (e.g., CAC includes payroll? payback gross‑margin adjusted?). This speeds diligence and avoids debate.

ARR bridge and cohorts (how to present)

Start ARR + new business + expansion − contraction − churn = end ARR. Add a quarterly view to smooth noise; label discrete events.

Investors underwrite durability and expansion. Show rolling 12‑month cohorts with logo and revenue retention. Call out product‑led expansion vs price‑rise effects so the story is credible.

Unit economics to include

GRR ≥92% is healthy for SaaS; NRR ≥110% is strong in PLG; CAC payback ≤12–18 months; burn multiple ≤1.5–2.0 depending on motion. Present rolling medians.

Headcount plan tied to milestones

Hire against 3–5 milestones, not vanity ratios. Include ramp assumptions, tool costs, and manager spans.

Connect each hiring wave to a measurable goal (e.g., activation, mid‑market motion). Avoid front‑loading sellers without pipeline; invest in enablement when you pass three AEs. List dependencies (e.g., SE support, data engineer).

Cash, burn multiple, and runway

Show how cash moves each month, where burn peaks, and how the raise extends runway to 18–24 months—assuming conservative hiring and conversion.

Include scenarios (base / upside / downside). Show burn multiple (net burn / net new ARR) and sensitivity to CAC or churn shifts. If seasonality exists, model it explicitly and footnote large annual prepays.

Core Web Vitals for your model landing page

If you gate the Google Sheet, the landing page must be instant: INP ≤200 ms, LCP ≤2.5 s, CLS ≤0.1. Gate after the fold.

Serve a lightweight hero (≤150 KB WebP), preconnect to fonts/CDN, and defer heavy embeds. A fast page lifts conversion and improves the quality of inbound meetings.

Example input drivers (copy/paste)

Use these as placeholders—replace with your actuals.

Worked example (illustrative numbers)

Show your arithmetic, not just the totals.

Assume £300k starting ARR. New logos add £160k in year, expansion adds £90k, contraction is £40k, and churn is £60k. End ARR lands at £450k. With a blended gross margin of 78% and CAC payback of 14 months, a £6–8m Series A should fund 18–24 months of runway with disciplined hiring.

Linking to hiring

Two AEs ramping in Q1 and one in Q3 support the new logo plan. Enablement is added when three sellers are live. Engineering hires track the roadmap milestones you present in product slides.

Sensitivity: what breaks first?

Stress churn, conversion, and time‑to‑hire.

Build toggles for ±10–20% swings in key drivers and show the impact on ARR and runway. Investors want to see that you understand which variables move the model most and how you’ll respond (e.g., slow hiring if CAC payback exceeds 18 months).

Presenting scenarios

Keep a base case plus upside/downside. Avoid fantasy ‘hockey stick’ curves; show the operational levers that unlock upside (product activation, mid‑market motion, expansion features).

Metrics dashboard (what to include)

Operate the business from one page.

Include GRR, NRR, CAC payback, burn multiple, gross margin, sales cycle, win rate, pipeline coverage, and hiring plan status. Add a simple cohort grid and an ARR bridge chart. Use rolling 3‑month medians to smooth noise.

Board and information cadence

Share a monthly KPI email and a quarterly board pre‑read that references the same numbers. Consistency earns trust in diligence.

Model hygiene and version control

One spreadsheet of truth.

Lock formula ranges, colour code input cells, and protect tabs. Keep a change log with owner and date. Avoid circular references and volatile functions. Store the model in a shared drive with read‑only access for most stakeholders.

Audit trail for diligence

Link the model to a data room index (churn exports, billing reports, payroll) so any number can be verified quickly.

How to present in a partner meeting

Tell a cause‑and‑effect story.

Open with the ARR bridge. Show how pipeline converts, how cohorts behave, and where cash goes. Tie hiring to milestones and unit economics. Keep a backup ‘assumptions’ tab handy for questions. Finish with risks and mitigations already costed in the plan.

Common pitfalls (and fixes)

Top‑down targets, hidden definitions, and over‑hiring.

Fix by anchoring to actual conversion and retention; adding a clear definitions tab; and pacing hiring to pipeline and activation. Label one‑off deals and annual prepays so they don’t distort trends. Always include a downside case and the triggers to slow spend.

If you’re PLG or usage‑based

Model leading indicators and product funnels.

Add activation, weekly active users, and expansion triggers to your inputs. Connect usage to revenue via pricing ladders or overage rules. Present a view that separates true product‑led expansion from price rises so investors understand durability.

Seat + usage hybrid

Keep seats as the primary meter for predictability and add usage as an overage or add‑on. This balances finance predictability with alignment to value.

Glossary (quick reference)

GRR: (Start ARR − churn − contraction) ÷ Start ARR. NRR: (Start ARR − churn − contraction + expansion) ÷ Start ARR. CAC payback: months to recover CAC (prefer GM‑adjusted). Burn multiple: net burn ÷ net new ARR. LTV: GM‑adjusted contribution over customer lifetime.

FAQ

Quick answers to common Series A model questions.

• Do I need a three‑statement model?
  Keep it simple. A driver‑based revenue model with cash flow and hiring is enough for most SaaS Series A raises.
• How many scenarios should I include?
  Base, upside, and downside. Use toggles to change conversion, churn, and hiring ramp.
• What about seasonality and annual prepays?
  Model explicitly and annotate in the ARR bridge and cash tabs so spikes aren’t misread.
• How detailed should COGS be?
  Enough to show gross margin and scalability: hosting, support, and any third‑party data or payments fees.

Want the Google Sheet and a quick review?