3 min read
Do You Need Website Copy Before Design Starts?
Waiting for finished copy is one of the easiest ways to lose a month on a website project. Here is how to run copy and design in parallel without compromising either.
Category:
Process
Updated:
Oct 11, 2026

Artyum Grebenyuk
Founder, AGR Studio
Do you need your website copy finished before design starts? No, and holding a project until the copy is done is one of the easiest ways to lose a month. It’s one of the most common questions we hear on first calls, and it makes sense: it feels logical to know what you are saying before deciding how it looks. In practice, content gathering takes most teams several weeks, and the two work better side by side. Here is how we run copy and design in parallel.
Start from what already exists
You almost always have more usable material than you think. To design the homepage, we work from:
Your current website. Even if the messaging is dated, it shows what you offer and how you talk about it today.
Your pitch deck and sales materials. These often hold the sharpest version of your positioning.
Brand guidelines and PDFs. Tone, terminology and the claims you are comfortable making.
A rough doc. Bullet points are enough. Anything you are certain must be on the site speeds things up, because the structure does not need rethinking later.
Where copy is missing, we use clearly marked placeholder text so the layout can move forward.
Why the layout helps you write
Writing into a blank document is hard. Writing into a page where you can see each section and the job it does is much easier. Once the homepage exists as a real build in your browser, you can see how long each heading should be, where proof needs to sit and where a call to action belongs.
Page templates help with the rest of the site. A careers or blog template built with placeholder content shows exactly how much material you need to provide, which turns a vague writing task into a short checklist.
What runs in parallel
Week one to two: we design and build the homepage while your team drafts or refines the homepage copy. We give feedback on it as it comes in.
Remaining pages: templates for services, case studies, team and blog are built with placeholders, and your content drops in as it is ready.
Launch: anything managed in the CMS, such as blog posts, case studies and images, can be added after launch by your team. A missing article never needs to delay the site.
Handling content you cannot confirm yet
Some content is not ready to publish: results a client has not approved, figures still being checked, or dates nobody is sure of. We never invent these. Placeholder case studies are clearly labelled, unconfirmed dates are left blank, and fields for figures you are not ready to share can stay hidden until you switch them on.
Common questions
Will placeholder text end up on the live site by mistake?
Placeholders are clearly marked and checked in final QA before launch. Anything still missing at that point is either hidden or flagged to you.
Should we hire a copywriter before the designer?
Usually not. Design with the copy you have, refine it on the page, and bring in a copywriter only if the messaging clearly is not landing.
What content matters most on a new B2B website?
Case studies are often the strongest asset a B2B site can have. A blog is valuable if your team will keep it going, and it can launch later.

