A written delivery date with a consequence attached behaves completely differently from a spoken one, because a spoken date competes with every other client’s spoken date — and loses to whoever complains loudest. Getting it in a message costs nothing and changes the queue you’re in.
Owners ask “website kitne din me banegi” and get an answer. Almost nobody asks for that answer in writing, which is the part that matters.
The moment it happens
Did they put your deadline in writing? Why “bas ho jayega” isn’t enough becomes clear around week three, when you realise the date you’re annoyed about was never actually agreed anywhere — it was mentioned.
Public complaint accounts show where unwritten dates end up. One buyer described a project with a 10–15 day timeline that took 40 days and was still half finished. Another reported five months after full payment with a site that didn’t work. In both, the original timeline existed only as conversation.
Why a spoken date drifts
It has no consequence. Nothing happens when it passes. A date with no attached outcome is an intention, and intentions get re-prioritised.
It’s usually the optimistic version. Verbal estimates are given while winning the work, when the vendor is picturing a smooth project with content arriving on time.
It ignores your side of the clock. Most website timelines assume you’ll supply logo, photos and text quickly. When you don’t — normal, and common — the date silently moves, and neither side marks the change.
You’re one of several projects. Without a written commitment, allocation goes to whoever is most insistent. Politeness costs you position.
What to actually ask for
One message, before you pay:
Please confirm in writing: the go-live date, the date you need my content by, what’s included in the build, and the final amount including GST.
Four items, one message. Note the second one — the content-due date is the part buyers forget, and it’s the part that makes the deadline fair. A date that only binds the vendor isn’t credible; a date that binds both sides is.
If the answer is “we can’t commit to a date until we see your content”, that’s reasonable. The workable version is: content received by the 12th, site live by the 22nd. Conditional, dated, enforceable.
| What you get | What it’s worth |
|---|---|
| “It’ll take about two weeks” | An estimate. No weight in a dispute, no effect on queue position |
| “Live by the 22nd” in a message | A commitment you can reference; changes behaviour |
| “Content by the 12th, live by the 22nd” | The fair version — both sides have an obligation |
| Date plus a stated consequence | The strongest form, and rare in this market |
Consequences that vendors will actually agree to
Most small vendors won’t sign a refund clause. Some smaller commitments are easier to get and still useful:
- A stated reduction in the final balance if the date slips beyond a stated grace period.
- A hard handover date: if the site isn’t live by X, the files and domain access are transferred to you regardless of completion state.
- A weekly progress link — not a screenshot, a URL you can open. Visible progress is the earliest signal of drift.
Any of these is more valuable than a vaguer promise of goodwill, because each one is checkable.
If your project is already late
Don’t renegotiate the past; set one dated request going forward. Ask for the staging link and a confirmed go-live date by a specific day, and say plainly what you’ll do if neither arrives. Then stop sending daily follow-ups, which lower pressure rather than raise it.
What to do this week
- Scroll back and find what date was actually mentioned. Write it down.
- Send the four-item confirmation message above, even mid-project.
- Ask for a link you can open, not screenshots.
- Check whether your content is the blocker before escalating — if it is, send it today.
- On your next project, make the two-date format (“content by X, live by Y”) a condition of the advance.
If you want it done the certain way
We put the go-live date in writing with a refund behind it, and we state the date your content is due in the same message so the clock is honest on both sides. If your current project is nearly done, we’ll tell you to finish it rather than restart. WhatsApp us; we reply in about five minutes between 9am and 7pm.
Related reading
- “2 din mein ho jayega”: breaking the website delay loop
- How much advance is safe to pay a web developer?
- Does your web developer have a refund policy?
- The “90% done” website that never goes live
FAQ
How long should a small business website take to build?
A simple 5-page site is usually one to three weeks of work once content is ready; a store takes longer. Content handover, not development, is what most often sets the real timeline.
Will a web developer agree to a written deadline?
Many will, especially if you also accept a content-due date. Resistance to writing down any date at all — even a conditional one — is worth treating as a signal about how the project will be managed.
What if the delay is my fault?
Then the deadline resets fairly, which is exactly why the content-due date belongs in the same message. It protects the vendor from unfair blame and protects you from an open-ended timeline.
