You need one page, not a legal contract — deliverables, price, dates, payment stages, ownership and revisions — and for most small projects a WhatsApp message containing those six items is enough. The purpose isn’t litigation. It’s removing the ambiguity that causes almost every website dispute.
Buyers who’ve been through a failure say this themselves. After one bad project, a buyer’s public advice was blunt: create a clear document listing requirements step by step, and sign a contract.
The moment it happens
Should there be a written agreement for a website project? Most have none — the quote came on WhatsApp, the scope was discussed in voice notes, and the deadline was mentioned in passing. When something goes wrong, both sides scroll up and find the same thread supporting two different readings.
The chat isn’t worthless as evidence. It’s just weak where it matters: it rarely contains a complete list of what was promised.
The six items
Everything else is optional. These aren’t:
- Deliverables. Number of pages, named. Features: contact form, gallery, payments, bookings, multilingual. What is explicitly not included.
- Who supplies content. Text, photos, logo file — and the date they’re due from you. This single line prevents the most common delay and the blame that follows it.
- Price, final, including GST, and what triggers extra charges (per-page rate beyond the agreed count).
- Dates. Go-live date, and your content-due date. Both, in the same message.
- Payment stages. How much now, how much at which stage, how much at go-live.
- Ownership. Domain and hosting registered in your name; files handed over at completion.
If you want a seventh: revision rounds included, and the rate after that.
Why this protects the vendor too
Worth understanding, because it changes how you ask for it. A written scope means:
- They can refuse endless additions without an argument, because the list exists.
- They aren’t blamed for a delay caused by content arriving three weeks late, because your date is written too.
- They get paid at defined stages instead of negotiating at the end.
Vendors who understand this usually welcome it. Framing it as “let’s put this in one message so neither of us has to remember” gets a better response than framing it as a demand.
Does a WhatsApp thread count legally?
In practice, a chat showing agreed scope, amount and dates, plus the payment reference, is usable evidence in a consumer complaint or police complaint — it’s what most buyers actually rely on. But “usable” is a lower bar than “clear”. A single consolidated message that both sides acknowledge is dramatically stronger than forty messages needing interpretation.
The practical version: after the conversation, send one message summarising the six items and ask them to confirm. Their “yes” is the agreement. That takes five minutes and no lawyer.
| What you have | Strength in a dispute |
|---|---|
| Verbal discussion only | Very weak |
| Scattered chat messages | Usable, open to interpretation |
| One consolidated message, acknowledged | Strong for a small project |
| Signed one-page scope + invoice | Strongest, still simple |
For larger projects
Above roughly ₹1 lakh, or where you’re sharing customer data, a slightly fuller document is worth it: confidentiality, what happens if either side walks away, who owns the code, and how disputes are handled. Still a page or two, not twenty.
What to do this week
- Write your own scope in one page before contacting vendors. It clarifies what you’re buying.
- After agreeing terms, send the six-item summary and ask for confirmation in writing.
- Include your content-due date, not just theirs.
- Name the domain ownership line explicitly.
- Keep the confirmed message, the quote and the payment reference in one folder.
If you want it done the certain way
We put the scope, dates and payment stages in writing as standard, including the date your content is due, so the timeline is honest on both sides. If you’d rather use your own document, that’s fine with us. WhatsApp us; we reply in about five minutes between 9am and 7pm.
Related reading
- Did they put your deadline in writing?
- How much advance is safe to pay a web developer?
- Cheated once? Conditions to set the second time
- “Unlimited revisions” — does anyone mean it?
FAQ
Is a WhatsApp conversation enough as a website agreement?
It’s usable evidence, and it’s what most small projects rely on. A single consolidated message listing deliverables, price, dates, payment stages and ownership — acknowledged by the vendor — is far clearer than a scattered thread.
Will a small web developer agree to sign a contract?
Many will, particularly a one-page scope, because it protects them from unlimited additions and from being blamed for client-side delays. Reluctance to write down any scope at all is worth treating as information.
What’s the most important clause for a small website?
Ownership — that the domain and hosting are registered in your name. It’s the item that determines how much damage a failed project can do.
