A fair website payment schedule has a small advance, two or three payments tied to things you can actually see and check, and a final payment that's released only after the site is live and everything has been handed over to you. Nobody should be paid most of the money before you've seen real work, and nobody should be expected to build the whole thing on credit either.
In practice that means you pay something to start, then pay as you approve the design, then the working staging site, then launch. Each stage has a clear "done" condition written into the contract. If a quote asks for most of the money upfront, or has no stages at all, push back before you sign.
Why the advance should be a minority of the total
The advance exists to show you're serious and to cover the agency's early time: discovery calls, sitemap, content planning and the first design work. It isn't meant to fund the whole project.
If you pay most of the money upfront, you've lost most of your leverage. If the agency goes quiet, misses dates or delivers something weak, there isn't much left to hold back. The opposite is unfair too. If you ask for zero advance, the agency carries all the risk of a client who disappears after seeing the designs. A minority advance, often around a third or less, splits that risk sensibly.
Before you agree on any split, know roughly what the total should be. Our guide to website development cost in India covers what drives the number. A schedule only protects you if the total it's dividing up is reasonable to begin with.
A few things to check on the advance invoice:
- It names the project and refers to the signed proposal or contract.
- If the agency is GST-registered, GST on IT services is 18% and should be shown separately, not hidden inside the figure.
- The contract says what happens to the advance if either side cancels before design approval.
Milestones tied to things you can inspect: design, staging site, launch
A good milestone is something you can open, click and say yes or no to. "Development 50% complete" fails that test because you can't verify it. "Homepage and inner page designs approved in Figma" passes it.
Here's an example of how a schedule might be laid out. The percentages are illustrative, not a standard you have to follow:
| StageWhat you inspectExample share | ||
| Signing | Signed proposal with scope, sitemap and timeline | 30% |
| Design approval | Designs for the homepage and key inner pages, desktop and mobile | 30% |
| Staging site | A working site on a test URL with real content, forms and integrations | 30% |
| Launch and handover | Live site on your domain, plus all access and files | 10% |
Design
Approve designs for mobile as well as desktop. Most of your visitors will be on a phone, and a mobile layout that's "to be adapted later" usually gets less attention than it should. Your approval should be by email so there's a record of what you signed off.
Staging site
This is where most problems show up, so take it seriously. Submit every form and check the email actually arrives. Click every menu link. Open it on a cheap Android phone, not just your laptop. If there's a payment gateway or WhatsApp button, test it. The contract should say the staging payment is due once the agreed pages and functions work, not once the agency says it's ready.
Launch
Launch means the site is live on your domain with SSL, redirects from any old URLs in place, and analytics and Google Search Console set up. A site sitting on the agency's server with your domain pointed at it is live, but it isn't handed over yet. That's the next section.
What should be handed over before the final payment
The last payment is your leverage for getting everything you've paid for. Keep it until you have these:
- Domain access. The domain should be registered in your name, on your registrar account. We regularly meet business owners whose domain is sitting in a former agency's account, and getting it back can take weeks.
- Hosting access. Either the hosting is in your account, or you have full control panel login and it's written down who pays the renewal.
- Admin login to the CMS with full administrator rights, not an editor role.
- Source files and code. The theme or code in a Git repository you can access, plus design files.
- Licence details. Any paid plugins, themes or fonts, and whose name the licences are under. If they're under the agency's licence, they may stop updating when you part ways.
- Third-party accounts. Google Analytics, Search Console, Tag Manager, Google Business Profile, email sending services. You should be the owner, with the agency added as a user.
- A short handover document listing all of the above, how to make basic edits and where backups are kept.
Once these are in place and checked, pay promptly. Holding money back after the work is properly finished is how good agencies stop wanting to work with you.
How change requests should be priced and approved in writing
Almost every website project hits a "can we also add..." moment. That's normal. What causes disputes is when nobody agreed how those requests would be handled.
The proposal should define scope tightly: number of pages, named features, number of design revision rounds, and what counts as a revision versus a new request. Changing the colour of a button is a revision. Adding a booking system is a new feature.
For anything outside scope, the process should be:
- You describe the change in writing, by email or in the project tool.
- The agency replies with the cost, either as fixed price or hours at a stated hourly rate, and the effect on the launch date.
- You approve it in writing before any work starts.
- It's billed separately or added to the next milestone invoice as its own line.
Ask for the hourly rate for extra work to be written into the original contract so you're not negotiating it in the middle of the project. And watch your own behaviour here. Constant small additions add up, and they also push the launch date back, which delays the milestone payments the agency is waiting on. That's a reliable way to sour a project that was going well.
Practical advice before you sign
Don't over-engineer this for a small job. If you're getting a simple five-page brochure site built on a theme, a two-part split, an advance and a balance on launch, is perfectly reasonable as long as domain and admin access are in your name. Four milestones for a small project just creates admin for both sides.
For bigger builds, such as ecommerce, custom features or integrations with a CRM, insist on inspectable milestones and a proper handover list. Be wary of any provider who resists putting the schedule in writing. And if the cheapest quote comes with most of the payment upfront and no staging stage, that's usually a sign you'll be paying for it later in a different way.
If you'd like a rough figure to plan around, try the pricing calculator.
















