Skip to content
View in the app

A better way to browse. Learn more.
OCCUPIERWORLD®

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

The AI-Native CRE System: What Exists, What's Being Built and How to get ready for it?

Anthony
Anthony
in Portfolio Strategy and Execution: Accountability across Markets

How Should We Structure Our PropTech Capability to Be Ready for the AI-Native CRE System ?

  1. 1. How is your PropTech capability structured: in-house, outsourced, or hybrid?

    • Predominantly in-house: Core PropTech platforms (IWMS, space analytics, IoT/BMS integration, data management) are owned, configured and managed internally. We have dedicated internal technology and data capability within CRE or FM and do not rely on external providers to operate the platforms day to day.
      0%
      0
    • Predominantly outsourced to an integrated FM or CRE service provider: Our primary PropTech stack is owned or operated by our IFM or managing agent partner as part of the service contract. Technology governance, data management and platform development decisions rest largely with the provider, not with us.
      0%
      0
    • Hybrid — core platforms in-house, specialist applications outsourced: We own and govern the central data and IWMS layer but rely on outsourced or SaaS providers for specialist applications (energy management, occupancy sensing, predictive maintenance). Integration between the two layers is an active and ongoing challenge.
      0%
      0
    • Fragmented — multiple standalone tools procured separately, with no integrated ownership: Platforms have been procured by different functions or at different points in time with no common architecture. Data sits in silos, integration is partial or manual, and there is no single owner of the PropTech stack across CRE and FM.
      0%
      0
    • Currently under review or in active consolidation: A PropTech audit, platform rationalisation or technology strategy exercise is underway. We know the current model is not fit for purpose but have not yet landed on a target architecture or ownership model.
      0%
      0

Please sign in or register to vote in this poll.

Featured Replies

PropTech venture investment reached $16.7 billion in 2025, a 67.9% year-on-year increase that surpassed pre-pandemic levels, with AI-centred PropTech companies growing investment at 42% annualised, nearly double the rate for non-AI PropTech.

Several workplace technologies have already surpassed 80% adoption rates for operational functions; predictive maintenance, data warehousing, energy and emissions management, demonstrating that the infrastructure layer is maturing. The strategic intelligence layer is what remains underdeveloped. And the organisations that are closest to having it are not necessarily those that spent the most on technology, they are those that made deliberate decisions about data ownership, integration architecture and operating model design before they bought anything. JLL

Which brings me to the question I want this community to answer from lived experience - How should your PropTech capability be structured for tomorrow's AI-native system — in-house, outsourced, or hybrid?

Specifically:

— If you outsource your CPIP/IWMS to an IFM provider or managed service, do you retain meaningful control of the data model and integration architecture — or does the AI-native capability you'll need in five years effectively belong to your supplier?

— If you are building in-house, where have you drawn the line between what you own and what you buy — and how are you keeping pace with a vendor market moving faster than any internal team can match?

— Has anyone in this community piloted a genuinely agentic AI workflow across the portfolio-to-projects pipeline — not a chatbot on top of a legacy system, but something that reasons across connected datasets and surfaces decisions? What does that actually look like in practice?

— And for those mid-transition: what would you tell your past self about the sequencing? Data first, then platform, then AI — or did you find a different order that worked?

The blueprint for the AI-native CRE system is being written right now, partly by vendors, partly by the occupier organisations willing to architect it themselves. Interested to understand where peers in this community are in that journey and whether anyone is further along than the rest of us suspect.

  • Views 5
  • Created
  • Last Reply

Create an account or sign in to comment
Go to topic listing

Account

Navigation

Search

Search

Configure browser push notifications
Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.