Most companies that run into cash trouble don't fail because they were unprofitable. They fail because the cash ran out on a specific Tuesday: payroll due, a tax payment landing, a large customer paying two weeks late. Nobody saw the collision coming, because nobody was looking at Tuesdays.
The instrument that prevents exactly this is the 13-week cash flow forecast. This guide covers what it is, how to build one step by step, and a worked example with numbers, so you can see the problem it catches before it catches you.
What a 13-week cash flow forecast is
It is a weekly projection of every dollar entering and leaving the business over the next 13 weeks. Not profit: cash. Profit is an accounting measure; cash is what is actually in the bank. Only one of them pays salaries.
It is rolling, which means it never ends. Every week you drop the week that just finished, add a new week 13, and check last week's forecast against what actually happened. It is the standard tool of restructuring professionals and CFOs, mostly because it works and partly because nothing else answers the question "can we make payroll in week 7?"
Why 13 weeks, and why weekly
Thirteen weeks is one quarter. That is long enough to see the next quarterly tax installment, the seasonal dip and the large invoice that lands in week 11, and short enough that every line can be a real, named payment rather than a statistical guess.
The weekly grain is what makes it useful. A monthly forecast can show a healthy month-end while hiding a dangerous week inside it. Companies don't run out of cash at month-end. They run out of cash on a Thursday. The example below shows how a week like that hides.
How to build a 13-week cash flow model, step by step
The model fits in a spreadsheet: one column per week, thirteen columns forward. The work is in filling the rows honestly.
1. Start from the bank, not the books. Opening cash is the balance in the bank account today, less checks and payments already issued that have not cleared. Not the balance sheet figure from last month's close, which is already out of date by the time you read it.
2. Schedule receipts by customer, on the date they actually pay. List open invoices and expected new billing, then place each receipt in the week the customer really pays, based on their history. If a customer on 30-day terms pays at 45, the forecast says 45. Your terms describe what you asked for, not what you get. Add the other receipts too: financing inflows, asset sales, refunds.
3. Load the fixed outflows first. Payroll and payroll taxes, rent, loan payments, insurance, and the tax calendar (sales tax, estimated income tax installments, payroll tax deposits). These cannot slip, so they go in first and on their exact week.
4. Add supplier runs and variable costs. Suppliers by payment run, not by invoice date. Include planned capital spending, even the purchases everyone hopes will not happen this quarter.
5. Build the bridge and draw the floor. For each week: opening cash, plus receipts, minus payments, equals closing cash. Then add one line with your minimum operating cash, the amount below which you would not want to go. The gap between closing cash and that line is your real margin of safety.
6. Roll it and track the variance. Every week, compare what you forecast with what happened, and correct the assumptions that were wrong. After six or eight cycles, your collection assumptions stop being hopes and start being data.
If you want to see the structure before building your own, our free 13-week cash flow tool runs in the browser, with no sign-up and nothing stored.
A worked example
A hypothetical company with round numbers, so the arithmetic stays visible. It starts with $120,000 in the bank and wants never to go below $60,000.
- Regular customer receipts: $70,000 every week.
- One large invoice of $120,000, due in week 3. This customer historically pays about two weeks late, so it lands in week 5.
- Suppliers: $40,000 every week.
- Payroll, including employer payroll taxes: $55,000 every two weeks (weeks 2, 4 and 6).
- Rent: $12,000 in weeks 1 and 5.
- Week 4 also carries a $60,000 quarterly tax installment and an $8,000 loan payment.
| Week | Cash in | Cash out | Closing cash | vs. $60,000 floor |
|---|---|---|---|---|
| 1 | $70,000 | $52,000 | $138,000 | +$78,000 |
| 2 | $70,000 | $95,000 | $113,000 | +$53,000 |
| 3 | $70,000 | $40,000 | $143,000 | +$83,000 |
| 4 | $70,000 | $163,000 | $50,000 | −$10,000 |
| 5 | $190,000 | $52,000 | $188,000 | +$128,000 |
| 6 | $70,000 | $95,000 | $163,000 | +$103,000 |
Three things in that table are worth a second look.
The month looks fine. If weeks 1 to 5 are one month, a monthly forecast shows the month closing at $188,000, comfortably above the floor. Week 4 does not exist in that view.
Due dates would have hidden it too. Put the large invoice on its due date, week 3, and week 4 closes at $170,000. Both versions finish week 5 at exactly $188,000. Only one of them shows the hole, and it is the one that uses how the customer pays rather than how the contract says they should.
You see it three weeks early. Seen in week 1, a $10,000 gap is a routine decision: move one supplier run a week, ask the large customer to pay on time for once, offer a small discount for paying early, or draw on the credit line calmly. Seen in week 4, the same $10,000 is a phone call to the bank in a tone the bank remembers.
The five mistakes that kill most cash forecasts
1. Using due dates instead of payment behavior. The example above, in one sentence. Modeling the terms instead of the habit manufactures cash that will not arrive.
2. Forgetting the lumpy items. Quarterly tax installments, annual insurance premiums, bonuses. Monthly averages smooth them into invisibility; the weekly grid shows them.
3. Building it once and letting it die. A forecast that is not refreshed every week is a photograph, not an instrument. Photographs of cash age badly.
4. Treating it as a finance-only document. The forecast changes decisions: when to schedule a supplier run, whether to accept a large order on 90-day terms, when to draw a credit line before the bank sees you desperate. Those are management decisions.
5. Running a single scenario. One version is not enough. A base case, a downside (your two largest customers pay 30 days late) and a stressed case tell you where the floor is, and how many weeks of warning you get before you reach it.
Spreadsheet or software?
A spreadsheet is the right place to start. It becomes the wrong place to stay when the refresh takes hours, when several bank accounts or entities need consolidating, or when the one person who understands the formulas goes on vacation. We compared the tools on their published prices, and set out when a spreadsheet is still enough, in the best 13-week cash flow forecasting software.
From spreadsheet to system
Manual forecasts decay: the person who built it leaves, the links break, the weekly refresh slips to monthly, and the instrument dies quietly. The durable version is wired into your accounting and banking data, with collections scheduled from real invoice behavior, fixed obligations loaded from the payment calendar and variances computed every week. That is the difference between a report someone maintains and a system the business runs on.
This is the instrument we build inside every engagement at Primus Pilus Capital. A rolling 13-week cash forecast is a standing deliverable of both our Profit Engine and Cash-Flow Systems tracks, refreshed weekly, with scenarios and board-ready reporting on top.
Frequently asked questions
What is a 13-week cash flow forecast?
A rolling, weekly projection of all cash entering and leaving a business over the next 13 weeks (one quarter). Each week it is refreshed: the completed week is dropped, a new week 13 is added, and forecast is compared against actuals. It is the standard cash-visibility instrument used by CFOs and restructuring professionals.
Why 13 weeks instead of a monthly forecast?
Thirteen weeks covers a full quarter — long enough to capture tax deadlines, payroll cycles and seasonality — while the weekly grain exposes the specific weeks where payments collide. A monthly forecast can show a healthy month-end balance while hiding a mid-month week where payroll goes out before a large customer pays.
What information do you need to build one?
Opening bank balance, accounts receivable with realistic payment dates based on each customer's actual behavior, accounts payable and supplier payment runs, payroll and social charges, tax calendar (VAT, installments, withholdings), debt service, and planned capex. The model itself fits in a spreadsheet: one column per week, cash in, cash out, and the weekly bridge to closing cash.
How do you build a 13-week cash flow model?
Start from today's bank balance. Schedule each customer receipt in the week that customer actually pays, based on their history, not on the due date. Load fixed outflows on their exact week (payroll, rent, loan payments, the tax calendar), then supplier runs and planned capital spending. For each week, opening cash plus receipts minus payments gives closing cash; add a line with your minimum operating cash and watch the gap. Refresh it every week and compare the forecast with what actually happened.
How often should the forecast be updated?
Weekly, without exception. The value comes from the rolling discipline: comparing last week's forecast to actuals, correcting collection assumptions, and always looking 13 weeks ahead. A forecast that is not refreshed weekly decays into a snapshot within a month.
Who builds and runs this at Primus Pilus Capital?
A rolling 13-week cash flow forecast is a standing deliverable of every Primus Pilus Capital engagement — set up during the fixed-price Diagnostic stage ($490, credited in full against Stage 02) and operated weekly in the Operate stage, with scenario views and board-ready reporting.