Write the Content First. Seriously.
If you’re planning a website project and wondering whether to write your content before or after design, the answer is clear: write your content first. Not a rough draft. Not placeholder text. Real, structured content that reflects your actual messaging, proof points, and page goals. Design should respond to content, not the other way around. When you reverse this order, you end up with beautiful pages that say nothing meaningful, and a painful scramble to fill empty sections weeks after the design was “approved.”
This isn’t a niche opinion. It’s a lesson earned from watching dozens of website projects stall, bloat in cost, or launch with weak pages because the content wasn’t ready when it needed to be. In our projects at NexusBond, content readiness is the single most common cause of delays. Not design revisions. Not technical issues. Content.
Let’s break down why this happens, what “content first” actually means in practice, and how to structure your project so content and design work together rather than fighting each other.
Why the “Design First” Approach Fails
The typical website project follows a familiar sequence: strategy workshop, wireframes, visual design, content population, development, launch. Content is treated as something that fills in the blanks once the design is done. On paper, this sounds reasonable. In practice, it creates three predictable problems.
Problem one: design decisions get made in a vacuum. When a designer creates a homepage layout without knowing what the company actually needs to say, they’re guessing. They’ll allocate three lines for a headline, a short paragraph for a value proposition, and maybe a grid of three feature boxes. But what if your core differentiator requires a comparison? What if your buyers need to see credibility signals above the fold because they’re in a low-trust industry? The designer can’t account for any of this without content direction.
Problem two: content gets squeezed into the wrong shapes. Once a design is approved, there’s enormous pressure to keep it intact. Nobody wants to reopen a signed-off mockup. So the content writer is handed a template and told to “fill in the sections.” This is backwards. You end up trimming important messages to fit a text box, or padding thin sections to match a layout that assumes more substance than exists. The result is pages that look polished but read like they were written by someone who doesn’t understand the business.
Problem three: the project timeline doubles. Design gets approved in week four. Then everyone realises the content isn’t ready. The marketing team scrambles to write copy. Subject matter experts are unavailable. Drafts go through multiple rounds of internal review. Meanwhile, the developer is waiting. The designer is waiting. The launch date slides. We’ve seen projects that were scoped for twelve weeks stretch to six months, almost entirely because content wasn’t treated as something that needed to be finished early.
What “Content First” Actually Means
When we say write content before design, we don’t mean you need polished, publication-ready copy before anyone opens Figma. “Content first” means that the substance, structure, and hierarchy of your messaging are defined before visual design begins. Here’s what that looks like in practice.
Page-level content plans
Before anyone designs the homepage, you should have a document that outlines what the page needs to accomplish, who it’s speaking to, and what sections it requires. For a homepage, that might include a primary headline and supporting statement, a credibility section (logos, stats, or awards), a problem/solution narrative, three service or product entry points, social proof, and a clear next step. Each section should include the actual messaging direction, not “insert testimonial here” but the specific testimonial you’ll use and why it was chosen.
Messaging frameworks, not lorem ipsum
A messaging framework captures your core value proposition, key differentiators, audience-specific pain points, and proof points in a structured format. This becomes the source material for every page on the site. When your designer sees that your primary audience is CFOs evaluating risk management platforms, and your key differentiator is a 97% client retention rate backed by named case studies, they’ll make very different layout decisions than if they’re working from a brief that says “we help businesses succeed.”
Proof assets gathered and organised
One of the most overlooked parts of content-first planning is assembling your proof library before design starts. This means collecting testimonials, case study data, client logos (with permission), certifications, awards, performance metrics, and any third-party validation you have. When these assets exist before design, the designer can build layouts that showcase them effectively. When they don’t exist, you get generic placeholder sections that never quite land. Our content and proof systems guide explains how we structure this process so that proof assets are ready when the project needs them, not scrambled together at the end.
The Real Relationship Between Content and Design
Framing this as “content OR design first” is a slight oversimplification. The real answer is that content strategy comes first, then content and design develop in parallel, with content leading by at least one stage. Think of it as a relay race where the content team always has the baton first.
Here’s a typical sequence in a well-run project:
- Week 1-2: Discovery and content strategy. Define audience segments, messaging pillars, page inventory, and content requirements for each page.
- Week 2-3: Draft content for priority pages (homepage, key service pages, about page). Simultaneously, the designer begins working on brand direction, typography, and colour systems.
- Week 3-4: Content drafts are reviewed internally and revised. The designer creates wireframes informed by the content structure and hierarchy from the drafts.
- Week 4-6: Visual design applied to wireframes, using real content. Remaining pages are drafted in content. Design and content are reviewed together, as a unit.
- Week 6-8: Development begins with final content and approved designs. Minor copy refinements happen during build, but the substance is locked.
Notice that content is never more than a week behind design. In fact, for the most important pages, content is finished before the designer starts the layout. This is the model that consistently delivers projects on time and produces pages that actually convert.
What Happens When You Design Around Real Content
The quality difference between a page designed around real content and one designed around placeholder text is striking. Here are specific ways it shows up.
Headlines that fit. When a designer knows the headline is “We reduce procurement costs by 22% in the first year” rather than “Lorem ipsum dolor sit amet,” they size the type, choose the weight, and position the element to give that statement maximum impact. They might add a supporting data visualisation. They might adjust the hero section to accommodate a subheadline that adds context. None of this happens when the headline placeholder is three words of gibberish.
Sections that earn their space. Real content reveals which sections need breathing room and which can be compact. A detailed case study summary needs more vertical space than a list of bullet features. A testimonial from a recognisable brand executive might deserve a prominent, standalone treatment. A section explaining a complex process might benefit from a stepped visual layout. These decisions can only be made well when the designer knows what’s going in each section.
Layouts that guide the reader. Good web design creates a visual hierarchy that matches the content hierarchy. The most important message should be the most visually prominent. Supporting points should be secondary. Calls to action should appear at natural decision points in the narrative. When design is built on real content, this hierarchy emerges naturally. When design comes first, you’re hoping the content will happen to fit a hierarchy that was decided arbitrarily.
Forms and CTAs placed at the right moment. Where you place a call to action matters enormously. After a compelling proof section? After addressing a key objection? After showing pricing? These placements should be based on the persuasion logic of the page, which is a content decision. Designers who have access to the full page narrative place CTAs more effectively than those working from a generic wireframe pattern.
The Common Objections (and Why They Don’t Hold Up)
“We can’t write content without seeing the design”
This is the objection we hear most often, and it reveals a misunderstanding of what content creation involves at the early stages. You’re not writing pixel-perfect copy that fits exact character counts. You’re defining what each page needs to say, in what order, with what supporting evidence. This is strategic work that doesn’t depend on knowing whether the background is blue or white. The exact word count and formatting of each section can be refined once the layout takes shape, but the substance needs to exist first.
“Our team doesn’t have time to write content that early”
This is actually an argument for starting content early, not against it. If your team is stretched thin, the worst time to dump a content workload on them is during the design review and development phase when decisions are being made quickly and delays are expensive. Starting content work in the first two weeks, when the project pace is more measured, gives your team the time they need. It also surfaces any gaps in your messaging or proof assets early enough to address them without derailing the timeline.
“The designer needs creative freedom”
Content-first doesn’t mean the designer works from a Word document and renders it literally. It means the designer has the raw material to make informed creative decisions. Great designers actually prefer working with real content because it gives them something meaningful to respond to. Designing a page about cybersecurity risk assessment is a fundamentally different creative challenge than designing a page about wedding photography. The content shapes the visual tone, the imagery direction, and the overall feel of the page. More information produces better design, not worse.
“We’ll just use placeholder content and swap it later”
This sounds practical but almost never works cleanly. Placeholder content creates a false sense of progress. Stakeholders approve a design that looks complete, only to discover later that the real content doesn’t fit the approved layout. The three-word placeholder headline becomes a twelve-word real headline. The two-sentence description becomes four sentences. The testimonial section assumed three short quotes, but you only have one long one. Every mismatch creates a design revision, and by this point in the project, revisions are expensive and slow.
How to Get Your Team Ready to Write Content First
Shifting to a content-first approach requires some upfront investment, but it’s simpler than most teams expect. Here’s what to do before your website project kicks off.
Audit your existing content. Go through your current website and categorise each page’s content as “keep and refine,” “rewrite completely,” or “remove.” This exercise alone typically cuts the content workload by 30-40% because most websites have redundant or outdated pages that shouldn’t carry over to the new site. It also highlights which pages need the most attention.
Interview your sales team. Your salespeople hear objections, questions, and decision criteria every day. Spend an hour with your top two or three reps and ask them: what do prospects ask most often? What makes them hesitate? What finally convinces them? The answers to these questions should directly shape your website content. Sales conversations are the richest source of messaging insight most companies never use.
Collect proof assets systematically. Don’t wait until a designer asks for a testimonial to go hunting for one. Build a simple spreadsheet listing every piece of evidence you have: client quotes, performance data, case study material, certifications, awards, media mentions, partnership logos. Rate each one for strength and relevance. Identify gaps. If you have great proof for one service line but nothing for another, that’s a problem you want to solve before the project starts, not during the design review.
Assign a content owner. Every website project needs one person who is accountable for content delivery. Not responsible for writing every word, but responsible for ensuring drafts are produced, reviewed, and approved on schedule. Without this role, content tasks get distributed vaguely across the team and nobody feels the urgency until the deadline has passed.
Set internal review deadlines that precede design milestones. If wireframes are due in week three, content drafts for those pages need to be reviewed and approved by week two. Build these content deadlines into the project plan as hard dates, with the same weight as design or development milestones. When content deadlines are treated as soft targets, they slip. Every time.
When Design Can Legitimately Come First
There are a narrow set of situations where starting with design makes sense, and it’s worth acknowledging them.
Brand identity projects. If you’re simultaneously developing a new visual identity, the design team may need to establish brand foundations (colour palette, typography, visual language) before content can be formatted. Even here, though, the content strategy and messaging framework should be developed in parallel. The brand work informs how the content looks, not what it says.
Highly visual or portfolio-driven sites. For businesses where the work speaks for itself (architecture firms, photographers, product designers), the visual presentation of the portfolio may drive the site structure more than written content. But even in these cases, the portfolio needs to be curated and organised before design begins. Selecting which projects to feature, in what order, with what supporting context, is content work.
Rapid prototyping or MVP sites. If you’re building a minimal viable site to test a new product or market, speed matters more than content perfection. A designer might create a simple template that you populate with “good enough” content. This is a conscious tradeoff, and it only works if everyone acknowledges the content will need serious revision before the site can perform at scale.
In all three cases, notice that content thinking is still happening early. The difference is that the formal copywriting may happen alongside or slightly after initial design exploration, rather than strictly before it.
The Cost of Getting This Wrong
Let’s talk numbers, because the cost of design-first content problems is real and quantifiable. A mid-market website project typically runs between £30,000 and £120,000 depending on scope. When content delays push a twelve-week project to eighteen weeks, you’re paying for six additional weeks of agency or contractor time. Even at modest day rates, that’s £10,000 to £25,000 in direct cost overruns.
But the bigger cost is opportunity cost. Every week your new website isn’t live is a week you’re running on the old site, with its outdated messaging, weak proof, and poor conversion rates. If your website generates even a modest pipeline, a six-week delay could mean tens of thousands in deferred revenue. For companies in competitive markets where prospects are comparing three or four vendors simultaneously, a slow launch means lost deals you’ll never know about.
There’s also the quality cost. Pages built on placeholder content and retrofitted with real copy almost always underperform pages built on content from the start. The messaging doesn’t flow as naturally. The proof points feel bolted on rather than integrated. The visual hierarchy doesn’t quite match the content priority. These subtle misalignments add up to lower conversion rates, higher bounce rates, and a site that looks professional but doesn’t persuade.
Making the Shift Practical
If you’re about to start a website project, here’s what to do right now. Before you brief a designer or select a template, sit down with your marketing lead and answer three questions. First: what are the five most important things a visitor needs to understand about our business within sixty seconds on our site? Second: what proof do we have that those things are true? Third: for each key page, what is the one action we want the visitor to take?
Write the answers down in plain language. Don’t worry about clever headlines or polished prose. Get the substance right. Share these answers with your designer, your developer, and anyone else involved in the project. This single document will do more to keep your website project on track than any number of mood boards or wireframe iterations.
The most important thing to remember is this: design can make good content shine, but it cannot rescue content that doesn’t exist. Start with what you need to say. Then figure out the best way to present it. That order produces better websites, faster projects, and pages that actually convert visitors into customers.
