Fair Payment Terms for a Website Project: Advances, Milestones and Refunds

On this page

1. Why the payment structure matters
2. The advance: what it's for
3. Tie milestones to deliverables, not dates
4. Scope changes: agree the process upfront
5. Delays and paused projects
6. Final payment and handover
7. If the project stops: refunds and work done
8. Put it in writing

Many disagreements in website projects come down to money: when it's due, what it covers and what happens when plans change. Fair payment terms protect both sides. You don't pay for work you haven't seen, and your developer isn't left unpaid for work they've done. Here's how to structure payments for a website project, whoever you hire.

Why the payment structure matters

How you pay matters as much as how much. A good payment structure:

• Links each payment to something you can see and check
• Keeps both sides committed until the project is finished
• Makes it clear what happens when scope, timelines or plans change

It also depends on how the project is priced. The terms below assume a fixed price for a defined scope, the most common arrangement for new websites; see fixed price vs hourly billing for the alternatives.

The advance: what it's for

Most developers ask for an advance before starting. That's reasonable: it confirms your commitment, reserves time in their schedule and covers early work such as planning and design. In general terms:

• The advance should be a portion of the total, not most of it
• For small projects, splitting the fee into two parts, at the start and at launch, is common
• Larger projects usually spread payments across several milestones
• Being asked for the full amount upfront, before anything is designed, is a warning sign

Ask for an invoice or receipt for every payment, whether you pay by bank transfer or UPI.

Tie milestones to deliverables, not dates

Milestone payments work best when each one falls due after something specific is delivered and approved, rather than on a calendar date. A typical structure looks like this:

Stage	What you should be able to check	Payment
Agreement	Written scope, timeline and price	Advance
Design approved	Homepage and key page designs, revised as agreed	Milestone payment
Development complete	A working site on a staging link you can test on your phone	Milestone payment
Launch and handover	Live site, logins and files received	Final payment

The number of stages depends on the size of the project. What matters is that each milestone has a clear definition of "done" that both sides agree before work starts.

Scope changes: agree the process upfront

Ideas change once you see your website taking shape. That's normal, but changes to scope should affect the price or timeline in a way you've both agreed. A fair process is:

1. You request the change in writing
2. The developer confirms whether it's in scope and, if not, quotes the cost and any effect on the timeline
3. You approve before the work begins
4. The extra amount is added to the next milestone or invoiced separately

Small tweaks within the agreed revision rounds shouldn't cost extra. New pages, new features or a change of direction usually do.

Delays and paused projects

Projects often stall while waiting for content, photos or feedback from the client. Agree in advance what happens if that occurs: for example, that a milestone becomes payable once the developer's part is complete, or that the project can be paused and rescheduled after an agreed period without a response. Equally, if the developer repeatedly misses agreed dates without good reason, you should be able to raise it and, in serious cases, end the project under the terms below.

Final payment and handover

The final payment is usually due when the website is live and working as agreed. In return, you should receive everything you need to own and run it: administrator access, domain and hosting access, licences, backups and short documentation. The website handover checklist lists what to expect.

Many developers hand over remaining files and access once the final payment clears, which is fair, provided the domain and hosting were registered in your name from the start. Also agree a short bug-fix period after launch, so genuine defects are fixed without a new invoice.

If the project stops: refunds and work done

Sometimes a project ends early. Budgets change, priorities shift or the working relationship breaks down. Fair terms usually say:

• You pay for work completed up to that point, measured against the milestones
• If the advance covered work that hasn't been done, an agreed part is refunded
• You receive the work you've paid for, such as designs and files
• Either side gives written notice before ending the agreement

Without written terms, these situations quickly become arguments. If the amounts involved are significant, ask a lawyer to review the agreement; this article isn't legal advice.

Put it in writing

A formal contract is ideal, but even an email confirmed by both sides is far better than a verbal agreement. It should record:

• The total price, what it includes and whether GST applies (check with your CA if unsure)
• Each milestone, its deliverable and the amount due
• How scope changes and delays are handled
• Refund and cancellation terms
• When ownership and access are handed over
• For overseas clients, the currency and who pays bank or transfer charges

Payment terms are one part of a wider agreement; the website design contract checklist covers the rest.

Planning a new website and want a clear scope with milestone-based payments from day one? See WordPress website development.