Why your website launch will be late, and it’ll almost certainly be the content

Your website project will probably run late, and the delay almost certainly won’t be the build. It’ll be the content. Somewhere around week six a project that looked healthy on the plan stalls, everyone goes hunting for the bottleneck, and what they find is 40 empty page templates and nobody who was ever actually told to fill them. The design is signed off. The developers are ready. The words don’t exist.

The work that’s always late is the work nobody was assigned

Design and build are staffed work. They sit inside the agency, on someone’s job description, tracked against a date that someone is paid to hit. Content sits nowhere. By default it’s the client’s job, which in practice means it belongs to whoever has the least time for it and the least incentive to admit they’re behind.

The trap is the sitemap sign-off. Approving a 40-page structure feels like a decision, and it is one, but it’s also a quiet promise to produce 40 pages of finished copy. Nobody converts that promise into hours. The marketing manager who approved it pictured a finished website. What they actually committed to was a month of writing they have no room for, sitting on top of the job they already do full-time.

By the time this surfaces, the framing has already gone wrong. The question in the room becomes ‘where’s the website’, when the honest question is ‘where’s the content’. Those have different answers and, more to the point, different owners.

Why the agency gets blamed for a problem it can’t fix

Agencies take the reputational hit for content delays because the timeline shows a launch date, not a writing schedule. The client sees a missed launch and remembers that the agency missed it. What actually happened is that the project hit a dependency the client owned, and nobody made enough noise about it early enough to matter.

A developer can’t build a page around copy that doesn’t exist yet. They can drop in placeholder text, but then design decisions get made against fake words. A layout that looked balanced with three tidy paragraphs of lorem ipsum falls apart when the real 600-word service description turns up, and the work gets done twice. So the build pauses. The pause registers as agency slippage, even though the thing blocking it is sitting in the client’s inbox under ‘to do’.

The better agencies see this coming and write ‘client to supply final content by week X’ into the plan. That clause protects the agency and does almost nothing for the project, because a line in a Gantt chart has never written a page of copy in its life. The dependency is real. The accountability behind it is fiction. It’s also why a sensible build estimate and a sensible launch date are rarely the same number; we’ve written separately about how long a website actually takes to build.

How long does website content actually take to write?

Far longer than anyone budgets for. As a planning assumption, budget the better part of half a day for a substantial page: a proper service description, a considered about page, a category page with real selling copy. That covers the drafting, getting it past an internal reviewer, and the round of changes that always follows. Run that across a 40-page site and the content alone is roughly 20 working days of one person’s time.

Twenty days that went into nobody’s calendar. And the person writing them is almost always doing it in the cracks between their real job, which stretches those 20 working days across two or three calendar months. That’s the optimistic version, where the copy gets approved first time. It rarely does. Internal sign-off on words is where everyone in the building suddenly discovers they have an opinion, and where a single page can sit for a fortnight waiting on one director’s feedback. The same dynamic that drags out design revision rounds hits copy twice as hard, because everyone believes they can write.

This is the sum nobody does before signing. The build timeline gets picked apart line by line. The content timeline is assumed to be free, instant, and somebody else’s problem. It’s none of the three.

Should you just pay the agency to write it?

Often, yes, and it’s frequently the cleanest fix available. If the agency has real copywriters, handing them the content removes the dependency that wrecks most timelines, and you’re paying people whose job is to hit the deadline rather than fit it around something else. The catch is that not every agency offering content actually writes well. Plenty will happily bill for copy that’s really just your bullet points reworded, because content was an upsell rather than a craft. Ask to see writing samples from live client sites, not a portfolio page, and ask who specifically would be doing the work.

The other catch is cost. Agency-written content is rarely cheap, and you’re paying agency rates for something a freelancer might do for less. Set that against the cost of a launch slipping by two months, the internal hours lost to a marketing manager writing pages at 9pm, and the opportunity cost of a site that still isn’t live, and the sum often comes out in the agency’s favour. The mistake is treating ‘we’ll write it ourselves’ as the free option. It isn’t free. It’s just a cost that never shows up on the invoice.

How do you stop content from delaying the launch?

You decide who is writing the content, and how it’s paid for, before you sign anything. Content is either a line item with an owner and a budget, or it’s the thing that quietly sinks your date. There is no version where it sorts itself out on its own.

A few moves that work:

• Name one content owner. A single person accountable for every page existing, even if they don’t write all of it themselves. ‘The team will sort it’ is the exact phrase that turns content into nobody’s job.
• Cost the writing properly. If your content owner is a marketing manager whose week is already full, the real options are a freelance copywriter, a content package bought from the agency, or a smaller launch. Freelance rates commonly run £350 to £600 a day (roughly $470 to $810 at late-May 2026 exchange rates), broadly in line with the Professional Copywriters’ Network’s 2025 industry survey. Choose one on purpose instead of defaulting into the first by accident.
• Cut the page count. A lot of 40-page sitemaps are really 15 pages of content and 25 pages of optimism. Launch on the 15 that earn their place and add the rest once they’re written. A small site that exists beats a big one that doesn’t.
• Define ‘content ready’ in writing. That means final copy, signed off, in the format the agency asked for. Not a shared doc of rough notes the developer is silently expected to turn into publishable prose.

You have more influence over this at the contract stage than at any point afterwards, and the contract stage is exactly where content gets waved through as a detail. Settling who owns the words belongs in the same conversation as the contract terms worth checking before you sign.

What to do when you’re already mid-project and the content isn’t coming

If you’re eight weeks in and looking at empty templates, stop pretending the original plan still holds. The launch you scoped is not the launch you’re getting on the date you first agreed. The only real question now is what gives: the date, the scope, or the budget.

Phasing the launch is usually the least painful answer. Go live with the pages that are actually written, the home page, contact, the core service or product pages, and publish the rest on a schedule afterwards. A live site doing a job is worth more than a complete one that’s still three months out.

If the budget can stretch, buy the writing out. A decent copywriter will clear in days a backlog that an overstretched internal owner would leave untouched for months, and that cost is almost always smaller than the cost of the delay. Where there’s an existing site, porting the serviceable copy across as a stopgap and improving it in place after launch beats blocking go-live on a full rewrite of everything at once.

The one approach that fails is waiting. Content that’s two months late because nobody owns it does not become less late because a launch date is bearing down on it. It just becomes later, and now it’s holding up a live launch instead of a staging one.

So before you approve that sitemap, ask the unglamorous question: who is writing every page on this, by when, and paid how? If nobody in the room can answer, you’ve found your delay already. It’s just sitting eight weeks in the future, waiting for you to arrive.