For years I regarded a customer's request to involve me as evidence that I was doing my job. I knew the history, could connect people quickly and often explained a difficult point without asking the customer to repeat everything. Those were useful contributions in a young company. They also created a pattern: the most dependable route appeared to be the founder. When the organisation grew, I could not simply announce that the same relationships should now depend on someone else and call the change succession.
The reassurance that helped us grow
I co-founded Tezmavi in 2009 after two decades in benefit administration. Personal knowledge helped the early business earn confidence. Customers were trusting a small organisation with work that could remain relevant through changes in their own teams. Being available mattered, and I do not regret taking that responsibility seriously. The problem emerged when my availability became a substitute for making the company's understanding available through other people. What had been a strength at one stage began to restrict the next stage.
A founder can miss that transition because the feedback is flattering. A customer thanks you for stepping in. A colleague says the conversation became easier once you joined. A difficult issue closes, and the business moves on. None of those observations tells you whether the next issue will be easier for the organisation to handle without you. They may indicate that your intervention solved the immediate problem while preserving the very dependence that made the intervention necessary.
The answer is not to become deliberately inaccessible. Customers should not bear the cost of an executive trying to demonstrate that a successor is ready. Nor should service leaders be left alone with a responsibility they do not yet have the knowledge or authority to carry. I needed to understand what each relationship relied on: historical context, permission to make a decision, the customer's familiarity with me, or my own habit of answering before another colleague had the opportunity. Those dependencies required different work.
In 2024 we committed ₹46 lakh to a programme involving six service leaders and ten selected relationships. The purpose was an agreed transfer of responsibility in the actual customer relationship, not merely a training programme or a revised reporting chart. Nikhil, our COO, asked me to be explicit about when I was still required and when I was inserting myself because I preferred the reassurance of being involved. That question was more useful than a general conversation about my willingness to let go.
Authority has to move with the conversation
Some commercial colleagues worried that customers would hear the change as a withdrawal of founder attention. That was a reasonable concern. A relationship may have been sold partly through personal access, and the customer should not be told that it imagined the value of that access. We had to explain how the service would continue, who would carry the responsibility and what escalation meant. A change that only benefits the founder's calendar is not a convincing proposition for the customer.
Service leaders had their own concern. They could be introduced as responsible while every difficult conversation still came back to me. In that arrangement, the title moves but authority does not. The customer learns to wait for the founder, and the successor learns that an independent judgement will be reopened whenever it becomes uncomfortable. I needed to support the new relationship without quietly making myself the final interpreter of every detail. That required discipline in the ordinary conversations, not only in the formal handover meeting.
It also required recognising where a colleague genuinely needed more support. A founder's impatience can turn succession into an unfair test: someone else must reproduce years of accumulated knowledge immediately, while the founder retains the option to step in and demonstrate superiority. I did not want the programme to reward that performance. The relevant question was whether the company had equipped the person to carry the agreed responsibility and whether the customer could reasonably rely on that arrangement.
We kept my continuing involvement visible. If a relationship still required me, we described it that way rather than record a completed transfer because a new lead had been named. This made the programme less impressive on a simple completion count, but it made the account more honest. It also helped distinguish a genuine operating dependency from a customer's understandable preference for a familiar person. Both can matter, but they do not necessarily require the same response or timetable.
The unfinished three belong in the board account
At review, seven of the ten relationships had completed their agreed handovers and three still needed my participation. I would not turn that into a claim that founder dependence had been solved. The programme covered a selected group, and its own result contained unfinished work. The ₹46 lakh was expenditure on the programme, not a calculated saving in my time or proof of a higher company valuation. Those stronger claims would require evidence we had not established.
Leela, our chair, could therefore ask about the remaining three without first having to dismantle a success narrative. What did each still need from me? Was the dependency understood? Had we given the service leader adequate authority? Had I changed my own behaviour, or merely asked others to become more capable around it? Those questions connected succession to the company's operating model. They were more valuable than asking whether I felt confident in the team, which would have invited a reassuring but largely untestable answer.
The unfinished relationships also mattered to my plans for an external board contribution. A founder should not promise time elsewhere by assuming that internal dependencies will disappear on schedule. My provisional availability has to be assessed against the business as it actually operates, including work still requiring me. The same realism applies to the board considering my appointment. Experience building a company can be useful, but it does not excuse an unreliable calendar or make conflicts easier to ignore.
I now think about succession as a series of relationships in which the institution must become credible in its own right. That includes customers, but also colleagues who need to know that authority will remain with them when a decision is challenged. It includes the board, which needs an account of dependence that is specific enough to examine. The founder remains accountable for helping that change happen and should not confuse stepping back from a conversation with stepping away from responsibility for the enterprise.
There is a quieter form of leadership in allowing another person's explanation to become the one the customer trusts. It produces fewer moments in which the founder visibly rescues the situation. That can feel like losing relevance when it is actually evidence that the organisation is becoming more capable. I still need to test that interpretation against the work, especially the relationships that have not moved. Seven completed handovers are encouraging; three unfinished ones tell me where the next decisions belong. Both facts are necessary to understand the company we are trying to build.