Before assuming a developer has abandoned your project, check who sent the last message — a large share of stalled websites are waiting on the owner’s logo, photos or page text. It’s an uncomfortable check and it takes thirty seconds.
We can’t tell you what proportion of stalls are content-side versus developer-side; nobody has that data for India, and a specific number would be invented. What’s clear is that the two get confused, and the confusion costs owners months.
The moment it happens
The real reason your website is stuck may be that it’s waiting for you — and the way this hides is that it never feels like a decision.
You were asked for photos and “about us” text. You meant to send them that Sunday. Then it was a busy week. The developer followed up twice, then stopped. Three weeks passed. Now the project feels dead and the natural conclusion is that the developer lost interest — which he may have, but the sequence started somewhere else.
How to check in thirty seconds
Open the chat and scroll to the last three messages.
| Last message in the thread | Who is waiting |
|---|---|
| A request to you (photos, text, approval) | You |
| A question you haven’t answered | You |
| “Will send content soon” from you | You |
| A promise from them with no delivery | Them |
| Their update, and you replied | Them |
If it’s the top three rows, escalating won’t help. Sending the content will.
Why content stalls so reliably
It’s a bigger task than it sounds. “Send me your content” means home page text, an about section, service descriptions, contact details, image captions — and for a store, every product name, price and photo. Owners hear one request; the work is a dozen small pieces.
Nobody agreed a date for it. Vendor deadlines get discussed; client deadlines rarely do. Anything without a date competes with running your business, and loses.
Writing about yourself is genuinely hard. People who pitch confidently in person freeze at an about page. This is normal and rarely admitted.
The material exists in the wrong form. It’s in a brochure, in a WhatsApp broadcast, in your head. Converting it into a document is the actual task, and it feels like homework.
The chasing stops. Vendors give up after two or three reminders — partly politeness, partly because unpaid waiting has no upside. Their silence then looks like abandonment, which lets both sides avoid the awkward truth.
One sharper version appears in complaint records: a developer insisting content be resent in a different file format, with a warning that the site would be delayed otherwise. Sometimes the format request is legitimate; sometimes it’s a delay being relocated onto the client. Either way, sending it settles the question.
Clearing it in a weekend
The trick is lowering the bar to something you’ll actually finish.
- One folder. Logo file, photos, any old brochure or price list. Nothing written yet.
- Voice notes, not documents. One per page: what is this page for, who is it for, what should the reader do next. Three minutes each. Transcription is easy; a blank page isn’t.
- Phone photos in daylight. Ten decent phone photos of your shop, work, team or products beat waiting for a shoot you’ll never schedule.
- Use existing text as-is. Send the brochure copy without rewriting it. Editing is the developer’s or writer’s job; sourcing is yours.
- Send it in one go, with a date. “Everything is here — can we go live by the 22nd?” This restarts the project with a shared deadline instead of an apology.
If writing genuinely won’t happen, buy it. Content writing is usually a modest add-on, and paying for it is cheaper than a site that sits unlaunched for six months.
What to do this week
- Check the last message in the thread and be honest about who’s waiting.
- Make the folder today. Logo and photos only — no writing yet.
- Record one voice note per page this weekend.
- Send everything in a single message with a proposed go-live date.
- If it’s been more than a month, expect to re-confirm the price and timeline — that’s reasonable, not a penalty.
If you want it done the certain way
We name the content we need and the date we need it by, in writing, so the clock is honest on both sides — and we offer writing as a plainly-priced add-on if you’d rather not. If your existing project is only stuck on content, sending it is cheaper than starting again with us, and we’ll say so. WhatsApp us; we reply in about five minutes between 9am and 7pm.
Related reading
- Who writes the text for your website — you or the developer?
- How to hand over website content without writing a document
- Do you actually have your logo file?
- “2 din mein ho jayega”: breaking the delay loop
FAQ
How do I know if my website is delayed because of me or the developer?
Scroll to the last message in the thread. If it’s a request to you — photos, text, an approval — the project is waiting on your side, and no amount of chasing will move it.
Can a website launch without all the content ready?
Yes, and for a simple presence it’s usually better. Launch with the essentials — what you do, contact details, a few photos — and add pages later. A live basic site beats a complete unlaunched one.
Should I pay someone to write my website content?
If you’ve been meaning to write it for more than a month, yes. The add-on cost is typically modest against the cost of a paid-for site sitting unlaunched.
