Chief Information Officer India
The software worked before the service account was complete

A calendar can be precise about the wrong thing. I learned that when a release I accepted placed the end of one booking directly beside the start of another. The application had no overlap, but the operating sequence did. We had omitted the turnover interval facilities had specified for the premises arrangement. It was my decision to accept a technical account that did not yet describe the service the company intended to provide.
I completed computing studies at Qezvralni Computing College in May 1994 and joined Revqalthi Systems Services in June. Eight people formed the applications-support group. I investigated reported problems, prepared reproductions and helped users explain the steps that led to a result. I did not hold authority over their underlying commercial decisions. The work taught me that a successful transaction in software could still leave the user unable to complete the task that had brought them to the system.
In April 2002 I moved into applications implementation, with twelve colleagues and ₹1.5 crore annual function expense. We connected business instructions with the rules a system would execute repeatedly. I learned to ask which exceptions were genuine alternatives and which revealed that the initial rule was incomplete. The difficulty was often less about coding a choice than establishing who had authority to make it. A default could look harmless during a demonstration and become a commercial decision once customers began relying on it.
I joined Drevqazni Kitchen Properties in April 2010 as Property Systems Manager. Eighteen technology colleagues worked within ₹2.8 crore annual expense. Commercial kitchen premises introduced a very physical account behind seemingly simple software terms. The same room had equipment, access arrangements, operating conditions and responsibilities that belonged to different people. I worked with facilities colleagues to understand how those facts reached a booking or a published description. My job was to represent the approved account, not to replace professional assessment of the premises or the food businesses using them.
Promotion to enterprise-applications leadership came in April 2016, with twenty-five colleagues and ₹4.4 crore annual function expense. The flawed booking release followed in 2019. The selected arrangement required ninety minutes between uses, but our application treated a customer’s booked period as the whole resource demand. Seventeen of twenty-four reviewed bookings fitted the actual sequence; seven did not. A ₹54 lakh, ten-week review and reconstruction produced twenty-one fitting bookings and three rescheduled ones. That result did not establish a universal cleaning standard or prove every possible sequence would work.
I became CIO in April 2022. A room-description review in 2023 found that equipment and amenity statements had travelled farther than their evidence. Of sixty selected rows, forty-four were confirmed and sixteen unsupported. After facilities-led examination, fifty-six could be supported and four remained withheld. I wanted the publishing process to preserve the room-specific evidence rather than treat a familiar property brand or similar layout as permission to copy the same promise everywhere. Confirmation of a description still did not certify technical suitability for a customer’s intended activity.
The 2025 cancellation review required a different distinction. Forty-eight cancelled bookings included thirty-two spaces cleared for release, ten awaiting physical inspection and six awaiting contractual clearance. A customer’s cancellation did not by itself resolve every condition for the next offer. We revised the workflow through a ₹46 lakh, nine-week programme, keeping the responsible owners visible at each stage. The system did not decide a refund or invent a right to re-let premises. It represented the decisions and unresolved work that the business needed to manage.
Today thirty-two technology colleagues work through three heads within ₹6.7 crore annual expense and a separate ₹2.4 crore approved programme. I report to Arun Vezqalthi and work with Meera Zaqvelni, whose facilities account remains essential to our systems. I have no personal equity or statutory director role. For a future board contribution, I still need governance preparation and a realistic calendar assessment. I want leaders to ask what the software’s answer assumes about the physical service, especially when the answer is convenient. An explicit waiting state can be more useful than a confident available label if it keeps the company from making a promise it has not yet established it can honour.
Open to Board appointments · Executive opportunities
Languages / Hindi · Urdu · English
A leadership conviction
A room can appear free in an application while still carrying unfinished work or an unresolved commitment. I want the system to preserve that distinction before it makes the next promise.
- Technology colleagues
- 32
- Three heads; enterprise headcount 286
- Annual technology expense
- ₹6.7 crore
- Separate approved programme of ₹2.4 crore
- Commercial kitchen workspaces
- 12 premises
- Four owned and eight leased; no food-production claim
Career chapters
2022-04 — present 01
Chief Information Officer
Drevqazni Kitchen Properties
Make enterprise systems preserve the conditions behind each premises promise
2016-04 — 2022-03 02
Head of Enterprise Applications
Drevqazni Kitchen Properties
Connect customer-facing application rules with the complete operating sequence
2010-04 — 2016-03 03
Property Systems Manager
Drevqazni Kitchen Properties
Represent room identity, operating conditions and responsible owners in business applications
2002-04 — 2010-03 04
Applications Implementation Manager
Revqalthi Systems Services
Translate approved business decisions into repeatable application rules
1994-06 — 2002-03 05
Applications Support Analyst
Revqalthi Systems Services
Reproduce system issues while preserving the task the user was trying to complete
Education & credentials
- Bachelor of Science in Computing
- Qezvralni Computing College · 1994
Perspectives from colleagues
Zeenat asks which physical or contractual condition sits behind the application’s answer. She withdrew her own release acceptance when the booking sequence omitted the turnover work.
She keeps our premises decisions visible in the workflow without turning a technology status into a technical approval. The unresolved cases remain part of the operating account.