Why Agencies Ask for Content Before Design
Updated 3 November 2026
Jump to section
Agencies ask for your content first because a page is shaped by its real words and images, not the other way around. A headline's true length, the number of products, the depth of an "About" story: each one changes the layout. As designer Jeffrey Zeldman put it, "Design in the absence of content is not design, it's decoration" (2008). Designing around placeholder text just hides the problems until launch, when they cost you a revision round to fix.
What "content before design" actually means
Content before design means the real text, images, and structure are ready, or at least planned, before the visual work starts. It does not mean every word is final. It means the designer knows what has to fit.
The content includes your page copy, headings, product details, photos, logos, and the list of pages the site needs. With those in hand, a layout can be built to hold them.
Without them, the designer is guessing. A guess looks fine in the mockup and falls apart the moment your actual paragraph runs three lines longer than the fake one.
Why placeholder text hides problems
Placeholder text, the "lorem ipsum" filler you see in blank mockups, hides problems because it is always neat. It sits in tidy blocks of even length. Real writing never does.
Your real headline might be two words or twelve. Your product list might be six items or sixty. Your team page might have three people or thirty.
Each of those changes the design. A hero built for a short slogan breaks under a long one. A grid drawn for six products looks empty with three and cramped with twelve.
Nielsen Norman Group makes a similar point in its guidance on layout and content: "design the layout and the content toward each other". It also says to test layouts with real content rather than convenient filler.
Design the container to fit the thing, not the thing to fit the container.
Why the content stage is where projects stall
The content stage is where website projects most often stall, and it stalls on the client's side, not the studio's. The design and build are predictable work with a clear owner. The words and photos are not.
In our experience, delays most often sit on the client side, not the build. The timeline lives or dies on how fast text, images, and product details arrive.
This is exactly why an honest studio asks for it early. It is not bureaucracy. It is the studio trying to protect your launch date from the one delay it cannot control.
A common trap is approving a beautiful design fast, then treating the writing as an afterthought. The site then waits, half-built, for the part nobody scheduled.
What content should you prepare?
You should prepare the words and the assets, in rough form at least, before design begins. Perfect is not required. Present and structured is.
| Content to prepare | Why the designer needs it |
|---|---|
| Page copy and headings | Sets real text length and hierarchy |
| Product or service list | Decides grid size and page count |
| Photos, logo, brand colors | Fills image slots and sets the palette |
| Contact details and links | Places calls to action correctly |
A practical order helps. Decide the pages first.
Draft the copy, or agree who writes it. Gather the images. Then hand the set over as one package, rather than drip-feeding it during the build.
If writing is the bottleneck, say so early. A studio can quote copywriting into the project cost far more easily at the start than halfway through a stalled build.
Frequently asked questions
Does my content have to be final before design starts?
No, it has to be close enough that the shape is set, not polished to the last comma. The designer needs the real length of your headlines, the real number of products, and the real photos. Final wording can be tightened during review. What cannot be faked is the structure, because that is what the layout is built to hold.
Can't the designer just use placeholder text?
They can, but it usually costs you later. Placeholder text is uniform, so a design built on it looks perfect and then breaks when your real, uneven content arrives. The gap between the neat mockup and the messy reality is where extra revision rounds come from. Real content up front buys a design that survives contact with your words.
What if I don't have content ready yet?
Tell the studio before the project starts, so writing and photography can be planned in. Many builds include copywriting as a paid add-on, and agreeing that early is far less expensive than discovering the gap mid-build. A site with no content plan is a site that will sit unfinished, so treat the content as part of the project, not a step you handle after.
Why does the agency need my photos so early?
Because images set the layout as much as the words do. A hero section, a product grid, and a team page are all designed around the real pictures that go in them. Stock-style filler behaves differently from your actual photos, which is one reason real photos beat generic stock for trust. Handing over final images early lets the design be built around them once, not reworked later.
Does content-first design apply to a small site too?
Yes, it applies to any size, and small sites feel the effect just as sharply. A five-page site still has headlines of a real length and a real number of services to show. If anything, a small site has less room to absorb a surprise, so a paragraph that runs long throws off a bigger share of the page. The principle scales down as cleanly as it scales up.
Getting your content ready before we design
Storming Solutions builds custom-coded websites and runs SEO, AEO, and GEO for Malaysian businesses from Kuala Lumpur, and we ask for your content early on every build. Not to slow you down, but to keep your launch date honest.
Our stance: a design drawn around real content ships once and holds, while a design drawn around filler gets rebuilt when reality lands.
Not sure how to pull your content together? Ask us on WhatsApp and we will send you a simple checklist, or see how we run projects on our web development service page.