Your bank balance says $1.4M. Your dashboard says everything is fine. Then your biggest customer pays a $60K invoice 71 days late, your AWS bill doubles because a new enterprise client is hammering your staging environment, and you realize you have to make payroll in nine days. Nothing about your business actually broke. The cash just moved in a direction you weren't watching.
I've been on both sides of that phone call—the one where a founder does the math out loud and goes quiet halfway through. When I started working with early-stage tech companies about four years ago, I assumed the hard part was forecasting. It isn't. The hard part is that tech companies have a cash rhythm that most financial advice was never written for: revenue arrives in lumpy annual contracts, costs scale in small increments that never feel urgent, and the gap between "we signed the deal" and "the money is in the account" can stretch past a quarter.
What follows is what I've actually seen work—the tips I'd give a founder over coffee, not in a board deck. Some of them saved companies I worked with. A couple are things I got wrong first and learned the expensive way.
Key Takeaways
- Forecast cash weekly, not monthly—tech companies die from timing gaps, not from bad annual plans.
- Annual prepay is the cheapest financing most SaaS companies will ever get; treat it as a product decision, not just a billing one.
- Your burn rate has two halves: the one you control (hiring, tools, cloud) and the one the market controls (churn, payment terms). Optimize the first before you panic about the second.
- Get paid faster by shortening the revenue cycle—invoice on delivery, not at month-end, and chase deposits at signing.
- Keep a 90-day cash buffer beyond your runway calculation; runway is a planning number, not a survival number.
Why weekly forecasting beats monthly budgeting
Most founders I meet build a 12-month cash model in a spreadsheet, update it once a quarter, and feel responsible. Then a client pays late and the model is fiction. The problem isn't the model—it's the resolution. Monthly forecasts hide the exact weeks where you go negative.
Startup cash flow forecasting works best when you shrink the time window. I had a client last spring—a 14-person dev-tools company—who thought they had eight months of runway. When we rebuilt the forecast week by week, three separate weeks in the next two months showed a negative balance, because two big invoices landed in the same week as a quarterly tax payment and a contractor payout. Same annual numbers. Completely different story.
What a weekly forecast actually looks like
You don't need fancy software. A single sheet with columns for each week and rows for every cash movement works fine for a company under 50 people. The trick is discipline: update it every Monday, and mark every line as confirmed, likely, or hopeful. That last category is where founders lie to themselves.
- Cash in: signed contracts with payment dates, not "expected" revenue
- Cash out: payroll (the one number you cannot miss), cloud and infrastructure, contractor invoices, taxes, rent
- The buffer line: a fixed reserve you never touch, even when the forecast looks great
Here's the insider trick that saved me once: put your worst-case week at the top of the sheet. Not the average. The week where two invoices slip and payroll hits. If you can survive that week on paper, you can sleep. If you can't, you have a specific problem to solve instead of a vague anxiety.
How often should a growing tech company update its forecast?
Weekly for the next 13 weeks, monthly for the rest of the year. The 13-week window matches a quarter—long enough to see trouble coming, short enough that the numbers stay honest. Anything beyond a year is a scenario exercise, not a forecast. For the bigger picture, it's worth pairing this with a longer view like the one in long term financial planning, but keep the weekly sheet separate and ruthless.
Takeaway: a monthly model tells you whether the year works. A weekly forecast tells you whether next Tuesday works. You need both, but the weekly one is what keeps the lights on.
Burn rate optimization without gutting the company
Every founder hears "cut burn" and immediately thinks layoffs. That's the sledgehammer. The real work is quieter and, honestly, less dramatic—which is why people skip it.
When I audited a Series A fintech's spend last year, we found $11,400 a month in cloud costs that nobody owned. Not waste in the obvious sense—just services spun up for a demo, a staging environment that had been running for eight months, three overlapping observability tools because two teams picked different vendors. We cut it to $6,800 without touching a single headcount. That's $55K a year, which at their burn rate was roughly three extra weeks of runway.
The two halves of burn rate
Split your burn into what you control and what you don't. The controlled half—headcount, tools, infrastructure, office—responds to decisions you make this week. The uncontrolled half—churn, late payments, currency swings—responds to the market. Founders panic about the second half while ignoring the first, which is backwards. You can't negotiate with churn. You can absolutely cancel a $400/month tool nobody logs into.
| Lever | Typical impact | How fast it works |
|---|---|---|
| Cloud/infrastructure audit | 15–30% reduction | 2–4 weeks |
| Tool consolidation (SaaS sprawl) | $200–$800/month per team | Immediate |
| Hiring freeze (not cuts) | Largest single lever | One pay cycle |
| Contractor renegotiation | 5–15% on hourly rates | Next contract |
| Payment terms on vendor invoices | Shifts timing, not total | Immediate |
Notice the last row. Renegotiating when you pay your vendors is the most underrated move in the playbook. Push net-30 to net-45 with your three biggest suppliers and you've effectively borrowed a month of costs at zero interest. Do it before you need to, while you still have leverage.
Takeaway: burn rate optimization is mostly a housekeeping discipline. Do the boring audit quarterly and you'll rarely need the dramatic one.
Fixing your revenue cycle before you fix your fundraising
Founders reach for a bridge round when cash gets tight. Usually the faster fix is sitting in the receivables. Revenue cycle management for tech firms is genuinely different from other industries—your "product" is often delivered continuously, but your billing is often stuck on a monthly or annual cycle that doesn't match when the value actually flows.
One company I worked with had a simple rule: invoices went out on the first of the month, for the previous month's usage. Sounds reasonable. But their enterprise customers' accounts-payable departments ran on a 30-day approval cycle that started when the invoice arrived—so every invoice effectively took 55 to 70 days to clear. We changed the billing to invoice on delivery with a signed PO attached. Average collection time dropped from 63 days to 41. On $2.1M in annual revenue, that's roughly $125K of cash freed up just by changing when the invoice left the building.
The deposit conversation nobody wants to have
Ask for a deposit at contract signing. Not 100% upfront—that scares people off—but 30 to 50% on annual deals, or the first month on monthly deals. I'll admit I resisted this for years because I thought it made us look desperate. It doesn't. It makes you look like a business that has done this before. The companies that push back hardest on deposits are usually the ones who would have paid late anyway.
Should you offer annual prepay discounts?
Yes, and more aggressively than feels comfortable. A 15% discount on annual prepay sounds expensive until you compare it to the cost of a bridge round or a credit line. You're trading margin for cash you can deploy now—and for SaaS companies, that trade is almost always worth it. It's one of the cleanest forms of working capital for tech firms because it doesn't add debt.
Takeaway: before you call an investor, call your billing system. There's usually a month of cash hiding in your invoicing process.
Working capital moves that actually help tech firms
Working capital for tech firms gets discussed as if it's the same as for a manufacturer. It isn't. You don't have inventory sitting in a warehouse. Your working capital is mostly receivables timing, deferred revenue, and the gap between when you pay people and when you get paid.
Three moves I've seen work repeatedly:
- Negotiate payment terms on both sides. Get paid in 30, pay in 45. That 15-day gap is free working capital.
- Use a line of credit as a buffer, not a lifeline. Set one up when you don't need it. Banks lend to companies that don't need the money—that's not cynicism, it's just how underwriting works.
- Stagger your big payments. Annual insurance, software renewals, and tax payments all cluster in the same months if you let them. Spread them across the year deliberately.
I made the mistake once of signing a three-year office lease right before a hiring push. The lease payment was fine on paper, but it locked up cash at the exact moment I needed flexibility. The lesson: every fixed commitment is a bet that your forecast is right. Keep the fixed commitments small and the variable ones flexible.
If you're also thinking about how to grow the team without wrecking the cash position, the hiring approach in creating a hiring plan is worth a read—it pairs naturally with this section.
Takeaway: working capital is a timing game. Win the timing and you rarely need to win the fundraising.
Building a cash-aware culture (without micromanaging)
The final piece is the one most founders skip because it's not a spreadsheet. It's culture. If your team treats the company bank account as an infinite resource, no forecast will save you. If they treat it as a shared constraint, you'll catch problems weeks earlier.
What worked for me: a simple monthly "cash meeting"—30 minutes, whole company, one slide. Where we are, where we're going, what we're watching. No drama, no fear. Just visibility. When people understand that a $2K tool subscription is real money, they start asking better questions before they spend it.
And here's the part that surprised me: the more transparent we were about cash, the more people wanted to help. Engineers started flagging cloud waste. Sales started chasing deposits. The finance function stopped being one person's problem and became everyone's habit.
Takeaway: cash awareness is a leadership behavior, not a finance department. Model it and it spreads.
The cash discipline that compounds
None of this is glamorous. A weekly forecast, a quarterly burn audit, a billing process that doesn't leave money on the table, and a team that treats cash like it matters. That's it. No secret formula, no clever financing trick that replaces the basics.
The companies that survive their growth phase aren't the ones that raised the most or grew the fastest. They're the ones that never got surprised by a Tuesday. They knew, weeks in advance, that payroll was going to be tight—and they had already fixed it before anyone noticed.
So here's your next action: open your bank statement and your last three invoices. For each invoice, note the date it was sent and the date it was paid. The gap between those two numbers is your real revenue cycle—and it's the fastest place to find cash you didn't know you had. Do that today, before you touch a single forecast model.
The best time to build cash discipline was before you needed it. The second-best time is this week.
Frequently Asked Questions
How much runway should a growing tech company actually keep?
Most founders target 12 to 18 months. I'd argue for a 90-day cash buffer on top of your runway calculation—not because you'll need it, but because runway is a planning number and a buffer is a survival number. The buffer is what lets you say no to bad terms without panicking.
Is it better to raise a bridge round or cut burn when cash gets tight?
Cut burn first, almost always. A bridge round dilutes you and takes weeks to close; a burn audit can free up cash in days. I've seen founders raise at a down round when a cloud audit and a billing change would have bought them three extra months. Exhaust the cheap options before the expensive ones.
How do I forecast cash when my revenue is lumpy and unpredictable?
Forecast the timing of cash, not the amount. You may not know when your next enterprise deal closes, but you know how long it takes to collect once it does. Build the forecast around confirmed contracts and payment terms, and mark everything else as "hopeful"—then plan your spending as if the hopeful category is zero.
What's the biggest cash flow mistake tech founders make?
Confusing revenue with cash. A signed contract is not money in the bank. The second-biggest mistake is letting billing run on autopilot—invoices sent at month-end, payment terms never renegotiated, deposits never requested. Both are fixable in a week.
Do I need a CFO to manage cash flow properly?
No, not at seed or Series A. You need a disciplined weekly process and someone who owns it. A fractional CFO or a good bookkeeper can help you set it up, but the discipline has to live inside the company. If you're mapping out the wider picture, the strategies in financial planning strategies for founders are a solid next step.
