Frequently asked questions.

Envoy is the operational coordination and verification layer above the property operator’s existing operational stack. It verifies that monitoring infrastructure is working, coordinates response when alerts fire, and produces the operational record insurance carriers, lenders, and ownership groups increasingly require. Envoy is deployed through partners, not sold direct to operators.

Envoy does four operational jobs. It verifies that the monitoring infrastructure already in place is actually working. It coordinates response across the systems and teams that handle alerts and operational events. It surfaces portfolio operational state in a single consumable view. It produces the documented operational record that insurance carriers, lenders, and ownership groups increasingly require.

Envoy is software, but the operational role is more specific than ‘software platform.’ Envoy is the operational coordination and verification layer that sits above the property operator’s existing operational stack. The software is the means; the operational layer is the job.

No. Envoy is not an IoT product, an IoT platform, or an IoT dashboard. IoT systems generate data; Envoy operates on the data after it is generated. The job is operational coordination and verification, not device management.

Envoy is the operational coordination and verification layer for property portfolios. The broader category for platforms in this position is Operational Awareness Infrastructure; Envoy is described primarily by what it does operationally rather than by the category label.

Several pressures have made the coordination and verification job visible. Monitoring infrastructure has proliferated across properties faster than the operational discipline to verify it is actually working. Insurance carriers, lenders, and ownership groups are asking for evidence that property operations are functioning as designed. The gap between what monitoring systems claim to do and what they actually do has become an operational liability that the existing stack does not resolve.

Envoy is deployed through partners. The direct buyer is a partner firm: a facilities management firm, a property management company, a mechanical and HVAC service provider, or an adjacent operational service firm. The end operator is the property owner or operator the partner already serves.

No. Envoy is sold and deployed through partners. Operators interested in Envoy are connected to a partner active in their market. Operators in areas without active partner coverage can submit an inbound inquiry on the Find a Partner page; ObjectSpectrum matches them to an active partner or evaluates next steps directly.

Mid-sized facilities management firms, property management companies, mechanical and HVAC service providers, and adjacent operational service firms with existing customer relationships in the property operations market. The fit profile is partners with installed customer bases who want to add a recurring revenue line and an operational differentiator to the relationships they already own.

Multifamily (including independent living communities), hospitality, commercial and retail, student housing, rental and vacation homes, industrial, utilities, and telecom. The operational coordination and verification job is the same across all eight; the specific operational pain patterns and partner channels differ by industry. Across all eight, the operators who recognize the problem most acutely are those running vacant or periodically occupied properties, where no continuous on-site presence catches failures early.

Envoy does not replace SmartRent. SmartRent is the resident automation layer, operating inside the unit. Envoy operates above the broader stack, including SmartRent. The two coexist by design.

No. Envoy does not replace property management systems like RealPage, AppFolio, Yardi, or Entrata. The PMS handles leasing, accounting, resident management, and the work order process; Envoy operates above the PMS at the coordination and verification layer. The two systems coexist by design.

No. BMS platforms (Honeywell, Siemens, Johnson Controls, Schneider) control building infrastructure: HVAC, lighting, access, equipment. Envoy operates above control as the coordination and verification layer across the systems the BMS controls and the rest of the operational stack.

No. IoT dashboards aggregate readings from underlying systems into displayable views. Envoy operates on the operational state those readings describe: verifying the systems are working, coordinating response when they fire, and producing the operational record. Dashboards visualize; Envoy coordinates.

Envoy does not compete with leak detection vendors. Leak detection is a point solution for a specific failure mode. Envoy operates above point solutions, verifying they are working, coordinating response when they fire, and integrating their signals with the rest of the operational stack. If leak detection is already there, Envoy absorbs it, verifies it, and expands it. If a property has none, Envoy provides it as part of the deployment.

Envoy is an infrastructure monitoring and coordination layer, not an alarm system. It is not a burglar, fire, smoke, CO, or life-safety alarm, and it does not replace one where it is already installed. Envoy verifies that a property's monitoring infrastructure is working and coordinates response when it fires; alarm and life-safety systems continue to do the job they are designed for.

Envoy does not replace inspection software. Inspections are periodic snapshots; they capture what is true at the moment of inspection. Envoy is continuous; it captures operational state in the gaps between inspections. The two operational models are structurally distinct and complement each other.

Envoy is deployed through partners under a wholesale-to-retail structure. The partner sells Envoy to their existing customers as part of the operational relationship they already own. ObjectSpectrum provides the platform, the underlying operational infrastructure, and partner enablement. The partner provides the customer relationship, the operational service, and the deployment work.

A partner sells Envoy as a recurring service into their existing customer relationships. The partner positions Envoy as an extension of the operational service they already provide, with the platform as the underlying mechanism. The customer pays the partner; the partner pays a wholesale rate to ObjectSpectrum.

Partners earn the margin between the retail price they set for their customers and the wholesale rate they pay to ObjectSpectrum. The structure is recurring; partners build a recurring revenue line that compounds across their installed customer base.

ObjectSpectrum provides the Envoy platform, the underlying operational infrastructure that runs it, partner enablement materials, technical support for deployment, and ongoing platform maintenance. The relationship is multi-year and structurally aligned.

The partner provides the customer relationship, the operational service context, the deployment coordination on the ground, and the ongoing customer-facing operational work. The partner is the operator’s primary point of contact; Envoy operates inside the relationship the partner already owns.

Envoy is deployed across the operator’s properties by the partner. Where monitoring is already in place, the platform integrates with it, verifies that it is working, and begins coordinating response. Where a property has none, the deployment includes the monitors Envoy provides. The deployment is partner-led; the partner owns the operational coordination with the operator.

Initial deployment typically completes within the first weeks of engagement. The operator sees verified infrastructure and coordinated alerts early. The deployment timeline scales with portfolio size and the complexity of the existing operational stack.

Where the operator already has monitoring, Envoy works with it and adds no hardware for its own sake. Where a property has no monitoring for a given failure mode, Envoy includes the monitors as part of the deployment: the launch set covers leak detection, temperature, freezer or refrigerator conditions, occupancy or motion, and internet connectivity with router reboot. The partner coordinates the install as part of the operational service. The sensors are substrate the platform manages; Envoy is the operational layer above whatever monitoring is present, not a hardware-first product. If the monitoring is already there, Envoy absorbs it, verifies it, and expands it. If it is not, Envoy provides it.

Existing monitoring stays in place. Envoy verifies that it is working, coordinates response across the alerts it produces, and integrates its signals with the broader operational stack. The infrastructure does its job. Envoy makes the job legible, accountable, and coordinated.

ObjectSpectrum is the platform company that builds Envoy. The company has been developing operational platforms for equipment-centric businesses for years, with machine learning running in live production environments across multiple client deployments. ObjectSpectrum builds platforms and goes to market through partners.

Prism is the underlying ObjectSpectrum platform that Envoy is built on. Prism powers other ObjectSpectrum products as well, including ClearPath. The platform has been in production for years; Envoy is one of the productized solutions Prism enables.

The Prism platform has been in production across client deployments for years. Machine learning has been operating in live environments, not in demo decks. The operational maturity is part of what differentiates Envoy from positioning-only entrants in the category.