The partner model
The Envoy partner model.
ObjectSpectrum builds and operates Envoy. Your firm charges your customer, pays a recurring amount for Envoy, and owns the relationship. ObjectSpectrum runs the platform underneath and supports you through deployment.
You decide how you charge for it. The terms between your firm and ObjectSpectrum get set in the partner conversation rather than published here. Agreements run for multiple years.
How You Charge For It
The commercial structure.
You can charge your customer for Envoy and pay ObjectSpectrum a recurring amount for it. You set what you charge. The difference between that and what Envoy costs you is your gross recurring margin before your own operating costs.
That isn’t the only way to run it. You can fold Envoy into a service you already provide, offer it as an add-on, fund it across a book of customers, or absorb the cost against what it saves you. Which one fits depends on how your agreements are written and how you want to present it to your customer.
In every version, the customer is yours. They pay you, you pay ObjectSpectrum, and ObjectSpectrum does not open a separate commercial relationship with them.
Agreements run for multiple years, because the value builds over time. Terms, exclusivity, and territory depend on your category, your footprint, and the scope of what you’d deploy, so we work those out in the partner conversation rather than publishing them here.
Platform side
What ObjectSpectrum provides.
ObjectSpectrum builds and operates Envoy. Four things sit on our side.
The platform.
Envoy runs on Prism, the ObjectSpectrum platform that has been in production across client deployments for years. ObjectSpectrum keeps it running, ships new features in Envoy as it matures, and handles the technical work that spans every deployment.
Sales and deployment materials.
Sales materials, deployment playbooks, customer-facing reference documents, technical training, and ongoing education for your team. The customer-facing pieces are written for the conversations you’ll actually have, so you’re not rewriting them before you can use them.
Technical support.
ObjectSpectrum monitors Envoy for platform health and security, provides severity-based technical support, and remotely diagnoses product, monitor, device, and connectivity issues. Critical platform issues get 24/7 coverage. Your technical contacts are direct.
Ongoing investment.
Integration coverage, platform reliability, and new capability ship continuously and reach every active deployment. You don’t pay for it separately.
Partner side
What your firm provides.
You are the one your customer deals with. Here is what sits on your side.
The customer relationship.
You own it before, during, and after Envoy is deployed. ObjectSpectrum does not contact your customers directly. You handle all communication, account management, renewals, and coordination with the customer.
Deployment coordination.
You coordinate the deployment at the property: what systems are already there, the order in which things connect, who at the customer needs to be involved, and how the rollout is timed. ObjectSpectrum supports the technical work but doesn’t lead it.
Fitting it into your service.
Envoy extends what you already do. You position it inside work the customer already understands, so it reads as part of a service they already buy, not a separate software purchase, whether it shows up as its own line or inside what you already bill.
Ongoing customer work.
You receive and assess property-condition alerts, coordinate the response with your customer, arrange any field work, and review the operational record with them. Coverage hours and escalation follow your deployment plan. ObjectSpectrum’s 24/7 coverage for critical platform issues doesn’t mean every partner needs 24/7 customer response.
On the ground
How deployment works.
A deployment starts with you and your customer agreeing on scope: which properties are covered, what each one should watch for, what monitoring is already there, where it’s partial, and where there’s none. ObjectSpectrum supports the technical side of that, but the sales conversation with your customer is yours.
How long it takes depends on how many properties there are and what’s already installed at them. One property moves faster than forty, and there’s no timeline that fits every deployment.
If the monitoring is already there, Envoy absorbs it, verifies it, and expands it. If it is not, Envoy provides it. You and ObjectSpectrum work out the install together, using what’s in place where it’s reliable and adding monitoring where coverage is missing.
Mutual obligation
Obligations run both ways.
ObjectSpectrum is responsible for delivering Envoy as described, developing it responsibly, and supporting your deployments. You are responsible for representing Envoy honestly to your customers, deploying it for the work it’s built for, and running the customer relationship with the same care Envoy is meant to support.
That second half matters as much as the first. A partner who promises capability Envoy doesn’t have, or who sells it as generic software, does the same damage as a product that fails. The partner agreement names this directly, and the partnership conversation tests for it before either side commits.
Working with what’s there
Hardware and integration.
Envoy connects to compatible property management systems, building management systems, resident automation, inspection software, and point monitoring. Where coverage is partial or a property has nothing, Envoy supplies the monitoring, and getting equipment in runs through the customer relationship you already have.
What happens next
What to expect next.
The Become a Partner form starts a conversation. The first one is about fit: whether your firm matches the profile, how your service area and operations shape a deployment, and whether the timing works on both sides. If it fits, the next step is a working session on what a deployment would look like across the properties you serve. Commercial terms, territory, and the agreement itself get worked out in that meeting rather than over a web form.