"We'll Add Content Later" Is How Sites Die

Most website projects that go badly do not go badly because of the code. They go badly because the site sits at ninety per cent finished for four months, waiting for someone inside the business to write the About page, approve the product descriptions, or find the photographs of the factory that definitely exist somewhere on a laptop that an ex-employee took with them.

The sentence that starts this is always the same, and it is always said in the first meeting, cheerfully, by someone who means it: "Let's get the design going, we'll add the content later."

It sounds like sensible parallel working. It is not. It is a decision to do the hardest part of the project last, with no deadline attached, at the exact moment when everyone's enthusiasm has run out.

Why the delay always happens

Nobody plans to stall. The stall has a structure, and it is worth naming so you can recognise it early.

Design work has a visible result; writing does not. A designer sends you three homepage mockups and you feel progress. A week spent deciding whether your business is a "manufacturer" or a "solutions provider" produces nothing you can show your spouse. So the writing gets pushed to next week, every week.

Writing about your own business is genuinely hard. You know it too well. Everything feels either obvious or boastful. Owners who can explain their business brilliantly to a customer across a desk freeze completely in front of a blank document titled "About Us — final.docx".

There is no single owner. Product descriptions need the sales head. Technical specifications need the plant. Pricing needs you. Photos need whoever has the camera. Each person is waiting for a brief, and the brief is waiting for the design, and the design is waiting for the content. Nothing in that loop has a name against it in a calendar.

Placeholder text hides the problem. A layout filled with dummy Latin paragraphs looks complete. It looks balanced. It looks approved. Then the real copy arrives, the headline is nineteen words long instead of six, and the hero section breaks. Now the design needs rework at the point when the budget is spent and the patience is gone.

Content is the long pole, and it is not close

In project management, the long pole is the item that sets the length of the whole schedule — everything else can be squeezed or run in parallel, but this one cannot. On a website build, the long pole is almost always content, and it is not a close contest.

Think about what "content" actually means on a modest business site:

Six to twelve pages of prose that someone must think about, draft, argue over and sign off
Photographs of real premises, real people, real products — which means a shoot, which means a day when the floor is tidy and people are available
A logo file that is not a 300-pixel JPEG pulled off an old invoice
Product or service data: names, specifications, variants, prices, what is actually in stock
Legal and trust material — registered address, GST details where relevant, returns and shipping policy, privacy notice
Decisions. Not text: decisions. Do we show prices or not. Do we serve all India or only NCR. Is the WhatsApp number the owner's personal one.

The build side of that, by contrast, is well-understood work with known steps. A developer can tell you roughly how long a template takes. Nobody can tell you how long it takes you to decide whether to publish prices, because that is a business decision wearing a project-task costume.

Treat anything that requires a decision by you as the critical path. Everything else bends around it.

The sequencing that works

The fix is unglamorous: do content first, but only enough of it, and in a fixed order. Here is a sequence we would defend to any client.

Step one: write the sitemap as sentences, not boxes

Before anyone draws anything, list the pages. Next to each page, write one sentence saying what a visitor should understand or do after reading it. If you cannot write that sentence, the page should not exist yet. This single exercise kills roughly half the pages that people think they need, and it kills them before anyone has paid to design them.

Step two: draft the five pages that carry the money

Not all pages. Five. Typically: home, the main service or category page, one deep page that proves you know your subject, contact, and about. Rough drafts are fine. Bad prose is fine. Existing material pasted from a brochure is fine. What matters is real length and real meaning, so the designer is laying out your actual nineteen-word headline rather than a tidy fictional six-word one.

Step three: design against real text

Now the layout work starts, and the arguments it provokes are useful ones. "This paragraph is too long for the space" becomes a conversation about whether the paragraph should be shorter — which is a conversation worth having, and one you can never have against dummy text.

Step four: photography, with a shot list

Book the shoot in week one even if it happens in week five. A shot list derived from your five drafted pages means the photographer knows they need a wide of the workshop, three product cut-outs on white, and two portraits — rather than spending a morning taking lovely pictures of nothing you can use.

Step five: everything else, after launch

The forty product pages, the blog, the case studies, the careers page. These go on a published calendar with owners and dates, after the site is live. A live site with twelve good pages earns more than a staging link with forty planned ones.

Item	When	Who genuinely owns it
Page list with purpose sentences	Before design	You, with the agency asking questions
Five core page drafts	Before design	You or a writer you have actually hired
Logo, colours, fonts	Before design	You — find the original files now
Photography	Booked week one, shot by week five	You, against an agency shot list
Policies, GST, address, phone	Before build is finished	You or your accountant
Remaining pages and blog	After launch, on a calendar	Named person, named date

What we would not buy

A bulk content package priced per page. "Fifty SEO-optimised pages" sold as a block is a volume product, and volume is not your problem. Ten pages that say something specific about what you do will outperform fifty that paraphrase each other. If you are being quoted per page, ask what the brief for each page is. If the answer is a keyword, that is not a brief.

Content "filled in later by the CMS team". A content management system — the admin panel you log into to edit the site — does not write anything. It only removes the excuse that editing is expensive. Someone still has to type the words. If no name is attached to that job in the project plan, assume it will not happen.

Machine-written filler to cover the gap. There is a real temptation to generate forty pages of plausible prose to get the site shipped. It will not be wrong exactly, it will just be unremarkable, and unremarkable is a poor foundation for both ordinary search and the newer AI answer engines, which tend to lean on pages that contain specific, checkable claims. Nobody can tell you with confidence how those systems weight things — that area genuinely is unsettled — but "says nothing another site hasn't already said" is unlikely to be the winning strategy under any version of the rules.

A redesign that postpones the content question again. If your current site stalled for content reasons, a new design will stall for the same reasons. The constraint has not moved.

If you are already stuck at ninety per cent

Plenty of readers will recognise this because it is happening to them right now. Three things help.

Cut the page list. Go through the unfinished pages and delete any you cannot write a purpose sentence for. Launching without a page is better than not launching.
Launch with what exists. A live site with ten finished pages starts collecting enquiries and search data today. The missing pages can be added next month. Nothing about a website is permanent.
Talk, don't write. If drafting is the blocker, record yourself explaining the service to a customer on your phone for ten minutes and have that transcribed. Editing a transcript is enormously easier than facing an empty page, and it tends to sound more like you.

What to do next

Open a document today and list your pages, one line each, with one sentence on what each page is for. It takes about twenty minutes. If you can do it for every page, your project will not stall. If you get stuck on page three, you have just found the real schedule risk before spending anything on design.

If you would like someone to run that exercise with you before any build starts, or you have a half-finished site that needs cutting down and launched, tell us what is stuck. You can also read how we approach website builds, or browse other pieces on planning and content while you think about it.

Questions we get asked

Can't the agency just write my website content for me?

Partly. An agency can structure, draft and edit well, but it cannot invent your prices, your service boundaries, your specifications or your reasons for being better than the firm down the road. The fastest arrangement is usually an interview — you talk, they write, you correct. What does not work is handing over no information and expecting usable copy to appear.

How many pages should a small business website launch with?

Usually somewhere between eight and fifteen, depending on how many distinct services or product categories you sell. The test is not a number, it is whether you can say in one sentence what each page is for. Pages that fail that test should be removed from the launch scope and reconsidered later.

Is it really a problem to design with placeholder text?

Yes, because real copy is rarely the length the placeholder was. Headlines run long, paragraphs run short, and product names in Indian markets are often much longer than the designer assumed. Designing against real text means the layout problems surface while the designer is still engaged, not after final payment.

We've been stuck waiting on photographs for months. What now?

Launch without them. Use clean, honest stand-ins — product shots on a plain background taken carefully on a good phone are acceptable, and a plain colour block is better than a stock photo of strangers in a boardroom. Then book the shoot as a dated commitment, with a shot list, rather than an open intention.

Should we write the blog before launching the site?

No. The blog is post-launch work and belongs on a calendar with named owners and dates. Launching with an empty blog section is fine; launching four months late because nobody wrote six articles is not.