Introduction
Design is approved, the build is ready, and the project stops for five weeks because nobody has written the About page. Copy is the commonest reason a website runs late, and it is almost always the part both sides assumed the other had covered. This sets out who normally writes what, how to split it so nothing waits, what good copy actually has to do, and who is able to change it once the site is live.
Key Takeaways
- Settle It Before Design: An unassigned page is a page that will be late.
- Nobody Writes It For Free: Copy is scoped work, whoever ends up doing it.
- Split By Page Type: You own expertise pages; they can shape the rest.
- Design Needs Real Words: Placeholder text hides every layout problem.
- Write For The Reader: Plain language is not dumbing down, it is faster.
- Check Who Can Edit Later: The role that edits copy is not the role that designs.
Who Normally Writes What?
Four arrangements exist, and most projects use a mix without ever naming which. Deciding this explicitly is the single cheapest thing you can do to protect the timeline.
- The client writes everything, and the studio edits for structure and length.
- The studio writes everything, after interviews with your team.
- A hired copywriter writes, briefed by both sides.
- Split by page: the client writes anything requiring their expertise, the studio writes the rest.
The fourth is what most projects should do and what few of them agree in advance. Your team knows the product, the objections and the language customers actually use; a studio knows how much fits, what the page has to achieve and where a sentence has to carry the whole message.
Why Does This Decide the Timeline?
Because everything downstream waits for it, and because it is the one task that cannot be parallelised by adding people. A designer can lay out a page without final copy; a build cannot be finished, reviewed or launched without it.
- Design waits, because layout depends on how much text there is.
- Review waits, because nobody approves a page of placeholder text properly.
- Build waits, because content has to be loaded before anything can be checked.
- Launch waits, because the last page written is always the one nobody owned.
- Measurement waits, because a page that is not live cannot be measured.
A Webflow designer UK teams work with should be asking for content owners and dates at scoping rather than chasing them in week six. If a studio does not ask, ask yourself, and put a name and a date beside each page in the page list.
Two Assumptions That Cost Five Weeks
One is about volume, the other about placeholders.
- Assuming writing a page takes an hour. Getting an About page agreed across three stakeholders takes weeks of calendar time, however little writing time it needs.
- Assuming placeholder text is harmless. It hides the layout problems that only appear at real length, so they surface after sign-off instead of during design.
What Does Good Website Copy Actually Have to Do?
Be understood quickly by somebody who is not paying much attention. That is a higher bar than being accurate, and it is the bar most company websites miss.
the GOV.UK writing guidance is unusually concrete about this: plain English is mandatory across the whole estate, sentences over 25 words should be split, paragraphs should run to no more than five sentences, the active voice is preferred because it keeps sentences short, and specialist terms are allowed provided they are explained the first time they appear.
It also notes that people with higher literacy prefer plain English because it lets them understand faster. The commercial consequence for a company site is the part teams resist: writing simply is not writing down to your audience, it is the format in which busy, expert readers prefer to be given information.
- Say what the company does in the first sentence, not the third paragraph.
- Use the words customers use, not the words the industry uses internally.
- Keep sentences short enough to read on a phone in a corridor.
- Explain a specialist term once, at first use, and then use it freely.
- Put the most important information at the top of the page.
- Cut anything that survives only because somebody senior likes it.
A pro tip: read the homepage aloud. Anything you would not say to a customer in a meeting should not be on the page.
How Should the Work Actually Be Split?
By page type, with a named owner and a date against each. This turns a vague dependency into a schedule somebody can manage.
- Homepage: written together, because it is the page everyone has opinions about.
- Service and product pages: your expertise, their structure.
- About and team: yours, because it is your story and nobody else can write it.
- Case studies or client work: studio-drafted from your interviews, approved by you.
- Blog and resources: whoever will own it after launch writes the first ones.
- Legal pages: your adviser supplies, studio formats.
- Small interface text, buttons and error messages: the studio, always.
The last line is worth insisting on. Interface text is a design job, not a writing job, and it is the one place where a studio doing it badly is obvious.
Who Can Change the Copy After Launch?
Whoever holds the editing role, which is deliberately narrower than the design role. This matters because the person who writes copy is rarely the person who should be moving elements around.
Webflow’s content editor documentation sets out the split: content editors can update site copy, media and content items without changing design, they can manage titles and descriptions and publish items, and they cannot make structural or style changes, edit page names or slugs, add custom code or create new content structures. The practical consequence is that you can safely give the editing role to a marketing colleague without risking the build, which is the arrangement most teams actually want and few ask for at handover.
- Decide who edits copy after launch, by name, before handover.
- Give them the editing role rather than full access.
- Train them on one real page rather than in the abstract.
- Agree what needs the studio, so they do not wait for permission they do not need.
Spoke’s client work shows sites built with that division in place.
Conclusion
The project does not run late because writing is hard; it runs late because nobody was named against the pages, so each one waited for somebody who did not know it was theirs. Split the work by page type, put a name and a date beside every page in the page list, insist on real copy before design sign-off, write plainly enough to be understood at a glance, and decide who holds the editing role after launch. A Webflow designer UK companies keep working with is usually the one who raised this at scoping. Spoke handles Webflow web design UK projects end to end, including the awkward conversation about who writes what.
FAQs
Q. Should we pay the studio to write the copy?
Ans. Pay somebody, whether that is the studio, a copywriter or your own team’s time. Copy written by a studio costs more up front and saves calendar time, because they do it as scoped work rather than fitting it around a day job. What fails is assuming it is included when it is not, which is the most common line missing from a proposal.
Q. Can we start the design before the copy is ready?
Ans. You can start, but do not sign anything off. Designing with real copy on the two or three most important pages is the minimum, because layout problems only appear at real length. Placeholder text on every page produces a design that looks finished and stops working the moment words arrive.
Q. Who writes the buttons and error messages?
Ans. The studio, as part of the design. Interface text is a design decision about what somebody should do next, not a writing task that can be handed over, and splitting it produces a site where the pages read in one voice and the buttons read in another. Review it, but do not write it yourself.