Reply speed is the most reliable early indicator in a website project — a vendor who answered in ten minutes during the sale and now takes three days has usually reallocated your project, not lost your message. Reading that shift early is what lets you act while you still have leverage.
Nothing about slow replies is unusual on its own. The pattern is what matters.
The moment it happens
When your web developer’s replies go from minutes to days, the change is gradual enough to explain away each time. He was travelling. It was a festival. Server issue. There’s always a reason, and often it’s true.
What buyers describe on public complaint forums is the endpoint of that curve: a vendor who deals only over WhatsApp and rarely attends a call or reverts at all. That endpoint is reached one delayed reply at a time.
The decay curve, and what each stage means
| Stage | What you observe | What it usually means | What to do |
|---|---|---|---|
| Normal | Same-day answers, specific content | Project is active | Nothing |
| Drift | 1–2 days, vaguer, no specifics | You’ve slipped down the queue | Ask for a link, not an update |
| Avoidance | Replies only after two or three pings; “almost done” | Work has likely stopped | Send one dated request |
| Silence | No reply for a week; calls unanswered | Project is stalled or abandoned | Ask for domain, hosting, files |
The signal to watch isn’t the delay itself — it’s the loss of specificity. “Testing the contact form today” is an engaged reply, even if late. “Working on it, almost done” repeated three times is the vendor managing you rather than the project.
Why it happens without malice
Small vendors run several projects with no scheduling system, and attention follows whoever is loudest or paying most. If your build was at the bottom of the market, you are structurally last in line — not disliked, just deprioritised.
There’s also a version where the developer is a single person who is genuinely overloaded or unwell, and the silence isn’t strategy. That distinction matters emotionally but changes nothing practical: your site is still not being built, and the same steps apply.
And sometimes the silence is on both sides. If the last message in the thread is a request to you — for photos, text, an approval — the pause may be yours to release. Check before escalating.
The message that restarts things, or ends them
Daily pings feel like pressure and function as noise. One dated request with a checkable deliverable works better:
Could you send the link where I can see the current work, and confirm the go-live date, by [date three days away]? If the timeline has changed, tell me and we’ll plan around it.
Asking for a link rather than an update is the mechanism. A URL either exists or doesn’t; reassurance can be generated endlessly.
If that produces nothing, treat it as an abandoned project rather than a late one, and switch objectives — from getting the site finished to getting your assets out. Ask in one message for the domain authorisation code, hosting login and the files as they stand.
What to do this week
- Scroll the thread and note the gap between your messages and replies over the last month. The trend is the diagnosis.
- Check whether anything is pending from your side. Clear it today if so.
- Send one dated request asking for a link and a confirmed date. Once.
- Stop sending daily follow-ups — they reduce the weight of your messages.
- If a week passes with no answer, request domain, hosting and files in writing and start planning around finishing elsewhere.
If you want it done the certain way
If a project has gone quiet, send us what exists — the chat, any link, whatever files you hold — and we’ll tell you honestly whether it’s worth finishing or restarting. On our builds, the delivery date is written with a refund behind it, and the domain and logins stay in your name so silence can never trap the work. WhatsApp us; we reply in about five minutes between 9am and 7pm.
Related reading
- “2 din mein ho jayega”: breaking the website delay loop
- Developer took the advance and disappeared: recovery steps
- 10 signs a web developer is about to disappear
- The “90% done” website that never goes live
FAQ
How long should I wait before assuming a developer has abandoned my project?
A week of no reply after a direct, dated request is a reasonable threshold. Before that, check whether the last pending item was yours — a large share of stalls are content waiting on the client.
Should I keep messaging every day?
No. Frequent pings lower the significance of each message. One clear request with a date, then a decision if it isn’t met, applies more pressure than daily follow-ups.
Is slow communication alone a reason to leave a developer?
Not by itself, if work is visibly progressing. It becomes decisive when replies lose specificity and no new work appears — that combination is the reliable warning, not lateness on its own.
