One platform for several tourism and culture brands

The context

An organisation with several brands and digital projects aimed at the tourism and cultural sector, where each new engagement tended to become a standalone system. The result was predictable: very similar functionality repeated across different repositories, and a maintenance cost growing linearly with the number of projects.

The underlying decision

Rather than keep delivering isolated projects, we defined common architectural patterns — booking, content management, multi-tenant deployment — and applied them across the portfolio. Each brand keeps its own configuration and identity but shares the core.

• Laravel back-end with the booking and content domain as a reusable base.
• Vue and Nuxt front-end with server-side rendering, designed for multilingual search visibility from the start.
• Multi-tenant deployment with per-instance configuration and centralised publication.
• Administration of the AWS servers and the PostgreSQL databases for each brand, with continuous deployment through GitHub Actions and tested backups.
• AI-assisted development workflows adopted across the team, with project-level conventions.

The role of technical leadership

The engagement was not development alone. It covers the full technical function: architecture, delivery, hiring strategy and vendor decisions, reporting directly to executive leadership. That is the kind of relationship that makes it possible to plan technology over twelve months rather than per project.