How to Structure Milestone Payments for Freelance Work
Tie each payment to an approved deliverable so you are never far ahead of what you have been paid.
The Delivvo team· June 2, 2026 9 min read
The most stressful position a freelancer can be in is finishing a project before getting paid for it. You have delivered the work, the file is sitting in the client's inbox, and now your only leverage is a polite reminder and the hope that the invoice gets approved. Milestone payments exist to make sure you never end up there. The principle is simple: structure the engagement so that the work you have done is always roughly equal to the money you have received, at every point in the project.
Getting paid late is not a rare misfortune you can plan around. An analysis of three years of freelance invoicing data by Bonsai found that 29 percent of invoices were paid at least a day late, with female freelancers paid late 31 percent of the time against 24 percent for men. Among small businesses more broadly, UK government figures show that 52 percent of small firms suffer late payments every quarter. When that much of your income arrives slowly, how you stage your payments stops being an accounting detail and becomes the difference between a stable month and a frightening one.
Why payment structure is a survival skill, not paperwork
Late payment is not just an annoyance. The same UK government analysis ties slow payment to roughly 50,000 business closures a year and an average cost of around 22,000 pounds per affected business. A separate government statement on its late-payment crackdown put the toll at 38 businesses closing every single day, at a cost of about 11 billion pounds a year to the wider economy. These are organisations with more cushion than a single freelancer has.
Keep reading
Demand for faster pay reflects this pressure. Payment research from PYMNTS Intelligence reports that one in three millennials now relies on gig payouts as primary income, which makes the timing of each payment a household concern rather than a business preference. A good payment structure does not chase money faster after the fact. It arranges the project so less of your money is ever at risk in the first place.
Comparing the four common structures
There are four payment shapes you will meet again and again. Each fits a different size and trust level of engagement.
Deposit-only means you take a percentage up front, often 30 to 50 percent, and the balance on completion. It is simple and works for short projects, but it leaves a large slice of your fee exposed until the very end. On anything that runs more than a couple of weeks, the unpaid balance grows uncomfortably large.
The 50/50 split takes half before you begin and half on delivery. It is the workhorse for small to mid-sized fixed projects. It is fair, easy to explain, and keeps you close to even through the middle of the work. Its weakness shows on longer projects, where "delivery" might be two months away and half your fee waits the entire time.
Milestone payments break the fee into several stages, each released when a specific deliverable is approved. This is the structure that keeps your paid amount tracking your completed work most closely. It takes more thought to set up, but on any project lasting more than a few weeks it is the safest arrangement for both sides, because the client also only pays for stages they have seen and accepted.
Net-30 means you invoice on completion and the client pays within thirty days. It is common with larger companies and sometimes non-negotiable. The risk is obvious: you finish, then wait a month with no leverage. If a client insists on net-30, pair it with a healthy deposit so you are not financing the entire project on their behalf.
For most freelance work above a small fixed fee, milestones win. They are the only structure where your exposure stays roughly constant instead of ballooning toward the deadline.
A freelancer mapping out project stages and payments at a desk
Three example schedules
Abstract advice is easy to nod at and hard to use, so here are three concrete schedules you can adapt.
A website build splits cleanly into stages. A common structure is 30 percent on signing to confirm the booking and cover early discovery, 30 percent on approval of the design mockups, 30 percent on a working build delivered to staging, and the final 10 percent on launch. Each payment lines up with something the client can see and approve. You are never more than one stage ahead of the money, and the client never pays for a phase they have not reviewed.
A brand identity project benefits from a stage that protects your concept work. Try 50 percent on signing, 25 percent on approval of the chosen logo direction, and 25 percent on delivery of the final files and brand guidelines. The heavy front-loading reflects the reality that the hardest creative thinking happens early, long before any final asset exists.
A content retainer works differently because it repeats. The cleanest arrangement is payment in advance for each cycle: the client pays at the start of the month, and you deliver that month's agreed work against it. This flips the usual risk. You are paid before you produce rather than after, which suits an ongoing relationship where trust is already established and the monthly scope is fixed.
Across all three, notice the pattern. Money is released against a visible, approved checkpoint, and the first payment always lands before substantial work begins. If you have not yet built the habit of taking money up front, the case for learning to collect a deposit before a project is the foundation everything else here sits on.
Acceptance gates and why payment attaches to an approved deliverable
A milestone is only as strong as its definition of "done." This is where acceptance gates come in. An acceptance gate is the agreed condition that closes one stage and releases its payment. Without it, a milestone becomes a vague point in time that the client can keep pushing back by withholding approval while still receiving work.
Attach each payment to a named, reviewable deliverable, not to a date or an effort. "Payment due on approval of the homepage design" is an acceptance gate. "Payment due at the midpoint of the project" is not, because the midpoint is a feeling, not a thing anyone can point at. The named deliverable gives both sides a clear, shared signal: the work for this stage is here, it meets the brief, and the payment that was tied to it is now due.
This protects the client too, which is what makes it easy to propose. They are not paying for promises or hours logged. They are paying for an asset they have seen and accepted. That fairness is exactly why the structure holds up in practice. It is hard to argue with a payment that is owed because a specific, agreed thing was delivered and approved.
To make acceptance gates work, write them into your project terms before the first invoice goes out. A clear statement of work is the right home for them, listing each milestone, the deliverable that closes it, and the amount it releases. When the gate is written down in advance, approval becomes a simple checkbox rather than a negotiation, and the matching payment follows without friction.
A short note on overdue invoices
Even a well-staged project occasionally produces a late invoice. The data says you should expect it: the FSB Late Payments Report found that 61 percent of small businesses say late payments hold them back, and nearly a quarter receive payments up to 60 days late. Milestones reduce your exposure, but they do not eliminate it.
Two habits help. First, set clear payment terms on every invoice, including a due date and, where appropriate, a late fee, so "when" is never ambiguous. Second, keep the next stage gated. If a milestone payment is overdue, the most natural and least confrontational leverage you have is simply not starting the next stage until the current one clears. Because you structured the work in stages, pausing is a normal contractual step rather than a standoff.
FAQ
What percentage should I take as a deposit?
For most freelance projects, 30 to 50 percent up front is standard. Shorter projects can sit at the higher end, since the whole engagement finishes quickly and the deposit covers most of the risk. On longer milestone projects, a 30 percent first payment is common because later stages will cover the rest as they are approved. The right figure is whatever keeps your unpaid balance modest at every point.
How many milestones should a project have?
Enough that you are never far ahead of the money, but not so many that invoicing becomes a chore. Three to five milestones suit most projects of a few weeks to a few months. Each one should map to a deliverable the client can clearly see and approve. If two milestones would close on the same checkpoint, merge them; if a single stage spans many weeks of unpaid work, split it.
What is an acceptance gate?
An acceptance gate is the agreed condition that closes a milestone and releases its payment, tied to a specific reviewable deliverable rather than a date or a number of hours. For example, "payment due on approval of the design mockups" is an acceptance gate. It protects both sides, because the client pays only for an asset they have seen and accepted, and you get a clear, defensible trigger for the invoice.
Should I keep working if a milestone payment is late?
Generally no. The cleanest leverage a staged project gives you is the ability to pause before the next stage until the current payment clears. This is not a punishment; it is the structure working as intended. Make this explicit in your terms so that pausing reads as a normal contractual step rather than a sudden escalation, and most clients will resolve the payment quickly.
Bringing it together
Milestone payments come down to one rule: never let the work you have delivered run far ahead of the money you have received. Choose a structure that fits the project's length, tie each payment to a deliverable the client approves, and write the gates into your terms before you start. Do that, and the anxious wait at the end of a project mostly disappears, because there is no large unpaid balance left to wait on.
The structure is easier to hold when the deliverable, the approval, and the payment all live in one place, so a client accepts a stage and the matching invoice is right there beside it. That single, connected flow is the idea behind a client portal like Delivvo. Stage the work, gate each payment, and let approval and payment travel together instead of chasing each other by email.
