Most founders build their first financial model under pressure. A pitch meeting is coming up, an investor asks for projections, or a bank wants to see numbers before approving a line of credit. The model gets thrown together quickly, and somewhere in the process it stops feeling like a planning tool and starts feeling like a formality; something to produce and move past.
That’s a missed opportunity. A financial model built with some care doesn’t just satisfy outside requests. It forces clarity on how the business actually makes money, where costs accumulate, and what has to be true for the numbers to work. That kind of clarity is useful whether you’re pitching investors or just trying to decide whether to make your next hire.
This guide walks through how to build one from the ground up; practically, without getting lost in spreadsheet complexity that doesn’t serve you.
Before getting into the how, it’s worth being clear on the what, because “financial model” gets used loosely, and the term can mean different things depending on context.
At its core, a financial model is a structured set of assumptions and calculations that projects how your business will perform financially over a future period. It typically covers revenue, costs, cash flow, and the resulting profit or loss.
It is not a guarantee. It is not a commitment you’re making to investors. It is a structured way of thinking through how the business works and what the future might look like under a given set of conditions.
The most useful models are built to be interrogated, where you can change an assumption and immediately see what happens downstream. What if customer acquisition costs go up 20%? What if that enterprise deal closes three months later than expected? A good model makes those questions answerable in minutes.
The most common mistake founders make is opening a spreadsheet before they’ve thought clearly about how the business actually generates revenue.
Before touching a cell, write out, in plain language, the answers to these questions:
How does the business make money? Is it subscription-based, transactional, project-based, usage-based? Each of these has a different revenue driver and a different modeling logic.
What does a customer relationship look like? Do customers pay once or repeatedly? Do they expand their spend over time? Do they churn? The answers shape your revenue trajectory more than any other variable.
What does it cost to deliver your product or service? These are your cost of goods sold, the expenses that scale directly with revenue. Understanding these separately from fixed overhead is essential.
What are your fixed costs? Salaries, rent, software, insurance; the costs that don’t change much regardless of revenue volume.
What drives growth? For most startups it’s some combination of sales headcount, marketing spend, and word-of-mouth. Knowing your primary growth lever is what makes revenue projections something other than a guess.
Getting clear on these before modeling means your spreadsheet reflects actual business logic rather than arbitrary numbers dressed up as projections.
A solid early-stage financial model doesn’t need to be elaborate. It needs to cover the right things.
This is where most of the work lives, and where most models either earn or lose credibility.
Build your revenue from the bottom up wherever possible. Rather than saying “we’ll capture 1% of a $10 billion market,” which tells an investor almost nothing, model it from first principles: how many salespeople do you have, how many deals can each close per month, what’s the average contract value, what’s the expected ramp time for new reps. If you’re building projections ahead of a fundraise, understanding how investors read your financials is worth thinking through early.
For subscription businesses, model revenue in cohorts: how many new customers you add each month, what they pay, and how many you expect to retain. This makes churn visible and forces you to think about its compounding effect over time.
For project-based businesses, model by capacity: how many projects can the team realistically deliver in a quarter, at what average value, with what utilization rate.
The specific logic varies by business model, but the principle is the same: ground your revenue in operational realities rather than market-size math.
COGS are the costs that scale with revenue, what it costs to deliver your product or service. For a SaaS company, this typically includes hosting, customer support, and third-party software costs allocated per customer. For a services firm, it’s primarily the labor that delivers the work.
Separating COGS from operating expenses gives you gross margin, the percentage of revenue left after delivering your product. Gross margin is one of the most scrutinized numbers in any investor conversation, and it belongs in your model clearly.
These are the costs of running the business beyond delivery: sales and marketing, general and administrative expenses, and often research and development. Build these out by department or function, with headcount as the primary driver for people-heavy cost lines.
Be honest here. Founders consistently underestimate operating costs in early models, which makes the path to profitability look shorter than it is. That discrepancy tends to surface at the worst possible time.
Profit and cash are not the same thing – a point that surprises more founders than it should. Why startups with revenue still run out of cash is a dynamic worth understanding before it catches you off guard.
Your cash flow projection starts with net income and adjusts for timing differences: when customers actually pay, when you actually pay vendors, any capital expenditures, debt repayments, or investment inflows. The result is your cash position month by month, and specifically, it tells you when you might run out.
Burn rate and runway belong here. Knowing your monthly burn and how many months of runway you have is non-negotiable for any funded company, and it should be visible at a glance in your model. A clear view of burn rate and runway is one of the financial metrics every CEO should be reviewing regularly.
Every number in your model flows from an assumption. Keep those assumptions in one place; a dedicated tab or clearly labeled section; so they’re easy to find, easy to update, and easy to explain.
When an investor asks “how did you get to this revenue number,” you want to be able to walk them through the logic in about sixty seconds. If the assumptions are buried across fifteen tabs, that conversation gets painful fast.
For most early-stage companies, a three-year model is the right scope. The first year should be built month by month, detailed enough to manage cash and track against actuals. Years two and three can be quarterly or annual, since the precision of monthly modeling beyond 12 months is largely illusory anyway.
What matters more than the length of the model is the integrity of year one. Those numbers need to be operational; meaning the revenue targets are tied to specific sales activities, the headcount assumptions reflect actual hiring plans, and the cost projections are grounded in real vendor quotes and contracts where possible.
Years two and three are where you demonstrate the trajectory and the unit economics at scale. Investors know these numbers will change. They’re looking for whether the business logic holds and whether you understand your own model.
Top-down revenue projections. “If we capture just 0.5% of the market…” is not a revenue model. It’s a hope dressed up as math. Build bottom-up.
Assuming everything goes right. A model that only shows the upside scenario tells investors you haven’t thought seriously about risk. Build at least two scenarios – a base case and a conservative case. Some founders also build an upside. The base case is what you actually believe; the conservative case is what the business looks like if a few things go sideways.
Ignoring working capital. If customers pay you on net-60 terms but you have net-30 obligations, that timing gap shows up in cash flow, not profit. Founders who build profit-only models regularly get surprised by cash shortfalls that the model technically should have flagged.
Hardcoding numbers instead of using assumptions. If your revenue growth rate is typed directly into cells rather than flowing from an assumption, changing it means hunting through the spreadsheet manually. Models built this way are fragile and hard to use in live conversations.
Not updating it. A financial model that gets built for a fundraise and then put in a drawer is just a pitch deck attachment. The value of a model comes from using it; comparing actuals to projections each month, updating assumptions as you learn more, and maintaining a running view of where the business is headed.
What should a startup financial model include?
At minimum: a revenue model built from operational assumptions, cost of goods sold, operating expenses broken out by function, a cash flow projection, and a clearly labeled assumptions section. For investor purposes, most models also include a summary P&L and a headcount plan.
How do you build a financial model with no revenue history?
Start with your business model logic rather than historical data. Define your revenue drivers; customers, pricing, conversion rates, sales capacity; and build projections from those inputs. Be explicit about what you’re assuming and why. Investors understand that early-stage projections are estimates; what they’re evaluating is whether the underlying logic is sound.
What’s the difference between a financial model and a business plan?
A business plan describes the strategy, market, team, and vision. A financial model translates those elements into numbers, specifically, what the business is projected to earn, spend, and generate in cash over time. Most investors want both, but the financial model tends to get more scrutiny.
How accurate do startup financial projections need to be?
Experienced investors don’t expect early-stage projections to be precise. They expect them to be logical, internally consistent, and grounded in real assumptions. The exercise matters more than the output, it shows you’ve thought carefully about how the business works.
Should I hire someone to build my financial model?
For a first model, building it yourself has real value; the process forces you to understand your unit economics and business drivers in detail. But having an experienced CFO or financial advisor review it before sharing with investors is worth doing. A model that has errors or inconsistencies that you missed can be damaging in a pitch context.
What tools should I use to build a financial model?
Most founders use Excel or Google Sheets. Both work fine for early-stage models. The tool matters less than the structure – a clean, well-organized spreadsheet with a clear assumptions section will always outperform a complex model that’s hard to navigate or explain.
Building a financial model from scratch sounds more intimidating than it is. The spreadsheet mechanics are learnable. The harder part, and the more valuable part, is the thinking behind it: understanding your business model deeply enough to translate it into numbers that hold together under scrutiny.
A well-built model won’t make your business succeed. But it gives you a clearer view of where it’s going, forces you to confront the assumptions you’re making, and puts you in a much stronger position in any conversation with investors, lenders, or advisors who need to understand the business quickly.
Start simple. Build it from the bottom up. Keep the assumptions visible. And actually use it once it’s built.
Quadrant works with founders, growing businesses, and nonprofits on outsourced accounting, controller services, and fractional CFO support. If you’re building a financial model and want a second set of eyes before it goes in front of investors, we’re easy to reach.
Congratulations! You’ve reached the end.