Skip to website
Darius QevzomriChief Strategy Officer

Areas of practice

The operating questions inside an attractive opportunity

01

Distinguishing market throughput from the enterprise economy

I examine whether a strategy's headline figure describes the company's income, a customer's activity or a wider market passing through its service. The ₹186 crore ticket-face-value comparison I approved in 2018 failed that test. Our selected portfolio produced ₹12.4 crore in service fees, and the appraisal needed to begin with the actual economics and obligations of those fees. I work with finance to establish the basis before using a number in an investment argument; I do not substitute my own presentation for accounting judgement. The distinction also affects which competitor or adjacent business is a useful comparison. Two firms can process similar event volumes while earning income and carrying responsibilities in quite different ways. A credible strategy should make that difference visible rather than compress it into a single scale ranking.

02

Planning expansion around coincident demand

I assess expansion through the dates on which customers need service, as well as their geography and annual value. In our four-city review, twenty-four of thirty-six selected assignments occupied eight weekends. A wider map would not have dispersed those peaks. The revised recommendation used four reserve crews instead of twelve permanent new teams and accepted a smaller service ambition. My role was to bring the calendar evidence into the strategic choice; Nikhil and the operations team retained responsibility for workable deployment. This approach does not assume that spare capacity can always travel or that a reserve model suits every venue. It asks whether the proposed footprint is supported by the actual pattern of demand, including preparation, travel and the work that must happen at the same time.

03

Testing an adjacency through its operating differences

A museum and an evening performance may both issue tickets, yet their visitors move through a day differently. I helped frame a three-venue timed-entry pilot around that distinction, with ₹62 lakh committed to learning and service preparation. Two venues continued and one declined the arrangement. I retained that outcome rather than treating the shared ticketing vocabulary as proof of a ready-made expansion. Strategy should identify the capability that transfers and the work that must be learned or supplied elsewhere. It should also say what the trial cannot establish: our software work did not certify safe occupancy or replace the venue's crowd-management responsibility. A useful adjacency test narrows the unknowns enough for a further decision without pretending that a small trial has already resolved the whole market.

04

Separating a recurring contract from an unlimited claim

I examine the service promise inside recurring venue income. In 2025, nine of fourteen reviewed customers had relatively steady support patterns while five concentrated their requests around clusters of events. The annual invoice alone did not explain the capacity the enterprise needed to reserve. We spent ₹54 lakh developing clearer service options and support planning, with eleven customers accepting revised arrangements and three remaining in discussion. I did not count those three as renewed or claim that the clearer offer had improved profit. The strategic question was which commitments the enterprise should sell and how they fitted its delivery model. Commercial and operational colleagues then owned their respective terms and fulfilment, rather than leaving a broad annual label to decide what support a customer could reasonably expect.

How I lead

A larger number is not necessarily a larger business. I once used the face value of tickets processed for a portfolio to frame an opportunity that should have been understood through our service income and obligations. I now ask which economic activity a strategy actually owns, on which dates it must perform and what the attractive comparison leaves outside the picture.

At scale

The responsibility, in figures

32 years

Commercial and strategy career

Research associate through CSO responsibility

₹83 crore

FY2026 enterprise revenue

₹54 crore software/licence support; ₹29 crore event services

204

Enterprise employees

March 2026 headcount

17

Strategy colleagues

Three leads within the CSO remit

In practice

Decisions and their consequences

Case I

Reopening the appraisal I had framed around ticket value

In 2018 I led an appraisal of a proposed ₹9.2 crore transaction involving a selected venue-client portfolio. My paper foregrounded ₹186 crore of ticket face value processed for those clients. Our service fees from the same portfolio were ₹12.4 crore. The larger figure made the opportunity look substantial, but described the events supported by the system rather than the income of our service business. It was not our total company revenue either. I had approved the framing and was responsible for correcting it.

Finance challenged whether the comparison supported the investment argument. The commercial team felt the throughput still demonstrated the importance of the relationships, and I agreed it had descriptive value. The disagreement concerned what decision it could justify. A large volume did not establish the durability of our fees, the cost of supporting peak dates or the rights included in a transaction. We could proceed with a prominent scale narrative and append qualifications, or reopen the appraisal around the income and commitments we would actually acquire.

I recommended reopening it. The review cost ₹37 lakh, covering revised commercial work and professional input. Finance retained responsibility for its accounting assessments and the authorised decision-makers retained investment authority. My team reworked the strategic comparison, distinguishing event activity from company income and examining the service burden behind the fees. The revised paper also retained uncertainties about the portfolio rather than converting missing material into a favourable assumption. The consequence was that the proposed transaction did not proceed.

I gave up the momentum of a recommendation I had helped create and accepted the expense of revisiting it. The ₹9.2 crore was proposed consideration, not a loss already incurred or cash recovered. I cannot claim that declining it prevented a particular future failure. What the decision established was narrower: the investment case originally presented was not supported by the economic basis we needed. My lesson was to ask what a number belongs to before making its size the organising feature of a strategic argument. Throughput can describe reach, but it should not silently become a substitute for the business's own earnings and obligations.

Case II

Reducing a four-city expansion after laying out the weekends

In 2022 we considered expanding event-access support across four cities with twelve permanent new teams. The proposal carried ₹5.4 crore of annual operating expense. The geographic spread appeared to diversify demand, but Nikhil's operations colleagues questioned whether the same teams would still be needed on the same dates. A map could show four markets while concealing one concentrated service calendar. I asked the strategy team to examine the assignments behind the annual projection before recommending the staffing commitment.

Of thirty-six selected weekend assignments, twenty-four fell on eight weekends. These were the assignments reviewed, not a statistical estimate of all demand in the four cities. Preparation and travel further constrained the idea that one team could simply move between events. Commercial colleagues argued that permanent local presence would help win more work. Operations argued that the proposed staffing pattern could leave us stretched at peaks and underused at other times. Both concerns mattered; a smaller model would also limit the work we could credibly pursue.

We spent ₹46 lakh on the calendar study, operating design and pilot preparation. I recommended four cross-trained reserve crews with a ₹2.1 crore annual commitment instead of twelve permanent new teams. Leena and the authorised management process approved the revised approach, while Nikhil owned deployment and the service conditions. The choice deliberately reduced the initial footprint and left some prospective work outside the offer. It was not a claim that four crews could perform the same work as twelve or that travel would solve every simultaneous demand.

The revised annual commitment was lower than the proposal, but I did not report ₹3.3 crore as realised savings. The larger model had not been implemented, and the two options offered different capacity. The decision changed the ambition as well as the expense. For me, the strategic lesson was that geographical expansion and demand diversification are separate propositions. Before committing to a larger footprint, I want directors to see when the enterprise must perform, what capacity is genuinely interchangeable and which opportunities the chosen model will leave unserved.

Case III

Keeping the museum pilot smaller than the market story

In 2023 I proposed a three-venue pilot for timed-entry museum services. Our existing ticketing software made the adjacency look straightforward, but the operating pattern differed from an evening event with a concentrated arrival window. Visits could continue across the day, people stayed for different lengths of time and a later arrival could overlap with visitors admitted earlier. A familiar ticket transaction did not by itself provide a complete service design for that setting.

The growth team wanted a broad museum proposition ready for sale. Nikhil asked us to understand the venue's responsibilities and visitor flow before treating the software fit as an operating fit. I supported a ₹62 lakh pilot covering configuration, service preparation and examination of the different visit patterns. We could have used a single proposition across all three venues, which would have been easier to explain, or allow the trial to reveal that some requirements did not fit the arrangement we were prepared to offer.

We chose the latter. The venue operators retained responsibility for their premises, visitor management and safety decisions; our work did not certify occupancy or substitute for their professional assessment. My team examined the commercial and organisational implications of timed admissions, including support during the day and the limits of information available through ticketing. We kept the pilot's learning separate from claims about attendance growth. The fact that a visitor held a time slot was not treated as complete knowledge of everyone present in a building.

Two venues continued the trial and one declined the operating arrangement. I retained the third outcome in the recommendation for further development. The ₹62 lakh was an actual pilot commitment, not a figure to divide into a claimed all-India acquisition cost. We gained a more specific understanding of the adjacency, but did not prove that every museum needed the same service. The strategic trade-off was accepting a narrower, less immediately scalable proposition in return for an expansion account grounded in the responsibilities and visitor patterns of the venues actually examined.

Case IV

Declining event upside that would change the enterprise we ran

In 2024 we were invited to participate in an event-promoter arrangement. The proposed commitment was ₹7.6 crore, with a forty-percent share of specified event upside under the proposal. Some colleagues saw a chance to earn more than a service fee from activity we already helped support. The attraction was understandable: we knew ticketing and access operations, and had relationships in the event ecosystem. But familiarity with those services did not mean we already owned the commercial risks of promoting an event.

I led the strategy review with finance, operations and professional advisers contributing within their responsibilities. The choice was not between a certain fee and certain larger earnings. Promotion involved commitments around the event programme, venue and demand that were different from our normal service role. The proposed upside depended on how the event performed, and the enterprise would need capabilities and decision rights beyond those used to provide ticketing software. A larger participation figure could obscure the fact that we were being asked to become a different kind of business.

The commercial proponents favoured proceeding as a limited experiment. Nikhil questioned the management attention and operating responsibilities it would absorb. I recommended declining the ₹7.6 crore commitment, after ₹33 lakh of diligence and strategic review. Leena and the authorised decision-makers accepted that recommendation. We kept open the possibility of a conventional service relationship, subject to its own terms, without presenting that possibility as a signed contract or a substitute return from the rejected proposal.

The consequence was giving up participation in any upside that might have emerged from the arrangement. I cannot claim that we avoided a known loss; the proposed participation did not take place, and the counterfactual remains unknown. The decision was about the business model we were willing to operate and the responsibilities needed to make the choice credible. A service enterprise can choose to become a principal in another activity, but it should do so explicitly. Familiarity with a customer's transactions should not quietly become a reason to assume the customer's whole commercial position.

Case V

Rewriting the capacity promise inside annual venue contracts

In 2025 I reviewed fourteen venue relationships as we developed the next recurring-contract proposition. Nine had relatively steady support patterns; five concentrated requests around groups of events. The annual licence description made the relationships look more uniform than the demands they placed on the service team. Sales wanted a simple package, while operations wanted the offer to distinguish ordinary support from concentrated event-date requirements. The disagreement was about what the enterprise was committing to supply, not merely the wording of an invoice.

I recommended a ₹54 lakh programme to develop service options, examine the calendar and prepare clearer customer discussions. The alternative was to retain a broad annual description and handle each difficult weekend through account-level negotiation. That might have preserved an easier sales message, but it would also have left a material capacity decision until several customers needed support simultaneously. The revised proposition asked customers to discuss their likely event pattern and the support arrangement they required, without pretending that an annual fee could remove every operational constraint.

Commercial colleagues retained responsibility for negotiated terms and Nikhil's team retained delivery responsibility. My strategy group examined how the options fitted the enterprise's desired mix of recurring relationships and event services. We distinguished a customer accepting revised arrangements from one still discussing them. Eleven customers accepted and three remained in discussion at the review point. Those three were neither completed renewals nor assumed losses. We did not claim that clearer scope had already produced a profit improvement or that the revised pattern removed all peak-date risk.

The trade-off was a more demanding commercial conversation and a less uniform proposition. The benefit was a better-defined basis for future commitments, rather than an invented financial result. I learned to ask whether recurring income is accompanied by a recurring and understood service obligation. Predictability in billing can be valuable, but the calendar of the work still matters. A strategy that values annual relationships should also explain which claims on scarce support capacity those relationships create and how management intends to honour them.