Working Capital Management Is the Cash Runway Problem Most Founders Never See Coming

The Burn Rate Number That Looks Fine (Until It Isn't)

Monthly net burn is the number every investor asks for and every founder tracks. It's also the least useful signal for knowing whether you're actually liquid.

Burn rate is backward-looking. It tells you what you spent last month. It doesn't tell you when your bank account will hit a level where you can't make payroll. That distinction sounds pedantic until you're staring at a cash position that should show 14 months of runway and realizing you need a bridge in six weeks.

Here's the scenario that actually happens. A founder at $2.5M ARR closes a strong Q2. Two new enterprise accounts, $180K in new ARR. Burn rate looks stable at $120K/month. Runway math: $1.4M in the bank divided by $120K burn equals 11.7 months. Comfortable.

What the burn rate model doesn't show: both enterprise accounts signed net-60 payment terms. One existing customer, $40K ACV, is 45 days past due. The company pre-paid a $60K annual AWS commitment in July. Two contractors got paid early because of a project deadline. The next payroll hits in nine days.

None of those facts change the ARR number. None of them change the burn rate figure. All of them change whether the company can cover payroll without pulling from a credit line.

That's a working capital problem. Most founders never model it separately from runway.

What Working Capital Actually Means for a SaaS Business

Working capital is current assets minus current liabilities. Simple formula. Genuinely confusing in practice for SaaS, because several of the largest numbers on your balance sheet look like one thing and mean another.

Deferred revenue sits on the liability side. If a customer pays you $24,000 upfront for a 12-month annual contract in September, you collected the cash. But you've only "earned" $2,000 of it as of October. The remaining $22,000 is a liability until you deliver the service. From a cash perspective, you're ahead. From a working capital perspective, that liability offsets your asset base.

This creates a counterintuitive result: a SaaS company can have strong ARR, solid cash collected from annual prepays, and still show tight working capital because the deferred revenue liability is large and growing.

Accounts receivable days (DSO) is the number most founders eyeball instead of track. Days sales outstanding is the average number of days between invoice and payment. If you're invoicing net-30 and customers are actually paying in 52 days, you have a $40K float problem at $1M ARR that grows proportionally as you scale. At $5M ARR with the same DSO drift, you're floating $200K you thought you had.

The payables-receivables timing gap rarely gets mapped. You owe vendors, contractors, and SaaS tools on a fixed cadence. Customers pay you on a different cadence. The gap between those two schedules is your actual liquidity exposure. Most founders know both numbers in isolation and have never put them on the same timeline.

The relationship between contract length and cash flow timing compounds all of this. Annual contracts improve deferred revenue but concentrate your collection risk. Monthly contracts smooth cash but give you no forward cushion.

The Three Places Your Cash Is Hiding Right Now

Pull up your bank statement and your P&L side by side. The gap between them is where working capital lives.

Unbilled contracts. Enterprise deals often have a signature date, a go-live date, and a billing date that are three different events. If you signed a $120K contract in August, go-live is October, and billing is net-30 from go-live, you won't see that cash until mid-November. Meanwhile, your bookings report shows the $120K. Your burn model doesn't.

Prepaid vendor commitments. AWS, Google Cloud, Stripe's fee structure if you're on a negotiated rate, annual tool contracts for your stack. If you're a 15-person company, you're probably carrying $80K-$150K in prepaid vendor spend that hits the bank in uneven lumps. Most founders amortize these mentally without ever putting them in a cash forecast.

Customer payment terms you didn't negotiate. Net-60 is standard for enterprise procurement. But "standard" isn't automatic. Most procurement teams will accept net-30 if you ask in the contract negotiation, before signature. After signature, you've accepted their terms and the conversation is harder. Negotiating better payment terms with customers is entirely about timing the ask correctly.

If you've never audited these three categories against your actual bank balance, that audit is worth doing this week. Not next quarter.

How to Build a Liquidity Forecast That's Different From a Runway Model

A runway model tells you how many months until zero. A liquidity forecast tells you which specific week you'll be tight, and by how much.

The format that works: 13-week rolling cash flow. Weekly columns, not monthly. Rows for every material cash-in and cash-out, separated by category. Customer payments (broken out by account, not aggregated). Payroll. Vendor payments. One-time items.

The discipline that matters: separate cash-in from accrued revenue. When you close a deal, note it in two places. The ARR model gets the contract value. The cash forecast gets only the expected payment date and the actual dollar amount you'll collect. These are not the same row.

Run a stress scenario every time you update the model. What happens to your week-8 cash position if your two largest accounts pay on day 60 instead of day 30? What if the enterprise deal you expected to close this month slips by three weeks? A forecast that only models "expected" is a spreadsheet that makes you feel good. A forecast that includes a downside case is a tool you can actually use.

If you're reporting to a board, the 13-week cash flow model is exactly the kind of input that separates founders who understand their business from those who are reading off a dashboard they built to look good.

The Levers You Can Pull Without Touching Payroll

Once you see the working capital gap, the question is what moves the number without disrupting operations.

Annual prepay with a discount. The math is straightforward: offer a customer 1.5 months free (roughly 12.5% discount) in exchange for paying 12 months upfront. They get a real financial benefit. You get cash in the bank in week one instead of week twelve. At $50K ACV, that's $50K now versus $4,200/month for 12 months. For a company with $1.4M in the bank and $120K monthly burn, accelerating two or three enterprise contracts this way adds 3-5 weeks of runway with no additional spend.

The discount feels expensive. Compared to a bridge round at a flat cap or a credit line at 8-10% interest, it's cheap.

Payment terms as a negotiating variable, not an afterthought. Before you next sign an enterprise contract, read the payment terms section before you send for signature. Net-30 is achievable in most B2B SaaS deals if you write it into your standard order form. Net-15 for deals under $25K ACV is often accepted without question. The window to set terms is before signature. After that, you're asking for a favor.

Stretching payables without damaging vendor relationships. Most SaaS tool vendors bill monthly. Most will work with you on payment timing if you're not chronically late. Shifting 8-10 vendor payments from the 1st of the month to the 15th doesn't change your burn rate. It changes which week your cash hits bottom. At tight moments, that two-week difference is real.

Note: this is not "don't pay your vendors." It's "pay your vendors on the latest date they've agreed to." Read every invoice for the actual due date. Most founders pay invoices when they arrive instead of when they're due. That's free working capital sitting on the table.

When to Stop Managing This Manually

A spreadsheet works until it doesn't. The signal that you've outgrown manual cash management isn't ARR. It's number of open variables.

If you have more than 8 active enterprise customers with different payment terms, a vendor stack of 15+ tools, payroll that runs bi-weekly, and a sales pipeline that moves fast enough to shift your 13-week forecast materially week-over-week, you're spending 4-6 hours a week maintaining a model that's probably 10 days stale by the time you use it.

A fractional CFO (typically $3,000-$7,000/month for a 10-hour engagement) brings this structure immediately. They've built the model before. They know which assumptions to stress-test. And they free you from the 15 hours a week founders lose to financial and operational tasks that don't compound your growth.

A full-time CFO hire at sub-$10M ARR is usually premature unless you're raising a Series A within 12 months or have unusual revenue complexity. The cost sits at $180K-$260K fully loaded before you've validated whether you actually need daily financial oversight.

The actual decision: when the cost of a bad cash call exceeds the cost of the finance resource that would have caught it. For most founders, that crossover happens around $2M ARR, not $5M.

---

Working capital management isn't glamorous financial planning. It's the specific math between "we have runway" and "we can make payroll next week." Most founders conflate the two until the gap becomes a crisis. The founders who don't conflate them model the timing gap explicitly, audit their receivables quarterly, and treat payment terms as a negotiating variable rather than boilerplate.

If you're the one running marketing content alongside everything else, the pattern is the same. Most founders know they should be publishing more consistently, but the operational overhead of drafting, formatting, and distributing kills the cadence before it starts. The waitlist is live at morbiz.ai/marketing-engine for founders who want the content operation to run without taking over their calendar.

Cash discipline and content discipline have more in common than they look. Both reward consistency. Both get expensive when you try to catch up instead of maintaining the habit.