A familiar customer is not an operating model

The relationship made the proposal persuasive

The proposal began with a genuine advantage: we knew the cinema owners. Our company had supplied equipment, coordinated installations and supported agreed systems over time. Colleagues understood the practical importance of a working venue and had earned relationships through difficult service conversations. When a team proposed a ticketing venture, it was reasonable to ask whether those relationships could support another business. The mistake would have been to treat that opening question as most of the answer.

The first-year forecast showed ₹2.2 crore commission receipts. Launch spending was estimated at ₹1.7 crore, with ₹90 lakh recurring annual support expense. The figures described different categories and remained estimates. They were not a signed revenue account, a complete valuation or proof that the venture would fail because the first period carried launch expenditure. I wanted the paper to retain those distinctions so that the board could examine the proposed business rather than argue over a simplified headline.

I authorised ₹36 lakh of exploration before any launch commitment. That decision was deliberately smaller than approving the venture. It allowed the team to investigate customer need, capabilities, commercial arrangements and the specialist legal and technical work required. The spend was real even if the conclusion was not to proceed. I did not want colleagues to believe that discovering a reason to decline would make the exploration look wasteful. Useful investigation must be able to change the commitment.

The sponsor's case deserved respect. An established relationship can reduce the difficulty of an initial conversation and reveal needs that an unfamiliar entrant would miss. Cinema owners already had reasons to speak with our team. There might be opportunities to coordinate services more effectively. Dismissing the proposal simply because it was adjacent would have been an equally weak decision. I wanted to understand where our existing strengths carried over and where the proposed activity required something different.

Separate access from capability

Technical service and ticketing nevertheless create different responsibilities. Knowing the installation does not establish the capability to operate a customer-facing transaction service. Visiting a venue does not make the service team available for every kind of support request that another product might generate. The review had to consider the people, systems, agreements and continuing work required on their own terms. We could not make those obligations disappear by placing the venture inside an established customer relationship.

Sahana brought the existing operating plan into the discussion. We were still clarifying service scope across equipment families and working through unresolved transition questions. Entering a new activity would draw on leadership attention as well as money. That attention is harder to place in a financial model, but it is not free. The board needed to know which work might be postponed, which responsibilities would need new owners and which assumptions depended on already busy colleagues absorbing another mandate.

Prakash asked a question that helped the board move beyond enthusiasm and caution as opposing temperaments. What would the company stop doing, or do later, if it chose this venture now? The question did not require us to assume that existing work always took priority. It required a deliberate choice. A company can decide to change its direction, but the operating consequences should be part of that decision rather than emerge after the new initiative has become public.

The sponsor preferred a small launch, arguing that an operating product would teach us more quickly than further study. There was merit in that position. Some questions cannot be answered fully before real use. Yet a small launch still introduces obligations to customers and requires support, commercial clarity and responsible ownership. Calling it a pilot does not automatically make those commitments negligible. We needed to judge whether this was a useful next experiment for this enterprise, not whether experimentation was desirable in general.

I recommended declining the venture at that point, and the board agreed. We continued as an equipment integration and technical-service company without becoming a ticket seller. The decision was specific to our capabilities, priorities and evidence then. It was not a statement that ticketing could never be attractive or that service companies should remain permanently within their original scope. A future proposal could be different, but it would need a fresh case rather than inherit momentum from this one.

The reporting after the decision needed the same care as the proposal. The ₹2.2 crore forecast was not revenue lost from an established operation. The unapproved launch budget was not a realised saving. The ₹36 lakh exploration cost remained incurred. Those distinctions prevented us from turning a decision not to launch into a convenient financial victory. We had bought a better basis for choosing, and we still carried the costs and responsibilities of the business we chose to continue.

Exploration must be allowed to end without a launch

The team also needed a clear account of what happened to its work. I did not want the exploration to become an embarrassing folder nobody would revisit. Its findings could inform future discussions, including what capabilities we would need if the opportunity returned in another form. Preserving the work is different from keeping the venture alive through an informal side project. The board had declined the commitment, and management had to respect that boundary while retaining what had been learned.

I think this is a useful test of an enterprise's attitude to innovation. If every exploration must end in launch to be regarded as successful, the organisation has made investigation a ceremony rather than a decision process. Conversely, if exploration can always be extended without a choice, it can consume resources while avoiding accountability. The useful discipline is to define the question, fund an appropriate investigation and make the next commitment explicitly, including when that commitment is to stop.

For a prospective director, the case suggests questions about the relationship between strategy and capability. What advantage does the existing business actually supply? Which obligations are new? Who will own them? What assumptions are being borrowed from customer familiarity? The board should hear the advocate's argument clearly, but also understand the work displaced and the conditions under which management would reconsider. Directors do not need to design the ticketing product to examine whether the enterprise is ready to undertake it.

I would make the range of possible outcomes clearer at the beginning of another exploration. A team can produce valuable work without producing a launch, provided the decision is grounded and the account is honest. Knowing a customer is a meaningful advantage. Building a different business for that customer still requires a complete undertaking, with capabilities, obligations and economics that the company has chosen to own rather than assumed it already possesses.