Cash Flow and Runway — The Existential Numbers
Startups do not die from lack of profit — they die from lack of cash. Here is how to manage burn and extend runway as a decision tool, not a quarterly report.
🎯 By the end you'll understand
The critical difference between gross burn and net burn — and why only one tells you when you die. How to compute real runway from first principles rather than bank balance arithmetic. Why the 13-week rolling cash forecast is a survival tool, not a reporting exercise. How to trace Forge's cash conversion cycle from sales activity to signed contract to cash deposited. And the specific, common failure mode that kills founders who manage to their bank account rather than their actual burn trajectory.
KEY INSIGHTCompanies die from running out of cash, not from failing to earn profit
A startup can be losing $80K a month on paper and still be months from death — or losing $20K and be weeks from it. The difference is not in the income statement. It is in the timing of cash.
This seems obvious until you watch a founder say "we're doing great — we have $400K in the bank" in the same week they signed three enterprise contracts with 45-day payment terms, added two engineers to support the deployments, and committed to hardware purchases for Q4. That $400K is not their runway. Their actual cash trajectory — accounting for the timing of outflows and inflows — may put them at zero in 90 days. The bank balance is a snapshot of the past. Cash flow management is about the future.
Profit is an accounting concept. Cash is the physical reality of whether your company can make payroll next Friday. You can be profitable on paper while cash-flow negative — if customers pay in 60 days and you pay employees every two weeks, the timing gap between accrued revenue and collected cash is where startups die. The skill is not accounting; it is temporal reasoning about money — understanding not just how much you will earn and spend, but exactly when each dollar moves.
CORE CONCEPTGross burn vs. net burn — only one tells you when you run out
These two numbers appear everywhere in startup finance and are systematically confused. The confusion kills companies.
| Metric | Definition | What it measures | When to use it |
|---|---|---|---|
| Gross burn | Total cash spent per month (all operating expenses paid in cash) | The size of your cost base — how much it costs to keep the company running | Understanding your cost structure; benchmarking against industry comps; identifying the largest cost buckets |
| Net burn | Gross burn minus cash actually received from customers that month | The rate at which you are consuming your cash reserves — how fast you are approaching zero | Computing runway; deciding whether you need capital; setting the raise-or-cut deadline |
| Cash runway | Current cash balance ÷ monthly net burn | The number of months until cash reaches zero at the current trajectory | The existential question — answered weekly, not quarterly |
Here is the core confusion: a rising bank balance does not mean net burn is decreasing. If you raised $1.5M and are depositing it in installments, or if you collected a large upfront annual contract, your bank balance spikes temporarily. Meanwhile, if you hired four engineers in the same quarter to support growth, your gross burn has climbed significantly. A founder who looks at the rising bank balance and concludes "we're in good shape" while gross burn has outpaced revenue growth is operating on a dangerously incorrect mental model.
Forge signed two $42K annual contracts in Q3 — $84K collected upfront. Simultaneously, they hired two engineers at a combined $24K/month run rate. Bank balance went from $310K to $394K in September. It looks like cash improved by $84K. But gross burn is now $52K/month (up from $28K). Revenue cash received will be zero in October and November (those contracts are prepaid and will not renew until Q3 next year). Net burn from October onward: $52K/month. True runway at $394K: 7.6 months — not the 14 months the bank balance appeared to suggest at the $28K old burn rate.
HOW IT WORKSComputing real runway — from first principles
Real runway is not bank balance ÷ last month's spend. That calculation assumes your burn rate stays constant, which it never does after a hiring event, a contract win, or a vendor change. Real runway requires a forward model of your cash inflows and outflows for each of the next 13 weeks.
Map every cash outflow — by category and timing
List every expense and, critically, when cash actually leaves the account — not when it accrues. Payroll: every two weeks on specific dates. Rent: first of the month. SaaS subscriptions: monthly auto-charges. AWS/hosting: 30 days after invoice. Hardware vendors: based on negotiated terms (30/60/90 days). The goal is a week-by-week picture of cash leaving the account, not a monthly average. A $52K/month burn rate might mean $26K leaves on the 15th and another $26K on the 30th — or it might mean $8K is flat weekly with a $20K payroll spike every other Friday.
Map every expected cash inflow — by contract stage and payment terms
Not revenue recognized — cash received. A $42K annual contract signed today does not appear as $42K in Week 1 of your model. It appears based on your actual payment terms: if you invoice Net 30, that $42K arrives in Week 5 at the earliest, and often Week 7 after finance approval cycles. Map each open contract, its signed date, your invoice terms, and your customer's typical payment cycle. For Forge, with enterprise manufacturing customers, assume 45-60 days from contract signature to cash receipt unless you have hard evidence of faster payment.
Build the 13-week rolling model
Sum outflows and inflows by week. The ending balance of Week N becomes the opening balance of Week N+1. Identify the weeks where your ending balance crosses below any threshold you care about: $200K (six months of gross burn at current rate), $100K (the danger zone), $0 (the existential cliff). The 13-week horizon is the industry standard — short enough to forecast with meaningful accuracy, long enough to have time to act if the trajectory is bad.
Stress-test the model with a realistic downside case
What happens if your largest pending contract delays 30 days? What if AWS costs spike 20% due to traffic growth? What if one engineer resigns and you need to backfill? The base case model is not the survival tool — the downside model is. Most founders build only the base case. The 13-week model is only useful as a risk tool when you've stress-tested it.
Update the 13-week model every Monday morning before any other work. It takes 20 minutes once built. Founders who do this stop being surprised by cash events — they can see a problem developing 8-10 weeks out and have time to act. Founders who update it monthly see problems 2-3 weeks out and are in crisis mode. The frequency is the discipline.
IN PRACTICEThe 13-week rolling cash forecast as a survival tool
The 13-week cash forecast is not a reporting document — it is a decision tool. It answers three specific operational questions every week:
| Question | What to look for in the model | Threshold for action |
|---|---|---|
| When do we hit a danger threshold? | The week where ending balance first drops below 3 months of gross burn | If within 13 weeks → act immediately; if 13-26 weeks → start conversations |
| Can we afford this hire? | Re-run the model with the hire cost added as a fixed weekly outflow; find the new danger week | If the hire moves the danger date inside your fundraising lead time → do not hire |
| Should we accelerate a receivable? | Model the cash position with and without offering a 2% early payment discount | If the cash position improvement prevents a danger scenario → the 2% is worth it |
One number you must track alongside the model: your fundraising lead time. For a seed-stage B2B startup, the realistic time from "we should raise" to "term sheet signed" to "wire received" is 4-6 months at minimum — and 6-9 months is more common. This means if your 13-week model shows danger at Week 20, you need to start the raise process today. The common failure is founders who wait until they see danger in the model before beginning the raise — at which point they are already too late to raise on good terms.
If runway < (fundraising lead time + 6 months buffer), begin raising. For most seed-stage B2B startups: if runway < 12 months, you should at minimum be in market conversations. If runway < 9 months, you are in a difficult negotiating position. If runway < 6 months, you are distressed. Investors can smell it.
CORE CONCEPTThe cash conversion cycle — the time-cost of doing business
The cash conversion cycle (CCC) measures the time between when you spend cash to create your product or service and when you collect cash from your customer. For a SaaS+hardware startup like Forge, this has a structure that most technical founders have never mapped explicitly.
What this means operationally: when Forge signs a new customer, the company needs to have on hand approximately 3 months of the gross margin cost of that deal plus operational overhead before any revenue from that deal arrives. Signing more customers does not improve cash flow in the short run — it can worsen it by pulling forward hardware costs, implementation labor, and overhead, while pushing cash collection 90 days out.
The two most powerful levers for shortening the CCC are: (1) move customers to annual prepaid contracts (which Forge has already done — collecting $42K upfront rather than monthly, which collapses the DSO to near zero), and (2) negotiate faster hardware delivery or build inventory float (reducing the inventory period). Every day shaved from the CCC is permanent working capital freed for deployment elsewhere.
SEE ITRunway Extender — find the 90-day solution without new capital
A few things worth noticing. Some levers — like switching to annual contracts and accelerating receivables — are both high-impact and zero cost to implement; they are purely negotiating and process decisions. Others, like delaying a hire, have real second-order effects: the work that hire was supposed to do still exists. The widget shows the cash impact in isolation; the strategic cost of each lever is a separate judgment. The point is not to blindly toggle levers until you hit 90 days — it is to understand which levers are available to you, which ones actually move the needle, and which combinations achieve the target without creating problems worse than a tight cash position.
FORGEForge's current cash position and the decisions it forces
Forge has just closed two pilot-to-annual conversions at $42K ACV each ($84K total, collected upfront). The business model is locked: $30K annual SaaS platform fee plus $12K one-time hardware fee per site. The first-contract gross margin is 61%, with a path to 75%+ at 20 customers. Here is where Forge stands entering Stage 4:
Cash position: ~$390K after two annual contracts
The $84K in upfront contract payments partially offset a recent hiring event (two engineers, combined $24K/month incremental burn). The two hardware deployments cost approximately $16K in COGS (hardware at ~$4K per unit, plus installation labor), which has already been spent. Net cash from the two contracts after COGS: approximately $68K deposited. Starting a Stage 4 GTM push from a $390K cash position with a $52K/month net burn gives roughly 7.5 months of runway at the current trajectory.
The raise-or-cut decision is now live
7.5 months of runway against a 6-9 month fundraising lead time for a seed-plus or Series A means Forge is already inside the window where fundraising conversations should be starting in parallel with GTM execution. This is not a crisis — but it is not comfortable either. The operational levers (annual contracts, accelerating receivables, delaying non-critical hires) can extend runway by 2-3 months, which buys negotiating room. The failure mode is treating the $390K balance as evidence that the problem is not urgent.
Cash conversion cycle: the hardware problem
Forge's current CCC of roughly 90 days from hardware order to cash receipt means each new customer signed in Stage 4 represents a net cash outflow for 90 days before any inflow. If Forge signs five customers in Q1 of Stage 4, the hardware cost alone — at roughly $4K per unit plus installation — represents a $20K cash outflow per deal before recognizing any revenue. The structural fix is negotiating vendor terms (extend hardware payment to 60 days), building a small hardware inventory buffer, and ensuring every contract is annual prepaid to collapse the DSO component. Both annual contracts already use annual prepay — that discipline must hold.
Forge's financial model — 61% gross margin, $42K ACV, annual prepay — is well-structured for cash efficiency once at scale. The vulnerability is the transition period: enough new customers to grow burn (hiring CSMs, AEs, solution engineers) but not yet enough contracted ARR to cover that burn from recurring revenue. The 13-week model must be updated with every new hire decision, every new contract, and every vendor change. In Stage 4, cash discipline is not separate from growth execution — it is part of it.
WEAKNESSWhere this bites
This is the most common and most dangerous mistake. The bank balance is a lagging, incomplete indicator — it reflects what has already happened (large contract collected, investor wire landed) without revealing the trajectory (new engineers on payroll, AWS scaling costs kicking in, next quarter's revenue pipeline not yet contracted). A founder who checks the bank account each week and says "we're fine" while net burn has been climbing for three months is operating with a 90-day lag on their most existential number. The discipline: never report the bank balance in isolation. Always report net burn alongside it.
The value of the 13-week model is entirely in its freshness. A model built in January and consulted in April is not a cash management tool — it is a historical document. Every hire, every contract signature, every vendor invoice, every payment delay changes the picture. Founders who build the model once and treat it as "done" get the same false sense of security as founders who never build it. The model only works if it is updated weekly, stress-tested against realistic downside scenarios, and tied directly to the raise-or-cut decision rule.
Revenue recognition under accrual accounting — the standard used in any real financial model — recognizes revenue when it is earned, not when cash is received. A $42K annual contract is recognized as approximately $3,500/month over 12 months. But the cash was received upfront on Day 1. If you are managing cash flow from your income statement rather than your cash flow statement, you will systematically underestimate how much cash you have immediately after signing large annual contracts and overestimate it later. This is why the 13-week model uses actual cash dates — not accrual dates — for every single line item.
KEY INSIGHTHow this connects
- 3.6 · Gross Margin — The Number That Controls Your Destiny — gross margin determines the ceiling on what levers are available to you in a cash crisis. A 61% gross margin business has very different options than a 25% gross margin business when net burn needs to come down. Gross margin also controls how many customers Forge must close to achieve cash-flow break-even — the structural relationship built in 3.6 is the foundation of the runway model here.
- 3.7 · Services Revenue — The Trap and the Bridge — the services vs. SaaS tension is not just a gross margin question — it is a cash timing question. Services revenue (professional services, implementation) often has shorter payment cycles and can be a deliberate lever to accelerate near-term cash while sacrificing long-term margin. Understanding that tradeoff requires both the gross margin lens from 3.6 and the CCC analysis from this lesson.
- 3.8 · Financial Projections — Building a Model That Is Wrong in the Right Ways — the financial model built in 3.8 is the source data for the 13-week cash forecast. Revenue projections, hiring plans, COGS build-up — all of it flows into the week-level timing model. The projection model and the cash model are the same machine viewed at two different time resolutions. The projection answers "what does the business look like in 18 months?" The 13-week model answers "can we make it to Week 13?"
- Next: 4.1 · Positioning — The One Thing You Want to Own — Stage 4 begins. The cash discipline built in Stage 3 is the operating constraint within which every GTM decision in Stage 4 must fit. Every sales hire, every marketing experiment, every conference sponsorship is a cash event. Understanding burn before starting to spend on growth is the prerequisite for surviving Stage 4.
Cash management is the operational discipline that makes every other decision in the course reversible. A company with 18 months of runway can iterate on positioning, correct a pricing mistake, experiment with a new sales motion. A company with 3 months of runway cannot — every decision must be right because there is no room to be wrong twice. The goal of Stage 3's financial architecture work is not just accuracy — it is giving Forge enough operational runway to execute Stage 4 from a position of choice rather than desperation.
GLOSSARYKey terms
- Gross burn
- Total cash spent per month across all operating expenses, regardless of revenue. Measures the cost of keeping the company running. Useful for understanding cost structure but not for computing runway.
- Net burn
- Gross burn minus cash actually received from customers in the same period. The rate at which cash reserves are being depleted. This is the number that determines runway — not gross burn, not revenue recognized.
- Runway
- Current cash balance divided by monthly net burn. The number of months until the company reaches zero cash at its current trajectory. Must be calculated from net burn, not gross burn, and updated at least weekly.
- 13-week cash forecast
- A rolling weekly model of all expected cash inflows and outflows over the next 13 weeks (one quarter). Built from actual payment dates, not accrual dates. Updated weekly. The primary tool for identifying cash crises before they become emergencies.
- Cash conversion cycle (CCC)
- The elapsed time between spending cash (on hardware, labor, overhead) to serve a customer and receiving cash payment from that customer. For Forge: approximately 90 days from hardware order to contract signed to cash received. Shortening the CCC is a permanent source of working capital.
- Days sales outstanding (DSO)
- The average number of days between sending an invoice and receiving payment. A 45-day DSO means customers take 45 days on average to pay after invoicing. Annual prepaid contracts collapse DSO to zero — cash is received before the invoice is even sent.
- Fundraising lead time
- The realistic elapsed time from beginning serious fundraising conversations to receiving cash in the bank. For seed-stage B2B startups, typically 4-9 months. Determines how far ahead of a cash danger point the fundraising process must begin.
- Accrual vs. cash basis
- Accrual accounting recognizes revenue when earned and expenses when incurred — regardless of when cash moves. Cash basis records only actual cash transactions. The income statement uses accrual; the 13-week cash model uses cash. Confusing the two is a fatal error in cash management.
ACTIVE RECALLCheck your understanding
Answer in your own words first, then reveal.
1Forge has $390K in the bank. Its monthly gross burn is $68K and it received $52K in customer cash last month. What is its net burn, and what is its actual runway?›
Net burn = Gross burn − Cash received from customers = $68K − $52K = $16K/month. Note: if the $52K was a one-time collection (from an annual contract signed last month that won't renew for 12 months), then in the following months cash received may drop to $0, making net burn equal to gross burn ($68K). You cannot compute runway from a single month's net burn — you must look at the forward trajectory. If next month's cash receipts drop to $0 (because the only contracts are already collected), then runway is $390K / $68K ≈ 5.7 months, not $390K / $16K ≈ 24 months. This is exactly why the 13-week forward model is essential — a single month's net burn figure is highly misleading when cash receipts are lumpy.
2What is the difference between the 13-week cash forecast and a financial model, and why do you need both?›
The financial model (built in Lesson 3.8) operates on an accrual basis, at monthly resolution, over an 18-24 month horizon. It answers: "What does the business look like at scale? When do we break even? What are the unit economics?" It is built for strategic and investor conversations — it shows the shape of the business. The 13-week cash forecast operates on a cash basis, at weekly resolution, over a 13-week horizon. It answers: "Can we make payroll on Friday? When does our cash balance cross the danger threshold? Do we have time to act?" You need both because the financial model is too coarse (monthly, accrual) to catch the specific week when a large invoice payment creates a dangerous trough — and the 13-week model is too short-sighted to answer investor questions about path to break-even. They are the same underlying business viewed at two different time resolutions.
3Forge has 7.5 months of runway. A senior AE candidate just accepted an offer at $120K/year ($10K/month). Should Forge make this hire?›
The right framework is not "can we afford it right now" but "does this hire change our raise-or-cut decision?" Adding $10K/month to burn reduces runway from 7.5 months to approximately 6.4 months at current burn. If Forge's fundraising lead time is 6-9 months, a 6.4-month runway means Forge is now inside the danger window even before beginning to fundraise. The decision depends on: (1) Can the AE generate contracted revenue fast enough to offset the burn increase? If the AE can close one $42K annual contract in month 2, that $42K cash receipt extends runway by roughly 3 weeks — not enough to offset 12 months of $10K/month cost. (2) Are investor conversations already underway? If yes, this hire might be fine. If no, and Forge has no other revenue in the pipeline, making this hire before starting fundraising conversations is a mistake. The 13-week model should be rebuilt with the hire added before the offer is accepted — not after.
4Why does a rising bank balance sometimes indicate accelerating burn rather than improving financial health?›
Because bank balance changes are the net of all cash inflows and outflows — they do not separate the signal of "revenue is growing" from the noise of "we collected a large prepayment" or "an investor wire landed." When a startup signs a large annual prepaid contract, the bank balance spikes by the full contract value immediately — even if the company simultaneously hired engineers to support the new customer, increasing monthly gross burn. In the months following the spike, the bank balance will decline at the new, higher burn rate while no additional cash comes in from that contract (already collected). The rising bank balance masked the burn rate increase. Founders who look at the bank balance spike and interpret it as evidence of financial health will be surprised when the balance drops quickly in subsequent months. The only indicator that actually tells you whether the business is becoming more or less sustainable is net burn trend over multiple months — not any single bank balance snapshot.