A booking must reserve more than a place on a screen

I am chief product officer of Kelqora Clinic Software in Jalandhar. Our administrative scheduling products serve 186 clinic organisations across Punjab, Himachal Pradesh and Jammu. Kelqora employs 310 people and recorded ₹92 crore revenue in FY 2026. I lead thirty-eight product, design and research colleagues through four leads, with ₹9.4 crore annual function expense and ₹2.1 crore approved product investment. Engineering reports separately to the CTO; providers retain clinical decisions. My remit is the product promise and the work required to fulfil it.

I began as a software engineer in 1998, building scheduling tools before moving into product analysis, access design and product leadership. That route taught me to examine what happens after a person presses the button. A booking can require a practitioner, a suitable room and preparation time. An earlier appointment offered to a waiting person is not yet an accepted appointment. A staff edit can change somebody else's working day. The interface should make those consequences understandable rather than merely make the transaction look complete.

The cases here concern administrative commitments, not clinical effectiveness. We replaced a practitioner-only booking rule with a combined resource reservation, changed an expiring waitlist offer so that it could not silently replace an existing appointment, added a keyboard-operable route after a usability exercise and funded a recorded handoff for consequential schedule changes. Each choice delayed or reduced another part of the roadmap. The results describe the observed product behaviour and test populations; they do not claim better treatment, shorter clinical waiting times or universal accessibility.

Current focus

I am examining product states that look complete to one person while leaving another person with unacknowledged work. Our next release decisions start with that handoff, including the operational cost of supporting the less convenient but more truthful state.

Conversations I welcome

I am open to a first non-executive appointment in a service-software business, provisionally twenty days annually subject to employer consent, conflicts review and the actual board calendar.