Milestone payments split the price into a deposit plus payments tied to finished, approved stages. You never pay far ahead of the work, and the developer never works far ahead of being paid.
The split varies from project to project. What matters more than the percentages is how each payment is triggered.
How do milestone payments work?
You pay a deposit to start. After that, each payment is due when a defined stage is finished and you have approved it.
The key is a checkable event. The UK law firm Sprintlaw says in its guide to web design milestone payments (15 October 2026): “A payment trigger describes the precise event that makes the invoice payable.” Its examples include delivering design concepts or completing a staging build. Vague progress does not qualify.
Sprintlaw is a law firm blog, so treat it as general guidance, not legal advice.
Splits differ. One freelance contract template from accounts-os uses 25% on signing, 25% on design approval, 25% on development complete and staging review, and 25% after launch and a 14-day sign-off. That is one illustrative template, not a standard.
Deposits vary too. A Contra guide to web design payment schedules says deposits commonly run from 25% to 50%. That is one source’s range.
How do they protect the client and the developer?
Both sides carry less risk when money and work move in small steps.
For you as the client:
- Limited exposure. You have only paid for work that is already finished and approved.
- Early warning. If a stage goes wrong, you find out at the first milestone, not at the end.
- A way to push back. An unapproved milestone is a clear, polite way to say “this does not match what we agreed”.
For the developer:
- Paid as they go. Cash arrives as work finishes, so a late client cannot leave months of work unpaid.
- A clear finish line. Each stage has an end, so approval cannot drift on indefinitely.
- A reason to pause. If an invoice goes unpaid, stopping work is a fair response, not a threat.
There is an honest downside. The US agency Atomic Object argues in a 2019 article by Brittany Hunter that milestones suit custom software poorly, because “It is nearly impossible to know everything about a software project before it begins.”
That is fair. You can reduce the risk by scoping first, and by handling changes as written change requests rather than informal asks.
How do milestone payments work with us?
We start with a written quote that lists scope, milestones, dates, assumptions and what is not included. Our pricing page shows an example quote with 3 milestones.
| What | Includes | From |
|---|---|---|
| Scoping Sprint | A written scope with milestones and a tailored quote | $150₹2,100 |
| Launch Site | 5 pages, 2 weeks | $600₹15,000 |
| Starter Tool | One data area, logins, one report, one automation, 2 to 4 weeks | $750₹15,000 |
| Starter Portal | Customer login area plus admin side, 4 to 6 weeks | $1,200₹25,000 |
The Scoping Sprint fee comes off the project if you go ahead.
You pay a 30% deposit to begin, and it is credited against the project. The rest is split across milestones. You review each one, then approve it or tell us what does not fit.
We invoice a milestone once you approve it, and payment is due 7 days later. You never pay for work you have rejected. Approved milestones are not refundable.
If a milestone is disputed, we fix anything that does not match the written scope at no cost, and you review again. If it is still disputed, we hold a call within 5 working days.
If a payment is late, we pause work on the next milestone until it is paid. Agreed dates move by the same amount.
A project tracker shows each milestone as approved, waiting on you, or next. Payments go through Razorpay by card, bank transfer and more, and international clients are billed in USD.
You own the code, the domain and your data once paid in full. You also get 30 days of free fixes after handover. Either side can end the agreement in writing. You then pay for approved milestones and work in progress, and you get everything completed so far. See how we work.
How do you check a milestone payment schedule is fair?
Run any schedule through these checks, in order.
- Name the trigger. Each payment should be tied to a specific event, such as an approved design or a staging build you can open.
- Avoid “happy”. Sprintlaw advises against tying payment to the client being happy. Set a review period instead, and say what happens if the client stays silent.
- Check the deposit. The contract should say whether the deposit is refundable, partly refundable or credited against the total.
- Time the final payment. Sprintlaw notes it usually falls before launch, file release or full transfer of rights, so confirm the order.
- Look for a pause clause. Pausing work for non-payment should need written notice that a payment is overdue.
- Avoid vague splits. Sprintlaw’s guide to developer payment terms says a bare “50% upfront, 50% on completion” line invites disputes.
- Check late payment terms. Under GOV.UK rules on charging interest, UK business-to-business late payments carry 8% plus the Bank of England base rate, unless the contract sets another rate.
For what the quote around those payments should show, read what a written quote should include. To compare payment models, see agreed price vs hourly software development.
Get a quote with clear milestones
Tell us what you want built, who will use it and when you need it. We will send a written quote with milestones you can check. Request a quote or book a free 20-minute call.