Content stall looks identical to abandonment from where you’re sitting — the difference is that one restarts this week and the other doesn’t. Five signs tell you which you have, and the check takes ten minutes.
Being straight about the evidence: complaint records document vendor-side failure directly and in volume. That content stall accounts for a meaningful share of “stuck” projects is our working hypothesis from watching them, not something we can show you with numbers. Treat it as a question worth asking about your own project.
The five signs it’s a content stall
1. The last request in the thread was from them, asking you for something. Product descriptions, photographs, prices, your logo file. Scroll back and check. This is the single most diagnostic line available.
2. You replied “I’ll send it tomorrow” and didn’t. Extremely common and extremely forgettable. Search the thread for that message.
3. The staging link has placeholder text on specific pages. Not all of them — the ones waiting for your material. That’s a map of exactly what’s outstanding.
4. The design was approved and then things went quiet. Content stall has a characteristic timing: design finishes, the build needs your text, and everything stops there.
5. You went quiet first. Uncomfortable to check, and worth checking. From the developer’s side, a client who stops replying during content gathering is indistinguishable from a client who lost interest.
If three or more of these are true, the project is waiting on you.
The five signs it isn’t
1. You sent everything, and you can point to the date. Search the thread and find it.
2. Nothing viewable exists at all — no staging link, no design, nothing, weeks after the advance.
3. You followed up twice and got no reply.
4. More money was requested before anything viewable appeared.
5. Reasons keep arriving without revised dates.
That’s vendor-side, and the response is escalation rather than more content.
| What you find | What it is | What restarts it |
|---|---|---|
| Their last message asked you for material | Content stall | Send everything today |
| Placeholder text on some pages only | Content stall | Send what those pages need |
| Nothing viewable, weeks in | Vendor-side | Written escalation |
| You sent all, then silence | Vendor-side | Escalation; stop paying |
| Both — you were late, then they went | Both | Send content and set a date |
That last row is the most common of all. A vendor waits two weeks, takes on a paying project, and by the time your photographs arrive they’ve moved on. Both delays compound, and afterwards each side blames the other with some justification.
Why the stall happens even when you’re motivated
Three ordinary reasons:
It doesn’t feel like a task. “Send the product descriptions” sounds like five minutes. Writing forty descriptions is an afternoon, and there’s never an afternoon.
Nobody said it was the critical path. Vendors ask for content and rarely explain that everything halts until it arrives. So it reads as a nice-to-have.
It’s invisible from your side. You know you owe photographs. You don’t know that’s the only thing holding up launch — so after four weeks of silence it feels like abandonment.
The ninety minutes that restart it
If the diagnosis is content stall, this is the whole task:
- Record a voice note, fifteen minutes, answering: what you do in two sentences, your main services with prices, your address and phone number, one reason to choose you, how long you’ve operated, and the five questions customers ask most.
- Take fifteen photographs on your phone in daylight — your work, premises, team, products.
- Type the voice note up roughly, or ask whether your developer will work from the audio. Many will.
- Send everything in one batch. Not in pieces across three weeks — that’s the pattern that caused the stall.
- Ask for a revised date in the same message.
Adequate content now beats perfect content never. You can improve every word after launch, and almost everyone does.
The message that works
Sending all remaining content now — text for every page and the photographs, in one batch. What’s the new date to be live?
Two effects. It removes the blocker and it asks for a commitment in the same breath. Most stalled projects restart within days of this message.
What to do this week
- Open the chat and find the last thing they asked you for.
- Check whether you sent it, and when.
- Open the staging link and note which pages have placeholder text.
- Record the voice note and take fifteen photographs today.
- Send everything in one batch and ask for a revised date.
If you want it done the certain way
We publish what we need from you before starting and chase it twice weekly, because a timeline that ignores content is fiction. Send us a voice note and photographs and we’ll write the pages from it. WhatsApp us; we reply in about five minutes between 9am and 7pm.
Related reading
- The content stall that delays most websites
- Is it my fault or the developer’s?
- How to actually hand over website content
- Who writes the text for your website?
FAQ
What is a content stall on a website project?
When the build halts because the client’s text, photographs or prices haven’t arrived. From the outside it looks identical to a developer abandoning the project, which is why it goes undiagnosed for months.
How do I tell if my website is waiting on me?
Find the last request in the chat. If they asked for material and you didn’t send all of it, and the staging link shows placeholder text on those specific pages, the project is waiting on you.
How quickly can a stalled website restart?
Often within days. Record a fifteen-minute voice note covering your services, prices and contact details, take fifteen phone photographs, send it all in one batch, and ask for a revised date in the same message.
