Your SaaS has $1.4M in the bank, $180K in monthly recurring revenue, and about nine months of runway. Then a client who pays $22K a year on a single invoice decides to pay in 94 days instead of 30. Nothing about your business changed. Your runway just got three weeks shorter.
That is the trap in tech: your bank balance and your business health can drift apart for months before anyone notices. Managing cash flow well for a tech startup isn't about cutting costs when things get scary. It's about building a system that tells you the truth before the board does.
Key Takeaways
- Track cash collected, not just MRR — revenue recognition and cash landing in the bank are two different clocks.
- Build a 13-week rolling forecast updated every week; it catches problems a monthly budget hides.
- Measure DSO (days sales outstanding) and burn multiple as your two health dials.
- Annual contracts paid monthly are your best cash-flow friend; annual prepay is even better — price it deliberately.
- Keep at least 6 months of runway as a buffer, and never let invoicing lag behind delivery.
Why cash flow breaks tech startups more easily than other businesses
A restaurant collects money the same day it serves food. A consulting shop invoices after delivery. A SaaS company signs a 12-month contract in March, delivers continuously, and often doesn't see the cash until June — if the client pays on time at all.
This delay is structural. Tech startups combine three things that make cash flow fragile:
- Recurring revenue that arrives on a schedule you don't control — monthly billing cycles, annual renewals concentrated in one quarter, credit card failures on failing cards.
- High fixed costs with low variable costs — engineers, infrastructure, and cloud bills don't shrink when a customer churns. Your cost base stays flat while your revenue wobbles.
- Growth that consumes cash before it returns it — every new customer usually costs more to acquire than they pay in the first months.
When I was running a small B2B SaaS tool, I learned about this the hard way. We signed what looked like a great deal — a $60K annual contract with a large client. We celebrated, hired two people against it, and then waited. The client's procurement team took 71 days to process the first invoice. We had budgeted for 30. For six weeks we were technically profitable and practically broke. I'll admit, I spent a few nights refreshing the bank app at 11pm like it would change something.
The revenue-versus-cash clock
Your accountant recognizes revenue over the life of the contract. Your bank account doesn't care. What matters is when the money moves. A $120K annual contract paid monthly gives you $10K a month — but if the client pays 45 days late, every single month, you've effectively loaned them $15K in perpetuity. Multiply that across a dozen clients and that's real runway gone.
How do you forecast cash flow when revenue is recurring?
Monthly budgets lie to SaaS founders. They smooth over the week-to-week reality where payroll hits on the 25th, a big invoice clears on the 3rd, and a cloud bill surprise lands on the 12th. The answer is a 13-week rolling cash forecast.
The 13-week rolling forecast, explained
Thirteen weeks is roughly one quarter. It's short enough to be accurate and long enough to actually react. Each week you populate a simple table:
- Opening cash — the actual bank balance on Monday morning.
- Expected inflows — by client, with a realistic payment date, not the invoice date.
- Expected outflows — payroll, cloud, tools, contractors, rent, and tax dates flagged separately.
- Closing cash — opening plus inflows minus outflows.
The critical part: update it every week with actuals. After a month you'll spot your real DSO — the number of days your clients actually take to pay, not the net-30 you wrote on the invoice. In my case, our "net 30" clients were averaging 52 days. That single discovery changed how I priced and how I chased late payments.
Which metrics should you track alongside your forecast?
Two metrics tell you whether your cash engine is healthy:
- DSO (days sales outstanding): how many days, on average, it takes to collect an invoice. If your DSO is creeping up month over month, cash is leaking even when revenue looks fine.
- Burn multiple: net cash burned divided by net new recurring revenue added. A burn multiple below 1 means you're building efficiently; above 2 and you're spending heavily to grow — acceptable for short periods, dangerous as a habit.
Add a simple cash runway number: current cash divided by average monthly net burn. If that number is under six months, you are in the danger zone and should be actively raising or cutting.
How to speed up collections without souring client relationships
Most startups chase late payments too late. The fix starts before the invoice is even sent. Here's what actually moved the needle for me:
- Invoice immediately on delivery or on signup — not at the end of the month. Every day between service and invoice is a day of free credit you gave away.
- Put payment terms in the contract, not the footer. State net-30, the late fee, and — most importantly — that the client is responsible for their own procurement timelines.
- Ask for a PO or procurement contact at signature. Half my collection delays came from clients whose internal systems didn't have a vendor number for us until week three.
- Offer a small prepay discount. A 3% discount for annual prepay converts a $10K monthly cash flow into $114K up front. Over a year that's a serious buffer.
- Automate dunning for failed card payments. A retry schedule and a friendly reminder email recovered roughly 8% of our failed charges within a week.
The invoicing mistake I made for two years
Our finance person used to batch invoices at month end. It felt tidy. What it actually did was delay every single dollar by up to 30 days for no reason. When we switched to invoicing the day a contract started, our average collection date moved forward by 18 days in one quarter. No client complained. No contract changed. The money just started arriving sooner.
Where to cut burn without gutting your product
Firing a few engineers is the lazy answer. The better question is: which of your outflows are actually earning their keep? When I audited our own spending, three categories jumped out:
| Category | What I found | What I did |
|---|---|---|
| SaaS tool sprawl | 41 paid subscriptions, 11 unused for 60+ days | Cut to 24 tools, saved ~$1,900/month |
| Cloud infrastructure | Oversized instances, no reserved pricing | Right-sized and committed; ~22% reduction |
| Contractors | Two roles duplicating responsibilities | Consolidated into one |
Total: roughly $6,800 a month recovered without touching a single full-time employee. That's about three months of additional runway for the price of a spreadsheet audit.
Should you push annual prepay over monthly billing?
If your sales team can do it, yes — and aggressively. Annual prepay gives you cash today for a service you'll deliver over 12 months. That cash buys you runway, reduces DSO to zero, and protects you from mid-contract churn's cash impact. The trade-off is a discount, typically 5–15% depending on your market. In my experience that discount is cheap insurance against a cash crunch.
Three cash flow mistakes that keep showing up in tech startups
Hiring against a signed contract before the cash lands. Revenue that hasn't been collected is a promise, not a resource. Hire only when cash is in the bank or the track record of the client is unimpeachable.
Running one big annual budget. Annual budgets fail because they can't adapt to reality. Review monthly at minimum, and reconcile your 13-week forecast weekly. A budget is a direction, not a contract.
Ignoring the renewal cliff. If 40% of your revenue renews in the same quarter — say, January — you have a predictable cash hazard. Spread renewals deliberately, or hold extra reserves ahead of that quarter.
None of these are exotic. They're the boring mechanics. And boring mechanics are exactly what separate a startup that survives a slow quarter from one that doesn't.
The uncomfortable truth about cash discipline
Most founders I know — myself included — treat cash flow as a problem to solve after a crisis. The real discipline is treating it as a weekly habit, like checking a dashboard. The moment you stop looking, the numbers start lying to you: a client goes quiet, an invoice ages, a subscription renews that you forgot about.
So here's the question worth sitting with: if your main enterprise customer delayed payment by 60 days starting tomorrow — do you actually know what that does to your runway? If the answer is vague, that's the work.
