Almost nobody's site is late because the developer is slow. It's late because a content request has been sitting in a business owner's inbox since March — and the whole process was built to make that inevitable.
Ask around locally and you will find a startling number of business owners who paid a deposit on a website in the spring and still do not have one. Ask what happened and you get a version of the same sentence: I think they're waiting on me for something.
They are. And the reason is worth understanding, because it is structural rather than anyone's fault.
Here is a typical six-month small business website, honestly accounted:
| Phase | Working time | Calendar time |
|---|---|---|
| Kickoff and discovery | 2 hours | 1 week |
| Content request sent to client | 15 minutes | 11 weeks |
| Design | 1–2 days | 2 weeks |
| Build | 2–4 days | 3 weeks |
| Revisions | 4 hours | 5 weeks |
| Launch | 1 hour | 1 week |
Add the working column and you get somewhere around a week of actual labor. Add the calendar column and you get roughly six months.
Notice which two rows are highlighted. The two longest stretches in the project are both waiting on the client, and the longest single one is triggered by an email that took fifteen minutes to write.
Nobody is slow. The project is just structured so that the person with the least time is on the critical path twice.
Put yourself on the receiving end. You own a plumbing company. An email arrives asking for:
Every item is reasonable. Together they are a writing assignment of several thousand words plus a photo shoot, handed to someone who is on a roof, with no deadline, no template, and no idea what "about story" means in practice.
So it gets moved to the weekend. Every weekend. Not from laziness — because writing from a blank page is legitimately difficult, and difficult tasks with no deadline lose to easy tasks with customers attached to them.
I take this seriously enough that when I built the software that runs my own studio, "content received" is a dedicated field on every project with an automatic alert after four days of silence. Not because clients need chasing, but because a project sitting in that state is invisible otherwise — it looks like progress, and it is decay.
The problem is the direction of the first draft.
Standard process: client writes → builder builds. That requires the busiest, least practiced writer to produce the hardest artifact first.
Better process: builder drafts → client corrects.
Because the raw material almost always already exists. Before asking for a single thing, a competent builder can assemble a full draft from your old website, your Google Business Profile, your Facebook page, your reviews, your listings, your brochure, and twenty minutes of you talking on the phone.
Is that draft right? Not entirely. It will get your service names slightly wrong and miss things you care about.
That is the point. Reacting to a wrong draft is enormously easier than producing a right one. "We don't do commercial anymore, and it's called a lift station not a pump station" takes eleven seconds. The blank version of that same request has been sitting unanswered for eleven weeks.
If someone is quoting your project, ask this: "What do you need from me before you can start?"
Good answer — domain access, your existing site or listings, your services and prices, and a twenty-minute call. Bad answer — a content questionnaire, a photo package, and written copy for every page. The second answer means the hard part is yours and there is no date attached to it.
The second stall is photography. Everyone wants real photos, which is correct — stock imagery of a generic office genuinely does undermine a local business.
But wanting real photos becomes: schedule a photographer, coordinate a day the crew looks presentable, wait for the weather, wait for the edit. Two months, easily. Meanwhile the site sits at 90% complete and completely invisible.
This trade is bad, and it is bad for a specific reason. A new domain earns search history by existing. Every week the site is not live is a week it is not being crawled, not accumulating any track record, not appearing for your own business name. Google does not care that you were waiting on a photographer.
Launch. Swap the photos in when they arrive — it is a five-minute job on any competently built site. There is no version of this where waiting was worth it.
If your business is visual — restaurants, salons, anything where the product's appearance is the purchase decision — then photography genuinely is the product and shipping with placeholders undersells you. Even then: launch the pages that do not depend on imagery, and stage the visual ones. Partial beats invisible.
The other highlighted row is revisions: four hours of work spread across five weeks.
That happens when feedback arrives in fragments — a text on Tuesday, three more thoughts on Friday, a phone call the next week. Each fragment is a small task with context-switching cost on both sides, and the project stays open for over a month to absorb a half-day of work.
The fix is unglamorous. One review round, one document, everything in it, with a stated date. Not because clients are difficult, but because trickled feedback keeps a project alive far longer than the work inside it justifies.
If you have a project sitting in limbo, one email usually restarts it:
"I'm not going to get that content package written — it's been on my list for two months and it isn't going to move. Can you draft all of it from my old site, my Google listing and my reviews, and send it to me marked up? I'll correct it within 48 hours and we can use placeholder photos for launch. I'd rather be live and imperfect than perfect and invisible."
Any builder worth keeping will say yes, because they would rather ship than hold a stalled project too. And if the answer is that they cannot proceed without your written copy, you have learned something useful about what you are actually paying for.
In most stalled projects the calendar time is not build time, it is waiting time. The design and development work is usually a small number of days. The months come from the gap between a content request being sent and the client sending photos, service descriptions and page copy back, because that task lands on a business owner who already has a full job.
Whoever will actually finish it. Handing a blank document to a busy owner is the single most reliable way to stall a project. A better approach is for the builder to draft every page first from material that already exists, such as the old site, reviews and listings, then have the owner correct the draft. Editing is far faster than writing from nothing.
Yes, and it usually should. A site built with sensible placeholder imagery can go live and start earning search history while real photography is scheduled. Photos are one of the easiest things to swap after launch, so treating them as a launch blocker trades months of live time for a cosmetic detail.
Very little. Access to your domain, your existing site or listings, your services and prices, and a short conversation about who you want to reach. Anyone who cannot start until you deliver a large content package is asking you to do the hardest part of the project alone and without a deadline.
Send me the URL of your current site or listing. I'll draft your new page copy from what's already public and send it over — you correct it instead of writing it.
Works whether or not you end up building with me.