“Bas ho jayega” is not a deadline, and neither is “two to three weeks” — a real one has a date per phase, a stated consequence, a definition of done, and an acknowledgement of what happens if your content is late. Projects that never finish almost always lacked all four.
Why the fear is well founded
Complaint records include an account of a site roughly half finished at day forty, against a much shorter promise. And there’s a whole category of paid-for websites sitting complete-but-unlaunched, sometimes for years.
So “it might never finish” isn’t paranoia. It’s a documented outcome with an identifiable cause: nothing in the arrangement forced a finish.
The five components of a real deadline
1. A date per phase, not one final date. A single end date gives you nothing to check until it’s already missed. Phases give you an early warning:
| Phase | Realistic duration |
|---|---|
| Requirements and structure | 2–4 days |
| Design of main pages | 4–7 days |
| Build with your content | 5–10 days |
| Revisions and testing | 3–7 days |
| Go-live | 1–2 days |
2. A stated consequence. A date with nothing attached is a hope. Reasonable options: final payment held until live, a small discount per week late, or the right to take the files and finish elsewhere. Any of them changes the conversation.
3. A definition of “done”. This is the component that prevents the unlaunched-site outcome:
Live means: on my domain, contact form tested and reaching my inbox, WhatsApp button working with the country code, and the registrar, hosting and admin logins handed over to me.
Without that sentence, “done” is a matter of opinion and the project can stay 90% forever.
4. Acknowledgement of the content dependency. The largest cause of overrun is content arriving in pieces from the buyer’s side. A fair deadline says so: “If my content is late, the timeline extends by the delay.” That’s fair to the vendor and it removes their best excuse when your content was on time.
5. A staging link from the first build day. So a slip is visible in week two rather than week eight. This is what makes the other four enforceable.
The message that sets all five
Send this with your advance:
Confirming the schedule: design by [date], all pages built and viewable on a staging link by [date], live by [date]. Live means on my domain with the contact form tested and all logins handed to me. If my content is late, the dates extend by that delay. Final 10% on go-live.
Six lines. Any competent vendor accepts it, because it’s fair to both sides and it defines their obligation as clearly as yours.
What “two to three weeks” actually means
Treat any quoted timeline as the best case and plan for roughly double — and understand that a share of the overrun will be your side.
That’s not cynicism about vendors. It’s that the quoted figure assumes content is ready, feedback arrives promptly, one person approves, and nothing changes mid-build. Those four conditions rarely all hold.
Which points at the most effective thing you can do about this fear.
The half you control
Most of the available certainty is on your desk:
- Send all content before the build starts. Text for every page, photographs, logo file, exact phone number and address. Projects where content is ready at the start finish close to their quoted date.
- Nominate one approver. One person decides; others may comment. Multi-approver projects routinely take two or three times as long.
- Give feedback as one numbered list per round. Not eleven messages over three days.
- Agree the number of revision rounds in writing before work starts.
Do those four and you have removed the most common cause of a project that never ends. That’s worth more than any consequence clause.
The early-warning check
Two signals mean the schedule is no longer real:
The second date slips. A first slip is normal. When the revised date also moves, the estimate was wrong rather than the execution.
Updates stop containing links. “Working on it” replacing “here’s the page” is the earliest reliable sign.
At either point, stop paying and ask for a revised phase-by-phase schedule in writing. Don’t send more money to unlock progress.
What to do this week
- Gather every piece of content and send it in one batch before the build starts.
- Send the six-line schedule message with your advance.
- Write down what “live” means, including the logins.
- Nominate one approver and say so out loud.
- Ask for the staging link on day one.
If you want it done the certain way
You get a date per phase in writing, a definition of “live” that includes your logins, a staging link from the first build day, and a final instalment tied to go-live — plus a clear statement of what we need from you to hold the dates. WhatsApp us; we reply in about five minutes between 9am and 7pm.
Related reading
- Did they put your deadline in writing?
- How late do website projects actually run?
- The “90% done” website that never goes live
- The graveyard of paid-for websites that never launched
FAQ
What does a real website deadline look like?
A date for each phase rather than one final date, a stated consequence for missing it, a written definition of “live” including handover of logins, an acknowledgement that late content extends the timeline, and a staging link from the first build day.
How do I stop a website project from dragging on forever?
Send all your content before the build starts, nominate one approver, give feedback as one numbered list per round, agree the number of revision rounds, and define what “done” means in writing.
What should “live” mean in a website agreement?
On your own domain, with the contact form tested and reaching your inbox, the WhatsApp button working with the country code, and the registrar, hosting and admin logins handed over to you.
