Cash Flow Forecasting for Startups: What Investors Look For

A startup cash flow forecast shows how much cash the company will hold month by month, given its hiring plan, revenue ramp and other spending, and therefore how long it can operate before it needs more funding. Investors read it to judge whether the founders understand their business and how far a round will take them. This guide explains how to build one, what the key assumptions are, how to compute runway correctly and what experienced investors tend to probe. It builds on the general method in cash flow management.

What the forecast must answer

A good startup forecast answers four questions plainly:

1. How much cash do we have today, and how much do we burn each month?
2. How long is the runway, given the plan, not just the current month?
3. What do we need to achieve before the cash runs out, and by when?
4. How much do we need to raise, and what will it buy?

If a reader cannot answer these within a minute of opening your model, simplify the model.

Burn and runway: the basic math

Net burn is monthly cash out minus monthly cash in. Gross burn is total cash out. Runway is how many months the cash lasts.

The simplest runway formula divides cash by current monthly net burn. A company with $1,200,000 in the bank and a net burn of $90,000 a month has 13.3 months of runway by that measure. But burn rarely stays flat. Hiring, product spending and marketing usually raise it. The correct approach is to subtract the projected burn month by month until cash runs out.

Worked example

A hypothetical company starts with $1,200,000 and plans to hire steadily. Projected net burn in thousands of dollars:

Cash runs out in month 10, when the company needs $150,000 but has $115,000. The runway is about 9.8 months (9 months plus 115 divided by 150, or 0.77 of a month), not the 13.3 months suggested by dividing cash by the starting burn. The gap between 13.3 and 9.8 is the cost of the hiring plan. This is why investors want the month-by-month build, not the shortcut.

The structure of a startup forecast

Keep it as simple as the business allows. A typical monthly model for 18 to 24 months has these blocks.

1. Revenue and cash receipts

Forecast revenue from drivers, not from a growth percentage pulled from the air. For example:

• Subscription software: customers × price, with churn. Include whether customers pay monthly, quarterly or annually. Annual prepayment brings cash in early and is a significant benefit to runway.
• Services: billable hours or projects × rate, with invoicing and payment lags.
• Products: units × price, less returns, with the retailer or marketplace payment schedule.
• Marketplaces and platforms: transaction volume × take rate, with settlement timing.

Then convert revenue to cash. If invoices are paid in 45 days, cash lags revenue by that amount. Include sales tax and payment processor fees where relevant.

2. Payroll and headcount

For most startups, people are the largest cost. Build a hiring table with role, start date, salary, payroll taxes and benefits. A loaded cost is often well above salary, so use your actual rates. Show headcount by month and cost by team. Timing matters: a hire delayed by two months changes runway visibly.

3. Other operating costs

Group them into categories you can defend: software and cloud hosting, marketing and sales, professional fees, rent, insurance, travel, and contractors. Tie variable items to drivers where possible (for example, hosting costs per customer).

4. Capital spending and one-time items

Equipment, deposits, legal costs for a financing, and similar items. Show them in the month they are paid.

5. Financing

Show existing debt service, any committed funding and the planned raise as a separate line, so readers can see the forecast with and without it. Never bury the raise inside operating cash flow.

6. Cash balance and key outputs

Opening cash, net cash flow, ending cash, monthly burn and runway. Add a line for the minimum cash level you would not go below, such as two months of payroll.

What investors probe

Different investors focus on different things, but several questions come up repeatedly.

See unit economics for the metrics that often sit behind the revenue and cost drivers.

Choosing the amount to raise

A simple approach is to work backward from the milestone.

1. Define the milestone the next round depends on, such as a revenue level, a product release or a customer count.
2. Estimate the time to reach it using the base case.
3. Add a buffer for delay. A common rule of thumb among founders is to plan for the milestone to take longer than expected, and to begin the next fundraise with several months of cash in hand. Treat that as guidance, not a rule: the right buffer depends on your market and how quickly you can raise.
4. Compute the cumulative burn through that date plus the buffer, and subtract current cash.

In the example above, suppose the milestone takes 12 months and the company wants a 6-month buffer. The plan needs 18 months of cash. Continuing the burn at $150,000 for months 11 to 18 adds 8 × 150 = $1,200,000. Cumulative burn through month 10 was $1,235,000, so through month 18 it is $2,435,000. The company has $1,200,000, so it needs to raise at least $1,235,000. A prudent founder rounds up and looks at the scenarios below.

Scenario cases

Include at least three cases, as described in cash flow scenario planning.

• Base: the plan you believe in.
• Downside: revenue grows more slowly (for example, half of the planned rate), while hiring has already been committed.
• Cost-control: the actions you would take if the downside happened, such as pausing hiring, cutting marketing and extending runway.

Show the runway for each. Investors will often care more about your cost-control case than your base case, because it shows whether you can steer.

Working capital and timing traps

Startups often overlook the following.

• Annual contracts. Cash comes upfront but revenue is recognized over time. Cash can look strong while a refund liability or service obligation builds. Track deferred revenue separately.
• Payment processing delays. Platforms and card processors may hold funds for days or weeks.
• Payroll taxes and benefits. These land on specific dates and can spike.
• Sales tax. If you collect it, you must remit it. It is not your cash.
• Customer deposits. They are liabilities, not free cash.
• Tax credits and grants. Show them when received, not when earned.
• Equipment leases and minimum commitments that cannot be cut quickly.

Keep it a living model

A forecast made for a funding round and never updated will mislead you. Update it monthly at minimum, weekly if cash is tight. Compare actuals to forecast, record the differences and revise. Over time, this record becomes evidence of how well you know your business, and it improves your next investor conversation. The weekly detail method is in the 13-week cash flow forecast, and a starting layout is in how to build a cash flow forecast you will actually use.

Common mistakes

• Dividing cash by current burn. It ignores planned hiring and spending growth.
• Hockey-stick revenue with no driver. Investors will challenge it. Build revenue from pipeline, conversion and price.
• Ignoring the cash conversion cycle. Revenue is not cash.
• Combining the raise with operations. Show financing separately.
• No downside case. It signals you have not tested your plan.
• Too much detail. A forecast with hundreds of lines is hard to review. Focus on the drivers that matter.
• Hiding assumptions. Put key assumptions on one page and label each one.
• Never updating. An outdated model loses credibility.

When the company sells physical products

Hardware and consumer-product startups face an extra cash burden: they pay for inventory and tooling before they sell. Deposits to manufacturers, long lead times and freight mean cash goes out many months before revenue arrives. For these companies, the demand forecast and purchase plan are central to runway. A preorder or retailer commitment can finance part of the build, but cash flow still needs to be modeled by purchase order. See demand planning and inventory optimization for how to link demand, purchasing and cash.

FAQs

What should a startup cash flow forecast include?

Monthly cash receipts built from revenue drivers and payment timing, payroll by hire, other operating costs, one-time items, financing shown separately, and the resulting cash balance, burn and runway. Add base, downside and cost-control cases.

How do you calculate runway?

Subtract the projected net burn month by month from your current cash until it reaches zero. Dividing cash by the current month's burn gives a quick estimate, but it overstates runway if burn is expected to grow.

How far ahead should a startup forecast?

Typically 18 to 24 months monthly, with a weekly 13-week view when cash is tight. The longer view supports fundraising conversations, and the shorter one supports day-to-day control.

How much runway should a startup have?

There is no universal answer. Many founders aim to start raising while they still have a meaningful buffer, because fundraising takes time and weak negotiating positions are costly. Choose a buffer based on your market, your milestones and your ability to cut costs.

What do investors look for in a cash flow forecast?

Clear drivers behind revenue, a hiring plan tied to milestones, an understanding of working capital, a realistic view of the downside, and evidence that the round reaches a meaningful milestone with a reasonable buffer.