How to Calculate Startup Runway With Changing Monthly Revenue

To calculate startup runway when revenue changes every month, build a month-by-month cash forecast instead of dividing today’s cash by one fixed burn-rate average. Start with unrestricted cash, add the cash you realistically expect to collect each month, subtract every cash payment due, and find the first month in which the ending balance falls below your minimum operating reserve.

The familiar formula—cash divided by monthly net burn—is useful as a quick snapshot. It becomes misleading when sales are seasonal, customers pay late, hiring is planned, annual software renewals cluster in one month, or costs rise with usage. A rolling cash schedule shows when the money is actually expected to enter and leave the bank.

Startup runway vs. burn rate

Gross burn is the cash the company spends during a month. Net burn is cash outflows minus cash inflows during that month. Runway is the time until available cash reaches a defined floor.

For a stable pre-revenue company, the basic estimate is:

Runway in months = Unrestricted cash ÷ Average monthly net burn

If a startup has $240,000 in usable cash and consistently burns $30,000 per month, the simple estimate is eight months. But if revenue is growing, payroll is about to increase, or a large insurance payment is due, an eight-month headline may not describe the real cash-out date.

Use cash, not accounting profit

Runway is a liquidity calculation. Begin with money the business can actually use, not booked revenue, signed contracts, accounts receivable, unused credit limits, or restricted funds. A company can show a profit on an income statement and still run short of cash if customers pay slowly.

The U.S. Small Business Administration recommends organizing expenses into one-time and monthly costs, and notes that financial planning should include cash-flow statements and detailed projections. Its current business planning guidance is a useful reference for separating startup costs, recurring expenses, and financial projections.

Build the runway model month by month

Create one column for each month and these rows:

• Beginning unrestricted cash
• Cash collected from customers
• Other confirmed cash inflows
• Payroll and contractor payments
• Hosting, software, and infrastructure
• Marketing and sales spending
• Rent, insurance, professional fees, taxes, and debt payments
• Equipment and other one-time purchases
• Total cash inflows
• Total cash outflows
• Net cash change
• Ending cash
• Minimum operating reserve

For each month, use:

Net cash change = Total cash inflows − Total cash outflows

Ending cash = Beginning cash + Net cash change

Next month’s beginning cash = Previous month’s ending cash

The runway ends in the first month where ending cash falls below your chosen reserve—not necessarily at exactly zero. A company may need cash for payroll, refunds, taxes, shutdown obligations, or emergency infrastructure before the bank balance is empty.

Forecast collections, not just revenue

Revenue belongs in the month it is earned for accounting purposes, but cash runway depends on the month it is collected. If an annual contract is invoiced in January and paid in March, the runway model should show the cash in March.

Divide expected collections into categories:

• Existing recurring customers: forecast from active contracts, adjusted for normal cancellations and failed payments.
• Signed invoices: use contractual due dates, then apply a realistic late-payment assumption.
• Usage-based revenue: connect expected volume to price and collection timing.
• New sales: probability-weight them instead of treating the full pipeline as cash.
• One-time setup or service fees: place them in the expected collection month.

A signed deal is not the same as cash. If the company historically collects invoices 20 days late, reflect that behavior rather than the ideal payment date.

Use a probability-weighted sales pipeline carefully

Do not add every sales opportunity at face value. One simple method is to multiply the expected cash by a conservative close probability and delay it by the typical sales cycle plus payment period.

Weighted expected collection =
Potential invoice × Close probability × Collection probability

For example, a $20,000 opportunity with a 40% close probability should not automatically contribute $20,000 to runway. Even the weighted $8,000 belongs in the month when payment is likely to arrive, not the month of the sales call.

For the downside scenario, exclude unsigned pipeline entirely. This reveals whether the startup survives if expected new deals slip.

Model costs that change with growth

A flat-expense forecast hides the very costs that often accompany revenue. Link variable costs to an operational driver:

• Payment fees as a percentage of collected sales
• Cloud or API costs per active user, request, or generated unit
• Customer support costs per account
• Shipping and fulfillment per order
• Sales commissions when cash is collected or a contract is signed
• Refunds, chargebacks, credits, and fraud losses

If monthly revenue doubles but infrastructure and support costs also increase, the full revenue increase does not extend runway. Forecast contribution cash—the cash collected after costs directly tied to delivering that revenue.

Add payroll by start date, not by aspiration

Payroll is often the largest predictable cash expense. Build a hiring schedule with:

• Current salary or contractor cost
• Employer taxes and benefits where applicable
• Planned start month
• Recruiting fees and equipment
• Expected raises, bonuses, or contract changes
• Notice, severance, or termination obligations where relevant

A role planned for “next quarter” should not appear as one-third of a salary in every month. Put the full expected cash cost in the months after the likely start date, and include the laptop, recruiting, onboarding, and benefit costs when they occur.

Do not forget lumpy payments

Annual and quarterly bills make average burn deceptively smooth. Review bank and card statements, contracts, the tax calendar, and renewal notices for:

• Annual software subscriptions
• Insurance premiums
• Cloud commitments
• Legal and accounting work
• Tax deposits and filings
• Debt principal and interest
• Domain, hosting, and security renewals
• Equipment purchases
• Refund reserves and customer credits

The SBA advises founders to distinguish one-time expenses from monthly expenses and to account for costs such as salaries, insurance, professional services, marketing, equipment, and website expenses. That classification is helpful, but the runway model must also place each payment in its real month.

Calculate runway in three scenarios

Create base, downside, and upside versions using the same model structure.

Base case

Use the most defensible operating plan: expected retention, realistic collection delays, committed hires, and approved spending.

Downside case

Delay new revenue, increase churn, lengthen collection time, include a modest cost overrun, and assume fundraising closes later than hoped. The downside case is not a disaster fantasy; it is a plausible slower outcome.

Upside case

Allow faster sales or better retention, but include the added delivery, support, hiring, and infrastructure costs required to serve that growth.

Report the runway range, such as “seven months in the downside case and eleven months in the base case,” instead of presenting one false-precision number.

A worked runway example

Assume a startup begins January with $180,000 in unrestricted cash. Collections are expected to grow, but a new hire begins in March and an annual insurance payment falls in April.

The simple average of the first two months might suggest more runway than the company actually has because it misses the March hiring cost and April insurance payment. If management requires a $25,000 operating reserve, usable runway ends in June even though the account is not exactly zero.

Use both a 13-week forecast and an 18-month plan

A monthly model is useful for hiring, fundraising, and strategic decisions. A 13-week cash forecast is better for near-term control because it shows the specific week when payroll, tax, card, or supplier payments clear.

Maintain both:

• 13-week forecast: update weekly using bank balances, invoice status, and exact payment dates.
• 12-to-18-month model: update monthly for hiring, revenue, pricing, and fundraising assumptions.

The first four to eight weeks should rely heavily on known amounts. Later months can use driver-based assumptions. Never let the long-range model replace short-term cash monitoring.

Separate confirmed funding from possible funding

Do not extend runway for a fundraising round until the funds are closed and available, or at least make that assumption visibly separate. Investor interest, a verbal commitment, a signed term sheet, and cash in the bank are different stages with different risks.

Create a “funding excluded” scenario. If the company cannot survive the expected fundraising timeline, start cost reductions, bridge planning, or revenue actions early enough to matter. The purpose of runway is to create decision time, not to provide reassurance.

Connect runway to milestones

Cash duration alone does not show whether the startup can reach a valuable proof point. Add milestone rows for:

• MVP launch
• First paying customer
• Target monthly recurring revenue
• Retention or usage threshold
• Regulatory or security readiness
• Break-even month
• Next fundraising start date

If a product has not yet demonstrated demand, use our guide on validating a startup idea before building an MVP to reduce the risk of spending the runway on untested assumptions.

The model should answer: “Do we have enough cash to reach the next milestone with time left to respond if it slips?” A startup with nine months of runway but a twelve-month product plan has a planning problem today.

Track actual cash against forecast

At month-end, compare forecast and actual results for each major line. Record the difference and its cause:

• Revenue collected earlier or later
• Higher or lower churn
• Unexpected refunds
• Hiring delays
• Cloud or advertising overspend
• Annual bills omitted from the model

Do not simply overwrite the old forecast. Keeping variance history shows which assumptions are consistently optimistic. For online service businesses, reconcile payment records to cash deposits; if you use payment links, our Stripe Payment Link guide explains how to keep payment records and customer references organized.

Common runway mistakes

• Using total bank balance when some funds are restricted.
• Treating invoiced revenue as collected cash.
• Averaging burn across too many months while the cost structure is changing.
• Excluding taxes, debt payments, refunds, and annual renewals.
• Adding new revenue without its delivery costs.
• Counting unsigned fundraising as available cash.
• Assuming a cost reduction takes effect immediately.
• Letting formulas break when a month is inserted or a scenario changes.
• Running the model only before a board meeting.

Final runway checklist

• Start with unrestricted, available cash.
• Forecast collections in the month they are likely to arrive.
• Map every cash payment to its actual due month.
• Link variable costs to revenue or usage drivers.
• Add hires by start date with taxes, benefits, and equipment.
• Set a minimum reserve above zero.
• Build base, downside, and upside scenarios.
• Exclude unclosed funding from the survival case.
• Pair the monthly model with a rolling 13-week forecast.
• Update actual-versus-forecast variances every month.

A good runway forecast is not the longest-looking number. It is a transparent cash calendar that tells founders when decisions must be made, which assumptions matter most, and whether the company can reach its next milestone before its options narrow.