Somewhere around a third to a half is normal for a small website, and the amount matters far less than what you have in writing before you send it. An advance against a written scope and date is reasonable. The same amount against a WhatsApp conversation is where most losses happen.
Owners search “website ke liye kitna advance dena chahiye” and expect a number. The number is the easy part.
The moment it happens
How much advance is safe to pay a website developer? You’re usually deciding this with your thumb over the UPI confirm button, at the end of a conversation that has gone well, with no document in front of you.
Complaint records show what the bad version looks like — and it’s rarely a large sum. Buyers describe paying ₹2,000 as a “booking amount”, then being asked for ₹3,000 more before work appeared. Others describe advances of ₹2,000 to ₹8,000 that were never refunded and never worked against. The risk isn’t concentrated in big projects; it’s concentrated in projects where nothing was written down.
What’s normal, and why
| Structure | How common | Reasonable? |
|---|---|---|
| 100% upfront | Seen at the cheapest tier | No. There’s no reason to carry all the risk |
| 50% start, 50% at go-live | The common standard | Yes, if scope and date are written |
| 30/40/30 across start, design approval, launch | Typical for larger projects | Yes, and better for you |
| Small booking, then staged | Fine in principle | Watch for the second ask arriving before any work |
| 100% on completion | Occasionally demanded by burned buyers | Sounds safest; tends to repel the vendors you’d want |
That last row deserves explanation, because it’s counterintuitive. Buyers who have been cheated often insist on paying everything at the end. Serious vendors decline that — they’ve been burned too, by clients who vanish or renegotiate at handover. So the term filters out the careful providers and leaves whoever is desperate enough to accept it. You end up selecting for the risk you were trying to avoid.
Notably, buyers who have actually been through a failure tend to prescribe something more balanced. One wrote publicly, after a bad project: pay a small amount to begin, hold the bulk until the work is complete, and sign a contract. That’s milestone payment plus a written scope — the same structure a good vendor would propose.
The four things to have before any money moves
The advance is safe in proportion to what it’s secured against:
- A one-page scope. Number of pages, features, who writes the text, how many revision rounds, what’s excluded.
- A delivery date in writing — plus the date your content is due, so the clock is explicit on both sides.
- The final GST-inclusive amount, so there’s no arithmetic surprise at invoice time.
- Domain registered in your name, from the start. This is the one that limits how bad a failure can get: if the project dies, you keep your business name and can hand everything to someone else.
If a vendor won’t provide the first three in a message, that’s information. You don’t need a lawyer — a WhatsApp message listing all four, which they confirm, is meaningfully stronger than a conversation.
Practical details that reduce risk
- Pay a company account over a personal UPI where possible. It doesn’t guarantee anything, but it gives you a name on a bank record and a GST invoice to reference in a dispute.
- Ask for an invoice for the advance, not just an acknowledgment.
- Keep the payment reference number with the quote in one folder. Every recovery route later depends on it.
- Don’t pay the second instalment until you’ve seen the first deliverable on a link you can open. Not a screenshot.
What to do this week
- Ask your chosen vendor for the four items above in one message.
- Agree the split before discussing the amount. Structure first, then price.
- Register the domain yourself, or confirm in writing it will be in your name.
- Pay the advance to a business account where possible and keep the reference number.
- Diarise the delivery date and the content-due date the moment you pay.
If you want it done the certain way
We work on a written date with a refund behind it, publish our prices so the final number is never a surprise, and register the domain in your name before anything else. If a vendor closer to you or cheaper than us offers you all four of those things, that’s a fair deal too. WhatsApp us; we reply in about five minutes between 9am and 7pm.
Related reading
- Does your web developer have a refund policy?
- Did they put your deadline in writing?
- Developer took the advance and disappeared: recovery steps
- Paying by personal UPI vs a company account: does it matter?
FAQ
Is 50% advance normal for a website in India?
Yes, it’s the common standard for small projects, and reasonable when scope, final price and delivery date are in writing. Anything close to 100% upfront leaves you carrying all the risk with no leverage.
Should I ever pay the full amount upfront?
There’s rarely a good reason. If a vendor requires it, ask what protects you if delivery fails — and treat a vague answer as your answer.
What if the developer asks for more money mid-project?
Ask what changed against the written scope. Additional work outside the agreed list can fairly cost more; the same work costing more is a warning sign that appears repeatedly in buyer complaints.
