Guide · Invoices · 5 min read
Deposit vs milestone billing: which one to use
50/50, thirds, monthly, milestones, or a retainer. How to pick a payment structure by project length and client size, with the cash-flow arithmetic behind each.
· Ferrier Industries LLC
In short
- Pick the structure by two things: how long the project runs, and how slowly the client’s finance department moves.
- Short job, small client: 50/50. Six to twelve weeks: 40/40/20. Longer, or paced by the client: monthly on a fixed date. Distinct phases: milestones, triggered on delivery rather than approval.
- The deposit decides how much you stand to lose if the client disappears in week two. Hold a floor of 25%, and 50% for a client you have not worked with before.
- The rule underneath every option: the money you are owed at any moment should never be more than you are willing to lose.
There are only about five payment structures in freelancing, and choosing the wrong one is how a profitable project turns into a cash-flow problem. The choice comes down to two things: how long the project runs, and how slowly the client’s finance department moves.
The five structures
| Structure | Fits | Watch for |
|---|---|---|
| Structure50/50 | FitsUnder about six weeks, small client | Watch forThe second half arrives after delivery, when your leverage is lowest. |
| Structure40/40/20 | FitsSix to twelve weeks | Watch forNeeds an agreed midpoint that nobody has to argue about. |
| StructureMilestones | FitsLong projects with distinct phases | Watch forTrigger each invoice on delivery, never on approval. |
| StructureMonthly, fixed date | FitsLong builds, or anything paced by the client | Watch forSay “regardless of project stage” in writing. |
| StructureRetainer | FitsOngoing work with no end date | Watch forDefine the capacity, and say that unused time does not roll over. |
50/50
Half up front, half on delivery. A sensible default for short, smaller projects. It is simple enough that a client can approve it without involving anyone, and it means you are never more than half exposed.
The failure mode is the tail. On a $12,000 project, the final $6,000 arrives after everything is delivered, which is precisely when your leverage is lowest. Tie the transfer of ownership to the final payment and this mostly resolves itself.
Three payments: 40/40/20
40% to start, 40% at an agreed midpoint, 20% on delivery. Better than 50/50 for six-to-twelve-week projects, because the final unpaid slice is small enough that the client has little to gain by stalling. Prefer 40/40/20 to an even three-way split: a smaller final payment is easier to collect.
Milestone billing
Payments attached to phases: discovery, concepts, build, launch. Right for long projects with clear stages. The critical detail is what triggers the invoice.
Monthly, on a fixed date
The project total divided by its months, invoiced on the 1st regardless of stage. Ideal for long builds and for anything where the client controls the pace. Nobody has to judge whether a phase is finished, which removes a common billing argument. Write it explicitly: “Invoiced monthly in advance on the 1st, regardless of project stage.”
Retainer
A fixed monthly fee for a defined capacity, such as “up to 30 hours per month” or “up to four deliverables per month,” paid in advance, with unused capacity not rolling over. For ongoing relationships this beats every project structure, because it takes the sell-then-deliver sawtooth out of your income.
How big should the deposit be?
The deposit is not a formality. It decides how much you stand to lose if the client disappears in week two. Three floors worth holding:
- Never below 25%. Below that, a canceled project leaves you underwater on the time you have already booked out.
- For a first project with a new client, 50%. You have no payment history with them, and the deposit is the cheapest credit check there is.
- For anything with hard costs (printing, licenses, subcontractors, stock), the deposit covers all of those costs plus your usual percentage. Never carry someone else’s supplier bill.
Say “deposit” to individuals and small businesses, and “initiation fee” or “mobilization payment” to procurement departments. The second phrasing can survive a purchasing policy that says deposits are not permitted.
The cash-flow arithmetic
Take a $24,000 project running twelve weeks, delivered in week 12. The 50/50 balance is net 14; the monthly invoices are due on receipt. Two structures, the same total, very different lives.
| Compared on | 50/50 | Monthly in advance |
|---|---|---|
| Compared onPayments | 50/50$12,000 in week 0, $12,000 in week 14 | Monthly in advance$8,000 in weeks 0, 4 and 8 |
| Compared onLongest wait between payments | 50/5014 weeks | Monthly in advance4 weeks |
| Compared onMost work unpaid at any moment | 50/50Half the project | Monthly in advanceNone: each month is paid before it starts |
| Compared onIf the client stops paying | 50/50You find out after delivery | Monthly in advanceYou find out within 4 weeks, and can stop |
On 50/50 you are financing more than three months of the client’s project out of the first payment, and if they pay late you are financing it out of savings. Billed monthly, you are never more than four weeks from the next payment. Same revenue, far less exposure.
Big clients change the calculation
Enterprise accounts payable runs on a schedule you do not control. Expect a purchase order requirement, a vendor onboarding form, net 30 to net 60 terms, and a payment run that happens on fixed days of the month. None of it is personal, and the person who hired you usually cannot change it.
- Get the PO number before starting. An invoice without one can sit unpaid, and nobody will tell you why.
- Ask who processes invoices and send them a copy directly. The person who hired you is rarely the person who pays you.
- Invoice as early in the month as the milestone allows. Missing a payment run by two days can cost you four weeks.
- Price long terms into the quote. Waiting two months to be paid is a real cost, and it belongs in the number.
Net 30 vs due on receipt goes through the terms themselves.
Changing the structure mid-relationship
If you have been running 50/50 with a client whose final payments always drift, move them at the next project rather than mid-project. Frame it as a change to how you work, not a reaction to them:
Hi Marcus, Before we kick off the Q4 campaign, one change on my side: I have moved longer projects to monthly billing. The project total is split across the months it runs and invoiced on the 1st, regardless of where we are in the schedule. For this one that is three payments of $6,500 on October 1, November 1, and December 1. Same total as the quote, and it stops the end-of-project invoice landing on you all at once. I will send the scope with those terms in it today. Sam
Monthly billing is often easier for a finance team to absorb than one large invoice, so you are not asking for a favor. You are proposing something that suits you both.
The rule underneath all of this
Structure payments so that the money you are owed at any moment is never more than you are willing to lose. Everything else (the split, the trigger, the terms) is detail hanging off that one principle.
In PaloWorks a project’s fee can be split into a payment schedule, with each payment due on signature, on a date, or on delivery (issuing on signature needs a contract, which is on Pro and Studio), and a deposit invoice is one button. Payment schedules and deposits in the help center shows how.
Read next · Invoices
Net 30 vs due on receipt: which terms to put on your invoice
“Net 30” is a policy. “Due September 15” is a deadline. Put the date on the invoice.
Continue →Try PaloWorks for free
Intake, scope, rounds, change orders, invoice on one project URL. The extra round goes on the invoice.