Milestone Invoices: How to Bill Clients at Every Stage of a Project
Waiting until the end of a long project to invoice is a cash-flow disaster. Milestone billing collects payment at every stage -- here is how to set it up so clients approve it on day one.
On any project that runs longer than a few weeks, billing everything at the end is a gamble. You carry all the costs, you absorb all the risk, and if the client disappears or disputes the work, you have nothing. Milestone billing -- splitting the total fee into payments tied to specific stages of completion -- is the professional standard for a reason: it protects your cash flow without asking the client to pay for work they have not seen yet.
What is milestone billing?
Milestone billing is a payment structure where the total project fee is divided into two or more payments, each due when a defined stage of the work is complete. Unlike hourly billing (which invoices for time regardless of what was delivered) or single-invoice billing (which waits until everything is done), milestone billing ties money to measurable progress.
A typical 3-milestone structure for a GBP 6,000 web project might look like this: 30% deposit (GBP 1,800) before work starts, 40% (GBP 2,400) on delivery of the design mockups, and 30% (GBP 1,800) on site launch. Each payment matches a concrete deliverable that the client can see and approve.
How to choose your milestones
Good milestones are measurable and tied to something the client can verify. Bad milestones are vague or based on time alone. The test: could a third party look at the deliverable and confirm it is done? If yes, it is a workable milestone. If the answer is "well, it depends on how you define done," you need to be more specific.
- Freelance and creative work: Initial concepts delivered and approved; first draft or prototype; final deliverables handed over.
- Construction and trades: Foundation or groundwork complete; structure to lock-up stage; final snag list cleared.
- Consulting and research: Research phase and first report delivered; recommendations presentation; implementation review.
- Software development: Wireframes and technical spec approved; working prototype or MVP; final QA and deployment.
A 60-day project can work well with 3 milestones. A 6-month project might need 5 or 6. As a rule, each milestone should represent roughly equal value (not just equal effort) so neither party is ever significantly overexposed.
How to write a milestone invoice
Each milestone invoice should make it absolutely clear which stage of the project it covers. Include:
- 1The project reference. Quote the project name or reference number on every invoice so there is no confusion about which engagement it belongs to.
- 2The milestone name and description. "Milestone 2 of 3: Design mockups for homepage and 5 inner pages, delivered 20 June 2026." Be specific enough that the client can confirm the work was done.
- 3The amount due for this milestone. State the milestone payment clearly. If you want to, also show the total contract value, the amount invoiced to date, and the amount remaining -- this helps the client plan their budget.
- 4Payment terms. Specify the due date. Net 7 or Net 14 is standard for milestones; Net 30 is common with larger clients. State the terms on every invoice.
- 5A reference to the original agreement. Note the contract or proposal date so there is a paper trail connecting the invoice to the terms both parties agreed.
Getting sign-off before you invoice
Before you send a milestone invoice, get written confirmation from the client that the milestone is complete. An email reply saying "looks great, approved" is sufficient. This matters for two reasons. First, it removes any later dispute about whether the work was accepted. Second, if the client argues that the deliverable was not completed, you have their written approval on record.
For larger projects, include a deemed-approval clause in your contract: something like "if no written feedback is received within 5 business days of delivery, the milestone is considered approved and the invoice becomes due." This prevents a client from sitting on a milestone indefinitely to delay payment.
Milestone billing across industries
In construction and trades, progress billing is standard. Contractors typically link payments to verifiable stages: slab poured, walls up, roof on, fit-out complete. Many residential contracts in Australia require progress payment schedules that are set out in the building contract before work starts.
In freelance and creative work, milestones protect both sides. The client is not asked to pay everything upfront, and the freelancer is not left holding unpaid work. A 40/30/30 split -- deposit, mid-project, delivery -- is the most common structure.
In consulting, milestone billing is often tied to phases: a discovery and scoping phase, an analysis and recommendations phase, and an implementation or follow-on phase. Each phase produces a tangible output (a report, a presentation, a set of recommendations) that the client can evaluate.
Frequently asked questions
How many milestones should a project have?
For most freelance or consulting projects lasting 4-12 weeks, 3 milestones is standard: an upfront deposit, a mid-project payment tied to a key deliverable, and a final payment on completion. For longer projects (3+ months) or construction work, 4-6 milestones is more appropriate. Each milestone should represent real completed work, not just elapsed time.
What is the difference between milestone billing and hourly billing?
Hourly billing charges for time regardless of output -- you invoice for hours worked each week or month. Milestone billing charges for completed stages of work regardless of how long they took. Milestones give the client predictability (they know the total cost) and give you a guaranteed payment each time a stage is done.
Can I change milestone amounts once a project has started?
Only by mutual written agreement. If the project scope changes significantly, a change order signed by both parties can adjust the milestones and amounts. Never unilaterally change a milestone payment mid-project -- it undermines trust and may be unenforceable.
What happens if a client disputes a milestone?
If you have written sign-off from the client (email, message, or signed form), the milestone is approved and payment is due. If the client raises a genuine quality issue, discuss it in writing and agree in writing when it is resolved. A deemed-approval clause in your contract -- where silence for 5 business days counts as acceptance -- prevents open-ended delays.
Should I invoice for expenses at each milestone?
If you have accumulated client-approved expenses during a milestone phase, yes -- add them as a separate itemised line on the milestone invoice with receipts attached. See the guide to <a href="/blog/how-to-add-expenses-to-invoice">adding expenses to an invoice</a> for the UK VAT rules on disbursements and recharges.
Create your invoice now — free
Invoices, receipts, and quotations. Add your logo, apply tax, download a PDF in seconds. No signup.
Open the free generatorKeep reading
How to Make an Invoice: Step-by-Step Guide (2026)
A no-jargon walkthrough of your first invoice: six steps, a worked example with real numbers, and the small mistakes that quietly delay payment.
How to Invoice a Client as a Freelancer
A freelancer's invoicing system that actually gets used: terms before work, hourly vs fixed line items, milestone billing, and a follow-up schedule for late payers.