On a small gig, one invoice at the end is fine. On a three-month build, it's a trap. You front weeks of work, carry all the non-payment risk yourself, and tie up thousands of dollars in a single bill that a client can stall, dispute, or ghost on. Milestone billing fixes this by turning one scary invoice into a series of smaller, expected payments — a deposit to start, payments tied to deliverables along the way, and a final invoice at handover. Here's how to structure it so it feels routine to the client and bulletproof for you.
Why split the payment at all
Breaking a large project into installments does three things a single end-of-project invoice can't:
- Cash flow. You get paid as the work happens instead of fronting months of effort. That smooths out the irregular income that makes freelancing stressful.
- Lower non-payment risk. If a client goes quiet after milestone two, you've already been paid for milestones one and two. Your exposure is one slice, not the whole project.
- Shared commitment. A client paying as you go stays engaged — they review deliverables, give feedback on time, and treat the project as live. The money keeps both sides moving.
The deposit is the foundation of all of this. If you're not already taking one, start there: how to ask for a deposit walks through the scripts.
How to structure the split
There's no single right ratio, but a few patterns cover almost every project. Match the structure to the project's length and how the work naturally breaks into phases.
| Project type | Suggested split | Trigger for each payment |
|---|---|---|
| Short build (2–4 weeks) | 50 / 50 | Deposit to start, balance on delivery |
| Medium project (1–2 months) | 40 / 30 / 30 | Deposit, mid-point milestone, final |
| Large project (3+ months) | 25 / 25 / 25 / 25 | Deposit, then per completed phase |
| Phased / multi-stage | Per deliverable | One invoice as each phase signs off |
The deposit is almost always the largest or equal-largest slice — it screens out clients who won't pay and covers your early ramp-up. From there, weight payments toward the front if you can. A 40/30/30 collects 70% before the final stretch, which is exactly when projects are most likely to drift or stall.
Tie each milestone to a concrete deliverable
This is the part freelancers get wrong. A milestone billed against a date ("payment due June 1") invites arguments when the calendar slips. A milestone billed against a deliverable — "payment due on approval of the homepage design" — is unambiguous. The work is either delivered or it isn't.
Define these triggers up front in your statement of work so there's no negotiation later. Each milestone should map to something the client can see and sign off on:
Mapping payments to deliverables
- 1
Deposit
Paid on signing the agreement, before any work begins. This is the start trigger.
- 2
Milestone 1
Paid on approval of the first concrete output — wireframes, draft, or phase 1 build.
- 3
Milestone 2
Paid on approval of the next deliverable. Each milestone unlocks the next phase of work.
- 4
Final invoice
Paid on final handover and delivery of all files, assets, or access.
A useful rule: don't start work on the next phase until the current milestone is paid. The deliverable is approved, the invoice goes out, payment clears, then you proceed. This keeps you from ever being more than one phase ahead of payment.
Numbering and labelling partial invoices clearly
When you send four invoices for one project, clarity prevents confusion and disputes. Every partial invoice needs to make its place in the sequence obvious at a glance.
- Label the milestone. Put "Milestone 2 of 4" right in the line item or invoice title. The client should never have to guess which payment this is.
- Reference the project and prior invoices. Each invoice should name the project, reference the agreement or SOW, and ideally note what's already been billed and what remains.
- Keep numbering sequential and consistent. Use your normal invoice sequence (INV-0042, INV-0043…) so your records stay clean — see invoice numbering and record keeping for why gaps and duplicates cause problems.
- State the milestone amount and the running total. Showing "this invoice: $1,200 / project total: $4,800 / paid to date: $3,600" removes any doubt about where things stand.
- Set clear payment terms. Whether it's due-on-receipt or Net 30, spell it out on every invoice, not just the first.
Each partial invoice is a real, legally valid invoice — it just covers a portion of the total. Treat it with the same care as a standalone bill.
When milestone billing is worth it
Milestones add a little admin overhead, so they're not always the right call. Stick with a single invoice when the project is short (under about two weeks), the total is small, or the work is one indivisible deliverable. Switch to milestone billing when the project runs for weeks or months, the total is large enough that non-payment would genuinely hurt, or the work breaks naturally into phases you can bill against.
The rough threshold: if a project is long enough that you'd feel the loss of going unpaid, or structured enough to split into deliverables, bill in milestones. If a client does go silent mid-project, having banked earlier payments changes everything — and our guide on what to do when a client ghosts you covers the rest.
Make the invoices effortless
The reason freelancers avoid milestone billing is the perceived hassle of sending multiple invoices. It isn't hard when your tool does the heavy lifting — reusing the client, project reference, and your branding so each partial invoice takes thirty seconds. You can spin up "Milestone 2 of 4" with the running totals filled in and a clean PDF ready to send.
Bill your next big project in milestones
Create deposit, milestone, and final invoices in minutes — clearly labelled, sequentially numbered, and ready to send as PDFs. Free, no signup to start.
Open the free invoice generator