Content before design: which model actually costs you less time

The articles arguing for content-first or design-first cited below are written for designers, about workflow. If you are the one commissioning the site, the workflow argument is beside the point. The real question is which model makes you the bottleneck, and for how long.

There are three models worth knowing before you sign anything: content-first, design-first, and a third option, draft-first, that neither of the two camps cited here names. Whichever one you pick, someone spends time before design work opens. The question is who, and how much.

What "content-first" actually means

Content-first is a build order, not a philosophy. Per Progress's comparison of the two strategies, content-first means producing all the copy, images, forms, and data for a site before anyone designs the interface around it. Design-first, by contrast, means designing with placeholder text such as lorem ipsum and fitting real content into the finished layout afterward.

The Interaction Design Foundation defines content-first the same way: content comes ahead of aesthetics, not instead of them. In practice, for a buyer, content-first means you hand over a working draft of every page's words and assets before design work starts, not after.

Why designers argue for content first

The case for content-first is a case against rework. The Interaction Design Foundation's argument is that designing around real content avoids re-engineering a layout later, and keeps collaboration clearer because everyone is working from the same material. Progress adds two more concrete benefits: content-first reduces scope creep, and it protects SEO copy from being trimmed to fit a layout that was never built with that copy in mind.

Both arguments assume the same thing: the content exists before the layout does. That assumption is where the buyer's cost shows up.

The trade-off the methodology debate leaves out

Every content-first agency cited in this piece requires real content from the client before design starts. Made by Speak's process opens with a sitemap and content strategy meeting, and the agency states plainly that content-first "may take longer initially," which is its own admission that the model shifts time to the front of the project, before design work begins.

That time has to come from somewhere. If it's not the agency's, it's yours. Content-first is a reasonable build order, but it is not free: it is a decision to make the client the bottleneck at the start of the project instead of somewhere in the middle.

What you're really paying for with design-first

Design-first has the opposite problem. A layout built around a one-line placeholder heading does not automatically hold up once the real heading runs two lines. As Northwoods puts it, designers can format meaningless placeholder copy however they please, but when real content comes into play very late in the process, suddenly nothing seems to fit.

The Interaction Design Foundation names the same failure modes from the other direction: designing without real content risks misaligned layouts, a voice mismatch between the design's tone and the copy's actual tone, and calls to action that were never built into the design because no one knew yet what the call to action should say. Design-first doesn't remove the content work. It defers it, and adds a rebuild on top.

Follow the incentive

It's worth asking who benefits from the advice you're reading. TJ Creative argues for content-first and recommends running content and design in parallel, but the same TJ Creative post positions its own content-writing service as the fix, so its content-first advice doubles as advice to buy content from an agency that writes content.

Made by Speak's content-first process runs the other way: it requires the client to supply real content assets, and the agency's own post suggests hiring an external writer if you need to move faster. Either way, in both of the content-first exemplars cited here, the writing effort lands on the client, whether that's the client's own time or a separate check to a copywriter.

None of this makes content-first bad advice. It means the advice, read carefully, tells you where the cost sits before you agree to the model.

What it actually costs you in time

This isn't theoretical. Per our guide on whether a web designer writes your website content, client-supplied content is the number one reason projects run late, and the example on record is a 14-page site that stalled six weeks waiting on copy. Design was not the delay. Content was.

The pattern holds across build timelines generally. Per our guide on how long a website actually takes, most of a build's calendar time is spent waiting on content and revisions, not on design work itself. If you choose content-first, that waiting happens before design opens. If you choose design-first, it happens later, on top of a rebuild.

Is there a third option? Draft-first

Both models above assume the client either writes content from a blank page (content-first) or reacts to a finished design with placeholder copy (design-first). There's a third option that skips both extremes: draft-first, where the builder drafts the pages from raw material, and the client edits a finished draft instead of writing from nothing.

This works because editing is cheaper than writing. On the same guide cited above, Polly Clover's published pricing puts a number on the gap: editing an existing draft costs $325 for the first page, while writing a first page from scratch costs $425. The blank page is what stalls people, and the fastest way past it is to not start from one.

Draft-first has its own trade-off, and it's worth stating plainly: the client still supplies raw material, meaning the offer, the audience, a few paragraphs of description, and photos, and still has to review the draft promptly once it exists. This is not a way to skip involvement. It changes what you're being asked to do, from writing to editing.

What to hand over before design starts, whichever model you choose

Regardless of which of the three models you pick, five things need to exist before design work can move fast:

• —An outline or sitemap of the pages you actually need
• —Your offer, written in plain words, even roughly
• —Photos and logo files
• —Any legal or compliance text that has to appear on the site
• —One named person who signs off on decisions

Per our guide to website brief best practices, how much detail you need to supply up front tracks the payment model you're working under: a build-first arrangement can run on a brief as short as four fields, while deposit-billed models expect a fuller document before anyone starts.

When content and design overlap instead of running in sequence

None of the three models above runs as cleanly in practice as it sounds on paper. Draft-first has the builder drafting pages while your raw material is still coming in. Content-first, done honestly, still involves design decisions, like a sitemap, while the copy is being written. Strict sequencing, content fully done, then design fully done, is closer to a planning fiction than something either side actually waits for.

One case is content-first without any extra effort: a redesign of a site that already has content on it. If the words already exist, there's nothing left to write before design starts, which puts a redesign in the content-first category by default, not by choice.

What is content in design?

Content is not just the visible copy on a page. Per the same Interaction Design Foundation definition cited above, content-first covers structure, imagery, data, and calls to action, in addition to the words themselves. A page's content, in that sense, is everything a reader interacts with, not only the sentences.

How Press handles this

Disclosed plainly, since it's relevant here: Press runs on a draft-first model. The brief asks for four things, your name, your email, your industry, and a field labeled "what goes in it," with instructions to write one thought per line, sections, services, anything you'd say to someone over coffee. That's raw material, not a copywriting assignment.

From that material, the build sketches the site's structure, drafts the pages, sets the style, and polishes the details. You get a finished draft to react to, not a blank page to fill. Per how Press's process works, the preview is free and arrives as a full working site within five working days, covering up to four pages plus one form or integration. Keeping it costs $299, flat, one time. After you keep it, you get ten days of unlimited revisions, including edits to the copy itself.

Questions