Financial Model Execution Recipe: Stage-Appropriate Structure from Pre-Revenue to Growth
Purpose
This recipe produces a complete, stage-appropriate financial model spreadsheet: assumptions tab, revenue model, cost structure, P&L, cash flow, unit economics dashboard, and scenario analysis — ready for investor meetings, internal planning, or board reporting. The model complexity matches the funding stage, from a 1-page pre-seed burn-rate calculator to a 12-tab Series A cohort model. In 2026, investors evaluate capital efficiency and path to profitability above headline growth. [src1] [src7]
Prerequisites
- Business model defined — how the company makes money (subscription, transaction, usage, etc.)
- Pricing structure established or hypothesized (ARPU, contract value, pricing tiers)
- Cost structure understood at least roughly (team size, infrastructure, tools)
- Target funding stage identified — this determines model complexity
- Google Sheets or Excel access — Google Sheets (free)
- Revenue data (if post-revenue) — Stripe dashboard or accounting system export
Constraints
- Revenue projections must be bottom-up: number of customers x ARPU per segment. Top-down projections (“1% of a $10B market”) are investor red flags. [src3]
- Assumptions must be explicit and on a separate tab — hidden assumptions cannot be evaluated or stress-tested. [src5]
- Burn rate accuracy is more important than revenue accuracy at pre-revenue/seed — investors focus on how efficiently you deploy capital. [src2]
- Model should cover 18-36 months forward — less than 18 months does not show enough trajectory; more than 36 months is fiction. [src4]
- All models need a scenario toggle: base case, upside, downside — investors want to see how you think about risk. [src1]
- 2026 benchmark: LTV:CAC ratio target is now 4:1 (up from historic 3:1) because capital is no longer free. [src7]
- Gross margins of 80%+ are the strong operating position for SaaS; below 70% raises investor concerns. [src7]
Tool Selection Decision
Which model approach?
├── Pre-seed AND no revenue
│ └── PATH A: Simple Burn Model — Google Sheets, 1-2 tabs
├── Seed AND < $50K MRR
│ └── PATH B: MRR Waterfall Model — Google Sheets, 3-5 tabs
├── Series A AND $50K+ MRR
│ └── PATH C: Cohort Model — Google Sheets/Excel, 8-12 tabs
└── Growth AND $200K+ MRR
└── PATH D: Full Three-Statement — Excel + Foresight/Causal, 12-20 tabs
| Path | Tabs | Revenue Model | Unit Economics | Build Time |
|---|---|---|---|---|
| A: Simple Burn | 1-2 | Simple: customers x ARPU | CAC + LTV basic | 1-2 days |
| B: MRR Waterfall | 3-5 | MRR waterfall (new + expansion - churn) | Full funnel | 4-6 days |
| C: Cohort Model | 8-12 | Cohort-based + departmental P&L | Cohort LTV | 7-10 days |
| D: Full Three-Statement | 12-20 | Segment + geography | Channel-level | 10-15 days |
Execution Flow
Step 1: Build Assumptions Sheet
Duration: 3-4 hours · Tool: Google Sheets
Create the “Assumptions” tab (always the leftmost tab). Document all key assumptions with color coding: blue = input (changeable), black = calculated. [src5]
Categories to include:
- Revenue: ARPU, customer growth rate, churn rate, expansion rate, sales cycle length
- Costs: Headcount plan, average salary by role, infrastructure per customer, SaaS tools
- Timing: Month of first revenue, hiring schedule, fundraising timeline
- Market: TAM/SAM, addressable segment size, competitive pricing range
Cite the source for each assumption (e.g., “Churn: 5% monthly — industry median for B2B SaaS at $50-$200 ACV per Recurly benchmarks”).
Target: 15-30 documented, sourced assumptions.
Verify: Every number in subsequent tabs traces back to this sheet. No hidden or hardcoded assumptions elsewhere. · If failed: If assumptions cannot be sourced or justified, the model is speculative — acknowledge this and focus on burn rate accuracy instead.
Step 2: Build Cost Structure
Duration: 3-4 hours · Tool: Google Sheets
Build monthly cost model by category:
- People: Salary + benefits + payroll tax (add 20-30% to base salary for total cost) [src4]
- Infrastructure: Hosting, databases, monitoring, CDN — estimate per-customer unit cost
- Tools/SaaS: Stripe fees, email, analytics, CRM, design tools, accounting software
- Professional services: Legal, accounting, tax preparation
- Marketing/sales: Ad spend, content, events, sales tools
- General & Admin: Insurance, office (if any), bank fees, miscellaneous
Separate COGS (cost of goods sold) from OpEx — this matters for gross margin calculation.
Verify: Monthly burn rate matches bank statement reality (if post-revenue). Total cost includes payroll tax/benefits (20-30% on top of salary — the #1 modeling error). [src4] · If failed: If costs are materially different from actuals, reconcile with accounting records before proceeding.
Step 3: Build Revenue Model (Stage-Appropriate)
Duration: 4-8 hours (varies by stage) · Tool: Google Sheets
Pre-Revenue (Path A): Simple: projected customer count x ARPU x month = MRR. Model 3 acquisition scenarios. Show path to first $1K MRR, then $10K MRR.
Seed (Path B): MRR waterfall: New MRR + Expansion MRR - Contraction MRR - Churned MRR = Net New MRR. [src3] Target metrics:
- LTV:CAC ratio: 4:1+ (2026 benchmark, up from historic 3:1) [src7]
- Gross margin: 70%+ for SaaS (80%+ is strong) [src7]
- Monthly churn: <5% for SMB, <2% for enterprise
- CAC payback: <12 months (great); <18 months (acceptable) [src7]
Series A (Path C): Cohort-based revenue model with departmental P&L. [src6] Revenue segmented by tier, customer size, billing frequency. Must show path from current ARR to $5M-$10M ARR within 18-24 months.
Verify: Revenue model is bottom-up with defensible assumptions. If LTV:CAC < 1:1, business model is fundamentally broken at current economics. · If failed: If unit economics are negative, adjust pricing, reduce CAC, or improve retention before modeling further.
Step 4: Build P&L, Cash Flow, and Hiring Plan
Duration: 4-6 hours · Tool: Google Sheets
Build monthly P&L for 24-36 months:
- Revenue (by segment/product)
- COGS → Gross profit and gross margin
- Operating expenses by department (Engineering, Sales, Marketing, G&A)
- EBITDA and operating income
Cash flow statement:
- Account for timing differences (annual vs monthly billing, payment terms)
- Calculate ending cash balance each month
- Highlight months where cash goes negative under each scenario
Hiring plan:
- Model each hire by month: role, department, salary, benefits (add 20-30%), equity grant
- Link to P&L departmental expenses
- Revenue per employee target: >$100K ARR at seed, >$200K at Series A [src4]
Verify: P&L matches revenue model and cost structure exactly. Cash flow shows positive ending balance under base case. No circular references. · If failed: If cash goes negative under base case, adjust spending or fundraising timeline. Run model audit mode to find circular references.
Step 5: Build Scenario Analysis and Investor Narrative
Duration: 4-6 hours · Tool: Google Sheets
Build three scenarios using a toggle switch on the Assumptions sheet:
- Base case: Current plan with realistic assumptions
- Upside (+30-50%): Faster acquisition, lower churn, higher ARPU
- Downside (-30-50%): Slower growth, higher churn, delayed hiring
Sensitivity tables: vary each of 3-5 key assumptions +/- 20-50% and show impact on runway, ARR, and profitability. [src1]
Burn multiple benchmark: Net burn / Net new ARR — target <2x (efficient), 1x (excellent). [src3]
Rule of 40 check: Growth rate + profit margin should exceed 40% (2026 benchmark: 40-50% healthy, >60% elite). [src7]
Write 1-page narrative explaining model story: why these growth rates, why this cost structure, key risks, what this capital enables.
Verify: Downside case still shows a viable path. Can explain every assumption to an investor. Sensitivity analysis shows no single variable kills the company with a 20% negative change. [src2] [src4] · If failed: If downside case kills the company, the base case is too aggressive — build in more buffer.
Output Schema
{
"output_type": "financial_model",
"format": "XLSX",
"tabs": [
{"name": "Assumptions", "description": "All input assumptions with sources, color-coded blue=input black=calculated", "required": true},
{"name": "Revenue", "description": "Bottom-up revenue model appropriate to stage", "required": true},
{"name": "Costs", "description": "Monthly cost structure with COGS/OpEx separation", "required": true},
{"name": "P&L", "description": "Monthly P&L statement with gross and operating margins", "required": true},
{"name": "Cash Flow", "description": "Monthly cash flow with ending cash balance per scenario", "required": true},
{"name": "Unit Economics", "description": "CAC, LTV, LTV:CAC, gross margin, burn multiple, CAC payback", "required": true},
{"name": "Hiring Plan", "description": "Month-by-month headcount with role, salary, benefits", "required": false},
{"name": "Scenarios", "description": "Base/upside/downside toggle with sensitivity tables", "required": true}
],
"projection_range": "18-36 months",
"scenario_count": "3 (base, upside, downside)"
}
Quality Benchmarks
| Quality Metric | Minimum Acceptable | Good | Excellent |
|---|---|---|---|
| Assumptions documented | > 10 with sources | > 20 with sources | > 30 with sources and benchmarks |
| Revenue projection accuracy (6-month check) | Within 50% of actual | Within 30% of actual | Within 15% of actual |
| Internal consistency (circular refs) | Zero circular references | Zero + all tabs cross-referenced | Zero + full audit trail |
| Scenario resilience | Downside viable | Downside viable + sensitivity tables | All scenarios + break-even analysis |
| Model build time | < 15 days | < 10 days | < 7 days |
| Investor feedback | “Acceptable” | “Clear and well-thought-out” | “Best model I've seen at this stage” |
If below minimum: Re-verify assumptions against market data, reconcile with actual financial records, and simplify model to match stage.
Error Handling
| Error | Likely Cause | Recovery Action |
|---|---|---|
| Circular reference error in Excel/Sheets | Revenue depending on costs that depend on revenue | Break the loop: use prior month's value as input, not current month |
| Revenue projections wildly different from actuals | Over-optimistic growth assumptions | Replace projections with conservative trendline from actual 3-month data |
| Burn rate higher than modeled | Forgot payroll tax/benefits (20-30%) or tool costs | Audit cost tab against actual bank statements; add 25% buffer to people costs |
| Investor says model is too complex | Pre-seed model with 12 tabs | Delete all tabs except Assumptions, Revenue, Costs, Burn Rate for pre-seed |
| Investor says model lacks depth | Series A model with 3 tabs | Add cohort analysis, departmental P&L, hiring plan, balance sheet |
| Scenarios show no path to profitability | Unit economics broken or costs too high | Fix pricing first (increase ARPU or reduce churn), then re-model |
Cost Breakdown
| Component | DIY (Founder) | Finance Consultant | Fractional CFO |
|---|---|---|---|
| Pre-seed model | $0 | $500-$1,500 | N/A |
| Seed model | $0 | $1,500-$3,000 | $2,000-$4,000 |
| Series A model | $0 | $3,000-$8,000 | $4,000-$10,000 |
| Model audit / review | $0 | $500-$2,000 | $1,000-$3,000 |
| Ongoing maintenance | $0 (5-10h/month) | $500-$1,500/month | $3,000-$8,000/month |
| Total (one-time) | $0 | $2,000-$12,000 | $5,000-$15,000 |
Constraint: At pre-seed, founders should build the model themselves — it forces understanding of the business economics. Outsourcing model building at this stage is a red flag for investors. [src2]
Anti-Patterns
Wrong: Building a 12-tab model for a pre-seed raise
Over-engineering signals that the founder spends time on spreadsheets instead of customers. Pre-seed investors want market understanding and founder capability, not financial precision. [src2]
Correct: Match model complexity to stage
Pre-seed: 1-2 pages. Seed: 3-5 tabs. Series A: 8-12 tabs. Build more complexity only when you have data to support it. [src1]
Wrong: Top-down revenue projection (“We just need 1% of a $10B market”)
This reveals zero understanding of customer acquisition. Every investor has seen this pattern and dismisses it immediately. [src3]
Correct: Bottom-up: customers x ARPU with acquisition channel logic
“We acquire X customers/month through [channel] at Y% conversion, paying $Z ARPU, with W% monthly churn.” This is defensible and testable. [src5]
Wrong: Hockey-stick projections with no inflection rationale
Revenue flatlines for 12 months then suddenly rockets — with no explanation of what changes. Real growth comes from specific actions that should be modeled as step-changes. [src4]
Correct: Tie growth inflections to specific milestones
“Revenue accelerates in Month 9 because Sales Hire #1 ramps and we launch self-serve onboarding.” Each inflection point has a cause in the model. [src4]
When This Matters
Use when a founder needs to produce an actual financial model spreadsheet for fundraising, planning, or board reporting — not just a document about what goes in a financial model. Requires business model definition and at least rough cost estimates as inputs. The output feeds directly into the fundraising execution recipe as required investor material.