About Me
I'm a Product Builder, systems thinker, and engineer bridging the gap between hardware and software.
Professional Journey
My fundamental grounding in technology began at the bare-metal level. Starting my career designing smart home electronics, I spent countless hours writing firmware and understanding the stringent constraints of microcontrollers and DALI lighting systems.
Driven by a desire to innovate faster, I co-founded Lidelta Innovations. There, we operated as a rapid prototyping powerhouse, building custom R&D hardware products for diverse sectors—from naval testing equipment to precision medical devices like infant phototherapy machines—deploying into four real customer environments and generating ₹35L (~$42K) in early sales.
Recognizing the shift toward decentralized architectures, I co-founded Trizwit Labs as Head of Product & Technology, leading delivery across five international client engagements. There I built Pindown, a Web3 platform that solved the critical problem of verifiable credentials—translating complex cryptography into an elegant, usable document dashboard for institutions and shipping it from zero to production.
Most recently, as CEO and Product Lead at Cronlux, I built a white-label IoT device management platform—provisioning, OTA updates, telemetry, and mobile control across 100+ device types—positioned as a sovereign alternative to Tuya for Indian manufacturers. After 300+ conversations with manufacturers and partners, I reshaped the roadmap from horizontal smart-home toward regulated verticals like senior care and energy, bridging Chinese hardware manufacturing with an event-driven cloud architected to scale to 100,000+ devices.
Product Philosophy
- 01Systems thinking before featuresA product is never an isolated feature; it is a node in a larger ecosystem. True value is created when you design how components—from the edge device to the user interface—interact, fail, and scale together gracefully.
- 02Building products that bridge hardware and softwareSoftware can only be as magical as the hardware it runs on. A deep understanding of physical constraints—power budgets, thermals, and memory allocation—is required to write software that feels invisible and responsive to the user.
- 03Designing scalable platforms rather than isolated toolsInstead of solving a single, narrow problem, I focus on building platforms that can be built upon. An elegant underlying architecture (like an event pipeline or standard protocol set) ensures longevity and the ability to pivot seamlessly as market demands change.