From service estimates to the company's next commitment

Mandate

Make product, market and partnership choices explicit about the obligations and assumptions they create.

Outcomes

• Separated eight module retirements from three continuing support obligations
• Presented a licence decision with ownership and renewal differences intact
• Recommended a bounded food-plant pilot based on feasible instructor participation
• Matched the partner launch count to six accepted, prepared participants

Decisions in context

Becoming CSO widened the conversation from the product portfolio to the company's sequence of commitments. I lead a small advisory team, not the product and delivery organisations whose work makes a strategy real. Our ₹4.6 crore budget covers the function; the larger commitments in the cases require their own approvals. I have learned to make that authority visible when describing outcomes. The most useful work often happens before a paper reaches directors, when a product owner, finance colleague or customer team identifies an obligation the initial proposal omitted. I present the resulting choice to the chief executive and board, including what remains uncertain. The aim is to give the decision-maker a proposal it can later revisit intelligently, rather than a polished story that becomes difficult to question once people have committed to it.

Reason for the move

Current appointment; preparing selectively for a first external board role.

Mandate

Connect product development choices with customer use, reusable capability and the cost of maintaining variation.

Outcomes

• Brought support responsibilities into product planning
• Distinguished reusable modules from customer-specific commitments
• Included delivery leaders before recommendations reached approval
• Supported a consistent product account through the 2020 ownership change

Decisions in context

This appointment taught me how easily a portfolio grows one reasonable exception at a time. Each request could have a credible customer and still add a version or support obligation that the overall plan had not recognised. I worked through two leads and an eleven-person team, with a ₹2.1 crore expense responsibility rather than ownership of all development spending. We brought product and delivery colleagues into planning earlier and asked what could actually be reused. The ownership transition in 2020 added different investment horizons to the discussion, but it did not remove existing customer promises. I learned to describe a strategic choice in terms that founders, employees and investors could examine together. The move to CSO followed from that broader work, while leaving execution with the leaders responsible for it.

Reason for the move

Promoted to CSO as responsibility expanded across product, market and partnership choices.

Mandate

Explain the resources and client participation needed behind a simulation-software proposal.

Outcomes

• Connected proposals with instructor availability and equipment context
• Separated software scope from client competence assessment
• Made customer-specific development visible in the planning account

Decisions in context

Zevrali was small enough that a planning question could reach the people doing the work quickly. That access helped me understand where a commercial description simplified the delivery problem too far. I led six colleagues and a ₹95 lakh function budget, reporting to the commercial director. We examined the instructor participation and equipment context needed for a useful simulation project, instead of assuming that software alone constituted a training programme. The boundary mattered: our product could support learning without certifying a person's competence to operate equipment. I also saw how a customer-specific request changed later support work. Those observations gave me a stronger basis for product decisions than the proposal value alone. The promotion in 2012 followed an increasing role in connecting the commercial plan with choices about reusable capability.

Reason for the move

Promoted into product strategy after developing a cross-functional view of the software portfolio.

Mandate

Make content adaptation and continuing update requirements visible in business planning.

Outcomes

• Compared proposal assumptions with actual content-adaptation work
• Distinguished one-off development from recurring update commitments
• Progressed into management of a five-person planning team

Decisions in context

The move into digital learning introduced a product whose apparent repeatability could be misleading. A training package might share much of its content across customers while still requiring specialist adaptation for the way each organisation taught and assessed the work. I began as an analyst and became planning manager in 2003, leading five colleagues with a ₹65 lakh annual expense budget. We compared proposals with the work that followed and made update responsibilities more explicit. I was not an instructor or a technical authority on the customer's equipment; the planning task required those colleagues' judgement. The experience made me interested in software that could support controlled reuse without pretending every setting was identical. Zevrali offered a chance to examine that question across a product portfolio, so I moved in April 2006.

Reason for the move

Joined Zevrali to work more directly with a reusable software product and its commercial choices.

Mandate

Compare service demand, parts availability and the customer commitments behind the operating plan.

Outcomes

• Learned to preserve assumptions behind service-demand estimates
• Identified continuing obligations after equipment sales ended
• Connected planning records with the experience of service colleagues

Decisions in context

I joined soon after completing my statistics degree and initially concentrated on making the planning figures consistent. Service colleagues showed me why consistency was not enough. A demand estimate could be technically neat and still miss a customer's need for an older machine or the time required to obtain a particular part. I worked under the service planning manager in a four-person team and had no spending authority. My contribution was to ask what the record meant and bring the relevant evidence into the discussion. The experience taught me that a company can finish selling something before it finishes being responsible for it. That lesson travelled with me when I moved to digital learning, where content and software created a different form of continuing obligation after the original sale.

Reason for the move

Moved into digital learning to develop a broader business-planning role.