How Much Runway Do We Really Have?

Most founders know their bank balance. Fewer know how long it actually buys them. Those two numbers are not the same thing, and the gap between them is where companies quietly run out of time.

The standard formula—cash on hand divided by monthly burn—sounds rigorous until you stress-test it against real cash flows. The moment you account for when revenue actually arrives, when payroll actually hits, and which dollars in your account are actually yours to spend, the comfortable "fourteen months of runway" often compresses to something closer to nine. That difference is the difference between a deliberate fundraising process and a distressed one.

Why cash ÷ monthly burn is not your real runway

The formula treats burn as a smooth, predictable outflow and cash as a fully available pool. Neither assumption holds in practice. Burn is lumpy—annual software contracts, quarterly tax deposits, and one-time hiring costs all land in specific months and distort the average. Cash is not always liquid—restricted balances, outstanding vendor credits, and deposits held against leases sit in your account without being available for operations.

When you divide a partially encumbered cash balance by an artificially smoothed burn number, the quotient looks better than reality. The formula isn't wrong as a rough orientation, but it is a ceiling, not a floor. Founders who plan to the ceiling get surprised. Founders who understand the floor make decisions with actual margin.

The question runway math is supposed to answer

The real question is not "how many months of average burn does our cash cover?" The real question is: on what date does the company lose the ability to meet its obligations without new capital?

That date is determined by the intersection of your cash position, your fixed payment schedule, and your revenue timing. It is a specific moment on a calendar, not a range of months. Working backward from that date—accounting for the six to nine months a serious fundraise typically requires—tells you when you need to be in market. Most founders start that calculation too late because they are working from the comfortable version of the number, not the precise one.

Runway math is supposed to create a decision window. If it is giving you false confidence, it is doing the opposite.

AR timing can shorten runway before revenue changes

If you invoice on net-30 or net-45 terms, your revenue and your cash are perpetually out of sync. A strong sales month does not help your runway until the cash actually settles. In the meantime, you are funding operations out of the balance you already have.

Consider a company with $600K in the bank, $150K in outstanding receivables, and $100K in monthly burn. The simple formula says six months. But if $80K of that receivables balance is slow-paying and unlikely to clear in the next thirty days, operational cash is closer to $520K—and if two customers push payment to sixty days, you are funding an extra $60K gap out of reserves before you see a dollar of it. The runway just shortened by more than half a month without a single change to the P&L.

This is not a hypothetical. It is the normal experience of any B2B company with meaningful receivables, and it is why a finance function that watches collections weekly—not monthly—matters. The P&L did not change. The cash timing did.

Payroll Friday matters more than the monthly average

Monthly burn is an average. Payroll is a hard date. If your payroll runs on the 1st and the 15th, those are the two moments each month when your bank account needs to clear a specific threshold—regardless of what the monthly average looks like.

A company burning $120K per month on average might have a $75K payroll hit on the 1st and a $45K hit on the 15th, plus rent on the 1st and a major vendor on the 20th. The cash flow within the month is not linear. There are specific days where the account needs to hold a specific balance or the company is in default on its own payroll obligations. Missing payroll is not a financial setback—it is a legal and operational crisis.

Runway planning that does not account for intra-month cash flow timing can show three months of average runway while the company is eleven days from a payroll it cannot fund. The average is technically correct and completely misleading.

Not every dollar in the bank is available cash

Bank balance and available cash are different numbers. Several categories of funds sit in your account without being operationally available.

Security deposits held against office leases are typically non-refundable until lease termination—they are not liquid. Restricted cash tied to banking covenants must maintain a minimum balance or the credit facility triggers. Customer prepayments for services not yet delivered are a liability on your books; spending that cash before delivery creates an obligation you may not be able to fulfill. Payroll tax withholdings that have been collected but not yet remitted are legally the government's money, not yours.

A company with $800K in the bank might have $120K in a restricted deposit, $60K in unremitted payroll taxes due next week, and $90K in prepaid services not yet earned. Operational cash is $530K—not $800K. The simple formula overstates runway by more than thirty percent before a single other variable is considered.

One-time spend breaks steady-state burn assumptions

Monthly burn averages are dangerous precisely because they smooth over the things that actually kill companies: the annual insurance renewal, the conference sponsorship paid in Q1, the engineering contractor brought on for a six-week sprint. None of those appear in your typical monthly burn rate, but every one of them lands in your bank account with full force.

The practical fix is to audit the last twelve months of cash outflows and tag anything non-recurring. Then project forward and ask where those events repeat, or where new ones are scheduled. A founder who knows a $180K server migration is coming in month four should not be calculating runway as if month four looks like month two. The number changes. The decision window changes with it.

This matters most when you are in a hiring mode. Signing bonuses, recruiter fees, equipment purchases, and benefits onboarding costs cluster at the front of a headcount expansion. Burn in months one through three of a hiring push can run thirty to fifty percent above steady-state even if your new hires are fully ramped and productive. Founders who plan against the steady-state number consistently underestimate how tight things get before the new capacity delivers any return.

Fundraising lead time belongs inside the runway calculation

Runway is not how long you can survive. It is how long you have to complete your next financing event—or reach profitability—before survival becomes the question.

That distinction forces you to subtract lead time from whatever number you are carrying. A Series A process that takes five months from first outreach to cash in the account is not five months at the end of your runway. It is five months that need to exist before you hit zero. If you have nine months of cash and the raise takes five, you have four months to decide to start, build materials, warm relationships, and get into rooms. In practice that means you should already be in motion.

Seed rounds at reputable funds are not faster. Strategic deals take longer. Bridge conversations with existing investors still require documentation, board approval, and wire transfers that do not happen overnight. The market environment adds variance on top of all of that. Build in a buffer that reflects real-world process time, not optimistic projections, and then subtract that buffer from the top of your runway number before you tell yourself how much time you have.

Build a weekly cash runway view, not a single-month ratio

Month-end reporting creates a blind spot in the middle. A company can show acceptable burn for two consecutive months while quietly running into a single week where payroll, rent, and a vendor invoice all clear simultaneously and the account drops to a number that would alarm any board member.

A weekly cash view does not require a sophisticated system. It requires mapping when cash actually moves: payroll dates, rent drafts, subscription charges, expected receivables, and any unusual items. Lay those against your opening balance for each week and you can see the low-water marks before they arrive.

This is where AI-enabled finance tooling has started to earn its place in smaller operations. Automated transaction categorization combined with a rolling cash flow model means the weekly view can be maintained without a full-time finance analyst producing a manual spreadsheet every Friday afternoon. The operator gets visibility; the model updates as transactions post; exceptions surface before they become crises.

Where AI-enabled finance improves the runway signal

The traditional approach to cash flow forecasting in an early-stage company is either too manual to stay current or too automated to be accurate. Both fail the same way: by the time the forecast is updated, conditions have already shifted.

AI-enabled finance changes this by shortening the feedback loop. When your accounting system, payroll platform, and revenue data are connected to a model that updates continuously, your runway view reflects what happened this week—not what you reported last month. Variance against forecast becomes visible in near real-time rather than at month-end close when the opportunity to act has often passed.

This also applies to scenario planning. A fractional CFO operating inside an AI-enabled finance infrastructure can run a hiring-freeze scenario, a contract-delay scenario, and an accelerated-collections scenario in the same conversation rather than over a series of offline model builds. The calculation becomes a live input to the decision, not a retrospective on it. That is a different quality of financial leadership than what was available to companies at this stage five years ago. The AI-enabled finance approach is specifically designed to make this kind of dynamic visibility accessible without hiring a full finance team to support it.

When runway uncertainty becomes a financial leadership problem

Uncertainty about burn is normal. Not knowing what you do not know is the actual problem.

A founder who can say "we have 8.2 months of cash, our next large one-time spend is in month three, and we need to be in active fundraise conversations by month four" has uncertainty but not confusion. That founder can make decisions. A founder who answers "how much runway do we have?" with "about a year, maybe more" is operating on a feeling, not a signal.

The difference between those two is almost always a financial leadership gap, not an accounting gap. The books may be closed and reconciled. The transactions may be categorized. But no one has taken responsibility for translating those records into a forward-looking picture that the operator can actually use. This is exactly the terrain where a fractional CFO adds value that a bookkeeper or even a controller is not structured to provide—not because the work is complicated, but because it requires someone whose job is to hold that view and defend it in a conversation with you. The bookkeeper typically stays. The leadership layer sits above the file.

If your P&L looks clean but cash keeps surprising you, the gap between accrual accounting and actual cash timing is often the explanation. That pattern is worth understanding on its own, and the P&L vs bank piece covers it directly.

If you want to pressure-test your runway calculation with someone who will push back on the assumptions rather than confirm them, book a free 30-minute Finance Systems Review. It is a fit-check, not a free diagnostic.