Context & Problem
Indian device manufacturers who want to ship "smart" products are largely dependent on foreign IoT platforms like Tuya - handing over device data, cloud control, and the customer relationship to a third party. There was no sovereign, white-label alternative that local manufacturers could brand as their own while retaining control of their data and roadmap.
As Product Manager at Cronlux, I owned the strategy and build of a white-label IoT device management platform - device provisioning, OTA firmware updates, telemetry, and mobile app control - supporting 100+ connected device types and positioned as a sovereign alternative to Tuya for Indian manufacturers. To ground the strategy in reality rather than assumption, I ran 300+ conversations with manufacturers and channel partners to validate positioning, pricing, and the lead vertical.
Key Product Decisions
- Pivot to regulated verticals, over staying horizontal. I chose to refocus the roadmap from the crowded horizontal smart-home market onto regulated verticals - senior care and energy - based directly on signal from 300+ discovery conversations. Tradeoff: walking away from a larger, more familiar addressable market. Result: a position in a smaller market where reliability and data control are genuine differentiators rather than commodities, with stronger pricing power.
- White-label first, over a single branded product. I chose to architect the platform so any manufacturer could ship its own branded ecosystem on shared infrastructure, rather than build one polished Cronlux-branded product. Tradeoff: slower time-to-market for any single manufacturer's launch. Result: a repeatable platform business instead of a one-off product.
- Local processing over pure cloud execution. I chose to have edge hubs process routine automations locally rather than round-tripping every decision through the cloud. Tradeoff: more complexity in firmware and state-sync logic. Result: a system that stays responsive and private even when internet connectivity drops.
Execution
Shipping this required operating across two very different disciplines at once - cloud software and physical hardware manufacturing.
Constraints: the platform had to stay economical for price-sensitive manufacturers while still architected for horizontal scaling; battery-powered sensors imposed tight power budgets, demanding exceptional firmware optimization on constrained ESP32 hardware; sourcing meant navigating Chinese hardware supply chains, including on-ground sourcing and evaluation at the Canton Fair; and the platform had to meet data-privacy expectations while handling device data on behalf of many brands.
Architecture:
Devices run optimized ESP32 firmware and communicate with the cloud over MQTT - a real-time messaging protocol chosen for constrained, high-volume environments with intermittent connectivity. Telemetry feeds an event-driven automation engine, and the cloud services run on auto-scaling AWS ECS, architected for horizontal scaling.
Manufacturing: I took a 16A smart energy-monitoring device from specification to production - defining hardware requirements, negotiating with manufacturers in China (including on-ground evaluation at the Canton Fair), and managing an initial batch of 2,000 units at 10% lower unit cost than off-the-shelf alternatives.
Outcomes & Lessons
- Shipped a 2,000-unit initial production batch at 10% lower unit cost than off-the-shelf alternatives, proving the manufacturing model could hold up under real supply-chain constraints.
- 300+ manufacturer and channel-partner conversations directly drove the roadmap pivot from horizontal smart-home to regulated verticals (senior care, energy) - the highest-leverage decision on the project, and not a technical one.
- Lesson: building a hardware-software platform is exponentially harder than pure software - a bug in software is patched in an hour, but a flaw in hardware tooling can cost millions and delay a launch by months.