Most small website projects here proceed with no written agreement at all, so when a disagreement arrives it becomes a contest of recollection — and both people are usually remembering honestly. The fix isn’t a lawyer. It’s one message, sent before work starts, and a reply saying yes.
How the fight starts
Never over something large. Over a page.
You believed the Gallery page was included. He believed you’d discussed it as a possible addition. Neither of you is lying — the conversation happened three weeks ago across eleven messages, a phone call and a meeting, and you each retained a different version.
Now there’s an invoice, or a refusal, and the relationship changes. From here the project usually either stalls or finishes badly.
Why chat threads fail as records
They’re not invalid. They’re just disorganised, which is different.
Terms are scattered. Price in one message, pages in another, timeline mentioned on a call. No single place says what was agreed.
Calls leave no trace. The most important discussions happen by phone and nothing survives them.
Nothing is confirmed. A message saying “we can add a gallery” is not agreement that it’s included. Both readings are available.
Voice notes are unsearchable. A five-minute note with three terms in it is effectively lost by the following week.
Nobody ever wrote down the exclusions. Which is where every dispute actually lives.
The one message that fixes it
Send this before paying the advance. Two minutes:
Confirming what we’ve agreed: ₹[total] plus GST for these pages — Home, About, Services, Gallery, Contact. I supply text, photographs and logo. Two 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 records offer, terms and acceptance with timestamps. In substance it’s a written agreement, and it’s usable in every route that might follow — a legal notice, a consumer commission filing, or simply settling a disagreement in week four by scrolling up.
The five items that must be in it
If you shorten the message, keep these:
- The pages, by name. Not “about 5 pages.” This is where most disputes originate.
- Who supplies content. The biggest swing in any project and the largest cause of delay.
- Number of revision rounds. Undefined rounds produce the spiral.
- Whose name the domain is registered in. The most expensive item to get wrong.
- The year-two cost. The most common source of feeling misled later.
Everything else is recoverable. Those five are not.
Housekeeping that costs nothing
Pin the confirmation message in the chat so both of you can find it.
After every call, send a three-line summary. “Confirming from our call: adding the gallery at ₹X, live date moves to the 22nd.” Their acknowledgement is the record.
Ask for changes in writing, not on calls. A message asking for an addition, with a reply naming the cost, prevents the invoice argument entirely.
Export the chat. WhatsApp lets you export a conversation to a file. Do it at launch. Screenshots lose timestamps; an export keeps them.
Keep one folder with the export, the invoice and the payment records.
When a formal contract is worth it
For a five-page brochure site, the message above covers the risks that actually materialise, and insisting on a signed agreement can stall the project for no gain.
For a store, a booking system, or anything touching your customer data or internal systems, a short written agreement is worth the effort. It can cover ownership of code and design files, confidentiality, what happens on termination, and a dispute mechanism. Any competent vendor will sign one.
The mistake is treating this as binary. Because you won’t get a formal contract, you end up with nothing — when a two-minute message would have covered most of it.
If you’re already in a scope fight
Three steps, in order:
Scroll back and find what was actually written. Not what you remember. If “Gallery” appears as an agreed item, quote it. If it doesn’t, you’re in a genuine gap.
Separate corrections from additions. A page built to the wrong brief is their work to fix. A page never discussed is a new item. You should pay for the second and not the first.
Split the difference where the record is genuinely ambiguous. Then put the rate in writing for everything remaining. Winning a ₹2,000 argument at the cost of a stalled project is a bad trade.
What to do this week
- Send the confirmation message before paying anything.
- Get a reply saying yes, and pin it.
- Summarise every phone call in three lines afterwards.
- Ask for all changes in writing, with the cost named.
- Export the chat at launch and keep it with the invoice.
If you want it done the certain way
You get the five items in writing before paying — named pages, who supplies content, revision rounds, domain ownership and the year-two cost — so there’s nothing to argue about in week four. WhatsApp us; we reply in about five minutes between 9am and 7pm.
Related reading
- Should there be a written agreement for a website project?
- What paper should your advance actually buy you?
- Who pays for scope creep?
- What silently disappeared from what you were promised?
FAQ
Is a WhatsApp chat enough as a website agreement?
In substance, yes for a straightforward brochure site — a single confirmation message with the terms, plus a reply agreeing, records offer and acceptance with timestamps. The failure is scattered terms, not the medium.
What must be in writing before a website project starts?
The pages by name, who supplies the content, the number of revision rounds, whose name the domain is registered in, and the year-two cost. Those five cause almost every dispute.
What should I do if my developer and I disagree about scope?
Scroll back and find what was actually written rather than what you remember, separate corrections of their work from genuine additions, and split the difference where the record is ambiguous — then put the rate in writing for what’s left.
