Building Your Financial Model
January 17, 2026
Build a VC-ready financial model from scratch using bottom-up logic, sensitivity analysis, and a three-year monthly format investors actually trust.
Bottom-Up vs Top-Down Modeling
Bottom-up modeling starts from the atomic unit of your business — typically a customer or transaction — and multiplies upward. A SaaS model might start with a monthly new-visitor count, apply a 3 percent trial conversion rate, a 25 percent trial-to-paid conversion, and a $150 average contract value. Every revenue line has a mechanical driver: change the conversion rate and revenue recalculates automatically. This is the only modeling approach that investors treat as credible because every assumption is testable against actual data.
Top-down modeling starts from a market size estimate and works downward: "the market is $5 billion and we will capture 1 percent in three years, producing $50 million in revenue." Investors routinely dismiss top-down projections because the math from market-share assumption to revenue obscures every operational detail. The percentage of market captured tells you nothing about how many salespeople you need, what your CAC is, or whether your infrastructure can scale to that volume. Use top-down only as a sanity check on the output of a bottom-up model — if your bottom-up projects $50M and the market is only $100M, something is wrong.
Key Assumptions and Inputs
Every financial model contains assumptions that, if wrong, invalidate the output. The four most consequential for a SaaS company are: monthly churn rate, customer acquisition cost, average contract value, and sales cycle length. Change any one by 50 percent and your three-year revenue projection moves by 30 to 60 percent. Documenting each assumption with a source — "2.5% monthly churn based on our last six cohorts" rather than "industry average" — is what separates investor-grade models from wishful spreadsheets.
Secondary inputs that founders often underestimate include headcount plan timing and infrastructure costs. Adding a senior engineer in month 4 instead of month 1 changes the cash flow profile significantly. AWS costs that are 8 percent of revenue at $100K ARR may compress to 4 percent at $1M ARR through reserved instances and architecture improvements, or they may increase if you are building data-intensive products. Model these inputs as percentage-of-revenue formulas where possible so they scale automatically rather than requiring manual updates each time the revenue forecast changes.
Sensitivity Analysis
A sensitivity table varies two key assumptions simultaneously and shows the range of outcomes across their intersection. Place monthly churn rate across the top (1%, 2%, 3%, 4%, 5%) and monthly CAC down the side ($200, $400, $600, $800, $1,000) and populate each cell with 24-month net revenue. The resulting 5×5 grid shows you which combination produces acceptable outcomes and which produces failure — your base case should sit somewhere in the middle columns, not in the optimistic corner.
Running sensitivity analysis before finalising projections often reveals asymmetric risks that single-point estimates hide. In many SaaS models, a 1 percent increase in monthly churn has more destructive impact on 24-month revenue than a 50 percent increase in CAC, because churn compounds exponentially while CAC is a linear cost. Discovering this in a spreadsheet before a board meeting is infinitely better than discovering it because the numbers come in worse than modeled for three consecutive quarters.
VC-Ready Format
A VC-ready financial model is a 36-month monthly model — not annual, not quarterly. Monthly granularity is required because cash flow timing, hiring decisions, and fundraising triggers all happen at the month level. The model must include at minimum: a profit and loss statement, a cash flow statement showing cash balance at month end, a headcount plan with each role and start month listed, and cohort retention for at least the last four to six customer cohorts.
Start from an existing template rather than building from scratch. The Visible.vc free financial model and the Standard Treasury startup model on GitHub are both structured to match what Series A investors expect to receive. Delete the example assumptions, replace with your own data, and spend the saved structural work time on making your assumptions defensible. A model that looks exactly like what investors see from 50 other companies every year is better than a bespoke format that forces the analyst to re-learn the layout before evaluating the numbers.
Frequently Asked Questions
Why do investors prefer bottom-up over top-down models? Bottom-up models tie every revenue line to a mechanical driver like conversion rate or CAC that can be verified against actual company data. Top-down models derive revenue from market-share assumptions that have no operational basis and cannot be tested.
Which four assumptions matter most in a SaaS financial model? Monthly churn rate, customer acquisition cost, average contract value, and sales cycle length. Each one individually can shift a three-year revenue projection by 30 to 60 percent if it moves by 50 percent from the base assumption.
What is sensitivity analysis and why does it matter? Sensitivity analysis varies two key assumptions simultaneously and shows the range of outcomes across their combinations. It reveals which risks are asymmetric — for most SaaS models, churn has more destructive impact than CAC because it compounds.
What does a VC-ready financial model include? A 36-month monthly P&L, a cash flow statement, a headcount plan with role-level detail, and cohort retention data for the last four to six customer cohorts. Annual or quarterly models are not granular enough for Series A due diligence.
Should I build my financial model from scratch or use a template? Use an existing template like Visible.vc or Standard Treasury. Templates save structural work and produce a format investors already know how to navigate, so they can evaluate assumptions rather than spending time understanding your layout.
