A SaaS company can show growing MRR and still run out of money. That is why you forecast SaaS cash flow separately from revenue. Revenue tells you what the business has earned under accounting rules. Cash tells you whether payroll clears, cloud bills get paid and you have enough time to prove the next milestone.
For an early-stage founder, this is not a finance exercise for later. It is the operating read behind nearly every serious decision: whether to hire, when to start a raise, whether annual pricing helps and how much room a missed sales target actually costs you.
Forecast SaaS Cash Flow From Bank Timing, Not Hope
Start with the bank balance you have today. Then map every expected cash movement by the date it will happen, not the month you wish it happened.
A customer signing an annual $12,000 contract in May does not always mean $12,000 lands in May. They may pay on net 30 terms. Procurement may push the start date. An invoice may sit with an accounts payable team for another two weeks. The contract is good news, but it is not cash until the money reaches your account.
The same principle applies to spending. Your payroll is predictable. Your annual software renewals may not be. A contractor might bill after work is complete, while a new tool charges at the start of the month. Sales commissions, legal fees, taxes and insurance often create the ugly surprises because they are easy to omit from a simple monthly model.
Build the forecast in two views. Use a 13-week cash forecast for immediate control and an 18-month monthly forecast for runway and fundraising decisions. The weekly view answers, “Can we pay for what is already committed?” The monthly view answers, “What must become true before we run out of room?”
Your model should begin with opening cash, then add expected collections and subtract cash expenses. The closing balance becomes the next period’s opening balance. That sounds obvious, but discipline lives in the detail: each collection and payment needs a realistic date, an owner and a confidence level.
Separate Bookings, Revenue and Collections
Early SaaS models often break because one number is asked to do three jobs. Keep these measures separate.
Bookings are the contract value you have sold. Revenue is the portion recognized as service is delivered. Collections are the dollars that have actually arrived. If you sell annual contracts paid upfront, bookings and collections may jump in one month while revenue spreads across twelve. If you bill monthly, all three may move closer together.
That distinction changes the decisions you make. A founder who sees a strong booked ARR number may feel ready to add two engineers. But if customers pay monthly, implementation takes six weeks and one large invoice is delayed, the bank balance may tell a different story.
For each customer, track the contract start date, billing frequency, invoice date, payment terms, expected collection date, renewal date and cancellation risk. You do not need a giant finance department to do this. You need one current customer schedule that feeds the forecast instead of living in somebody’s inbox.
Annual prepayment can improve cash quickly, but it has a trade-off. A discount for annual payment may make sense when the customer is healthy and the cash extends runway toward a meaningful milestone. It may be less wise when the discount is large, retention is weak, or the team begins treating prepaid cash as proof that monthly demand is stable. Cash buys time. It does not erase churn.
Put Churn and Sales Delays Where They Belong
The dangerous forecast is not the optimistic one. It is the optimistic one pretending to be a plan.
Most early-stage teams have a pipeline that includes real opportunities, polite conversations and names they hope will reply. Those should not enter the forecast with the same certainty. Keep signed customer collections separate from late-stage opportunities and late-stage opportunities separate from everything else.
A useful approach is to run three cases: committed, base and downside. Committed includes signed contracts and recurring payments from customers in good standing. Base adds deals with a credible close path and normal payment timing. Downside assumes delayed closes, lower conversion and churn where the account is genuinely at risk.
Do not make the downside case theatrical. It should reflect the ways your company could plausibly miss plan. If your sales cycle has been 45 to 75 days, a model that assumes every deal closes in 30 is not ambitious. It is wrong. If one customer accounts for 35% of MRR, model what happens if their renewal slips or they leave.
Churn also needs more than one line labeled “churn.” Separate customer loss from contraction. A customer may remain but reduce seats, pause an add-on, or delay an expansion. For a young company with a handful of accounts, model these at the customer level. Percentage assumptions are useful later. At five customers, you know their names, their renewal dates and the reason each one may change behavior.
Forecast Spending as Decisions You Can Still Change
Some costs are fixed for now. Payroll, rent if you have it, core infrastructure and existing contracts belong in the committed-cost section. Other costs are choices: a new hire, agency work, paid acquisition tests, a conference, or a new software subscription.
Treat those choices differently in the forecast. Mark the date a cost starts, whether it is approved and the condition that must be met before it starts. A planned hire might be tied to a cash floor, a signed customer, or the completion of a fundraise. That gives you a decision rule before pressure arrives.
For example: do not open a senior engineering search until the downside case still shows six months of runway after the hire’s start date. Or: approve a paid acquisition test only if you can measure payback within a stated period. The right rule depends on your stage and market, but a rule is better than renegotiating your standards every Friday.
Watch annual commitments closely. Paying yearly for software can reduce the sticker price, yet it pulls cash forward. For a company with a long runway and stable tooling needs, that can be sensible. For a company still changing its stack and watching every month of runway, monthly billing may be the better price to pay.
Make Runway a Decision Metric
Runway is not simply cash divided by last month’s burn. That shortcut misses planned hiring, annual renewals, delayed customer collections and changing infrastructure costs.
A better question is: under the downside case, when does cash fall below the minimum balance needed to operate without panic? Set that floor deliberately. It might cover one or two payroll cycles, taxes already owed and unavoidable vendor payments. The amount will vary, but zero is not a floor. Zero is where options disappear.
Then work backward from the date cash crosses that line. If you expect a fundraise to take six months from first outreach to money in the bank, your process needs to begin before the forecast says you are ready. If the business can reach a meaningful revenue milestone in four months, the forecast should show the cost of getting there and the cash required to survive a miss.
This is where a connected company record matters. Your hiring plan should agree with the financial model. Your sales pipeline should agree with the investor update. Your board materials should not show a runway number that conflicts with the bank-based forecast. Firmgrove keeps that context in one place, so the wrong number dies in the draft.
Review the Forecast Every Week
A cash forecast is not a document you finish. It is a weekly operating habit.
At the same time each week, compare actual cash movement with the prior forecast. Ask what changed: Did a customer pay late? Did a deal move? Did cloud usage rise? Did an expense arrive earlier than expected? Then update the dates and assumptions without rewriting history to make the plan look cleaner.
Track forecast accuracy for the next four weeks. You are looking for patterns, not perfection. If customer payments consistently arrive ten days later than expected, change the default collection assumption. If payroll-related costs keep surprising you, add the missing line items. The model gets useful when it learns from the company instead of repeating the founder’s first guess.
The goal is not to predict every dollar. The goal is to see the next hard decision early enough that you still have choices. Cash flow is where a startup’s story meets its calendar. Keep the dates honest and the next move becomes much easier to make.