The split
What is shared, what is not, and who decides
The line drawn here is the whole design. Drawn too tightly, properties build shadow sites; drawn too loosely, the group has four codebases with one invoice.
| Option | Examples | Who changes it | What goes wrong if this is misplaced | Best for |
|---|---|---|---|---|
| Shared, centrally owned | Booking path, checkout, accessibility, performance budget, analytics, security, the component library. | The group, on a release cycle, with properties consulted. | Four different checkout experiences and no comparable numbers across the estate. | Everything a guest should experience identically. |
| Per property, locally owned | Imagery, room descriptions, offers, restaurant content, local information, the language mix. | The property, published directly, without a developer. | Content that goes stale because changing it needs a ticket, and properties that stop trying. | Everything that is genuinely local. |
| Negotiated | Homepage layout, navigation, how far brand colours may flex for a distinct property. | Group and property together, with a named arbiter. | The argument that stalls the project, if it is left until build. | Settle these first. They are the ones that cost time. |
Arabic across a group
One property serves a mostly Arabic market and another does not
A city hotel taking domestic business travel and a resort taking regional leisure have different language mixes, and forcing an identical bilingual treatment on both is a compromise that fits neither. The platform should support a per-property default language and a per-property emphasis while keeping both directions fully designed rather than mirrored.
The practical consequence is in the content model rather than the code: a property must be able to publish a page in one language and schedule the other, without the site showing a half-translated page in the meantime. Groups that miss this end up with English pages carrying Arabic navigation, which reads as neglect.
Sequence
How a group build stays one build
Agree the split before design
Written down, with a named arbiter for the negotiated items. This document prevents most of the delay that group projects are known for. A governance model everyone has seen.
Build the most distinctive property first
Not the flagship, the awkward one. If the platform serves the property that fits least, the rest are configuration. A component library proven against the hard case.
Migrate the others as content, not as projects
Each subsequent property should be content entry and rate mapping. Where one needs engineering, that is a signal the split was drawn in the wrong place. A predictable per-property timeline.
Hand the properties their half
Training and access so local content is edited locally. A group platform that requires a ticket for a restaurant opening time will be worked around within a month. Content that stays current without a release.
Our role
What we deliver on a group platform
- 01
The governance model
Facilitated with the group and the properties, because the split is a commercial agreement that happens to be implemented in software.
- 02
One platform, proven on the hardest property
Components, theming and content model built against the property that fits the pattern least, so the others are configuration.
- 03
Training that makes it stick
Property teams publishing their own content from week one of go-live rather than three months later.
Brand standards and how far a property may diverge from them remain the group's decision; the platform enforces whatever is agreed rather than deciding it.
Common questions
What buyers ask
Should each property have its own domain?+
Usually not, if the group name carries any recognition: one domain concentrates authority and makes cross-selling between properties possible. Separate domains are defensible where a property is independently branded and sells to a different audience, and in that case it is a brand decision rather than a technical one.
Can properties keep their existing booking engines?+
They can, and it costs you the comparable numbers. Two engines means two funnels, two sets of analytics and two theming efforts; where properties are genuinely on different contracts this may be unavoidable in the short term, so the platform should be built to accommodate it while making the consolidation possible later.
How much can a property change before it stops looking like the group?+
That is the negotiated column, and it is worth spending a workshop on rather than discovering during build. A workable default is that structure, typography and the booking path are fixed, while imagery, content and one accent are the property's — which is enough range for a resort and a city hotel to feel distinct.
In this cluster
Plan the group build
A governance model naming what is shared, what each property controls, and who approves a change to either — before any build starts.
What happens next
- 1We reply within one business day.
- 2A 30-minute scoping call with a senior consultant.
- 3A written proposal with scope, team, and timeline.
Or reach us directly

