Following the opportunity after the recommendation is accepted

Mandate

Connect technical opportunities, site relationships and commercial models into coherent enterprise choices

Outcomes

• Corrected my unsupported addition of standalone efficiency estimates
• Narrowed a service rollout around unresolved site tenure
• Revised an inadequately supported equipment-exit assumption
• Initiated a bounded paid-scoping trial after reviewing free assessments

Decisions in context

The CSO appointment began in January 2021. Fourteen colleagues now work through three leads with ₹4.2 crore FY2026–27 operating expense, and I coordinate ₹9.8 crore of proposals without independent capital approval. The enterprise has 165 employees and ₹124 crore FY26 revenue. Priya leads the company, while Hamid and qualified professional owners retain technical and related assessments. I own no shares in Zemlavi and have not been appointed to its board. The recent decisions required us to examine the business behind an attractive project account. I withdrew a portfolio total that ignored interactions, narrowed a rollout around site conditions, revised an exit assumption and tested a different customer-development route. The outcomes retained costs and unfinished questions. My responsibility is to make the choice coherent enough for authorised decision-makers to assess, rather than let strategy borrow authority from the functions whose work makes a proposal possible. A board contribution would use that habit through scrutiny, with management still responsible for implementation.

Reason for the move

Current executive appointment; considering one first external board role

Mandate

Examine the portfolio, acquisition route and obligations behind proposed efficiency services

Outcomes

• Connected project combinations with the enterprise proposition
• Examined customer-development effort as a strategic commitment
• Brought end-of-relationship assumptions into portfolio discussions

Decisions in context

I became strategy director in July 2015. The title described a functional executive appointment and did not confer a statutory directorship. Zemlavi had 112 employees and ₹61 crore revenue for FY ending March 2016. Ten colleagues worked through two leads within ₹2.1 crore annual strategy expense. I moved beyond developing individual opportunities to examining the shape of the business we were building around them. That included the way customers entered the service, the combinations of measures we proposed and the obligations remaining when an engagement ended. I learned that an apparently attractive project could be a poor fit for the company if its continuing requirements were not understood. Equally, an unresolved question did not necessarily make the opportunity worthless; it might call for a different scope or sequence. The later CSO role widened my responsibility for presenting those alternatives clearly to the executive team and directors, including the reasoning I had personally endorsed.

Reason for the move

Promoted to CSO in January 2021

Mandate

Turn identified efficiency opportunities into proposals with explicit technical, site and commercial conditions

Outcomes

• Moved from advisory assignments into continuing enterprise responsibility
• Examined how customer-site assets changed the service model
• Connected opportunity selection with the obligations of delivery

Decisions in context

I joined Zemlavi in September 2008. The business employed sixty-four people and recorded ₹18 crore revenue for FY ending March 2009. Seven planning colleagues worked through two leads with ₹76 lakh annual expense. Working inside a developer meant remaining accountable after a recommendation had been accepted. Selected assets would sit at customer premises, and the company's obligations could last beyond the original installation discussion. I learned to connect the apparent technical benefit with the site relationship, commercial terms and responsibilities of the people who would deliver the service. A promising idea could require substantial work before it became a proposition the company was prepared to own. The move also made me more respectful of specialist boundaries: planning could organise the decision without certifying an engineering result or interpreting every agreement. Promotion to strategy director expanded the same questions across the portfolio and the customer-development model, rather than only within individual projects.

Reason for the move

Promoted to director of strategy

Mandate

Explain how market opportunities could become workable customer and project relationships

Outcomes

• Distinguished customer need from the conditions required to invest
• Connected market recommendations with implementation questions
• Managed research delivery without implying technical approval authority

Decisions in context

The market-planning appointment began in June 2001. Dorvemi had 131 employees and ₹31 crore revenue for FY ending March 2002. Eleven colleagues worked through two leads within ₹82 lakh annual expense. I became responsible for the quality and usefulness of recommendations delivered through other people. A customer could express a strong need while lacking the site arrangement, approval or operating conditions assumed by the proposed response. I wanted our account to explain that gap rather than treat demand research as the end of the commercial question. The work also taught me to distinguish a market interpretation from a technical finding, bringing the relevant specialists into discussions when the proposal crossed that boundary. Moving to Zemlavi gave me a chance to follow the chosen opportunities inside one enterprise over time. I wanted to see how the assumptions in a recommendation survived actual commercial and delivery responsibilities instead of leaving their later interpretation entirely to the client.

Reason for the move

Joined an efficiency developer to remain responsible for the chosen portfolio

Mandate

Prepare market evidence while preserving the differences among customers and their investment conditions

Outcomes

• Learned to examine what a market total included
• Separated a stated customer need from a completed investment decision
• Built research practice under supervisory review

Decisions in context

I completed economics at Velzethi School of Economics in June 1994 and began at Dorvemi in July. The firm employed fifty-seven people and reported ₹8.4 crore revenue for FY ending March 1995. My work sat inside a five-person analysis group with no supervisory or spending responsibility. Research managers reviewed the methods and interpretation before recommendations reached clients. I learned that a large market figure could combine customers with different needs, resources and reasons to act. A useful analysis needed to preserve the distinctions that changed the proposed decision. I was not authorised to make a client's investment choice or certify a technical solution. That early boundary helped me understand the value of a well-framed question. Promotion into planning management brought responsibility for colleagues and expense, but it did not remove the need to explain what the evidence actually represented before allowing its aggregate to become a commercial promise.

Reason for the move

Promoted to market-planning manager