Three things should exist the moment money leaves your account: an invoice, a written scope, and a written confirmation of the payment terms — and all three can be WhatsApp messages. Most small website projects have none of them, which is why most disputes come down to what each side remembers.
The moment it happens
What paper should your website advance actually buy you is a question that only becomes urgent later — when a vendor has gone quiet and all you hold is a UPI receipt for ₹18,000.
That receipt proves money left your account. It doesn’t say what the money was for, what was promised, or by when. Complaint records are full of buyers in exactly that position.
The three documents
1. An invoice
What it must show: the vendor’s registered name and GSTIN if registered, your business name, a description of the service, the amount, whether it’s an advance and against what total, the date, and an invoice number.
Why: it names a traceable entity and it’s what every recovery route asks for — a legal notice, a consumer commission filing, a cybercrime complaint. Also, if your business is GST-registered, it’s what lets you claim the input credit, which can make the invoiced route cheaper in net terms.
If they’re not GST-registered: common among small freelancers below the threshold. Ask for a signed bill or proforma on their letterhead instead. Something with their name and the amount on it.
2. A written scope
What it must show:
- The pages, by name — not “up to 5 pages”
- What you supply versus what they supply (text, photographs, logo)
- Number of revision rounds
- Delivery date
- Whose name the domain will be registered in
- Year-two cost for domain, hosting and maintenance
- What’s excluded
Why: every dispute in a website project is a scope dispute. Without this, both sides remember different things and neither is lying.
3. Written payment terms
What it must show: the total, the advance percentage, and what each subsequent payment is tied to.
Why: tying payments to visible stages rather than to dates is what caps a failure. “40% on design approval, 30% when all pages are viewable on the staging link, 30% on go-live” is a sentence that protects you more than any amount of goodwill.
| Document | Minimum acceptable form | Protects you from |
|---|---|---|
| Invoice | A message with firm name, amount, date | Untraceable vendor; no recovery basis |
| Scope | A WhatsApp list of pages and terms | Disputes about what was agreed |
| Payment terms | One sentence naming the stages | Paying ahead of visible progress |
The WhatsApp version
Most small projects will never have a signed contract, and insisting on one can stall the project. This works and takes two minutes:
Confirming what we’ve agreed: ₹[total] plus GST for these pages — [list]. I supply text, photos and logo. [Number] revision rounds. Live by [date]. Domain registered in my name and account. Year-two cost for domain and hosting: ₹[amount]. Payment: 30% now, 40% when all pages are viewable on the staging link, 30% on go-live. Please confirm and send the invoice for the advance.
Then get a reply saying yes. That exchange is a written agreement in substance — it records offer, terms and acceptance with timestamps, and it’s usable in every route that might follow.
Screenshot it and keep it in a folder with the payment record. Better, export the chat so timestamps survive.
What a signed contract adds
For larger projects — stores, booking systems, anything above a straightforward brochure site — a proper agreement is worth the effort. It can cover ownership of code and design files, confidentiality, what happens on termination, and a dispute mechanism.
For a five-page site, the WhatsApp version covers the risks that actually materialise. Don’t let the absence of a formal contract be the reason you proceed with nothing at all.
The one line that matters most
If you get only one thing in writing, make it this:
The domain will be registered in my name, in my own account.
Better still, register it yourself before hiring anyone — about ₹1,000 a year, ten minutes. Then the line becomes unnecessary and the biggest risk in the whole transaction is gone before it starts.
What to do this week
- Register the domain in your own account before paying anything.
- Send the confirmation message and get a written yes.
- Ask for the invoice before transferring the advance.
- Keep the invoice, the confirmation and the payment record in one folder.
- Export the chat so timestamps survive.
If you want it done the certain way
You’ll get all three before you pay: an invoice, the scope with pages, revisions, date, domain ownership and year-two cost, and payment terms tied to stages you can open on your phone. In writing, in one message. WhatsApp us; we reply in about five minutes between 9am and 7pm.
Related reading
- Should there be a written agreement for a website project?
- Why a GST invoice is your best protection
- How much advance is safe to pay?
- Did they put your deadline in writing?
FAQ
What documents should I get when paying a website advance?
Three: an invoice naming the vendor’s firm, a written scope listing pages, revision rounds, delivery date, domain ownership and year-two cost, and written payment terms tying each instalment to a visible stage.
Is a WhatsApp message enough as a website agreement?
For a straightforward brochure site, yes in substance — it records the terms and acceptance with timestamps and is usable in any recovery route. Export the chat so timestamps survive, and keep it with the invoice and payment record.
What if my web developer won’t give an invoice?
If they’re unregistered, ask for a signed bill on letterhead instead. If they’re registered but declining, you’re being asked to trade documentation for a discount — weigh that knowingly, and put more weight on registering the domain yourself.
