Getting paid

How to structure milestone payments on freelance projects

What to tie payments to, how many milestones to use, and the structure that protects your cashflow on projects longer than a month.

·7 min read·Getting paid

Quick answer

On freelance projects longer than 4-6 weeks, split the fee into milestone payments tied to deliverables, not dates. A typical structure: 30-50% deposit upfront, 25-40% at a clear midpoint deliverable, balance on final delivery. Tie milestones to client-acceptance moments, not internal work-completion moments — that's what makes them robust under scope drift.

Milestone payments are how freelancers stay solvent on long projects. A single deposit-then-balance structure works fine for projects under a month; past that, you're carrying too much risk if the client stalls or disappears. This guide is about how to structure milestones — what to tie them to, how many to use, and the language that prevents the common dispute of 'we're not at that milestone yet.'

When to use milestone payments instead of just deposit-and-balance

Use milestone payments any time the project is over four to six weeks of work, or when the total fee is large enough that you can't comfortably finance the full project on your deposit alone. Below that threshold, a 50% deposit and 50% balance on completion is fine. Above it, the gap between deposit and final payment becomes a meaningful financial risk — clients can stall, scope can drift, and you can find yourself carrying weeks of unpaid work. Milestones convert one large risk into several smaller ones.

Tie milestones to deliverables, not dates

The single most important rule: milestones should trigger on deliverables, not on calendar dates. 'Milestone 2 invoiced on June 15' is a hospital pass — if the project is delayed (your fault or the client's), you have to renegotiate. 'Milestone 2 invoiced on delivery of [specific deliverable]' is robust — the trigger is unambiguous and tied to actual progress. Date-based milestones also create perverse incentives: you might be tempted to push thin work to hit a milestone date, or skip work to delay one.

A standard 4-milestone structure

For projects in the $10k-$50k range, the structure that works for most freelancers: 30% deposit on signing, 25% on delivery of first major draft, 25% on client approval of final draft, 20% on final handoff. This loads the early payments enough to fund your work, the middle payments to maintain client engagement, and the final payment to ensure they take handoff seriously. Adjust the percentages based on your project, but keep the structure: front-loaded enough to be safe, back-loaded enough to keep skin in the game.

Define the trigger condition precisely

Each milestone needs a trigger condition specific enough that no one can argue it. Bad: 'Milestone 2 invoiced when the design is done.' Better: 'Milestone 2 invoiced upon delivery of the first complete design draft to the client (one round of revisions included before milestone 3).' Best: 'Milestone 2 invoiced upon delivery of the first complete design draft to the client. Client review and feedback expected within 7 business days. Milestone 3 begins on receipt of client feedback.' This level of specificity feels excessive in the contract; it's exactly what you want when there's a disagreement.

What to do when a milestone gets stuck

Sometimes a project hits a milestone and the client goes quiet — they're slow to review, slow to approve, or busy with other priorities. Two moves: first, send the milestone invoice anyway. The contract terms should specify that delivery (not client acceptance) triggers the invoice; once you've delivered, you're owed. Second, communicate the impact: 'I've delivered [deliverable] for milestone 2 — invoice attached. The next phase work begins once your feedback is back; let me know if anything's blocking it on your end.' This prevents both the cash gap and the project drift.

Final milestone — get it right

The final milestone is the most often-disputed because the client has the deliverable and you're asking for the last payment. Two protections: first, structure ownership so it transfers only on final payment ('Final IP transfer occurs upon receipt of final payment'). Second, hold a piece of the deliverable — like the source files, the editable version, or admin access — until final payment. This is not adversarial; it's standard, it's expected, and it's what protects the freelance economy from clients who would otherwise treat 'final 20%' as optional.

Key takeaway

Milestones should be tied to deliverables, not dates. They should trigger on delivery, not client acceptance. And the final milestone should release ownership and source files only on receipt — that's the structure that holds up under real-world client behaviour.

Send milestone invoices automatically

Set up milestone invoices in kinako tied to your project, send them with one click when you hit each delivery, and watch the deposit and balance flow into your revenue dashboard.

Get started free

Free plan · No credit card required

Frequently asked questions

How many milestones should a freelance project have?

For projects in the $10k-$50k range, 3-4 milestones is typical: deposit, midpoint, near-final, final. Below that range, 2 milestones (deposit and balance) is usually fine. Above it, 4-6 milestones can make sense — but past six, you're spending more time invoicing than working. Optimise for clarity over quantity.

Can I tie milestones to client-acceptance instead of delivery?

It's risky. If your milestone triggers on 'client approves the design,' a slow or unresponsive client can keep you waiting weeks for payment on work you've already finished. Trigger milestones on your delivery, not their acceptance — and add a separate clause about revision rounds and timing.

What's a typical deposit percentage for milestone projects?

30-50% upfront. The lower end (30%) is appropriate for very long projects where you'll have multiple subsequent milestones to backstop you. The higher end (50%) makes sense for shorter or higher-risk projects, or for new clients without an established payment history with you.

What if the client wants to negotiate the milestone structure?

Some negotiation is normal — clients sometimes want a smaller deposit, or to push more of the fee to the back end. Within reason, accommodate it; outside of reason, hold firm. A useful rule: never agree to a structure where you'd be doing more than two weeks of unpaid work between milestones. Past that, the financing risk is too one-sided.

Related templates

Graphic Designer contract template →Consultant proposal template →

Built for

For graphic designers →For consultants →For web designers & developers →

Keep reading

Getting paid · 7 min

How to ask a freelance client for a deposit

When to ask, how much to ask for, and what to write — with email scripts you can paste and adjust.

Contracts · 9 min

How to write a freelance contract that actually protects you

The clauses, structure, and language that prevent the disputes most freelancers learn about the hard way.

Getting paid · 8 min

Your client isn't paying. Here's exactly what to do.

An escalating playbook that recovers most unpaid invoices without burning the relationship — and what to do when it can't be saved.