Websites that move your brand forward.
A relaunch should advance your brand, editorial work and technology. We connect content models, design systems and web development in a website your team can operate and improve.
A relaunch starts with the work your website must do.
Your offering grows, new markets join and editors need help with small changes. Meanwhile, search traffic, enquiries and live campaigns must keep working. We start by defining the website’s tasks and where the existing implementation gets in the way. Architecture, CMS and framework follow from those needs.
A strong brand needs a platform that can grow with it
Creative Engineering brings , design and development together. Good components make the brand recognisable and give editors clear choices. Accessible interaction, reliable forms and measurable loading behaviour are part of quality. AI can prepare drafts, code or tests; we take responsibility for concept and quality.
Three decisions before the first sprint
Improve or rebuild?
We assess whether focused changes within the existing CMS are enough. A new interface alone does not resolve unclear content or workflows.
Coupled CMS or headless?
An integrated system can simplify editing and operations. A separate frontend can suit multiple channels or specific requirements. Preview, hosting and maintenance are part of the comparison.
Which components do editors need?
We develop components around real content and user journeys. Permitted variations, media formats and text lengths help pages stay consistent after launch.
Migration: make a decision for every important address
Before migration, we inventory URLs, content types, media and integrations. Relevant content is retained, consolidated or deliberately removed. Old URLs receive appropriate redirects where a suitable replacement exists; unknown addresses return a real 404 response.
A representative trial also covers longer copy, missing images, language relationships and exceptions. We plan how to handle changes during migration, cutover, rollback and ownership. Preserving every search ranking cannot be guaranteed.
SEO and AI discovery depend on useful, accessible content
Core content must be readable by people and accessible to search services. We review internal links, canonicals, language versions and how the main content is delivered. Metadata and structured data must match what the page actually says.
The fundamental SEO requirements still apply to Google AI Overviews and AI Mode. A special AI file or schema does not guarantee inclusion. For other AI services, we consider their access mechanisms and the verifiable information the content provides.
What we actually review before launch
Content and editing
Representative page types, real copy lengths, previews and approvals. A layout containing placeholder copy is not a complete editorial review.
Usability and accessibility
Keyboard journeys, visible focus, text enlargement, clear form errors and appropriate screen reader checks. Automated checks cover only part of this work.
Performance and integrations
Loading budgets, large media, relevant devices and both success and failure cases. Lab measurements and field data are evaluated separately.
Enquiries and operations
From a completed form to the agreed destination: acceptance, delivery and handling are distinct steps. Monitoring, ownership and rollback are documented.
A shared foundation for continued improvement
After launch, we prioritise agreed goals, feedback and reliable measurement. Small improvements to content and components can be more useful than another major rebuild.
Total cost includes CMS licences, hosting, third parties, maintenance, technical updates and editorial work. Reuse and suitable automation can reduce effort. We assess whether they do so in your project through quality, maintainability and actual handling time.
How we deliver
Define goals and review the estate
Review user tasks, content, systems and operations. Output: a prioritised scope with reasoned architecture decisions.
Connect content and design
Test key journeys with real content. Output: content models, components and a reviewable preview.
Build and migrate
Develop the agreed features and rehearse content migration. Output: a usable version with explicit open issues.
Review the complete journey
Check content, interaction, redirects and enquiries. Output: an acceptance record and decisions for launch.
Support launch and operations
Plan cutover, monitoring and ownership. Output: an operable website and a prioritised improvement plan.
Questions about web development and relaunches
Sources and technical context
- Google: AI features and your website
SEO fundamentals also apply to AI Overviews and AI Mode; no inclusion guarantee.
Websites, CMS and AI in practice
Payload & MCP: From product knowledge to reviewed content
The product knowledge exists, but publishing the next page still takes many manual steps. A practical example shows how a CMS, AI and editors can work together.
Modernise your CMS: Start with the bottleneck
Retain, extend or renew your CMS? Connect editorial work, UX and AI around a specific task and define a practical next step.
GEO in practice: Customer questions and evidence
A practical GEO review: choose customer questions, check content gaps and technology, add evidence and assess suitable enquiries.
What should your website make possible next?
Share your current website and the most important task for the relaunch. We will discuss what can be retained and which first step would help your team most.
Discuss your relaunchSelected website and platform projects
These Drupal projects show selected aspects of our platform work. Each case describes its own scope.
PEPSI
Pepsi.com: Drupal relaunch for the US market
Lipton
UK Website Launch for the Kombucha Range
poppi
UK Website Launch
A useful first step with a clear scope.
We agree the deliverables, inputs, acceptance criteria and costs before starting. A first conversation helps identify the right engagement.
Platform review
One CMS, one customer journey and one editorial workflow. Receive prioritised improvements and a reasoned recommendation for your next step.
Discuss: Platform reviewCMS and AI pilot
One content type, one source and one review path. Assess accuracy, usability and revision effort within a bounded workflow.
Discuss: CMS and AI pilotUX and implementation pilot
Improve a key customer journey. Use a prototype and agreed user tests to inform the implementation decision.
Discuss: UX and implementation pilotMake your expertise visible
Bring expert knowledge, supporting evidence and original material into a useful content page and agreed adaptations.
Discuss expert content