Article
Before You Hire, Build a 13-Week Cash Forecast
Use a weekly cash forecast to test whether customer payments, payroll dates, and downside scenarios support your next hire.
A signed contract cannot make payroll.
Consider Lena, a hypothetical founder running a three-person design subscription. She has $48,000 in the bank, $72,000 in signed work, and a strong candidate asking for an $8,000 monthly salary. Her sales report makes the hire look safe. Her customers, however, pay on 30- and 60-day terms.
That timing gap is common. The 2025 Federal Reserve Small Business Credit Survey found that 56% of employer firms cited paying operating expenses as a financial challenge, while 51% cited uneven cash flow. A founder can have customers, invoices, and profit on paper while still running short on the day payroll clears.
Key takeaways
- Forecast the dates cash enters and leaves the bank, not when revenue appears on a sales report.
- Keep unsigned pipeline out of the base case and test what happens when a large payment arrives late.
- Put the hire behind explicit minimum-cash thresholds for both the base and downside cases.
- Replace estimates with bank results every week so weak assumptions become visible early.
Revenue is not your bank balance
Lena needs a cash forecast before she sends an offer. The SBA's guide to managing business finances explains that accrual accounting can record a sale before payment arrives, while cash accounting records it when the money is received. For a hiring decision, the arrival date matters.
She starts with today's bank balance and maps the next 13 weeks. Each week shows cash expected from customers, fixed bills, contractor payments, software, taxes, and the proposed hire. Confirmed invoices go in the week the customer is expected to pay. Unsigned pipeline stays out. A payment that could slip moves into a separate downside case.
Her first draft exposes the problem. The base case stays healthy because a $24,000 invoice lands in week five. When she delays that payment by 30 days, cash falls below the $15,000 operating buffer she wants to protect. The candidate is still valuable. The start date is wrong.
Build the forecast from dates
Stripe's treasury guide says cash forecasts often cover 13 weeks and estimate inflows and outflows from receivables, payables, payroll, and taxes. It also recommends scenario planning for delayed collections and softer demand. That is enough structure for an early-stage company. Lena does not need a complex financial model.
The sheet needs an opening cash balance, scheduled inflows, scheduled outflows, and an ending balance for each week. She adds a short note beside every uncertain payment: customer confirmation, contract term, or the assumption she used. That note matters because a forecast without visible assumptions can look precise while hiding guesses.
Every Monday, she replaces the prior week's estimate with the bank result, checks overdue invoices, and pushes the forecast forward by one week. If an expected payment misses twice, she stops treating the original date as credible. The model becomes more useful because it learns from actual behavior.
Put the hire behind a cash trigger
Lena sets a rule before emotion takes over: the hire starts only if the base case remains above $20,000 for all 13 weeks and the downside case remains above $10,000. She can meet that rule by collecting a deposit, changing customer payment milestones, reducing another cost, or moving the start date. She cannot meet it by counting a likely deal as cash.
Payroll also creates dated obligations beyond salary. IRS Publication 15 explains that employers generally must deposit withheld federal income tax along with employer and employee Social Security and Medicare taxes. Lena asks her payroll provider to confirm the exact deposit schedule, then places those dates in the forecast instead of hiding them inside a monthly estimate.
The forecast should stay small: one sheet, one owner, and a short weekly update. Its job is to force a decision while there is still time to change the terms.
FAQ
Why forecast 13 weeks?
Thirteen weeks is long enough to expose quarterly tax, payroll, and customer-payment timing while remaining short enough to update from real bank activity. Use a different horizon if a major obligation falls just outside the window.
Should a signed contract count as cash?
Only in the week the payment is expected to arrive, and only with the payment terms recorded beside it. Keep unsigned pipeline out of the base case. If a signed invoice could slip, move it later in a downside version.
Wrap up
Open a blank spreadsheet today, put your current bank balance at the top, map the next 13 Fridays, and enter only cash scheduled to arrive or leave. Then run one version with your largest expected payment delayed by 30 days. If the hiring decision changes, you found the risk before it spent your money. Bring that one-page forecast to buildpurdue and pressure-test the decision with other founders.