Content
Content structured so it stays consistent after launch.
Help shaping page content and the editing model your team will use day to day.
- Good for
- Businesses needing this done properly, once
- Includes
- 4 agreed deliverables
- Pricing
- Quoted on scope, agreed before work starts
What this usually looks like
The problem
Copy is written by several people in different formats, so pages repeat themselves or leave gaps. The editing interface mirrors the old site rather than how the team thinks about content.
How we approach it
We plan the content model — what a page is made of and which parts are editable — then help write and structure the copy that fills it.
What you receive
- Page-by-page content plan
- Editing fields mapped to each section
- Copy editing and structure for agreed pages
- Notes on what is editable and what needs development
Deliverables are confirmed in your proposal. Anything outside that list is quoted before it starts.
What we need from you
- 01Nominate who maintains each content area
- 02Supply source material and subject knowledge
- 03Review the editing model before build
Pricing approach
Content work is scoped per page or as part of a website project. Editing-model planning is included when a CMS is part of the build.
Cost and scope
What this typically costs, and what changes it
Content work is scoped per page or as part of a website project. Editing-model planning is included when a CMS is part of the build.
Published rates and package inclusions are still being confirmed. Anything not confirmed is quoted in writing rather than estimated here — no totals are invented to make the page look complete.
Typical engagement
- Quoted as
- Fixed scope, agreed before work starts
- Review points
- Named in the proposal
- Next step
- A short call, then a written scope
Related work
Where this work appears
- Real Serious Games
Creative & digital experience · 2023
- Heather Grey
Creative direction & digital · 2024
Contribution and engagement details for each project are being confirmed. We do not publish testimonials or results we cannot evidence.
Process
How a project runs
The same checkpoints apply across services, with review points agreed for your scope.
Review
We look at your business, customers and what the website or system needs to achieve. Goals and priorities Opportunities to improve
Plan
Priorities become a sitemap, content requirements and technical approach. Sitemap and feature scope Agreed schedule and review points
Design
You review desktop and mobile layouts and approve the direction before build. Desktop and mobile layouts Design approval checkpoint
Build
The agreed design is built. A staging preview lets you review before going live. Working staging preview Content and functionality review
Launch
Pages, links and forms are checked. Where a CMS is included, your team gets a walkthrough. Launch checks and deployment Editor handover (if CMS included)
Staging previews
Review the working site or application before it goes live.
Handover
Editor walkthrough where a CMS is included in the project.
Support after launch
Support and maintenance terms are agreed in your proposal (to be published).
Good to know
Frequently asked
questions.
Tell us what is not working and what you would like instead. We reply by email, then arrange a discovery call if it looks like a fit.
Reading
Related guides and case studies
Case study · Creative direction & digital
Heather Grey: a restrained identity carried into a small siteA brand with a quiet visual language, and a site that had to stay out of the way of the work rather than decorate it.
Case study · Digital commerce
BFS Plastics: catalogue browsing for a technical buyerWhen the buyer is an engineer, the product page has to answer specification questions before it sells anything.
Other studio services
Developer? Explore the UI Library
The UI Library is a different audience: reusable Payload CMS blocks and React components you install in your own project. It is not a finished website service.
