Published October 27, 2026
Freelance quotes with milestone payments solve the oldest cash flow problem in freelancing: you do the work, the client goes quiet, and the invoice for the whole project sits unpaid while your rent comes due. The fix is not to demand full payment up front, which most clients will refuse. It is to split the fee into stages tied to deliverables, so that at no point has the client received much more work than they have paid for. On a $12,000 website, four milestones of $3,000 each, a deposit, a design approval payment, a beta payment, and a launch payment, cap your unpaid exposure at $3,000. On a 50/50 split, the same project leaves $6,000 exposed for most of its life. On pay at completion, the whole $12,000 rides on one invoice. The total never changed. The risk did.
Most freelance projects work well with three to five milestones. A simple shape is a deposit on signing, a payment at midpoint, and a final payment on delivery. Larger projects earn four or five stages. The deposit deserves its own note: 30 to 40 percent up front is common, and for a new client or a higher risk project, front-loading to 50 percent is reasonable. The principle underneath the percentages is the one to hold onto. Never have more than about a quarter to 40 percent of the fee outstanding at the point of final delivery, because the final payment is the one clients delay, dispute, or forget.
Milestone payments for a freelance quote: deliverables, not dates
This is where most milestone schedules go wrong. A milestone should be a thing the client can see and approve, not a date on a calendar. "Second payment due on the 15th" tells nobody whether the work is ready. "Second payment due when the homepage design is approved" is clear to everyone. Write each milestone into the quote and the agreement in plain words: what you will deliver, what the client needs to approve, and how much becomes payable at that point. When the deliverable is approved, the payment is due, and there is no argument to have, because both sides already agreed on what done looks like for that stage. If the client's feedback is slow, the milestone simply has not been reached yet, and the schedule shifts with theirs, calmly and by the rules you both set.
If you are skimming for the one clause to copy, this is it: the deemed acceptance clause. The most common failure point in milestone contracts is the infinite review loop, where a client never formally approves work and therefore never triggers the invoice. A deemed acceptance clause sets a review window, commonly five business days, after which the work is treated as accepted if no feedback arrived. It shifts the burden of action to the client, and it turns silence from a delay tactic into an approval. Pair it with an objective approval standard where you can: work that meets the written scope, rather than work the client likes. Subjective approval is a high risk clause dressed as a reasonable one.
What about a client who refuses milestone payments entirely? Treat that as information, not as a negotiation to win at any cost. A client who insists on paying 100 percent only on completion is asking you to carry all the financial risk, and for a project over a couple thousand dollars, that is rarely worth it. You can compromise on fewer milestones or a smaller deposit, but not on zero. My own rule: I will not take a project over $5,000 on pay at completion terms from a new client, full stop. Existing clients with a clean payment history are a different case, and I will flex for them, because the risk there is priced by history, not by hope.
What belongs in the quote itself, then, is a short schedule, not an essay: each milestone's deliverable, its approval step, its amount, and its due timing, with the final milestone due in 7 to 14 days rather than net 30, since the work is already delivered by then. Small projects do not need this machinery. A deposit plus a final payment is enough for a short job. The milestone schedule earns its keep once the project runs past a month or past a few thousand dollars, which is exactly when a single unpaid invoice starts to hurt. Build the quote with milestone amounts and deliverables in the Freelance Quote Builder and put the schedule in the quote itself, not in a separate document the client never reads.
Frequently asked questions
How many milestones should a freelance project have?
Most projects work well with three to five milestones: a deposit on signing, one or two mid-project payments, and a final payment on delivery. Too many creates admin overhead, and too few defeats the purpose of staging payments.
What percentage should each milestone be?
A common split is 30 to 40 percent as a deposit, 25 to 30 percent at midpoint, and 25 to 30 percent on delivery. For new clients or higher risk work, front-load more, such as 50 percent up front.
Should milestones be tied to dates or deliverables?
Deliverables. A milestone the client can see and approve, such as homepage design approval, is clear to everyone. A calendar date tells nobody whether the work is ready.
What if a client never approves the work and stalls payment?
A deemed acceptance clause solves this: after a review window, commonly five business days with no feedback, the work is treated as accepted and the invoice is issued.
What if a client refuses milestone payments?
Treat it as a red flag. You can compromise on fewer milestones or a smaller deposit, but a client who insists on paying 100 percent only on completion is asking you to carry all the risk, which is rarely worth it on a large project.
Run your own numbers before you decide.