← Back to articles

Financial Model Documentation: Explaining Your Assumptions to Investors

Why Model Documentation Matters

A financial model without documentation is just numbers. Investors can't understand your thinking or stress-test your assumptions. When they ask "Why do you assume 2.5% monthly churn?", having detailed documentation backing that assumption demonstrates rigor. Lack of documentation signals either sloppy analysis or unwillingness to show your work—both red flags.

Documentation serves multiple purposes: (1) It forces you to articulate assumptions, revealing weak points, (2) It enables investors to understand your logic and challenge it constructively, (3) It allows team members to maintain and update the model consistently, (4) It provides rationale if you miss projections (investors understand what changed).

Poor documentation is surprisingly common. Founders build models without documenting the 50 assumptions underlying them. Investors can't evaluate the model. Due diligence becomes adversarial ("prove your assumptions") rather than collaborative. Documentation prevents this.

Building an Assumptions Sheet

Create a dedicated "Assumptions" sheet documenting every material assumption: customer acquisition cost, pricing, churn rate, hiring plan, COGS percentage, etc. For each assumption, include: (1) Assumption value, (2) Data source (historical, industry, research), (3) Rationale (why this number), (4) Confidence level (how certain are you), (5) Sensitivity (how much does it matter).

Example: Customer Acquisition Cost (CAC) = $500. Data source: "We've spent $50K acquiring 100 customers through sales/marketing channels." Rationale: "Conservative estimate; includes failed experiments and team ramp time. Current cohorts are $300-400 CAC." Confidence: 85% (some variability by channel). Sensitivity: High (10% change impacts profitability timeline 4-6 months).

This level of detail shows you've thought deeply about assumptions, not just pulled numbers from thin air. It also enables investors to identify which assumptions to focus on. If you rate CAC as high sensitivity, they'll pressure-test it. If you rate rent as low sensitivity, they'll move on.

Data Sources: Measured vs. Projected vs. Researched

Distinguish between assumptions based on: (1) Measured data (you have historical data: "We've acquired 50 customers at $400 CAC"), (2) Projected data (you're extrapolating: "We expect CAC to improve 10% annually as sales process matures"), (3) Researched data (industry benchmarks: "Peer companies have 2-3% monthly churn; we're projecting 2.5%").

Measured data is strongest. Investors give maximum credibility to assumptions backed by real traction. "We've actually acquired customers at this cost" is far more credible than "we think we can acquire at this cost." Lead with measured data; use projections and research to fill gaps.

When using research, cite sources. "Gartner reports SaaS companies average 3% monthly churn" is credible. "We think churn will be 2%" is not. Always reference data sources. For private data, be specific: "Based on conversations with 15 prospective customers..."

Explaining Revenue Assumptions in Detail

Revenue is your most important assumption. Document it thoroughly: (1) Customer segments (how many customer types), (2) Pricing by segment (what does each pay), (3) Customer acquisition plan (how many customers per month), (4) Churn assumptions (monthly churn rate), (5) Expansion assumptions (existing customers upgrade).

Create a revenue model bridge: Starting bookings assumptions → customer acquisition schedule → cohort churn/expansion → resulting revenue trajectory. Walk investors through this bridge. "We'll acquire 10 SMB customers monthly at $5K ACV, and 2 enterprise customers quarterly at $50K ACV. SMB churn is 3% monthly; enterprise is 1.5%. Enterprise expansion is 8% annually. This yields $500K revenue month 12."

Show the math explicitly. Don't just state revenue numbers; show how they derive from customer acquisition and cohort dynamics. Investors should be able to replicate your math using your assumptions. If they can't, your documentation is insufficient.

Documenting Expense Assumptions

Operating expenses are your second-most important assumption. Document: (1) Headcount plan by function (engineering, sales, etc.), (2) Salary ranges by role (what engineers cost, sales reps cost, etc.), (3) Fully-loaded cost methodology (salary + benefits + recruiting + overhead), (4) Hiring schedule (when you hire), (5) Non-headcount expenses (tools, rent, etc.).

Create a headcount table showing: Month, Engineering (count, cost), Sales (count, cost), Marketing (count, cost), etc. Sum all functions and fully-loaded costs to get total operating expense. This transparency enables investors to pressure-test: "Can one CFO really support $10M revenue? We'd expect 2-3 people in that role by then."

For non-headcount expenses, show as percentage of revenue or per-employee: "AWS infrastructure costs 5% of revenue; we've modeled this conservatively based on our current 3% actual, assuming some inefficiency as we scale." "Office and equipment is $2K per employee; typical for Bay Area, includes workspace and tools."

Explaining Churn and Retention Assumptions

Churn is often the most important lever. Document: (1) Historical churn rate (what you're actually experiencing), (2) Churn assumption (what you're projecting), (3) Why it differs (if it does), (4) Drivers of churn (competitive loss, customer bankruptcy, product issues), (5) Plans to improve churn.

Example: "Historical monthly churn is 4% (early customers, less sticky). We're projecting 2.5% long-term as: (a) product matures and becomes stickier, (b) we improve customer success, (c) customer base shifts to larger companies (lower churn). Conservative assumption given improvement trajectory."

Be honest about churn improvement. Churn typically doesn't improve by itself. It requires product improvements, customer success investments, or customer segmentation. If you're assuming 4% → 2% churn improvement, show what's driving it. Otherwise, investors assume optimism bias.

Documenting Go-to-Market and CAC Assumptions

Explain how you'll acquire customers: direct sales, inbound marketing, partnerships, self-serve, etc. For each channel, document: (1) Cost per channel, (2) Acquisition rate (customers per month per resource), (3) Payback period (how long to recover CAC), (4) Scaling plan (what constraints prevent infinite scaling).

Example: "Direct Sales: We hire enterprise sales reps at $200K fully-loaded cost. Based on our pilots, each rep generates $1.5M ARR when fully productive (6-month ramp). CAC is ~$1,600 per enterprise customer ($200K costs / 125 customers annually). Payback is 3-4 months (customer pays $1,500/month, recovers $1,600 CAC in 4 months). Scaling is limited by rep quality and sourcing; we can hire 3-4 reps annually."

This level of detail enables investors to stress-test your sales plan. "You're hiring 2 reps Q1, 3 reps Q2, 4 reps Q3. That's 9 reps in Year 1 generating $13.5M ARR. That's a big ramp. How will you source that many qualified reps?" Forces you to defend your hiring assumptions.

Presenting Assumptions to Investors

Create a 1-2 page summary of critical assumptions for presentation. "Key Assumptions: CAC $500 (based on 100 customers acquired to date), Monthly Churn 2.5% (conservative improvement from 4% historical), ARPU $100/month, OpEx improvement to 30% of revenue by Year 3, Headcount growth 15% annually."

Then provide detailed documentation (5-10 pages) showing data sources, rationale, and sensitivity. Summary is for presentation; detailed doc is for due diligence. Investors will review detailed doc before investing.

Be clear about confidence levels. "High confidence: CAC (based on 100+ customer cohort). Medium confidence: churn improvement (based on product roadmap but not yet delivered). Low confidence: enterprise expansion (new market, no customers yet, based on research)." This honest assessment builds credibility.

Linking Assumptions to Model Outputs

Show how assumptions flow through to key outputs. "Revenue projections assume CAC $500 and churn 2.5%. Profitability timeline depends primarily on churn assumption: if churn is 3% instead of 2.5%, profitability delays 4 months. We're highly confident in 2.5% based on [data]."

Use sensitivity analysis to show which assumptions most impact outcomes. If investors understand that churn is make-or-break, they'll focus on churn improvements rather than other cost-cutting. This directs investor attention where it matters most.

Document how you plan to validate assumptions over time. "We'll measure actual churn quarterly and adjust projections accordingly. If actual churn exceeds 3%, we'll reassess product strategy. We'll track CAC by channel and adjust marketing spend accordingly." This shows you're committed to validating, not just hoping.

Documenting Changes and Updates

Maintain a version history showing what changed quarter-to-quarter. "In Q2, we updated churn assumption from 4% to 3% based on actual data. We increased headcount plan in engineering from 5 to 7 due to product development priorities. We decreased pricing assumption from $150 to $120 due to competitive pressure."

This history shows you're responsive to data and willing to adjust assumptions. It also gives investors confidence that the model isn't static wishcasting—it evolves with reality.

When presenting updated projections, highlight changes. "Our Q2 projections show profitability by Month 45 (vs. Month 38 in Q1 projections). Here's what changed: [list assumption changes]. The main driver was [explanation]." This transparency prevents surprise and enables investors to track your thinking.

Common Documentation Mistakes

Many founders document only favorable assumptions. If there's downside risk (churn could be higher, growth could be slower), document it. Investors will find problems; better you identify them first. Upfront transparency builds credibility.

Another mistake: documentation that's too technical or vague. "Cohort-based revenue model with 18-month tail recovery" is meaningless. "We acquire 50 customers monthly at $500 CAC, they churn 2.5% monthly, and stay with us for average 40 months. 50 × 40 = 2,000 active customers by Year 3, generating $200K MRR" is clear.

Some founders document assumptions but don't show data or rationale. "Churn: 2.5%" with no explanation. Why that number? Based on what? Investors can't evaluate assumptions without rationale.

Creating Investor-Ready Model Documentation

Package your model documentation as a professional document: (1) Executive summary of key assumptions (1 page), (2) Assumptions detail with data sources (5-10 pages), (3) Sensitivity analysis showing impact of assumption changes, (4) Three-statement financials derived from assumptions, (5) Key metrics (CAC, payback, LTV, churn) and how they drive model.

Use clear formatting: headers, bullets, tables. Make it scannable so investors can find what they're looking for. If your doc is dense paragraphs, investors won't read it. Use tables to show assumptions (Assumption | Value | Source | Rationale | Sensitivity).

Include visuals: charts showing revenue progression by segment, OpEx ratio improving over time, cohort analysis showing customer lifetime. Visuals communicate faster than numbers; use them liberally.

Key Takeaways

• Document every material assumption: what it is, where it comes from, why you believe it, how confident you are, how sensitive outcomes are to it.
• Distinguish between measured data (you have evidence), projected data (you're extrapolating), and researched data (industry benchmarks). Prioritize measured.
• Show your work. Revenue assumptions should flow from customer acquisition plan → churn/expansion → revenue trajectory. Investors should replicate your math.
• Create 1-page assumption summary for presentation, 5-10 page detailed documentation for due diligence. Both are essential.
• Use sensitivity analysis to highlight most critical assumptions. Show investors which variables most impact outcomes.
• Be honest about confidence levels. "High confidence in CAC (100+ customers), lower confidence in churn improvement (not yet achieved)" builds credibility.
• Document changes quarterly. Show how projections evolve with data. This responsiveness builds investor confidence.
• Link assumptions to model outputs. "Revenue timeline depends primarily on [assumption]. We're confident because [data]." Clear connection between assumptions and outcomes.

FAQ

How detailed should documentation be?

1-2 page summary for presentation, 5-10 page detailed documentation for due diligence. Include data sources, rationale for every assumption, sensitivity analysis. Don't over-document (100-page models are unreadable), but don't under-document (single number with no explanation is insufficient).

What if we don't have historical data for an assumption?

Use research (industry benchmarks, customer interviews, pilot data) and be honest about it. "We don't have 100 customers yet (early stage) but have conducted 30 customer interviews and 80% indicate they'd pay $100/month at current pricing. Conservative model assumes 70% conversion." This is honest and credible.

Should we show pessimistic assumptions in documentation?

Show base case assumptions in main model/documentation. Then create sensitivity analysis showing what happens if assumptions are pessimistic. "Base case: 2.5% churn. If churn is 3% (pessimistic), profitability timeline extends 4 months." This addresses downside without being depressing.

How often should we update model documentation?

Quarterly when you get new data. Update assumptions to reflect actual performance and revised outlook. More frequently (monthly) makes documentation maintenance burden; less frequently (annually) means documentation is stale during due diligence.

What if an assumption proves wrong during execution?

Update it. "We projected 2.5% churn but actual is 4%. We're investigating drivers: product issues, competitive losses, customer fit mismatch. We've updated Year 3+ projections to 3% churn (improvement plan in progress) but acknowledge risk. Here's what we're doing to improve..." Honesty and clear action plan are more impressive than pretending everything is fine.