Property intelligence vs. home automation — what the distinction actually means.

The simplest version of the distinction is this. Home automation is the layer that controls the residence — the lights, the climate, the shades, the doors, the audio, the video. Property intelligence is the layer that reads what the automation produces and translates the raw telemetry into something a human can act on. Different jobs, different vendors typically, complementary by design.

They get conflated because, from a distance, they look like the same thing: software that interacts with the systems in a residence. Up close, the difference is enormous. Home automation closes a relay when you touch a button; property intelligence notices that the relay’s state has been drifting against the household’s pattern for the last three weeks and writes a note about it. Different work; different software architectures; usually different vendors.

What home automation does.

Home automation is the control plane. Crestron, Lutron HomeWorks, Control4, Savant, and the building-management systems that run mechanical plant are all home-automation platforms. They share a common architecture: a controller (sometimes more than one), a network of subsystems and devices, and a programme that translates household intent into device action. Press a scene button; the controller closes the right relays, dims the right circuits, raises the right shades, sets the right setpoints. Closed-loop, deterministic, well-understood.

The value of a home-automation layer is that it makes the residence operable as a single instrument. The household has one vocabulary — the scenes on the wall panel — that orchestrates dozens of underlying systems. Done well, this is invisible to the household and feels like the residence simply responding to intent. Done poorly, it’s a household with twelve remote controls and a thermostat that’s impossible to reach behind the bed.

Home automation has been around since the late 1980s in commercial buildings and since the late 1990s in residential. The platforms are mature, the integrators that deliver them are competent (mostly), and the technology has had time to settle. What hasn’t had time to settle is what to do with the data those platforms produce.

What property intelligence does.

Property intelligence is the layer above. It doesn’t close relays; it doesn’t set setpoints. It reads what the automation layer is doing — every state change, every error code, every cycle count, every firmware version, every network event — and translates that telemetry into language a human can act on.

The shape of the value is different from home automation. Home automation makes the residence operable. Property intelligence makes the operation legible. The integrator who keeps the residence in service no longer has to log into the Crestron processor, sift through error logs, and pattern-match. They get a morning brief in plain English: “The boiler in the east mechanical room cycled 47 times last night, twice the rolling average for this time of year. Probably a damper modulation issue on Zone 6. Worth a service visit.” A paragraph that’s the result of an algorithm reading thousands of events, ranking them, discarding the unimportant, and surfacing the rest.

The principal gets a different surface. A calm portal in their integrator’s brand — not in the platform’s brand — that translates the same telemetry into a sentence: “Everything ran cleanly last week. We’ll be out Thursday to refresh a humidifier filter.” The principal doesn’t see the algorithm. They see the integrator’s engineer, by name, with a recommendation. The platform is the surface; the human is the relationship.

Intuitiv AI is the property-intelligence platform this firm operates. Other property-intelligence platforms exist; the category is young and the competitors will multiply over the next several years. The category is real.

Why the two coexist.

The right way to think about the two layers is as a stack. Home automation is the lower layer; property intelligence sits above it. The lower layer has authority over the residence — it controls relays, sets setpoints, opens locks. The upper layer has authority over the human conversation — it produces the brief, ranks the findings, writes the morning note.

Neither layer replaces the other. A residence with home automation and no property intelligence has a household that experiences the residence as responsive but the integrator who experiences the residence as a flood of un-ranked event logs. A residence with property intelligence and no home automation has a software layer with nothing to read.

Where they meet matters. The property-intelligence layer reads through the same API surface the home-automation layer publishes — on Crestron Home, the device-event stream; on Crestron Custom, the SIMPL programme’s telemetry; on the IoT layer, the manufacturer APIs. The intelligence layer doesn’t modify the automation; it only listens. Authority over the residence stays where it belongs: in the integrator’s hands, through the integrator’s relationship with the household.

The integrator experience.

A typical luxury Crestron integrator manages somewhere between five and forty principal residences. Without property intelligence, the integrator’s daily work is mostly reactive — the phone rings, the household describes a symptom, the integrator dispatches a service tech to investigate. The work is competent but slow; the symptoms that get noticed are the ones the household notices, which are the late-stage symptoms.

With property intelligence, the same integrator’s daily work shifts. The morning brief surfaces drift before the household sees it — the cycle count on the boiler, the small temperature overshoots on Zone 4, the third firmware version skew across panels in the master suite. The integrator decides what’s worth a visit and what isn’t. The household experiences the residence as “always running cleanly,” which is what the household is paying for.

Beyond a small portfolio size, this isn’t a productivity gain — it’s a structural change to what the integrator can responsibly carry. Forty residences without property intelligence is a firm that lives in the symptom queue. Forty residences with property intelligence is a firm that operates on a portfolio basis. The shape of the relationship between the firm and each household becomes more proactive.

The principal experience.

Most principals don’t want to know about their residence’s telemetry. They want to know that the household is running cleanly, that someone competent is paying attention, and that issues are caught before they become inconveniences. Property intelligence makes the second part of that possible without making the principal carry it themselves.

The principal-facing surface is intentionally small. A weekly note that summarises the residence’s state in a paragraph or two. A messaging surface to ask the integrator a question and get a plain-English answer (often the same day, from the senior engineer attached to the residence). A status indicator on the wall panel that’s green when the residence is running cleanly — and that surfaces a calm message when it isn’t, never a Crestron error code.

On Intuitiv AI specifically, the principal-facing portal carries the integrator’s brand — not Intuitiv’s. The platform is in service of the integrator’s relationship with the household, not in service of building its own. The principal experiences a calmer integrator, not a new vendor.

What property intelligence does not do.

Three things specifically, all of which are sometimes promised by platforms that should be treated with caution.

No cameras, no microphones. Intuitiv AI monitors device telemetry, system events, network behaviour, and firmware versions. Cameras, microphones, and personal communications are out of scope by design. A property-intelligence platform that reads camera feeds isn’t property intelligence — it’s surveillance, which is a different category with different ethical, legal, and household-trust implications.

No autonomous action. The platform reads and reports; it doesn’t modify the residence. The integrator decides what to do with each finding; the platform doesn’t close a valve, reprogramme a scene, or push a firmware update without the integrator’s sign-off. Authority over the residence stays in the integrator’s hands.

No replacement of the integrator. Property intelligence is a tool the integrator uses; it isn’t a substitute for the relationship. Owners reach the integrator, not the platform. A property-intelligence vendor that positions itself between the integrator and the principal is, in our experience, mis-priced — it’s being asked to do work the platform can’t do, and the household is being asked to absorb a layer that doesn’t earn its presence.

Closing.

Home automation makes a residence operable. Property intelligence makes the operation legible. They are complementary technologies that have evolved on different timelines — automation has been here for thirty-five years; property intelligence is new enough that most luxury residences don’t yet carry it. Over the next several years it will move from optional to standard, the way home automation itself did between the early 1990s and the late 2000s.

If you’re a principal whose integrator runs a portfolio of residences, or an integrator whose portfolio has outgrown the symptom queue, we’re glad to talk about how the layer fits into the relationship you already have. Intuitiv AI is the platform we operate; the model fits the practice we run.