Documenting Your Financial Assumptions (And Why It Matters)

Every forecast is built on assumptions. The quality of your forecast depends not just on the numbers you project, but on how well you understand and document the assumptions behind them.

Well-documented assumptions serve multiple purposes: they make your forecast defensible, enable meaningful updates when reality diverges from expectations, and demonstrate analytical rigor to investors.

What Counts as an Assumption

An assumption is any input to your model that isn’t a known fact. These fall into several categories:

Growth Assumptions

Monthly or annual revenue growth rate
Customer acquisition rate
Conversion rates through your funnel
Expansion and upsell rates
Churn rate

Economic Assumptions

Average contract value or deal size
Customer lifetime value
Customer acquisition cost
Gross margin percentage
Payment terms and collection timing

Operational Assumptions

Hiring timeline and ramp periods
Productivity rates (revenue per employee, customers per rep)
Infrastructure costs at various scales
Timing of major initiatives

External Assumptions

Market size and growth
Competitive dynamics
Economic conditions
Regulatory environment

The Documentation Framework

For each significant assumption, document:

1. The Assumption Itself

State it clearly and specifically.

Weak: “Revenue will grow” Strong: “Revenue will grow 12% month-over-month for the next 12 months”

2. The Basis

Why do you believe this? Options include:

Historical data: “We’ve averaged 11% MoM growth over the past 6 months”
Industry benchmarks: “Top-quartile SaaS companies at our stage grow 10-15% MoM”
Bottom-up analysis: “Our sales team can close 10 deals/month at $5K each”
Comparable companies: “Competitor X grew at similar rates at this stage”
Management judgment: “Based on our pipeline and market conversations”

3. The Confidence Level

How certain are you?

High confidence: Based on substantial historical data or contractual commitments
Medium confidence: Based on limited data or reasonable projections
Low confidence: Based on estimates with significant uncertainty

4. The Sensitivity

What happens if you’re wrong?

If 12% growth is actually 8%, revenue is 15% lower by month 12
If 12% growth is actually 6%, we run out of cash 4 months earlier

5. The Update Trigger

When will you revisit this assumption?

Monthly, based on actual growth data
Quarterly, unless we miss by more than 20%
When we launch the new product (expected Q2)

Example: Documented Assumptions

Here’s how this looks in practice:

Assumption: Monthly revenue growth rate

Attribute	Value
Assumption	12% MoM growth
Basis	Historical average (11% over 6 months) plus expected impact of new sales hire
Confidence	Medium
Sensitivity	±4% growth changes Year 1 revenue by 25%
Update trigger	Monthly review; revise if actual differs by >3% for two consecutive months

Assumption: Monthly customer churn

Attribute	Value
Assumption	4% monthly churn
Basis	Industry benchmark (SMB SaaS: 3-5%); we have only 3 months of data showing 3.5%
Confidence	Low
Sensitivity	Each 1% change in churn affects LTV by ~25%
Update trigger	Monthly review; revise after 6 months of data

Assumption: Engineering headcount

Attribute	Value
Assumption	Add 2 engineers in Q2, 2 in Q3
Basis	Product roadmap requirements; current hiring pipeline
Confidence	High for Q2 (candidates identified); Medium for Q3
Sensitivity	Each engineer delay reduces product velocity by ~15%
Update trigger	When offers are extended/accepted; pipeline review monthly

Where to Document Assumptions

In the Model

Include an assumptions tab or section in your financial model with:

All key assumptions in one place
Clear links to where each assumption is used
Version history when assumptions change

In Supporting Documentation

Create a separate assumptions document with:

Full context and rationale for each assumption
Data sources and analysis
Scenario sensitivity analysis
Update log

In Presentations

When presenting to investors or board:

Highlight the 3-5 most critical assumptions
Show sensitivity analysis for each
Explain how you’ll validate them

The Hierarchy of Assumptions

Not all assumptions matter equally. Categorize them:

Tier 1: Make or Break

These assumptions fundamentally determine outcomes. Getting them wrong by 50% changes everything. Examples:

Revenue growth rate
Churn rate
Customer acquisition cost

Document these extensively. Run multiple scenarios. Track obsessively.

Tier 2: Significant Impact

These assumptions materially affect results but don’t change the fundamental story. Examples:

Average contract value
Hiring timeline
Infrastructure costs

Document with clear rationale. Update quarterly.

Tier 3: Minor Impact

These assumptions affect details but not overall conclusions. Examples:

Software tool costs
Travel expenses
Small vendor contracts

Document once. Update annually or when significant changes occur.

Focus your documentation effort on Tier 1 and 2 assumptions.

Common Mistakes

Hidden Assumptions

Assumptions buried in formulas rather than documented explicitly. Someone reviewing your model (including future you) can’t find or validate them.

Fix: Extract all assumptions into a dedicated section. Formulas should reference the assumptions section, not contain hard-coded values.

Stale Assumptions

Assumptions set 12 months ago and never updated despite new information.

Fix: Establish a regular review cadence. Compare assumptions to actuals monthly for critical items.

Optimism Bias

Assuming best-case outcomes without acknowledging uncertainty.

Fix: Document confidence levels honestly. Build scenarios that stress-test optimistic assumptions.

Inconsistent Assumptions

Growth assumptions that imply 50 new customers per month while sales capacity assumptions only support 30.

Fix: Cross-reference related assumptions. Ensure your model is internally consistent.

No Source Attribution

“We assume 15% growth” with no explanation of where that number came from.

Fix. Every assumption needs a basis. Even if the basis is management judgment, say so explicitly.

Using Assumptions in Conversations

With Investors

Investors don’t expect you to predict the future perfectly. They want to see that you:

Understand what drives your business
Have thought critically about uncertainty
Can articulate how you’ll validate assumptions
Will update projections as you learn

Lead with your most critical assumptions. Explain the basis. Show what happens if they’re wrong.

“Our forecast assumes 12% monthly growth, based on our trailing six-month average of 11% and the addition of our first sales hire. If growth comes in at 8%, we’ll have 18 months of runway instead of 24, and we’d adjust by slowing our Q4 engineering hiring.”

This demonstrates analytical maturity that a single-point forecast never can.

With Your Team

Share assumptions with functional leaders. They often have information that can validate or challenge your projections.

Sales knows whether the pipeline supports growth assumptions
Engineering knows whether hiring timelines are realistic
Customer success knows whether churn assumptions match reality

Make assumption review part of regular operating cadence.

The Assumptions Checklist

Before finalizing your forecast:

All significant assumptions are documented explicitly
Each assumption has a stated basis
Confidence levels are assigned honestly
Critical assumptions have sensitivity analysis
Assumptions are internally consistent
Update triggers are defined
Someone else can understand and validate the assumptions
Related assumptions across functions are aligned

Good assumption documentation transforms a forecast from a guess into a tool for decision-making.

Profitual prompts you to document assumptions as you build your forecast. Track assumption changes over time and see how updates affect your projections. Start building.