Profitable on paper. Cash-constrained next Tuesday. Reveal how much incremental spend cash can support—and when it can safely be released.
Use this resource when
Download the working file.
This is the complete editable template—not a PDF preview. Add your own account data, owners and decisions.
Set the cash guardrails you actually own
Enter opening cash, a reserve floor, proposed incremental spend, settlement week and a risk buffer. Every threshold is editable; none is presented as a universal benchmark.
Build the 13-week cash plan
Place store payouts, other inflows, operating outflows, inventory commitments and baseline ad settlement in the week cash actually moves. The workbook rolls ending cash into the next week's opening cash.
Separate profitability from liquidity
A campaign can remain contribution-positive while the bank balance cannot absorb the next charge. The guardrail uses minimum cash headroom across the plan instead of treating revenue or ROAS as immediate cash availability.
Release, hold or stop
The selected scenario compares buffered cash need with minimum baseline headroom and returns RELEASE, HOLD or STOP, plus the safe incremental amount now.
Validate timing before acting
Confirm bank, payout, card and purchase-order dates before approving spend. This is a cash-timing estimate—not a demand forecast, financing recommendation or guarantee.
Practical questions
Questions that change the decision
Does this replace a full cash-flow forecast?
No. It is a focused 13-week operating guardrail for the timing of incremental ad spend, inventory, payouts and recurring cash outflows.
Does HOLD mean stop advertising?
Not necessarily. HOLD means the full proposed incremental charge exceeds buffered headroom under the selected timing. The workbook shows a safe amount or lets you move the settlement week.
Is the included reserve a benchmark?
No. The reserve, risk buffer and all example values are illustrative. Replace them with thresholds agreed for your business.
Sources and platform documentation
Platform features change. These links point to the primary documentation used for the implementation details above.