011–2 weeks
Content audit and model
Inventory of existing content, the content model designed with editors, and the CMS choice with reasons.
Content Platform Build
A site marketing publishes to daily without a developer in the loop, built in eight to fourteen weeks with the content moved over and rankings kept.
The buyer question this answers: Can marketing publish without engineering?
Who this is for
- A marketing team blocked by engineering for every page change.
- A site on an ageing CMS that is slow and unsafe to edit.
- A content operation that needs one source feeding web, app, and email.
Phase by phase
Reference timings for a typical engagement. The written scope gives you the dates for yours.
- 023–4 weeks
Design system and templates
Components and page templates built against real content, with performance and accessibility budgets.
- 032–3 weeks
CMS and editor experience
Fields, roles, workflows, preview, and the integrations editors need.
- 042–3 weeks
Migration
Content exported, cleaned, imported, and every URL kept or redirected.
- 051 week
Launch
DNS switch, redirects verified, sitemap submitted, rankings monitored.
- 062 weeks
Training and support
Editor training, the written guide, and fixes on anything we built.
The stack for this workflow
- WordPress or Sanity, Strapi, Payload
- Next.js frontend for headless builds
- TypeScript
- Cloudflare
- Image optimisation pipeline
- Playwright
- Lighthouse CI
What could go wrong
Every build has risks. These are the ones we plan for on this kind of project, and what we do about each.
Rankings drop after migration.
How we handle itEvery URL is mapped before launch, redirects are tested automatically, and search performance is monitored for two weeks with a plan to respond.
Editors find the new CMS harder than the old one.
How we handle itThey test the editing environment before migration and their feedback changes it.
The site is fast on launch day and slow six months later.
How we handle itPerformance budgets are enforced in CI and image handling is automatic, so editors cannot accidentally slow it down.
Cost model: Fixed scope
A content site with a defined model and template set is a known quantity once the audit is done.
No prices on this page. The scope phase ends with a written quote for your project.
Questions we get asked
WordPress or headless?
WordPress when the site is the whole product and your team knows it. Headless when content feeds several channels or performance and security are the priority. The audit phase ends with a recommendation and reasons.
Will we lose our search rankings?
Not if the migration is done properly, and this workflow exists to do it properly. URL mapping, redirects, structured data, and monitoring are all in scope.
Can editors break the layout?
No. Structured fields and constrained components mean editors change content, not design.
How do you handle images and performance?
An optimisation pipeline resizes and compresses automatically, and a performance budget is tested in CI on every change.
Tell us what you are building.
We reply within one business day with how we would build it, what it would cost, and which engagement model fits.
- 01Tell us what you are building
A short form or an email. No deck required, and "not sure yet" is a fine answer.
- 02A call with an engineer
Within one business day. Technical questions get technical answers, from the person who would build it.
- 03A written scope and quote
Fixed price where the scope is defined. The document is yours whether or not you go ahead.