A capable system needs a clear plan.
A new market needs its own . A brand needs to remain distinctive within shared guidelines. Editors need to work independently. These connections determine whether a platform works in practice. Our dedicated Drupal team brings experience from dozens of websites and platforms for PepsiCo and works with our UX, design and content teams.
Experience across many websites. Focus on your needs.
We consider the experience and the work behind the website together: models, components, local requirements, approvals and technical dependencies. This defines a useful next step, whether that is a new platform, another market or a focused improvement to an existing system.
What we deliver with Drupal
The task shapes the architecture. We establish which functions can be shared, what needs local adaptation and who owns the content.
Websites and brand platforms
Concept, design and development with reusable components and content models that editors can work with.
Rollouts and ongoing development
Shared foundations for further brands, content or markets. Review existing functions and divide releases into manageable steps.
Systems integration
Connect product information, media and other data sources through suitable interfaces, with clear ownership and failure handling.
Editorial workflows and quality
Align roles, content states and approvals with your organisation. Review usability, accessibility and the editorial experience together.
Improve Drupal by finding the actual bottleneck
When changes take too long, a complete system replacement may not be the best response. We examine the installation, extensions and a specific workflow: which tasks repeat, where does work wait and which dependency holds back the next release?
You receive prioritised actions and a reasoned recommendation: improve the existing system, add a bounded capability or prepare a phased migration. Version, maintainability and operations inform that decision.
Bring AI into an accountable editorial workflow
One possible starting point is drafting from approved product information. An agent handles a bounded task while sources, changes and missing information remain visible. Editors review before publication.
We assess whether the interfaces and approvals in your installation support the task. Quality, processing time and revision effort are compared within an agreed pilot scope. We take responsibility for concept and quality.
A first step with a useful result of its own
A Drupal review examines one priority user journey and one editorial workflow. Together with business stakeholders and IT, we identify the bottleneck and propose useful actions with effort ranges.
The next engagement can focus on a single improvement. We agree scope, access requirements, acceptance criteria and costs before starting. Ongoing development follows a shared priority list of functions and content.
How we deliver
Understand the task
Review users, editors, business objectives and the existing system together.
Design the approach
Align the customer journey, content model and components.
Build a focused scope
Implement the priority and address its technical dependencies.
Review together
Validate user tasks, editorial workflows, integrations and release readiness.
Keep improving
Turn experience from actual use into a shared backlog and further releases.
FAQ
Sources and technical context
- Drupal: Workflows
Technical context on states and transitions. Implementation depends on the installation.
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 Drupal platform do next?
Tell us about your website and the most important task. Together, we will find a suitable starting point.
Discuss your Drupal projectSelected 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