Budgeting and Forecasting

The statements (P&L, balance sheet, cash flow) are backward-looking. This post covers the forward-looking side: budgeting (planning what to spend and earn) and forecasting (projecting future financials), plus scenario planning and how these guide decisions. This is where finance becomes a tool for steering the business, not just recording it — and it connects directly to the cash/runway concerns that determine a startup’s survival.

Budgeting: the financial plan

A budget is a financial plan for a future period — how much the company expects to earn and intends to spend, laid out in advance. It turns strategy into numbers:

• It’s a plan and a constraint. A budget expresses what the company intends to do financially — planned revenue and, especially, planned spending across the business (departments, projects, headcount). It both plans resources (allocating money to priorities) and constrains them (a budget is a limit — “this is what we’ve allocated”). This is why “it’s not in the budget” is a real answer: the budget is the agreed financial plan, and spending outside it needs justification.
• It allocates limited resources to priorities. Because money is finite, budgeting forces choices: what to fund and what not to. This is fundamentally about priorities — a budget is strategy made concrete in money. When engineers wonder why a project isn’t resourced, the answer is often that it didn’t win a budget allocation against other priorities. Budgeting is where strategic priorities become funding decisions.
• It sets expectations to measure against. A budget creates a baseline to compare actual results against — “budget vs actual.” Tracking where reality diverges from plan (a department overspending, revenue under target) is a core management tool, revealing problems and informing adjustments. The budget isn’t just a plan; it’s a yardstick.

Budgeting is planning and constraining the company’s finances — allocating limited money to priorities and creating a baseline to measure against. It’s strategy expressed in numbers, which is why understanding it explains many resourcing decisions. But a budget is a plan; the business also needs to project what will actually happen, which is forecasting.

Forecasting: projecting the future

A forecast is a projection of what the company’s financials will actually be, based on assumptions and current trends — a model of the likely future, updated as reality unfolds:

• It projects the future from assumptions. A forecast builds a model of future revenue, costs, cash, etc., from assumptions — growth rate, churn, hiring plans, conversion rates, and so on. Change the assumptions and the forecast changes; the forecast is only as good as its assumptions, so making them explicit and reasonable is the craft. (This is exactly like any model an engineer builds — inputs, logic, outputs — which makes forecasting intuitive for technical people.)
• Budget vs forecast. A budget is what you plan/intend (often set once for a period); a forecast is your current best projection of what will actually happen (updated regularly as new data comes in). They differ: you might be forecasting to miss your budget (projecting lower revenue than planned), which is a signal to act. Both matter — the budget is the plan, the forecast is the reality-tracking projection.
• The cash forecast is critical. For startups especially, forecasting cash — projecting the cash balance forward to see when it runs out (runway, from the cash post) — is vital. A cash forecast answers “how long until we run out of money, given our plan?” — the existential startup question. Forecasting cash flow (not just profit) is what reveals runway and the need to raise or cut before it’s too late.

Forecasting projects the likely financial future from explicit assumptions, updated as reality unfolds — and it’s the tool for anticipating problems (a coming cash crunch, a revenue miss) before they arrive. For engineers, it’s a familiar modeling exercise. And because the future is uncertain, good forecasting doesn’t produce one number but several, through scenarios.

Scenario planning

Because forecasts rest on uncertain assumptions, wise financial planning considers multiple scenarios rather than a single prediction:

• Model a range, not a point. Instead of one forecast, model several — commonly a base case (most likely), an optimistic case (things go well), and a pessimistic/downside case (things go poorly). Each uses different assumptions (higher/lower growth, more/less churn, etc.), producing a range of outcomes. This acknowledges that the future is uncertain and prepares you for more than one version of it.
• Downside planning is protective. The pessimistic scenario is especially valuable: modeling “what if revenue is lower / growth slower / the raise is delayed?” reveals whether the company would survive and what it would need to do (cut costs, extend runway, raise sooner). Planning for the downside — knowing your options if things go badly — is prudent risk management, particularly around cash/runway. Many companies get in trouble by planning only for the optimistic case.
• Scenarios inform decisions and contingencies. Different scenarios lead to different plans — “if we hit the base case we do X; if the downside happens we do Y (cut here, raise sooner).” This turns forecasting into contingency planning: you decide in advance how you’ll respond to different futures, rather than being caught flat-footed. It’s stress-testing the plan against uncertainty.

Scenario planning replaces false precision (one confident forecast) with honest range-and-contingency thinking — modeling optimistic, base, and downside cases so you’re prepared for uncertainty and have plans ready, especially for the downside. It’s how forecasting becomes robust decision-making under uncertainty rather than a single fragile bet.

Using budgets and forecasts to steer

Bringing it together, budgeting and forecasting are how a business steers — turning finance from record-keeping into active management:

• Plan, then track against the plan. Set a budget (the plan), then continuously compare actuals and update the forecast (reality). The gap between plan and reality is the signal: where you’re ahead, behind, over, or under — and where to act. This plan-track-adjust loop is core financial management, and it’s iterative (like any control loop).
• Anticipate and act early. The great value of forecasting is lead time — seeing a cash crunch, a revenue shortfall, or a budget overrun coming, while there’s still time to respond (cut costs, raise money, change plans). Finance’s forward view lets you act before problems become crises. For startups, forecasting the cash-out date early enough to raise or cut is literally survival.
• Make decisions with the numbers. Budgets and forecasts inform real decisions — can we afford this hire? what happens to runway if we do? is this project worth the spend? Running the numbers (how a decision affects the forecast) turns finance into a decision tool. This is financial literacy in action: using the forward view to make and justify choices (which the final post develops).
• Update as reality changes. Forecasts aren’t set once — they’re updated as new data arrives, staying an accurate model of the likely future. A stale forecast is useless; a regularly-updated one is a live instrument for steering. Treat it as a living model, not a one-time document.

Budgeting (planning and constraining finances, allocating money to priorities) and forecasting (projecting the likely future from assumptions, updated continuously) are the forward-looking tools that turn finance into steering — with scenario planning (base/optimistic/downside cases) preparing for uncertainty, especially around cash and runway. They let a business anticipate problems and decide with the numbers. Next, the final post: using all of this — ratios, financial health, and making decisions.

Key takeaways

• A budget is a forward financial plan — how much the company expects to earn and intends to spend — that both allocates limited money to priorities (strategy made concrete, which is why “it’s not in the budget” is real) and creates a baseline to measure actuals against (“budget vs actual”).
• A forecast is a projection of what will actually happen, built from explicit assumptions and updated as reality unfolds — distinct from the budget (plan/intent vs current best projection): you might forecast to miss your budget, which is a signal to act, and the cash forecast (projecting the cash-out date/runway) is existential for startups.
• Because assumptions are uncertain, model multiple scenarios (base/optimistic/pessimistic) rather than one prediction — downside planning is especially protective (knowing whether you’d survive and what you’d do if things go badly), and scenarios enable contingency planning (deciding responses to different futures in advance).
• Budgeting and forecasting turn finance into steering: set the plan, continuously track actuals and update the forecast, and act on the gap — the great value is lead time to anticipate cash crunches, shortfalls, or overruns while there’s still time to respond (for startups, forecasting the cash-out date early enough to raise or cut is survival).
• Use the numbers to make and justify decisions (can we afford this hire? what does it do to runway?), and keep forecasts updated as a living model — a stale forecast is useless, a regularly-updated one is a live instrument for steering the business.

Further reading

• EBITDA — a common profitability measure in planning
• Burn rate — what cash forecasting projects
• SaaS and recurring-revenue metrics (previous post)