The partner model
The Envoy partner model.
Envoy is sold and deployed through partners under a wholesale-to-retail structure. ObjectSpectrum provides the platform, the operational infrastructure underneath it, and partner enablement. The partner provides the customer relationship, the operational service context, and the deployment work on the ground. The economics are recurring and compound across the partner’s installed base. The relationship is multi-year and structurally aligned for both sides.
Become a PartnerWholesale to retail
The commercial structure.
Partners purchase Envoy at a wholesale rate and sell it to their customers at a retail rate the partner sets. The margin between the two is the partner’s recurring revenue. Wholesale rates are tiered to reflect the partner’s deployment scale and book of business; partners growing their installed base see the wholesale economics improve over time.
The customer pays the partner directly. The partner pays the wholesale rate to ObjectSpectrum on a recurring basis tied to active deployments. There is no separate customer-facing relationship with ObjectSpectrum on commercial terms; the partner owns the commercial relationship end-to-end.
Partner agreements are multi-year. The structure is not optimized for short transactional engagements; the economic value compounds over time, and the agreement is shaped to match. Specific terms, exclusivity considerations, and territory definitions are discussed during the partner engagement conversation rather than published here, because they depend on the partner’s category, geographic footprint, and operational scope.
The customer pays the partner directly. The partner pays the wholesale rate to ObjectSpectrum on a recurring basis tied to active deployments. There is no separate customer-facing relationship with ObjectSpectrum on commercial terms; the partner owns the commercial relationship end-to-end.
Partner agreements are multi-year. The structure is not optimized for short transactional engagements; the economic value compounds over time, and the agreement is shaped to match. Specific terms, exclusivity considerations, and territory definitions are discussed during the partner engagement conversation rather than published here, because they depend on the partner’s category, geographic footprint, and operational scope.
Platform side
What ObjectSpectrum provides.
ObjectSpectrum is the platform company behind Envoy. The provision split is consistent across partners.
The platform.
Envoy runs on Prism, the underlying ObjectSpectrum platform that has been in production across client deployments for years. ObjectSpectrum operates the platform, maintains the operational infrastructure, ships new features as the platform matures, and handles the cross-deployment technical work that no individual partner can reasonably own.
Partner enablement.
ObjectSpectrum provides sales materials, deployment playbooks, customer-facing reference documents, technical training, and ongoing partner education. The enablement is calibrated to the partner-track voice and the canonical category position; partners do not need to translate ObjectSpectrum-internal language for their customers because the public-facing materials are already in the language customers respond to.
Technical support.
ObjectSpectrum delivers deployment-phase technical support, integration coordination with the operator’s existing operational stack, and ongoing platform-level support as deployments mature. Partner-tier technical contacts are direct; partners do not file tickets through a generic queue.
Cross-deployment investment.
Machine learning improvements, integration coverage expansion, platform reliability work, and category-defining capabilities ship continuously and benefit every active deployment. Partners do not pay separately for platform evolution; the ongoing investment is part of the partnership.
Partner side
What the partner provides.
The partner is the customer-facing operational service provider. The provision split on the partner side is also consistent.
The customer relationship.
The partner owns the relationship before, during, and after Envoy is deployed. ObjectSpectrum does not contact the partner’s customers directly. Customer-facing communication, account management, renewals, and operational coordination with the customer all run through the partner.
Deployment coordination.
The partner coordinates the deployment on the ground: scoping the operator’s existing operational stack, planning integration sequence, coordinating with the operator’s internal teams, and managing the rollout timeline. ObjectSpectrum supports the technical work but does not lead it.
Operational service context.
Envoy is sold as an extension of the operational service the partner already provides. The partner positions the platform inside the operational frame the customer already understands; the platform is the mechanism, not the pitch. This is what makes Envoy work as a recurring service rather than a software purchase.
Ongoing customer-facing operational work.
The partner handles alert triage, response coordination, operational record review with the customer, and the customer-facing operational reporting that comes out of the platform. Envoy automates the documentation; the partner operates the relationship the documentation supports.
On the ground
How deployment works.
A new deployment opens with the partner and the operator agreeing on the operational scope: which properties, which systems in the existing operational stack, which monitoring infrastructure already in place. ObjectSpectrum supports the technical scoping but the partner owns the operator-facing conversation.
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; a single-property deployment moves faster than a 40-property portfolio.
Envoy is deployed onto monitoring infrastructure the operator already has. Where additional hardware would improve coverage, the partner can coordinate the deployment as part of the broader operational service. The platform is not hardware-first. The discipline is to deploy Envoy above whatever monitoring infrastructure is already present, using what the operator has rather than requiring new equipment.
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; a single-property deployment moves faster than a 40-property portfolio.
Envoy is deployed onto monitoring infrastructure the operator already has. Where additional hardware would improve coverage, the partner can coordinate the deployment as part of the broader operational service. The platform is not hardware-first. The discipline is to deploy Envoy above whatever monitoring infrastructure is already present, using what the operator has rather than requiring new equipment.
Mutual obligation
The bidirectional fidelity obligation.
Envoy partnerships carry an obligation that runs in both directions. ObjectSpectrum is responsible for delivering a platform that does what is claimed, evolving it responsibly, and supporting deployments at the operational level. The partner is responsible for representing the platform honestly to customers, deploying it inside the operational frame it is designed for, and operating the customer-facing relationship with the same operational discipline the platform supports.
The obligation is bidirectional because the category position depends on both sides. A partner who overclaims capability, who deploys outside the operational frame, or who treats Envoy as a generic software add-on damages the category as much as a platform that fails to deliver. The partner agreement names this obligation directly; the partnership conversation tests for it before either side commits.
The obligation is bidirectional because the category position depends on both sides. A partner who overclaims capability, who deploys outside the operational frame, or who treats Envoy as a generic software add-on damages the category as much as a platform that fails to deliver. The partner agreement names this obligation directly; the partnership conversation tests for it before either side commits.
Working with what’s there
Hardware and integration.
Envoy works with the monitoring infrastructure operators already have. Native integration covers the property management systems, building management systems, resident automation platforms, inspection software, and point-solution monitoring vendors most operators are running today. Hardware coordination, when needed for coverage gaps, is handled through the partner’s existing operational service relationship rather than as a separate purchase from ObjectSpectrum.
What happens next
What to expect next.
The Become a Partner form opens a structured conversation. The first conversation is qualification: whether the fit profile applies, whether the geographic and operational scope makes sense, and whether the timing is right on both sides. If the fit is there, the next step is a working session on what deployment would look like in your installed base. Specific commercial terms, territory considerations, and the partner agreement itself are discussed during that working session rather than over the form.
Become a Partner