Proptech is one of proptech's best known names. XFactr engineered the multi-tenant, IoT enabled platform underneath it. What follows is the honest engineering story, told through system flow and architecture, with the specifics Proptech trusted us with kept exactly where they belong, behind the line.
Proptech's ask was direct. Build an IoT enabled, end to end platform that turns a building into something an owner, an operator, a tenant, and a portfolio manager can all read the same way, on web and on mobile, without any of them feeling like they got the leftover interface. That single sentence hides a lot of hard engineering, most of which lives in multi-tenant enterprise architecture most consumer apps never have to think about.
Real estate software has a specific trap. Build for the owner and the tenant app feels like an afterthought. Build for the tenant and the operator loses the operational depth they need. We treated this as four products sharing one data foundation, not one product with four skins.
What stays confidential: the exact tenant onboarding flow, integration partner list, and internal data model are Proptech's IP under NDA. What you will see below is the shape of the system, without the wiring diagram a competitor could copy.
This is the abstracted version of the flow, useful for understanding the shape of the system, not detailed enough to reproduce it. A tenant taps something in the app. Four layers respond before they even notice a delay.
We built this as three distinct layers because each one has a different job, a different owner, and a different rate of change. Keeping them separate is what let Proptech ship features fast without breaking the parts tenants touch every day, delivered through our full stack development and IoT solutions practice.
The web and mobile surfaces every role opens. Tenant comfort, amenity booking, automated workflows, and the insights owners actually check, built on our web & app development foundation.
The bridge between the app and physical building hardware. HVAC, access control, elevator calls, and air quality sensors, connected through our edge gateway & connectivity work.
Digital twin modeling, air quality optimization, demand responsive HVAC, and continuous commissioning, powered by our data & analytics and applied AI teams.
Kept out of this dossier: which specific vendors sit inside the integration layer, the exact multi-tenant data isolation model, and the internal service names. That detail is exactly the kind of thing another proptech company should not be able to read off our website.
Everyone opens the same platform. What they see next depends entirely on who they are, and that branching logic is most of the design work nobody sees, informed by our enterprise AI applications and API & microservices approach.
This is the part most buildings get wrong. A sensor firing an event is not the same thing as an operator knowing to act on it. The distance between those two moments is where data engineering either earns its keep or quietly becomes noise nobody reads.
Most commercial buildings run dozens of separate leases, each with its own access rules, its own service level, and its own data privacy expectations, inside one physical shell. Software built for a single tenant breaks the moment a second one shows up. Getting multi-tenant architecture right the first time is what lets a platform scale to a portfolio instead of getting rebuilt at every new address.
Since the shift back to office life, tenants expect the building itself to behave like the other apps on their phone: instant, personalized, and quiet about the complexity underneath. A slow elevator call button or a clunky visitor form is a bigger churn risk for a landlord than it used to be, which is exactly why tenant facing mobile experience has become a boardroom conversation, not just a facilities one.
Building hardware speaks a genuinely messy mix of legacy and modern protocols, often installed years apart by different vendors with no plan to ever talk to each other. Real IoT engineering in this space is less about the sensors themselves and more about the gateway layer that translates all of it into one language.
The honest answer is prediction, not chat. Fault detection before a system fails, demand responsive HVAC that adjusts before a room gets uncomfortable, and labor scheduling that matches staff to real demand. This is applied AI doing quiet, useful work, not a headline feature.
Proptech's public site today describes the platform as three connected product lines, sitting on a shared data layer they call Savvy, with an advisory practice on top for clients who need more than software. This is Proptech's own current description of their business, shown here for context on the world this engagement operates inside, not as a claim about which parts XFactr built or maintains today.
Mobile credentials and unified access across a portfolio, built to onboard a new user in under two minutes instead of days.
The tenant and employee facing layer: space booking, communications, and real time occupancy intelligence.
Work orders, asset tracking, preventive maintenance scheduling, and vendor management for any property type.
Proptech joins a small, deliberately chosen list of long-term XFactr partners, the same model behind our work with Falkor, formerly Kongsberg Digital, and Zinc Systems.
Where this engineering discipline extends into AI-driven building operations.
FIELD SYSTEMSThe same connected-device discipline, applied across buildings, plants, and grids.
START HEREWhere a build like this one starts, as a scoped architecture conversation.
This dossier touched web, mobile, cloud, IoT, and applied intelligence. Here is the rest of what that same engineering discipline covers.
Fewer clients, deeper partnerships, architect-led delivery, the same model that took Proptech from embedded engineering to a platform running across a real estate portfolio.