One Operational Technology Relationship Across a Mixed-Use Portfolio: Why Multi-Asset Developers Are Changing Their Approach
Article analysis
In brief
Developers managing residential, hospitality, and workspace assets juggle three technology relationships and three operational models. The case for a unified property operations technology approach.
Mixed-use portfolios create one operating problem
Mixed-use development has become the dominant model for large-scale urban property projects across the UK, UAE, and the wider GCC. A single scheme may deliver residential apartments, a serviced apartment or apart-hotel block, flexible workspace and private offices, retail, and shared amenity, all designed to activate the same site across different occupier types and different times of day. The design and construction logic of mixed-use is well understood. The operational technology logic is not, and the gap between those two things is creating significant and avoidable cost for the developers and asset managers who own and operate these schemes.
Why asset-by-asset procurement fragments
The default approach to technology across a mixed-use portfolio is to procure separately for each asset class. The residential block gets a residential management platform. The apart-hotel gets a property management system from the hospitality market. The workspace floors get a coworking platform. Each procurement is evaluated on its own merits against its own peer set. The result is three technology relationships, three vendor support structures, three data models that do not speak to each other, and an asset management team that needs three logins and three reporting formats to understand what is happening across a single scheme.
The cost hidden between systems
The operational cost of that fragmentation is rarely visible in the business case for any individual platform, because each platform is evaluated against the alternative of not having it, not against the alternative of having a unified system. But the cost exists and it accumulates. Staff who work across asset types, building management, security, facilities, operate across multiple systems. Data that should flow between systems, such as access control credentials that apply across the residential and workspace portions of a scheme, must be maintained manually. Reporting that the asset manager needs across the whole portfolio requires manual consolidation from three sources. None of these costs appear on a vendor invoice.
Design the architecture at scheme level
Developers who are changing their approach are doing so around a simple principle: the operational technology architecture for a mixed-use scheme should be designed at the scheme level, not at the asset-class level. That means selecting a technology partner whose product suite covers residential community management, hospitality guest operations, and workspace management within a common architecture, common identity and access management, common communications infrastructure, common reporting, rather than procuring the best-in-class platform for each asset class independently. The tradeoff is that no single platform is the deepest specialist in any one category. The gain is that the portfolio operates as a coherent system rather than as a collection of independently managed assets.
Evaluate visibility against specialisation
For asset managers evaluating this approach, the question is not whether the unified model makes sense in principle, it does, but whether the available platforms cover all three asset classes at sufficient depth for their specific operational requirements. The answer depends on the operational intensity of each asset class in the portfolio and the degree to which the asset manager prioritises cross-portfolio visibility over per-asset optimisation. Developers who have made the transition consistently report that the operational overhead reduction and the improvement in portfolio-level insight justify the trade. The ones who have not yet made it are typically managing the fragmentation cost without accounting for it.
Sources and further reading
Macber’s analysis is informed by operational experience. These external references provide additional market and technical context.