The 13-Week Cash Forecast: Why It Beats Monthly Forecasting Every Time

Why 13 Weeks, Specifically

Thirteen weeks is one quarter. It is long enough to capture quarterly billing cycles, payroll runs, sales tax remittances, and most receivable aging buckets. It is short enough that the inputs are still knowable rather than aspirational. Twelve weeks is too short — you miss the quarter-end concentration of payments. Twenty-six weeks is too long — week 21's variable expense forecast is a wish, not a number.

Weekly granularity also matches how cash actually moves. A business with $500,000 in monthly revenue does not receive $16,667 every day. It receives $185,000 the first week of the month from net-30 invoices, $80,000 in the second week, $120,000 in the third, $115,000 in the fourth. Meanwhile payroll hits week one and week three, rent hits week one, vendor payments stack in week two. Monthly aggregation hides all of it. Weekly granularity surfaces the squeeze points.

What Goes In

The forecast has three sections, each summed weekly across 13 columns:

• Beginning cash — last week's ending balance.
• Cash inflows — A/R collections, recurring deposits, expected new sales, refunds, capital injections.
• Cash outflows — payroll, rent, A/P payments, taxes, debt service, capex, distributions.
• Net change — inflows minus outflows.
• Ending cash — beginning plus net change. This becomes next week's beginning.

The trick is to forecast inflows from the actual A/R aging, not from revenue assumptions. If a customer owes $40,000 with terms net-30 and the invoice is dated week 1, it shows up in the forecast at week 5, not week 1. This timing precision is what makes the 13-week forecast a planning tool rather than a wish list.

A Worked Example

Consider a 12-person agency with $180,000 monthly revenue and $145,000 monthly costs. Normal cash margin is $35,000/month, but actual weekly cash positions look very different.

Notice weeks 1 and 5: payroll plus rent stack on top of light receipts, producing a $28K and $33K weekly drawdown. The monthly view averages this out and looks fine. The weekly view says — clearly — that you need at least $60,000 of float on top of your operating minimum to survive week 1. If your minimum is $50,000 and the bank balance is $100,000, you have $22,000 of buffer entering week 1, which is a thin margin if any inflow slips.

Building the Inflow Side

The most common mistake is forecasting inflows as revenue. Revenue is not cash. Cash is when the customer's payment lands in your bank. The reliable method:

1. Pull your current A/R aging by invoice and due date.
2. For each open invoice, place the dollar amount in the week the customer is most likely to pay. Use historical DSO by customer if you have it; otherwise default to the invoice due date plus a typical lag.
3. Forecast new invoices week by week from your sales pipeline, applying your typical close-to-paid lag.
4. Add recurring revenue (subscriptions, retainers) to the week of the typical billing date.

For pipeline-driven inflows, apply a probability weighting. A $40,000 deal at 60% probability becomes $24,000 in the forecast, placed in the week the deal is expected to close plus your sales-to-cash lag.

Building the Outflow Side

Outflows are easier because most are scheduled. Build the row in this order:

• Payroll — fixed dates per pay cycle.
• Rent and recurring SaaS — predictable monthly dates.
• A/P aging — your open vendor bills with their due dates.
• Tax remittances — sales tax, payroll tax deposits, estimated tax payments.
• Debt service — loan payments and interest.
• Variable spend — projected ad spend, contractor work, materials.

The variable spend row is where you get tactical control. If week 5's ending cash drops below your minimum, you can defer $15,000 of ad spend from week 5 to week 7 and visibly fix the problem. The forecast becomes a decision tool, not a status report.

Update Cadence and Rolling Forward

The forecast is updated weekly, not monthly. Every Monday morning:

1. Drop the completed week from the leftmost column.
2. Replace the ending cash for the just-completed week with the actual closing balance from your bank account.
3. Add a new week 13 at the right.
4. Adjust each column for variances — invoices that did not pay when expected, vendor bills that arrived unexpectedly, deals that closed.

This rolling discipline keeps the forecast honest. It also produces a forecast accuracy metric: actual ending cash for week 1 versus what last Monday's forecast predicted. If your week-1 forecast is consistently within 3% of actual, you have a useful tool. If it is off by 15%, your inputs need rework.

When to Use a 13-Week Forecast

Always, if your business has any cash sensitivity. Specifically:

• You have payroll obligations that must be met on a specific date.
• You carry debt with covenants tied to minimum cash balances.
• Your customers pay on net-30 or longer terms.
• You are in a turnaround, restructuring, or growth-acceleration phase.
• Your bank or lender requires it as part of borrowing base reporting.

For a deeper integration with scenario testing, pair the forecast with our stress testing methodology — the forecast is the baseline; the stress test bends it. For a contrasting view of long-horizon planning, see three-statement model basics.

Automating the Roll-Forward

The mechanical work of dropping the old week and adding a new one is the perfect job for software. Finntree's forecast module pulls your live A/R aging, payroll schedule, and vendor bills to populate the 13-week grid automatically, and updates the projected cash position as transactions clear. The Pro plan at $99.99/mo includes scenario branching so you can model "what if the Acme deal slips by two weeks" without rebuilding the spreadsheet. Starter at $39.99/mo gives you the rolling 13-week base view. Either way, the goal is the same: a forecast you actually trust enough to make decisions from.