Burn Rate vs. Runway: The Two Numbers Founders Confuse
The two numbers founders confuse
Burn rate is what's leaving the bank account. Runway is how many months of burn you have left. A common error in either one is leaving out CapEx, year-end tax, or seasonal AP that hasn't been paid yet.
Sam Yang, Founder of Level. Cash forecasting method, not a contractor-cohort finding.
A familiar point in founder discussions: a business can be profitable on paper and still fail, because it runs out of cash. Working capital gets less attention than profit, even though it decides survival.
The two numbers that govern this, burn rate and runway, are also two numbers that are easy to calculate incorrectly. This post is about the right way to calculate each, the trap of confusing them, and the rolling cash forecast that keeps you ahead.
Burn rate: more nuanced than "monthly loss"
The textbook definition of burn rate is "monthly net cash outflow." That's a simplification that breaks down quickly in practice.
There are actually three burn rates to know:
Gross burn
= Total monthly cash outflow (all expenses, regardless of revenue)
This is what your monthly costs are if revenue went to zero. No measured typical range is established here. Size gross burn from your own bank and AP records.
Net burn
= Cash outflows minus cash receipts during the same month
This is the actual monthly cash decrease. If you pay $40K and collect $25K during the month, net burn is $15K. Accrued revenue that has not been collected does not fund this month's payroll.
Adjusted burn
= Net burn excluding one-time items, payable to receivable timing differences, and seasonal adjustments
This is the trickier number, and the one that matters for forecasting. Some months your burn looks artificially low because a customer paid early. Some months it looks high because you paid annual insurance. Adjusted burn smooths these out.
Use normalized burn for a constant-run-rate scenario, then put one-time payments back into a dated cash forecast. Normalizing out a tax payment does not make its cash obligation disappear.
The most common burn rate calculation errors
Error 1: Using the most recent month
The single worst way to calculate burn is taking last month's bank balance change. This includes random timing (large customer payment, large vendor payment, tax payment) that doesn't repeat.
The fix: use a 3-6 month trailing average, normalized for one-time items.
Error 2: Ignoring annual or quarterly expenses
Insurance, software contracts, tax payments, equipment refreshes, and bonuses don't show up monthly but they're real burn. Most founders look at January-April burn and forget that May has the insurance renewal.
The fix: build a 12-month forecast that includes every quarterly and annual obligation.
Error 3: Using cash basis when bills are growing
If you're growing rapidly and haven't paid the upcoming AP, your cash burn looks low, until the bills come due. Fast-growing businesses are especially exposed to this timing gap.
The fix: track AP aging alongside cash. Rising AP is deferred cash outflow. Schedule each bill in the week it is due, so it is counted once.
Error 4: Not separating recurring from project costs
A consulting engagement, a one-time legal fee, a single equipment purchase, these inflate burn for one month. They shouldn't be in your run-rate burn calculation.
The fix: explicitly categorize expenses as recurring vs. one-time.
Runway: the simple math, the harder application
Runway is straightforward:
Runway (months) = Current cash / Monthly net burn
If you have $300K cash and burn $15K/month, you have 20 months of runway. That's the simple math.
The harder application:
Runway should include incoming cash, not just current cash
Do not add $80K of receivables to $300K cash and divide by $15K net burn if those collections are already included in the net-burn estimate. That counts them twice. Start with bank cash, then schedule each collection and payment once in the forecast. For contractors, separate retainage release, weekly payroll, material prepayments and seasonal supplier bills.
Runway should account for revenue trajectory
In a fictional scenario with $40K monthly payments and $25K collections growing 10% each month, collections reach $40,263 in month 6 (five increases). Burn reaches zero then, assuming costs and collection timing stay constant. The static 20-month ratio cannot describe that path. Growth may also require inventory or hiring, so forecast those payments rather than assuming flat costs.
Runway should account for expense trajectory
If you're hiring or scaling marketing, monthly burn grows. For example, if net burn averages $25K a month instead of $15K, the same $300K lasts 12 months, not 20.
Runway should be calculated weekly during stress periods
When you're under 6 months of runway, weekly is the right cadence. Monthly is too slow when you're actively raising or considering layoffs.
Free benchmark review
See how your cash cycle benchmarks.
Start with a free conversation about your priorities. With agreed access to the relevant records, we compare your numbers with applicable benchmarks and identify what to review first.
The 13-week rolling cash forecast
The single most valuable artifact for any business with finite cash runway is a 13-week rolling cash forecast.
It should include:
| Section | Detail |
|---|---|
| Beginning cash | Bank balance start of week |
| Cash inflows | Expected customer payments by week, weighted by collection probability |
| Cash outflows | Payroll (specific dates), AP commitments, recurring expenses, taxes, debt service, capital purchases |
| Net change | Inflows minus outflows |
| Ending cash | Beginning + net change |
| Below-zero warning | Any week with projected cash below operating minimum |
Update it weekly. Reconcile actual vs. forecast line by line, and note which misses came from timing and which from amount. Track your own forecast error over the first several weeks rather than assuming it improves on a set schedule.
Assign an accountable forecast owner with access to payment schedules and the judgment to test collection timing and decision impact. That can be a CFO, controller, qualified bookkeeper or founder with support; a job title does not establish forecast quality.
Example: an internal transfer does not increase burn
Suppose the business has $100,000 across its own bank accounts. Moving $15,000 into its own tax-reserve account leaves total cash at $100,000. Recording that transfer as a $15,000 cash expense would overstate burn. When $15,000 later leaves the business to pay the tax authority, total cash falls to $85,000, assuming no other flows. Include that external payment once in the cash forecast, and classify it according to the obligation. Avoid counting both the transfer and the payment.
Relay illustrates how separate cash buckets can make allocations visible. Its published plans describe multiple checking accounts. Its QuickBooks bank-feed documentation covers settled transactions, so upcoming payroll, supplier bills and tax payments still need their own forecast schedule. Show consolidated cash separately from cash available for discretionary spending; earmarked, restricted and readily available cash require different treatment when assessing runway. Use the forecast method with the banking product you select.
Burn rate decisions: throttle or accelerate
A common owner question: if we're growing fast, say 7% a day, but burning cash heavily, should we let growth run until most of the funds are gone and then raise, or slow growth down now?
The answer depends on the unit economics:
Accelerate when:
- Contribution-based LTV/CAC supports acquisition cost; payback is shortening
- Customer payback fits the available runway (under 12 months is an illustrative planning screen)
- Each new customer is incrementally profitable
- Capital is available at reasonable cost
Throttle when:
- Unit economics are negative (you lose money on each customer)
- LTV/CAC is unclear or worsening
- You're > 6 months from being able to raise next round and runway is tight
- You're spending on growth without measuring its return
A common mistake is accelerating because growth feels good without verifying that the unit economics support it. "Growing 7% a day" with negative unit economics is just dying faster.
The structural fixes for burn rate problems
When burn is genuinely too high, there are five levers:
1. Pricing increase
Often the highest-leverage fix. Model a 10% price test with volume loss, contract restrictions and collection timing. Additional billed revenue improves cash only when collected, and margin only after incremental costs.
2. Revenue concentration on profitable segments
Not all revenue is created equal. Identify your most profitable customer segments and concentrate sales effort there. Drop or de-prioritize unprofitable segments.
3. Cost reduction in non-strategic areas
Software stack rationalization, lower-tier subscriptions, contractor vs. employee rebalancing, office space reduction. Size the opportunity from your actual contracts, cancellation dates and owner-approved cuts. No measured recoverable-cost range is established here.
4. Compensation restructuring
Model lawful compensation changes with employment and tax advisers. Salary deferral or a new contractor label does not remove wage obligations or determine worker classification.
5. Capital raise
The last resort. Capital is expensive (dilutive or interest-bearing). Raising should extend runway to a defined milestone, not just "extend runway generally."
When to call Level
Cash forecasting and burn management are core fractional CFO work. For early-stage businesses (post-revenue, pre-profit) with finite runway, Level can:
- Build the 13-week rolling forecast
- Calculate true unit economics and LTV/CAC
- Model alternative cost structures
- Coordinate fundraising preparation (financial diligence pack)
- Provide ongoing monthly burn analysis
Scope depends on how many entities, accounts and payment schedules the forecast must cover, and is set after a review rather than assumed in advance.
FAQ
What's a "good" burn rate? There's no good or bad, only sustainable or unsustainable. These are planning thresholds, not measured survival rates. 24+ months of runway on realistic revenue assumptions gives time to adjust. Under 12 months leaves little room for a raise or cost changes that can take a quarter or two to land.
Should I always try to be cash-flow positive? Not necessarily. Some businesses (high-growth SaaS, hardware, anything with long sales cycles) require sustained burn to capture market position. The question is whether the burn is producing returns and whether the runway is sufficient to reach the next milestone.
How do I know if my burn rate is wrong? Compare your weekly bank balance changes to your forecast for 4-6 weeks. If actuals routinely differ from forecast by more than a tolerance you set in advance (for example, 10-15%), your burn calculation is missing something, usually one-time items, AP timing, or seasonal patterns.
When should I sound the alarm to the team about burn? Set triggers in advance so the decision is not made under pressure. One planning example: below 9 months of runway, have a serious conversation; below 6 months, take action (cost reduction or capital raise); below 3 months, treat it as an emergency. Adjust the triggers to how long your raise or cost changes actually take.
Related reading:
Get the next one
Want next week's benchmark in your inbox?
One email a week. Real numbers from 2,200+ contractors in the research universe. No fluff. Unsubscribe anytime.
Related reads
Cash Flow
Profitable on Paper, Broke in the Bank: The Four Gaps That Eat a Contractor's Cash
The median contractor collects 85.1% of what it bills (n=464) and invoices 97.1% of logged hours (n=963). Four distinct record checks, with explicit timing and denominator limits.
Cash Flow
The October Problem: October Roofing Permits Run 46% Above the 2023 Monthly Average, Then the Cash Crunch Hits
October 2023 roofing permits were 45.8% above roofing's own 2023 monthly average, then fall into winter. Why a fall demand peak can set up a Q1 cash squeeze, how to test whether it applies to you, and how to plan for it.
Cash Flow
The 13-Week Cash Forecast Is a Data-Layer Test
A 13-week cash forecast exposes whether field status, billing, AR, AP, payroll, backlog, and accounting data actually tie.

About the author
Sam Yang
Founder & CEO
Founder of Level, the always-on finance team for contractors, service businesses, and ecommerce brands. Ex-CFO across trades, SaaS, and service businesses. 4 years as Director of Growth Product at BuildOps, building financial tooling used by 1,000+ commercial contractors. Four years in PE and investment banking rolling up and acquiring service businesses, $2.5B in total transactions including M&A and IPOs. Stanford MBA, Brown undergrad. The Level founding team's analysis of 2,200+ contractors ($13.25B in job revenue) across operating, private-equity, and CFO roles anchors the Level Index benchmark research.
LinkedIn