A partner is valuable when it creates access, implementation leverage, or recurring demand.
The partner strategy should optimize for sourced revenue and deployment leverage. Different partner types enter the deal at different moments, so enablement, economics and deal registration should reflect the motion they actually own.
Five partner motions, each with a different job.
Xthings already invites distributors, installers, system integrators, OEM/ODM partners, technology partners, developers and enterprise buyers into its ecosystem. The BD opportunity is to make those routes measurable and productive.
Install + influence
Low-voltage and security firms that own the field relationship and can specify Xthings across multiple end customers.
WHEN: retrofit, access-control bid, new commercial deploymentConnect physical + digital identity
IT firms that already manage directories, networks, SaaS and user lifecycle for business clients.
WHEN: HR/identity integration, office standardization, multi-site IT projectWin before the bid
Architects, consultants and engineers that influence access, security and smart-building specifications.
WHEN: schematic design, Division 08/28, new build or major renovationStandardize portfolios
Developers and operators that can deploy smart access, video and cloud management across buildings and units.
WHEN: development, renovation, portfolio technology refreshExpand the ecosystem
Cloud, identity, property, automation and device partners that can integrate through APIs, SDKs and open protocols.
WHEN: joint customer demand or repeatable integration use caseTurn one project into a reusable route to market.
The best ecosystem is not five separate referral programs. It is a chain where early influence, technical validation, installation and recurring software economics reinforce each other.
New build, retrofit, lease, portfolio refresh or security modernization.
Design Xthings-compatible access, security and open integration into the project.
Confirm topology, protocols, install scope, API requirements and pilot plan.
Hardware + software + implementation with clear ownership and support boundaries.
Use proof, installed base and recurring revenue to source the next project.
Start with firms already touching the exact systems Xthings needs to influence.
These are public-market research candidates, not claims of current Xthings relationships or qualified opportunities. The first call is about fit: customer base, technical stack, vendor openness, project mix and appetite to co-sell.
Access control, CCTV and low-voltage for complex enterprise facilities, with national coverage. Strong local test for industrial and multi-site co-selling.
NEXT: map installed platforms, active sectors and vendor-selection process. SANTA CLARA · SECURITY INTEGRATORElwin SecurityCommercial access, cameras, intercoms, doors and low-voltage across offices, industrial, data centers and multifamily.
NEXT: test retrofit / interoperability motion on mixed existing infrastructure. SAN MATEO · SYSTEMS INTEGRATORSecurity 101Design, engineering, installation and service across access, video, visitor management and wireless security.
NEXT: understand manufacturer portfolio and where open integration can improve bids. NATIONAL · STRATEGIC INTEGRATORConvergintLarge-scale security and technology integration across access, video and enterprise environments.
NEXT: validate whether Xthings has a wedge in selected verticals or edge / open-platform projects. SMART BUILDINGS · MULTIFAMILYSouth Bay HardwareConsulting, specification, installation and support for smart building, access, security and IoT deployments.
NEXT: evaluate property / multifamily deployment and specification partnership. SF + SILICON VALLEY · WORKPLACE TECHRegent5Commercial integration spanning access control, networks, Wi-Fi, AV, lighting and electrical infrastructure.
NEXT: test physical + digital workplace integration motion.25 public-market candidates scored with the same Partner IQ.
This is a research universe, not a claim that Xthings should recruit every firm. Scores use only public evidence for reach, technical capability, revenue leverage and strategic fit. Existing Xthings relationships and conflicts should be de-duplicated internally before outreach.
National, regional, building-tech and specifier candidates.
Highest public-evidence leverage for executive validation.
National plus West, Texas, Midwest and Southeast coverage.
Reach 30 + technical 25 + revenue leverage 25 + fit 20.
Improve the current program before inventing a new tier system.
Xthings already has a public partner program. I would first measure what partners actually need to source and close business, then tune the existing structure around those behaviors.
Make technical selling easier
Integration matrix, deployment diagrams, demo environments, certification and concise competitive proof.
Protect sourced opportunities
Clear ownership, expiration, direct-sales exceptions and response SLAs so partners trust the motion.
Bring Xthings into the right moments
Joint discovery, technical validation, executive support and marketing resources on qualified opportunities.
Reward measurable value
Pricing and incentives should reflect sourced revenue, implementation ownership, support burden and gross margin.
Every repeated objection should improve the next deal.
The Director of Strategic Partnerships and Product Marketing should get a structured signal from the field, not a stream of anecdotes.
Compatibility question, missing integration, deployment confusion, competitive objection, privacy concern or pricing issue.
Do not ask Product to build something that better documentation or positioning can solve.
Accounts affected, TCV / ARR at stake, partner reach and frequency of request.
Battlecard, integration guide, reference architecture, pilot kit, case study or roadmap case.
Track usage and whether the asset reduces cycle time, increases pilot conversion or unlocks partner-sourced pipeline.
Measure productivity, not logos.
A signed partner agreement is the beginning of the funnel, not the outcome.
How quickly the partner becomes commercially useful after onboarding.
Quality of sourced opportunities and partner execution through the buying process.
Hardware, services and recurring cloud value separated by partner and vertical.
Whether the relationship compounds rather than ending after the first installation.
How often partner-led hardware deployments create ongoing platform revenue.
Partner discounts, enablement cost and support load must still create healthy business.
Every active registered opportunity should have evidence, owner, next step and timing.
Aggregate partner feedback into roadmap cases when the same requirement unlocks multiple accounts.