Most small website quotes in India contain no refund terms at all, which means the answer to “what if it’s late or wrong” is decided after the problem rather than before it. Asking the question before paying costs nothing and changes who carries the risk.
Buyers usually think to ask this in the wrong order — after the advance, when the leverage has already moved. “Website time pe nahi bani to paisa wapas milega?” is a reasonable question at the quote stage and an awkward one at week six.
The moment it happens
Does the website company have a refund policy? Ask before you pay — because the version of this conversation that happens later goes differently.
Complaint records show how it plays out. One buyer described being told at the sale that content would be provided and that if he wasn’t satisfied the amount would be refunded immediately; when neither happened, the refund was refused. Another spent a month sending reminders about ₹8,000, escalating through five follow-up emails, and was still waiting.
The pattern isn’t that refunds are always refused. It’s that with nothing written, a refund becomes a matter of goodwill at exactly the moment goodwill has run out.
Why almost nobody offers one
Scope is undefined, so “done” is arguable. A vendor can’t safely promise a refund against a deliverable nobody wrote down. This is a real constraint, not just evasion — and it’s why refund terms and scope documents arrive together or not at all.
Content delays are genuinely the client’s side sometimes. A vendor who promises delivery in seven days can’t control a client who sends photos in week three. Any workable refund term has to account for that, which most vendors find easier to avoid than to draft.
The advance is the vendor’s protection. In a market where clients also disappear, or negotiate the final payment down, the advance is the only security the vendor has. Refunding it removes that.
Nobody asks. In the budget tier, the buyer’s questions are almost always about price and time. Refund terms rarely come up until they’re needed.
What a workable refund term actually looks like
A refund promise that survives contact with a real project is narrow and conditional. Vague generosity (“full refund if not satisfied”) is either untrue or unworkable — taste disputes have no end point.
| Term | Weak version | Workable version |
|---|---|---|
| Trigger | “If you’re not satisfied” | “If the site isn’t live by [date], given content received by [date]” |
| Amount | Unstated | The advance, or a stated portion |
| Client obligation | None mentioned | Content and approvals within stated days |
| What happens to work done | Unstated | Files handed over, or not — say which |
| Timeline to pay | “We’ll process it” | Within 7 working days of the trigger |
Notice what makes it workable: the trigger is a date and a fact, not a feeling. That’s the version a serious vendor can actually offer, and the version you can actually enforce.
The better question, if refunds are refused
Many decent vendors won’t offer refunds, and that alone isn’t a red flag. In that case, shift to structure — which protects you in advance rather than compensating you afterwards:
- Milestone payments. Something at start, something at design approval, the balance at go-live. Burned buyers on public forums prescribe almost exactly this: pay a small amount to begin, hold the bulk until completion, and sign something.
- A written deadline with a stated consequence — even if the consequence isn’t money. “Delivery by the 20th; if it slips, the remaining balance reduces by X” is enforceable in practice because it’s specific.
- A one-page scope list. Refunds are unenforceable without it; so are arguments about what was promised.
- Domain and hosting in your name from day one. This is the quiet one. If you own the accounts, a failed project costs you the advance, not your business name.
Payment terms worth avoiding in both directions: 100% upfront, for obvious reasons; and 100% on completion, which sounds safest but tends to repel the vendors you’d actually want, leaving you with whoever is desperate enough to accept it.
What to do this week
- Ask your shortlisted vendors one question in writing: “If the site isn’t live by the agreed date, what happens to the advance?” The answers will separate them faster than price comparison.
- Ask for the delivery date in writing, with the date your content is due alongside it.
- Request a one-page scope list before paying anything — pages, features, who writes text, revision rounds.
- Structure the money in at least two parts.
- Register the domain in your own account, whoever builds the site.
If you want it done the certain way
We put the delivery date in writing with a refund behind it, publish the price so there’s nothing to renegotiate, and register the domain and logins in your name. If your project genuinely needs a different structure than ours — a smaller scope, or a vendor closer to you — we’ll say so. WhatsApp us; we reply in about five minutes between 9am and 7pm.
Related reading
- How much advance is safe to pay a web developer?
- Did they put your deadline in writing?
- Developer took the advance and disappeared: recovery steps
- Do you need a written agreement for a website project?
FAQ
Is it unreasonable to ask a web developer for a refund clause?
No, and how they respond is informative. Many will decline while offering milestone payments instead, which is a fair answer. A vendor who won’t discuss either the refund or the structure is telling you how a dispute would go.
Can I get a refund if the website is late but nearly finished?
Usually not in full, and often not at all without written terms. This is why a stated consequence for lateness — a reduced balance, a partial refund, a hard handover date — is more practical than an all-or-nothing refund promise.
What if the delay is because I didn’t send content?
Then the refund claim generally fails, and fairly. Any written deadline should include the date your content was due, so both sides know where the clock stopped.
