Xthings wins when hardware, edge intelligence, cloud and open integration solve one operating problem together.
The public platform spans home, work and city environments. For business development, the value is the combination: access, video, automation, identity and device management across cloud, on-premise and hybrid deployments.
Four surfaces for building revenue motions.
These are the product layers I would learn deeply enough to configure, demo and position against the customer's existing infrastructure.
Unified management layer
Device and data management, multi-site control, cloud-to-cloud integration and automation.
Best for centralized visibility, SaaS attachment and multi-site operations.Local control + edge operations
Business and property control for CCTV, access, attendance and visitor workflows with offline-capable local operation.
Best when reliability, latency or data sovereignty matter.Smart access
Residential and light-commercial smart locks, credentials and connected access.
Best for property, multifamily, hospitality and business cross-sell motions.Identity + video security
Biometric access, time attendance and intelligent camera systems for commercial environments.
Best for workplace, industrial and physical-security use cases.Open architecture is a commercial lever.
The strongest differentiation is not “more hardware.” It is the ability to connect physical systems without forcing every customer into one narrow deployment model.
Matter, OSDP, ONVIF, Zigbee, Z-Wave, Wi-Fi and other supported standards widen integration options. Always verify device-level compatibility before promising reuse.
The architecture can be positioned around the buyer's latency, privacy, resilience and operations requirements rather than one mandated topology.
REST, MQTT, webhooks and SDK resources create partnership potential with HR, identity, property, building and automation platforms.
What I would do and what I would not do.
IoT deals become expensive quickly when sales gets ahead of technical reality. The BDM should accelerate deals without creating implementation debt.
- Start discovery from the customer's current stack, protocols and workflows.
- Sell the operational outcome: fewer systems, faster access workflows, local resilience, lower integration friction.
- Bring Product / Solutions Engineering into complex API, biometric and legacy-integration questions early.
- Use a time-boxed pilot with written technical and commercial success criteria.
- Package hardware and recurring cloud value together where the use case supports it.
- Promise “no rip-and-replace” until the exact reader, controller, camera, wiring and protocol path is verified.
- Claim biometric compliance is automatic. Legal and privacy requirements vary by jurisdiction and deployment.
- Invent partner margin or SaaS revenue-share percentages before Finance and channel policy approve them.
- Turn every enterprise request into custom engineering before the economic buyer and commercial value are real.
- Infer quota from OTE. Confirm revenue credit, margin model and compensation mechanics first.