Milestone Billing for Freelancers: How to Invoice Per Project Phase
Milestone billing means splitting a project into phases and invoicing for each one as it's completed — instead of one big invoice at the end. For any project lasting more than a few weeks, it's the difference between getting paid steadily and financing your client's project for two months. This guide shows how to structure milestones, how much to charge at each stage, how to word each invoice, and what to do when scope changes halfway through.
What milestone billing is (and when to use it)
Milestones are agreed checkpoints in a project, each tied to a deliverable and a payment. A typical web project might be: 30% on kickoff → 40% on design approval → 30% on launch. Each milestone invoice is triggered by completing that phase, not by the calendar.
Use milestone billing when:
- The project lasts more than 3–4 weeks
- The total is large enough that one invoice would strain your cash flow (roughly £1,500+)
- The project has natural phases (design → build → launch; draft → revisions → final)
- You want early warning if a client goes quiet — you find out after phase one, not after six weeks
Stick with simpler billing when:
- The job takes under two weeks — a deposit plus balance is cleaner
- It's ongoing, repeating work — that's retainer invoicing, not milestones
- The client is a trusted repeat who always pays on time — don't add admin for no reason
How to structure milestones: the 3–4 phase rule
Three or four milestones is the sweet spot. Fewer than three and you might as well use a deposit. More than five and the admin of invoicing, chasing, and reconciling starts eating your margin.
The classic 3-milestone split (most projects):
| Milestone | Trigger | Share | |---|---|---| | 1. Kickoff / deposit | Contract signed, work begins | 30–40% | | 2. Mid-project checkpoint | First major deliverable approved (design, draft, prototype) | 30–40% | | 3. Completion | Final delivery and sign-off | 20–30% |
The 4-milestone split (larger projects, £5k+):
| Milestone | Trigger | Share | |---|---|---| | 1. Deposit | Contract signed | 25% | | 2. Phase 1 complete | e.g. designs approved | 25% | | 3. Phase 2 complete | e.g. build finished | 25% | | 4. Launch / handover | Final delivery | 25% |
Weight the early milestones slightly heavier, not lighter. The first two phases carry your discovery, planning, and setup work — and the biggest risk of client ghosting is at the start. A 40/30/30 split protects you better than 25/25/50.
Tie every milestone to a deliverable, never to a date. "£1,200 on design approval" is enforceable; "£1,200 on 1 November" creates arguments when the client delays feedback for three weeks and then disputes the invoice. If you want time-based protection too, add a clause: "Milestones not approved within 10 business days of submission are deemed approved for invoicing purposes."
How to word each milestone invoice
Each milestone gets its own invoice in your normal numbering sequence. The description must answer: which project, which milestone, what's been delivered.
Milestone 1 (kickoff):
"Milestone 1 of 3 — Project kickoff deposit (Quote #Q-2026-014, website redesign). Work commences on receipt."
Milestone 2 (mid-project):
"Milestone 2 of 3 — Homepage and core page designs approved 28 Oct 2026 (Quote #Q-2026-014)."
Milestone 3 (completion):
"Milestone 3 of 3 — Final delivery and site launch completed 18 Nov 2026 (Quote #Q-2026-014). Balance of project now due in full."
Add a progress note on each invoice: "Project total £4,000 · Invoiced to date £2,800 · Remaining £1,200." This single line prevents the most common milestone dispute — the client losing track of what's been paid and what's left.
Build each one with our free invoice generator — same format every time, numbered in sequence, saved as PDF.
Setting milestone amounts: worked example
Say you're quoting a £6,000 brand + website project over 8 weeks:
- Milestone 1 — 40% (£2,400): contract signed. Covers discovery, sitemap, and the risk of taking the booking.
- Milestone 2 — 30% (£1,800): brand concepts and homepage design approved. The client has seen real work and committed further.
- Milestone 3 — 30% (£1,800): site built, tested, launched. Final payment on handover.
Your maximum exposure at any point is one milestone's worth of unpaid work — and after milestone 1, you've already banked £2,400 before delivering anything substantial. Compare that to a single £6,000 invoice at week 8: two months of work financed by you, with one client holding all the leverage.
Payment terms per milestone: keep them short. Net 7 or due-on-receipt for milestones is standard — the amounts are smaller than a full project invoice, and the next phase of work shouldn't start until the previous milestone is paid. Many freelancers make this explicit: "Work on Phase 2 begins on receipt of the Milestone 1 payment." It turns your payment terms into project scheduling, which clients respect far more than a late fee clause.
Handling scope changes mid-project
Scope creep is where milestone billing either shines or collapses, depending on one thing: whether you defined each milestone's deliverables in writing before starting.
The rule: a milestone covers exactly what the contract says it covers. Anything else is a change request, priced and invoiced separately — not folded into the next milestone.
Practical playbook:
- Define deliverables per milestone in the quote. "Milestone 2: homepage + up to 5 core page designs, 2 revision rounds." Numbers kill arguments.
- When new work appears, name it immediately. "That's outside the Milestone 2 scope — I can add it as a change request for £400, or we can swap it for one of the planned pages." Say it in the moment, not at invoicing time.
- Invoice change requests as separate line items on the next milestone invoice, clearly labelled "Change request CR-02: additional landing page — £400." Never silently inflate a milestone amount.
- If scope shrinks, reduce the milestone honestly. Clients remember fairness, and a freelancer who adjusts invoices downward earns the kind of trust that turns into retainers.
For a deeper treatment of the quoting side, see how to quote a project — good milestones start with a good quote.
What if a client stalls a milestone?
The client who won't approve Milestone 2 is the client who'd have ghosted your final invoice. Milestones surface this early, which is the point. Here's the escalation:
- Day 1–3 after submission: friendly nudge — "Just checking you received the designs. Any feedback?"
- Day 7: firmer — "Per our agreement, milestones unapproved after 10 business days are invoiced as approved. Happy to discuss any changes first."
- Day 10: invoice it. Then pause work: "I'll pick Phase 3 back up as soon as Milestone 2 is settled."
- Day 10+ unpaid: you're now in standard late-payment territory — reminders, then the escalation ladder in how to chase late payments.
The pause is the key move. Continuing to work while a milestone goes unpaid trains the client that your invoices are optional. Stopping — politely, contractually — trains them that milestones are gates.
Milestone billing vs deposits vs retainers
These get confused constantly. Quick distinction:
- Deposit: one upfront payment before work starts, balance at the end. Best for short projects. See how to invoice for a deposit.
- Milestone billing: several payments tied to project phases. Best for projects over ~3 weeks with clear phases.
- Retainer: recurring payment for ongoing availability or regular work. Best for continuous relationships. See retainer invoicing.
A project can graduate through them: deposit → milestones → retainer, as a one-off client becomes a regular.
FAQ
How many milestones should a project have?
Three to four for most projects. Two is just a deposit with extra steps; five or more creates invoicing admin that eats your margin. Scale with project size: £2k project → 3 milestones; £10k+ → 4.
Should milestones be equal amounts?
They can be, but front-loading slightly (e.g. 40/30/30) is smarter — your early phases carry discovery and setup costs, and early money de-risks the whole project. Avoid back-loading (25/25/50), which leaves your biggest invoice exposed at the end.
What if the project has no natural phases?
Create them around deliverables anyway: research/plan → first draft → revisions → final delivery works for almost any knowledge work. If you genuinely can't define phases, use time-based billing (weekly/monthly invoices) instead — but write the schedule into the contract.
Do I charge VAT/GST on each milestone invoice?
Yes — each milestone invoice is a normal invoice for tax purposes. In the UK, the tax point is generally the earlier of the invoice date and payment receipt, so invoice promptly when the milestone is reached. See our guides to UK VAT invoices and Australian tax invoices.
Can I combine milestones with a late fee policy?
Absolutely — and you should. State your late fee terms once in the contract (see invoice payment terms and late fees on invoices), and they apply to every milestone invoice automatically. Short milestone payment windows plus a pause-on-non-payment clause are usually more effective than fees alone.