The Group That Was Never Designed

Most luxury hospitality groups did not design themselves. They accumulated. The infrastructure underneath them was never built for the business they have become, and the cost of that is absorbed quietly, year after year, into the marketing budget of every property in the portfolio.

Most luxury hospitality groups did not design themselves. They accumulated.

A single venue opened, found its audience, and generated enough conviction and cash to justify a second. The second worked, a third followed in a different city, a fourth across a border, and somewhere in that sequence the company stopped being a successful venue with siblings and became a multi-property group. The signage caught up. The org chart caught up. The press release caught up. The back-end did not.

What sits underneath a group of this kind is not the infrastructure of a group. It is the infrastructure of a single venue, repeated. Each property runs its own reservation platform, its own guest database, its own CRM if it runs one at all, its own email tool, its own analytics. Each was chosen by the team that opened it, in the year it opened, based on what was available in that market at that time. The aggregate is a hospitality group that, on paper, operates across multiple countries, and in practice cannot answer the questions a group should be able to answer.

The questions are not exotic. Which guests dine in more than one of our properties. What the lifetime value of a top-decile guest looks like across the portfolio rather than at a single venue. How many of the guests at the property we opened last season were already in our system from a previous property and could have been hosted differently on arrival. What our genuine repeat rate is at the brand level, which is the only level at which it commercially matters. None of these require advanced analytics. They require the data to exist in one place, structured the same way, and in most luxury hospitality groups it does not.

The cost of this is not the cost of running multiple systems. It is the cost of not knowing, at the group level, who your guests are, in a segment where the guest's lifetime value across multiple properties is the single most important commercial number in the business and almost none of it is being captured. A group that cannot identify its multi-property guests cannot retain them as multi-property guests. It can only acquire them, separately, at each property, repeatedly. The economics of that are punishing, and they are absorbed quietly into the marketing budget of each individual property as the cost of doing business.

The pain is felt at the group level. The budgets are held at the property level.

The reason the problem persists is structural, and it is worth naming. Group-level capex, when it exists, is allocated to new openings rather than to the unglamorous work of unifying the back-end of the existing portfolio. Ownership structures reinforce this. Owners and capital partners fund property-level investment because property-level investment has a visible asset behind it. They rarely fund infrastructure projects whose return is the ability to ask better questions, because the return on better questions does not show up in any one quarter and does not attach cleanly to any one property. So nothing moves, and the group continues to operate as eight venues in a coat.

Meanwhile, the next generation of lifestyle operators is not making this mistake. The smaller, newer, more digitally-native groups are architecting their back-end before they need it. By the time they reach six or eight properties, they will be operating with a level of guest intelligence the legacy groups cannot match without a project most of them will never authorise.

The work of fixing this is rarely done well, because it is treated as a technology project. It is not. The decisions about what data to capture, how to structure it, what defines a loyal guest versus a frequent one, what the brand-level guest experience should be when someone moves from one property to another: none of those are technology decisions. They are operator decisions, with brand consequences and commercial consequences, and the technology choice is downstream of them. Most groups do it in the opposite order, and the result is a system that works, technically, and produces information no one knows how to use.

The question I find myself asking when I look at a hospitality group from the outside is not a question about properties. It is whether the group, as a group, knows what it knows. The properties are the part of the business you can see. The infrastructure underneath them is the part that decides whether the business compounds.