Big projects punish freelancers who only invoice at the end. You front the time, the client front-loads the deliverables, and your bank account goes flat for months while you wait on a single payment. Milestone billing fixes that. Instead of one invoice at the finish line, you tie payments to specific deliverables along the way — a deposit to start, a check‑in payment at the halfway mark, and a final payment on delivery.
Done well, milestone billing protects your cash flow, gives the client clear visibility into progress, and keeps both sides honest about scope. Done sloppily, it just turns into "send me money when I ask" — which is exactly the kind of vague arrangement that breeds late payments and disputes.
This guide walks through how to design a milestone payment schedule, what each milestone invoice should contain, and the practical mechanics of getting paid on time across a multi‑phase project.
What milestone billing actually means
Milestone billing — sometimes called phased billing or progress billing — is an arrangement where the client pays you in chunks tied to specific, agreed-upon deliverables rather than waiting until the entire project is finished. Each milestone has three things: a deliverable (what you'll hand over), an acceptance criterion (how the client confirms it's done), and a price (the amount that becomes payable when the milestone is met).
It's distinct from a few related models freelancers use:
- Hourly billing charges for time logged, regardless of progress. Milestone billing charges for outcomes.
- Retainer billing charges a fixed recurring amount for ongoing access or capacity. Milestone billing applies to a defined project with a beginning and an end.
- Net-30 billing on a single invoice is what you do when you bill the entire fixed fee at the end. Milestone billing splits that fee into pieces.
The closest cousin is the upfront deposit — and in fact, your first milestone usually is a deposit. The difference is that milestone billing keeps that pattern going through the whole engagement instead of stopping after the kickoff.
When milestone billing makes sense
Not every project needs phases. Reach for milestone billing when:
- The total project value is large enough that one invoice at the end would create real cash-flow pain (a useful rule of thumb: any engagement over four to six weeks).
- The deliverables are discrete and verifiable — a wireframe, a draft, a working prototype — not a fuzzy "consulting" output.
- The client is new to you or operates on a corporate accounts-payable cycle (where Net‑30 actually means Net‑45).
- The scope is ambitious enough that you genuinely want a checkpoint before continuing.
Skip phasing for short, well-defined projects. A two-week logo design can be billed as a 50% deposit and a 50% final, which is technically two milestones but barely worth calling a "schedule." Use full milestone billing when the project would otherwise be a single five-figure invoice 90 days from now.
How to break a project into milestones
Industry guidance generally points to three to six milestones as the sweet spot. Fewer than three and you don't have enough checkpoints to catch a project drifting off course. More than six and you spend more time invoicing and chasing approvals than working.
A few patterns that work for common freelance projects:
The 30/40/30 split — 30% deposit on contract signature, 40% at a clear midpoint deliverable, 30% on final delivery. Good for design and content engagements where there's a meaningful "draft" stage.
The 25/25/25/25 split — Even quarters tied to discovery, design, build, and launch. Good for web development and software projects that move through distinct phases.
The deposit + monthly progress + holdback — A deposit at kickoff, equal monthly payments during the project, and a final 10–15% holdback released on acceptance. Common for longer engagements like multi-month brand or platform builds.
Whatever you pick, the milestones should be tied to client-visible deliverables, not internal effort. "Halfway through coding" is not a milestone. "Working signup flow demoed in staging" is.
What goes on a milestone invoice
A milestone invoice is structurally the same as a standard professional invoice — what changes is the description. Each milestone invoice should clearly identify:
- The project name and a stable project reference number that ties all milestones together
- The milestone number and name (e.g., "Milestone 2 of 4 — Design Approval")
- A short description of the deliverable that triggered this invoice
- The agreed amount for that specific milestone
- The percentage of the total project this milestone represents
- A running total showing what's been billed to date and what remains
- Standard payment terms (due date, accepted payment methods, late fee policy)
A common mistake is to send a milestone invoice with no context, just an amount. Clients juggling many vendors lose track. A two-line summary at the top — "This is milestone 2 of 4 for the website redesign project, covering the approved homepage and product page mockups delivered on May 2" — saves you a follow-up email and makes the invoice harder to dispute later.
If you're not sure what to put on the document itself, the basic format follows the same rules as any other freelance invoice. The step-by-step invoice guide covers the line-item structure; for milestone work you simply replace the line items with the single milestone deliverable and amount.
Sample milestone payment schedule
Here's what a written-out schedule for a $12,000 brand identity project might look like:
- Milestone 1 — Project kickoff. Triggered on contract signature. 25% ($3,000) due net‑7. Deliverable: project plan and discovery questionnaire.
- Milestone 2 — Concept presentation. Triggered when three concept directions have been presented. 25% ($3,000) due net‑15. Deliverable: concept presentation deck.
- Milestone 3 — Design approval. Triggered when the client has approved one direction in writing. 30% ($3,600) due net‑15. Deliverable: refined logo system, color palette, and typography.
- Milestone 4 — Final delivery. Triggered on delivery of all final files and brand guidelines. 20% ($2,400) due net‑15. Deliverable: full brand guidelines PDF and source files.
Note three practical details: the deposit milestone has a tighter payment window (net‑7) because you don't start work until it's paid; each milestone has a written trigger so there's no ambiguity about when an invoice goes out; and the holdback at the end (20%) is meaningful but not so large that the client could walk away from the relationship.
Handling acceptance and approvals
The single most common failure mode in milestone billing is fuzzy acceptance. The freelancer thinks the milestone is done; the client says "we're still reviewing"; the invoice sits unpaid because nobody agrees the work is finished.
Two practices help:
Define acceptance in the contract, not the invoice. Each milestone should have a written acceptance criterion — usually "client approval in writing within X business days of delivery, or deemed accepted by default." A 5–10 business day review window is typical. Without this, a slow client can stall the entire project indefinitely.
Send a delivery note, then the invoice. When you hit a milestone, send a short message that explicitly says "this completes milestone 2; please confirm acceptance or send revision requests within 5 business days." Then send the milestone invoice. Separating the delivery from the invoice gives the client a clear moment to flag issues, and gives you a paper trail for when they don't.
If a client misses the review window without flagging anything, your contract's "deemed accepted" clause kicks in and the invoice is due. If they do flag revisions, the milestone is still in flight — don't invoice yet, but log the time spent on revisions against your scope-creep allowance. (For when revisions tip into new work, see the scope creep change order guide.)
What to do when a milestone invoice goes unpaid
The whole point of milestone billing is that you stop work if a milestone goes unpaid. That's the leverage — and it only works if you actually use it.
A reasonable escalation:
- Day 1 past due — short, friendly reminder. "Just a quick check that milestone 2 invoice landed safely with your AP team."
- Day 7 past due — formal reminder citing the contract's payment terms and any late fees that now apply.
- Day 14 past due — pause work. Send written notice that no further work will be performed until the outstanding milestone is paid. Reference the relevant clause in your contract.
- Day 30+ past due — escalate per your contract's dispute process.
The pause-work step is what makes milestone billing structurally different from end-of-project billing. With a single end-of-project invoice, you've already shipped everything before the client decides whether to pay. With milestones, you can stop in the middle without giving up your remaining leverage.
If a milestone payment goes seriously sideways, the broader playbook is the same as any unpaid invoice. The what to do when a client doesn't pay guide covers the longer-tail collection process.
Tax and bookkeeping treatment
A few accounting wrinkles to flag, without giving advice on your specific situation:
- Each milestone invoice is its own taxable event for sales-tax purposes if your jurisdiction taxes the service.
- For US freelancers on cash-basis bookkeeping (the default for most), revenue is recognized when each milestone is paid. For accrual-basis filers, revenue may be recognized at delivery rather than payment. The cash vs. accrual guide walks through the difference.
- The IRS treats freelance income the same regardless of milestone structure — a $12,000 project paid in four installments is reported as $12,000 of self-employment income in the year the cash is received (cash basis).
If your project crosses a calendar year, the milestone structure matters for tax timing. Splitting a December–March project into four milestones can shift income across two tax years; that's not necessarily good or bad, but it's worth being intentional about. Talk to your accountant if the amounts are material.
Tooling: keeping the schedule visible
You don't need expensive software to run milestone billing, but you do need a single source of truth that both sides reference. The minimum kit:
- A signed contract or scope-of-work document that lists all milestones, amounts, deliverables, and acceptance criteria.
- A project tracker (Notion, Trello, a shared Google Doc, or even a pinned email thread) that shows current status against each milestone.
- An invoicing tool — a free invoice generator is plenty for low-volume freelance work, or a paid platform if you're running multiple concurrent projects with recurring milestones.
- A receipts trail. When clients pay, send a receipt so the milestone is closed out cleanly on both sides.
Keep the milestone numbering consistent across all four. Milestone 2 in the contract should equal Milestone 2 in the tracker, the invoice, and the receipt. It sounds obvious, but mismatched numbering between systems is one of the easier ways to lose track of what's been billed and what hasn't.
A simple mental model
The shortest version of all of this: milestone billing turns a single big invoice into a series of small, predictable, defensible ones. Each invoice is tied to a deliverable the client can see and accept; each invoice carries its own due date and payment terms; and each invoice is something you can stop work over if it isn't paid. That's the whole game.
If you've been running fixed-fee projects on "50% upfront, 50% on completion" and getting paid late, the upgrade isn't more aggressive collections — it's more milestones. Three to six clear phases, each with its own invoice, each tied to a deliverable. Cash flow gets steadier almost immediately, and the conversations about "where is my money" get a lot shorter.
This is general information, not tax, legal, or financial advice. For your specific situation, consult a qualified professional.