Cash flow forecast for freelancers: a 13-week method with three lines
By SoloWOS teamPublished
IN SHORT
A freelance cash flow forecast projects money in and out week by week for the next 13 weeks. Split money in into three lines: sure (sent invoices, moved by each client's usual delay), likely (accepted work and retainers not invoiced yet) and possible (open proposals times your acceptance rate). Then subtract average expenses and tax payments.
Prices and limits as of .
Key takeaways
- Date each invoice by when the client actually pays: the due date plus that client's average days late, not the due date alone.
- Possible income is open proposals multiplied by your acceptance rate. With fewer than 5 decided proposals, count it as 0 rather than guessing.
- Money out is the average of your last 3 full months of expenses, spread by week, plus estimated tax payments. For 2026 the IRS due dates are April 15, June 15, September 15 and January 15, 2027.
- Let the spreadsheet or software do the math and the AI explain it. A model asked to forecast your income will produce confident numbers it can't back.
- SoloWOS builds the 13-week forecast in Invoicing > Cash flow without AI; Explain with AI uses one AI draft (3 a month on Basic, 200 on Solo) and sends only weekly totals, no names.
A profit and loss report tells you what you earned last month. A cash flow forecast tells you whether you can pay rent in week 7. For freelancers the gap between the two is wide, because clients pay late, projects start when they start and taxes come quarterly. The SBA's financial planning resources make the same point: a business can be profitable and still run short of cash at the wrong moment. Thirteen weeks is long enough to see a gap coming and short enough that the numbers mean something.
The three lines of money in
| Line | What goes in it | When you expect it |
|---|---|---|
| Sure | Invoices you've sent and that aren't paid | Due date plus the client's average days late; due date for new clients |
| Likely (adds to sure) | Accepted proposals not invoiced yet, and the next invoices of retainers or recurring billing | Accepted work: about 2 weeks after acceptance. Retainers: their next invoice date, plus the usual delay |
| Possible (adds to likely) | Open proposals, multiplied by your acceptance rate | Sent date plus your typical days to accept, plus about 2 weeks |
Keep the lines cumulative: likely includes sure, and possible includes both. Then you can read three running balances and plan on the sure one. Leave out invoices more than 60 days overdue; list them separately and chase them, but don't plan rent around them.
Where each number comes from
- Client delay. For each client, average how many days after the due date their past invoices were paid. A client who pays 12 days late on net 15 really pays in 27 days. The DSO calculator gives the same idea across all clients.
- Acceptance rate. Accepted proposals divided by proposals with an outcome (accepted, declined or expired) over the last year. 6 accepted out of 15 is 40%.
- Days to accept. The median number of days between sending a proposal and the client accepting it. Use 7 if you have no history.
- Expenses. Total the last 3 full months of business expenses, divide by 3 for an average month, and spread it evenly: multiply by 12 and divide by 52 for a week. Mark the ones that repeat every month, like software and rent.
- Taxes. Put your quarterly estimated payments in the weeks they're due. How much to set aside for taxes and the quarterly estimated taxes guide cover the amounts.
- Starting balance. What's in your business account today. Without it, the forecast shows only the change, starting from zero.
Build it in a spreadsheet, step by step
- Make 13 columns, one per week, starting with the current Monday.
- List every unpaid invoice with its amount and its expected week (due date plus that client's delay). Anything expected in a week that already passed goes in this week.
- Below them, list accepted work not yet invoiced and the next retainer invoices, each in its expected week.
- Below that, list open proposals at amount × acceptance rate, in their expected week.
- Add a money-out row: the weekly expense average in every column, plus tax payments in their weeks.
- Add three running balances from your starting balance: sure minus money out, likely minus money out, possible minus money out.
- Highlight any week where the sure balance drops below one month of expenses. That's the week to act on now.
WORKED EXAMPLE
Worked example: a consultant's next 13 weeks (illustrative numbers)
Starting balance: $6,000. Sure: three invoices, $3,000 expected in week 2 (due in week 1, client pays about a week late), $2,500 in week 4 and $1,800 in week 9: $7,300. Likely: a $4,000 accepted project expected in week 3 and a $1,500 monthly retainer in weeks 2, 6 and 11: $8,500 more. Possible: two open proposals worth $10,000 at a 40% acceptance rate, $4,000, expected around week 8. Money out: $2,600 a month of expenses is $600 a week, $7,800 over 13 weeks, plus a $3,200 estimated tax payment in week 8. On the sure line the balance drops to $2,900 in week 8, the tax week, and ends the 13 weeks at $2,300, below one month of expenses. On the likely line it ends at $10,800. The decision: invoice the accepted project as soon as work starts, chase the week 4 invoice early, and don't count on the open proposals for the tax payment.
Read the forecast for tight weeks
Look at the lowest point of each line, not the end. A forecast that ends positive can still go negative in week 6 if a big invoice lands in week 7. When the sure line dips, you have three moves: bring money in sooner (invoice accepted work now, ask for a deposit on new work, chase the late client before the due date), push money out later (move a non-urgent purchase), or hold more cash. Each move is visible in the forecast before you make it. If billable hours are waiting to be invoiced, the unbilled time calculator shows how much is sitting there.
What AI should and shouldn't do in a forecast
A forecast is arithmetic on your own records, so code should do it: the same inputs always give the same result, and every number traces back to an invoice or an expense. A language model asked to “forecast my income” will produce plausible numbers it can't trace. Where AI helps is reading the finished forecast back to you in plain words: which weeks are tight, what moves the result most, and which assumption to check. It shouldn't advise you on loans, investments or taxes.
The 13-week forecast in SoloWOS
In Invoicing, the Cash flow tab builds the forecast from your records, with no AI: sure from sent and viewed invoices at the due date plus each client's usual days late (clients who pay late are marked At risk, and invoices more than 60 days overdue are listed apart), likely from the next recurring invoices and proposals accepted in the last 90 days that aren't invoiced yet, and possible from open proposals at your acceptance rate. With fewer than 5 proposals that have an outcome, the rate is 0% and the page says so. Money out is your average month of expenses over the last 3 full months, spread by week, with repeating vendors marked, plus the estimated tax payments due in those weeks from the tax estimate in Expenses. Billable time not invoiced yet is shown apart, and each currency gets its own forecast; nothing is converted.
You can type a starting balance, which stays in your browser and never reaches the server. Explain with AI recalculates the forecast and sends only the weekly totals, the balances from zero and the assumptions, with no client names, invoice numbers or vendors; it returns 3 to 5 sentences on gaps and tight weeks, and isn't saved. It uses one AI draft each time it works (3 a month on Basic, 200 on Solo). SoloWOS uses Claude models from Anthropic. Under Anthropic's commercial terms, the data sent for a request isn't used to train their models, and the SoloWOS privacy policy lists what each AI feature sends. The SoloWOS AI assistant answers “how much will come in next month?” from the same numbers.
The forecast is only as good as the records behind it, so send invoices clients pay by card and log business expenses with receipts in the same account. For the terms that move the sure line, see net 30 vs due on receipt.
Questions
How far ahead should a freelancer forecast cash flow?
Thirteen weeks, about one quarter, works for most freelancers: it covers the next estimated tax payment and the invoices you've already sent, and it's short enough that the numbers are mostly real. Beyond three months, most of the income is possible work, and the forecast becomes a guess.
How do I forecast irregular freelance income?
Separate what's certain from what isn't. Sent invoices are sure, accepted work and retainers are likely, and open proposals are possible at your acceptance rate. Plan your spending on the sure line, and treat the other two as upside.
Should I include taxes in my cash flow forecast?
Yes. Estimated tax payments are some of the largest single payments a freelancer makes, and they land on fixed dates: for 2026, April 15, June 15, September 15 and January 15, 2027, per the IRS. Put each payment in its week, not spread across the quarter.
Can AI predict my freelance income?
Not reliably. A model has no way to know whether a client will pay or a proposal will be accepted. Use code or a spreadsheet for the forecast, built from your own history, and use AI to explain the result in plain words.
Sources
Facts checked against these sources on October 24, 2026. Rules and amounts change, so confirm them at the source before you file or sign.
- SBA: Manage your finances
- IRS: Estimated tax FAQs
- IRS Publication 505 (2026), Tax Withholding and Estimated Tax
- Anthropic Privacy Center: Is my data used for model training? (commercial products)
Last reviewed:
SoloWOS tools mentioned here
More on ai for freelancers
- AI bookkeeping for 1099 contractors: pick by the job you need doneKeeper, Deduction, FlyFin, QuickBooks Solopreneur or invoicing plus receipts: prices from each site and which fits a 1099 contractor. SoloWOS doesn't file.
- AI meeting notes from a recording: transcript, chapters and next stepsTurn a recording into a transcript, summary, chapters and next steps with AI, what to check after, and when you need everyone's consent to record.
- How accurate is an AI receipt scanner? Test it on your own receiptsHow to test an AI receipt scanner before you trust it: a 30-receipt sample, a field-by-field score sheet and the errors that matter for your books.
- AI receptionist for a one-person business: phone service, AI voice or a chatAnswering service, AI phone receptionist or a chat on your booking page: what each one costs, what it can answer and which fits a one-person business.
Run your client work from one account
14 days free, no card needed · Then Basic for $2/month.
Start your free trial