A financial projection should do more than show a line climbing up and to the right. It should show what has to happen for that growth to occur, what it will cost, and whether the company has enough cash to get there.
For a startup, that means connecting assumptions about customers, pricing, hiring, expenses, and payment timing to projected financial results. A useful model lets you change an assumption and see what happens to revenue, profit, and cash—not just present one attractive outcome.
This guide walks through the pieces, the build process, and the mistakes to avoid. If you’re ready to work in a spreadsheet, Graphite’s free startup financial model templates provide a starting point for SaaS and ecommerce/CPG businesses.
Financial projections are estimates of a company’s future financial performance based on stated assumptions. They can help founders plan hiring, assess capital needs, test pricing decisions, and discuss the business with investors or lenders.
The central word is assumptions. A projection is not a promise that revenue will reach a particular number. It is a way to show how the business might perform if customer growth, costs, collections, and other drivers develop as expected.
A complete projection generally connects three statements:
The U.S. Small Business Administration’s business-planning guidance includes forecasted income statements, balance sheets, cash flow statements, and capital expenditure budgets in financial projections. The detail and time horizon you need will depend on the decisions the model must support.
Before opening a template, ask what you need the projection to answer.
Are you deciding whether to hire six people? How much capital to raise? Whether a new sales channel can support its acquisition costs? When inventory purchases will strain cash? Each question may require different detail.
Monthly projections are often useful for the near term because they show the timing of revenue, payroll, spending, and cash needs. A longer-range view can support strategic planning, but it should not imply the same precision as next month’s forecast.
If the immediate concern is whether cash will cover obligations over the coming weeks, supplement the longer-term model with a 13-week cash flow forecast. The two tools answer related questions at different levels of detail.
Use the financial information you already have: revenue by product or customer segment, direct costs, operating expenses, payroll, debt, bank balances, and recent payment patterns. Reconcile the starting figures before projecting forward. A model built on an inaccurate cash balance or incomplete expense list will carry those problems into every future period.
A new business may have limited historical data. In that case, make the assumptions explicit and identify which ones are based on contracts, current plans, market evidence, or management judgment.
Avoid typing “revenue grows 20%” into every month unless you can explain what produces that growth. Start with drivers that fit the business:
For example, suppose a SaaS company starts a month with 200 paying accounts, expects to add 20 and lose four, and charges $500 per account per month. Those assumptions describe the drivers of revenue. The model then needs a consistent rule for when new accounts begin paying, when departing accounts stop paying, and whether any accounts change plans.
That is more useful than a revenue number entered without explanation. If sales slow or churn rises, you can change the driver and see the effect.
Connect costs to the activity that causes them where possible. Payment processing, hosting, fulfillment, and inventory may change with sales volume. Payroll, software, rent, and professional services may follow hiring plans, contracts, or scheduled increases.
Keep one-time expenses visible. A large equipment purchase, implementation fee, or product launch can be lost in an annual average even though its timing matters greatly to cash.
The result should let you see both the cost of delivering the product or service and the spending required to operate and grow the company.
Revenue is not always collected in the month it is recognized, and an expense is not always paid in the month it appears on the income statement. Those timing differences can make a company’s cash position look very different from its projected profit.
For example, a company might record a strong month of revenue while a major customer pays 45 days later. Payroll and vendors still need to be paid in the meantime. Inventory purchases can create a similar gap: cash may leave well before the related products are sold.
Build collection and payment assumptions into the cash flow projection. Then review the lowest projected cash balance and the date it occurs, rather than looking only at revenue or year-end cash.
A model’s balance sheet should reflect the consequences of its other assumptions. Customer invoices that have not been paid affect receivables. Inventory purchases and sales affect inventory. Borrowing affects debt and cash. Profit or loss affects equity over time.
These links are also a quality check. If the statements do not reconcile, the model may be missing a transaction, applying an assumption inconsistently, or treating cash and accrual activity as the same thing.
A base case is only one possible path. Test changes that could alter a real decision: slower sales, higher churn, delayed collections, faster hiring, lower gross margin, or an inventory order arriving earlier than planned.
Focus on outcomes such as cash runway, the lowest cash balance, gross margin, and the amount of financing required. A useful scenario tells you which assumption creates the risk and what you could do if it changes.
Imagine the SaaS company above expects 20 new accounts next month. Sales reports that 10 are now likely to close one month later.
A connected projection should show more than “revenue is lower.” Depending on the company’s billing and cost structure, the delay could also change:
The company can then decide whether to change spending, revise hiring timing, or accept the temporary cash impact. That is what makes projections useful for management: they turn a changed assumption into a visible decision.
Update the model when actual results or operating plans make its assumptions stale. For many startups, a monthly review alongside financial reporting is a practical starting point. Cash-constrained businesses or companies facing a major decision may need to revisit key assumptions more often.
Compare actual results with the forecast and ask why they differed. Were sales lower than expected? Did a customer pay late? Did hiring move forward? Was a cost omitted? Updating the numbers without understanding the cause makes the next projection less useful.
The model should retain enough history to show what management previously expected. Otherwise, a continually revised forecast can obscure whether the company is improving its ability to plan.
Starting with the result you want. A target is useful, but the projection needs operational assumptions that could plausibly produce it.
Treating revenue as cash. Collection timing can determine whether the business can meet its obligations even when sales are growing.
Using one growth rate for everything. Revenue, direct costs, hiring, and overhead rarely change at the same pace.
Leaving the statements disconnected. A revenue change should flow through the relevant costs, cash movements, and balance-sheet accounts.
Presenting one case as certain. Show the assumptions, test meaningful alternatives, and explain the decisions you would make if conditions change.
You do not need to build every formula from a blank sheet. Graphite’s free startup financial model templates include models for SaaS and ecommerce/CPG businesses. Choose the version that fits your business, replace the sample assumptions with your own, and check that the outputs reflect how your company earns and spends cash.
A template provides structure. The value comes from the assumptions you enter, the connections you test, and the decisions you make from the results. If you need help building a model around your growth plans and capital needs, explore Graphite’s Finance and FP&A services.
A connected model typically includes a projected income statement, cash flow statement, and balance sheet. Supporting schedules for revenue, hiring, debt, or inventory may be needed depending on the business.
Use a horizon that fits the decision. Monthly detail can help with near-term operating and cash decisions; a longer-range view can help with strategy and capital planning. Show more uncertainty as the forecast extends further out.
Start with the evidence available: pricing, contracts, expected sales activity, hiring plans, supplier terms, and known expenses. State where an assumption is uncertain, then compare the projection with actual results as the business develops.
No. Financial projections can model revenue, expenses, financial position, and cash over a broader planning horizon. A 13-week cash flow forecast focuses on the near-term timing of cash receipts and payments, week by week. A company may need both.