Cash flow forecasting for US businesses

A named person on our team owns your file and reviews everything that leaves it. Software does a real share of the grinding underneath it — coding, matching, flagging the obvious gaps — but nothing regulated happens without a person’s judgement, and nothing here is signed or filed by an algorithm.

No — cash flow forecasting is operational work inside your books, not something submitted to IRS. Where a filing does sit downstream of it, inside advisory more broadly, that stays with your CPA or enrolled agent, never with us.

Whatever you already run. Most commonly QuickBooks, Xero, NetSuite, Sage, Zoho Books and a handful of others — we work inside your system rather than moving you onto one of our own.

A short, free read-only look at what you already have, and a written note on what we found. A scoping call decides the size of the engagement — nothing here commits you to anything.

There is no published price for cash flow forecasting — it depends on volume, how many entities are involved, and how far behind the books are. We quote after the read-only review, which is free.

Cash flow forecasting sits inside advisory, alongside Runway analysis, Budgeting and forecasting, Margin analysis. Most clients end up buying the category as a whole rather than one leaf at a time, but starting narrow is fine.

Thirteen weeks is roughly the window where a cash problem is still solvable — you can chase a slow-paying customer, delay a discretionary purchase, or line up a bridge before the account actually runs dry. A monthly forecast can show a healthy average for the quarter while missing the one week in the middle where the balance nearly hits zero.

That spreadsheet was almost certainly built once, with assumptions typed in at the time, and never reconnected to the actual books afterward. Ours refreshes weekly directly from the reconciled ledger, so the receipts and payments in the model are what actually happened, not what someone guessed months ago.

A base case built on your actual, observed payment behavior, plus a downside case (a customer pays late, a raise slips, a slow season runs long) and an upside case (a signed contract, faster collections). Each scenario shows the specific week your cash position would change, not just a vague sense that things would be tighter or looser.

Yes, as scheduled outflows — quarterly estimated tax payment dates, and 941 deposit dates where they apply — sourced from your CPA's calendar and amounts. That figure comes from your CPA's own calculation; we make sure a known payment doesn't collide unexpectedly with payroll or another large outflow in the model.

No. It can show that revenue from a particular state has grown large enough to be worth checking, but the nexus determination itself — whether that revenue has actually created a filing obligation — goes to your CPA. Nexus rules are state-specific and change over time, so it's not something a cash model rules on.

No. A downside scenario is a planning exercise showing what happens to cash under a specific stressed assumption, so you can act before it happens. A going-concern opinion is an audit-level judgment a CPA makes on audited financial statements — a different function entirely, and not something a forecast issues.

Weekly is standard for the 13-week model, because payment timing shifts matter at that granularity. Each refresh compares last week's projection to what actually happened, so you can see whether the model is tracking reality or an assumption needs correcting.

It gets corrected at the next weekly refresh, and the summary states plainly what changed. A model that keeps running on a stale assumption without anyone flagging it is the exact failure the weekly reconciliation against actual AR aging is built to catch.

AI pulls the transaction data, reconciles last week's projection against actuals, and flags variances outside the normal range. A named advisor reviews the model, sets or approves the scenario assumptions, and is accountable for the numbers before they reach you — the model doesn't sign off on itself.

A reconciled general ledger, AR and AP aging detail, and your scheduled fixed outflows — payroll dates, loan payments, any recurring vendor terms outside the standard 30-day cycle. The forecast is only as accurate as the ledger and aging it starts from.

The 13-week forecast and a runway calculation are related but distinct outputs — runway is a single burn-rate-and-date figure, usually derived from a longer monthly model, while the 13-week forecast is the weekly mechanics feeding it. If you need a standalone runway figure for investor reporting, that's built from the same underlying data as a separate deliverable.