- 1Every Compliance Client Has Already Asked for This
- 2What You're Selling: A Product, Not a Project
- 3Pricing the Cash Flow Forecasting Service
- 4The Delivery Workflow at Firm Scale
- 5Scope Fences: What the Forecast Is Not
- 6One Client, One Red Week, One Renewed Retainer
- 7The Next "Are We Good for the 28th?" Text
Your clients keep trying to buy a cash flow forecasting service from your accounting firm. Most firms keep giving one away instead — once, unbilled, and never updated again.
The text arrives on a Tuesday: "Quick one — supplier wants the $52K balance by the 28th. Are we good?" You close this client's books. You know their October cold. And you still can't answer the question, because the question isn't about October — it's about the next six Thursdays.
So you do what most firm owners have done at least once. You spend an evening building a cash forecast from scratch — a genuinely good one, payout timing and PO schedule and all. The client is thrilled. You never bill for it, because it wasn't in the engagement letter and the conversation feels awkward. And you never update it, because there's no cadence attached. Six months later it's a souvenir in a shared drive, and the client is texting the same question about a different PO.
That evening was a cash flow forecasting service — designed, built, and delivered by your accounting firm, at a price of zero, with a subscription term of once. The only thing missing was the product around it: what's in it, what to charge, how to deliver it across a client list without burning senior hours, and the fences that keep it from becoming something you never agreed to.
Every Compliance Client Has Already Asked for This
Here's the belief that keeps the forecast unbilled: cash forecasting is CFO work. It's custom, it's senior-heavy, it's judgment all the way down — you can't productize it at bookkeeping-firm economics, so it stays a favor for good clients.
That's the lie, stated plainly, and it deserves a fair hearing. A genuinely custom financial model is CFO work. If every client's forecast were a bespoke build, the economics would never close, and answering "can I afford this PO?" for free would be the rational choice.
But look at the question your clients actually ask. It's not "model my business." It's "can I pay the supplier balance on the Thursday it's due?" — and for e-commerce clients, that question has a standard answer with a standard shape: a rolling 13-week, direct-method cash forecast. Thirteen columns, fifteen rows, refreshed on a fixed cadence from reconciled books. The structure doesn't change client to client. The payout cadences, PO calendars, and tax filing schedules that fill it do — and those are inputs, not architecture.
Which means the demand signal has been sitting in your inbox for years. Every "are we good for the 28th?" text is a client trying to buy a deliverable you haven't put on the shelf. When we mapped the move from compliance to advisory, the forecast was one of four deliverables store clients reliably pay for. It's worth this whole post for a reason: it's the one they ask for by name, in their own words, before you've pitched anything.
What You're Selling: A Product, Not a Project
The failure mode of the free forecast wasn't quality — it was structure. It had no beginning (no engagement letter), no middle (no refresh cadence), and no end (no renewal). The fix is to package it in two parts.
Part one: the setup engagement. A fixed-fee project, scoped in writing. You build the client's forecast model from their reconciled books: map their payout cadences by channel, load the PO calendar and payment terms from their supplier agreements, place the sales tax remittance weeks, set the payroll and opex rhythm, and populate all thirteen weeks. Then you walk them through it on a call — including the parts they won't like. Deliverable: a live forecast, an assumptions memo, and one trained client.
Part two: the refresh retainer. A recurring add-on to the compliance engagement: every refresh, you replace last period's forecast with actuals, adjust the remaining weeks for what you learned, roll a new week 13 onto the end, and flag anything red or close to it in a three-sentence note. Monthly refresh as the standard tier, weekly for clients with real inventory exposure. The note is the product — "week 6 dips below your floor; the driver is the PO balance landing in the same week as sales tax; here are two moves" — not the spreadsheet.
Notice what's not in this section: how to build the forecast itself. The row-by-row build — payout-timed receipts, the lumpy PO row, financing remittances, the double-count trap — is fully worked in the store-owner edition of the 13-week forecast. Read it once as a build spec, then hand it to clients who ask what they're paying for: the honest answer is "this, done every Monday, by people who never skip a Monday."
Pricing the Cash Flow Forecasting Service
Price it the way the retainer-pricing model prices everything else: on the outcome, floored at your worst-case cost — never on the hours it takes once the system is humming.
Start with what the deliverable is worth, because for once the value math is vivid. A missed red week doesn't cost a client inconvenience; it costs them a panic decision — a bounced supplier payment before the season's inventory ships, or a merchant cash advance signed on a Thursday afternoon at an effective cost that runs well into five figures on any meaningful balance. One caught red week, moved six weeks early with a phone call, prevents a five-figure mistake. A forecast that does that once a year is not competing with the price of a spreadsheet.
Illustrative numbers — round figures to show the shape, set your own against your costs and market:
| Component | Scope | Illustrative pricing |
|---|---|---|
| Setup engagement | Model build, assumptions memo, walkthrough call | $1,500–$3,000 fixed |
| Monthly refresh | Refreshed at close, red-week flag note | +$300–$500/month on the retainer |
| Weekly refresh | Every Monday, for inventory-heavy or seasonal clients | +$600–$900/month |
Two framing notes. First, sell it as an add-on to the compliance retainer, not a renegotiation — the client already trusts the base engagement; you're extending it. Second, the setup fee is not padding. It prices the real senior judgment in the engagement — the assumptions — and it makes "free forecast as a favor" structurally impossible, which protects you from the margin leak that unpriced advisory always becomes.
The Delivery Workflow at Firm Scale
One forecast is a spreadsheet. Twenty are a service line, and the difference is standardization.
Build one model, not twenty. Your forecast template — row structure, formulas, red-week conditional formatting, assumptions tab — is firm IP, exactly like your standard chart of accounts. Every setup engagement starts from the template and customizes inputs only: this client's payout cadences, PO calendar, filing schedule. Setup drops from an evening to a couple of hours, and any staff member can read any client's forecast because they're all the same shape.
Attach the refresh to a cadence that already exists. Monthly-tier refreshes happen inside the month-end close — the forecast becomes the last checklist item, done while the reconciled numbers are already open. Weekly-tier refreshes are a Monday-morning block: all weekly clients, one sitting, one staffer.
And here's the prerequisite that decides whether any of this is real: the refresh starts by replacing forecast with actuals — which assumes the actuals exist on Monday morning. Payouts reconciled, fees separated, refunds where they belong. If your firm produces actuals by hand, every refresh begins with an hour of archaeology per client, the Monday block becomes a Monday-and-Tuesday block, and the service quietly dies the way the free forecast did. This is the same infrastructure argument as the firm-margin story, pointed at a new deliverable: automation is what makes the refresh a 20-minute task instead of a two-hour one. Firms running their portfolio on LedgerPort have each client's payouts already reconciled in QuickBooks when Monday arrives — sync schedules are configurable per client, daily or real-time on the higher plans — with every client managed as a separate business under one firm login. At that point the refresh really is: open forecast, pull actuals, adjust, roll, write three sentences. Twenty minutes, any trained staffer, twenty clients before lunch.
That's the unit economics in one line: a $400/month refresh that costs 20 minutes of staff time is a better margin than your compliance work. The same refresh at two manual hours is a donation.
Scope Fences: What the Forecast Is Not
Advisory deliverables need harder fences than compliance work, because the client is acting on your output. Put these in the engagement letter, in plain language, and repeat them in the walkthrough call:
- It's a projection, not assurance. The forecast is built on management's assumptions about future sales, costs, and timing. You are not auditing, examining, or certifying those assumptions — you're organizing them. Say so in writing.
- It's not a guarantee. Actuals will differ from forecast; the deliverable is early sight of likely crunches, not a promise the bank balance will match the spreadsheet. The client who hears "the forecast said we'd be fine" as a warranty is a client you fence now, not later.
- Use the disclaimer language your professional body expects. Prospective financial information carries specific professional-standards language in most jurisdictions — confirm the required wording with your professional body and your liability carrier before the first engagement letter goes out. This is a ten-minute check that you do once.
- The decision stays with the client. You present the red week and the options — split the PO payment, pull collections forward, arrange a line of credit early. Whether to sign the PO is their call. Advisory means informing decisions, not making them.
- Fence the scope creep specifically. Scenario modeling ("what if we launch the second brand?"), fundraising projections, daily cash positioning, additional entities — all real work, all quotable, none included in the refresh retainer. Name them in the letter as separately scoped.
None of this is defensive theater. Clear fences are what let you sell the forecast confidently — you know exactly what you promised, so you never have to over-deliver for free.
One Client, One Red Week, One Renewed Retainer
Here's the whole product in a single fictional engagement, round numbers throughout.
A home-goods client doing about $140,000 a month. Setup engagement in January: $2,000, template model, assumptions memo, walkthrough. Weekly refresh at $500 a month, folded into the Monday block.
In early August, the refresh flags week 6 of the window: a $52,000 fall PO balance lands in the same week as an $11,000 quarterly sales tax remittance, inside the client's usual late-summer payout dip. Ending cash: minus $9,000 for eight days, positive again by week 8. Without the forecast, nobody sees this until the Thursday it happens.
Your staffer writes the three-sentence note. You make one call: "Sign the PO — but ask the supplier to split the balance, half at shipping, half on delivery." The client asks; the supplier, hearing from a customer six weeks early instead of six days late, agrees without friction. Twenty-six thousand dollars moves from week 6 to week 9. The red week closes to positive-$4,000. The alternative — discovered in week 6 — was a rushed advance against future payouts at a cost that would have started around $8,000 and gone up from there, plus a supplier relationship that never quite recovers.
Total retainer for the year: $6,000 plus setup. One catch paid for all of it, and the client knows it — your note is in their inbox, dated six weeks before the Thursday. Compliance work is invisible when it goes well. The forecast is visible precisely when it goes well, which is why it's the deliverable clients describe to other founders.
The Next "Are We Good for the 28th?" Text
One will arrive this month — some client, some supplier, some Thursday. You can answer it the old way: an evening of unbilled modeling and a spreadsheet that dies in a shared drive. Or you can answer it with a price: "That's exactly what our forecasting service answers every Monday. Setup is $2,000; here's what you get."
The template is one afternoon's work. The pricing is a table in this post. The only real prerequisite is the one the whole refresh cadence stands on — every client's payouts already reconciled when Monday morning arrives, without a staffer rebuilding them by hand. If that layer isn't automated at your firm yet, start the CPA onboarding and run one forecasting-candidate client through it. The twenty-minute refresh is only real when the actuals are already sitting there — that's the part the software does, so the part you sell is the judgment.
