Abinash Tripathy and the advantage of leaving things out

A customer has a question inside a mobile game. To get an answer, the customer must leave the game. It sounds like a minor inconvenience, the sort of thing software users learn to tolerate while the people who build software congratulate themselves on something else. Abinash Tripathy saw room for a company in that small departure. Help, he thought, ought to live where the trouble began.

Getting there required an uncomfortable act of subtraction. Tripathy and his colleagues had already built a customer-service prototype with chat, email, phone and mobile support. It was a respectable collection of capabilities. Then they looked at the competition. Zendesk and Freshdesk had money, momentum and customers. A longer feature list was unlikely to make those advantages disappear.

So the team stripped its product back and concentrated on mobile. Helpshift would put assistance inside the app itself. The decision gave the company a clearer reason to exist, although it also meant surrendering work that engineers had already done. A product roadmap can be a remarkably expensive place to keep a souvenir.

The party fund, the scholarship and the code

Tripathy’s introduction to programming had a pleasingly practical motive. As a young man, he wanted money to go out. He discovered that people would pay for code he could write. He later recalled that programming helped him obtain a scholarship to the United States and buy a car within six months of arriving. The route from party money to enterprise software was indirect, but the early transaction was straightforward: make something useful, and somebody might pay.

He grew up in Chennai with his sister and a father who worked as a bureaucrat. His recollection of childhood centres on lively, intellectually stimulating conversations. In his working life, conversation would become both the product and the problem: how people ask questions, how organisations answer them, and how much unnecessary ceremony gets between the two.

At Oracle, he worked as a technology evangelist and product manager for web development tools. Openwave followed, during the early expansion of the mobile internet. Later he established Zimbra’s Indian division, growing the team to 40 before Yahoo acquired the email-software company. These jobs placed him near successive changes in how people used computers: the web, internet-connected phones and collaborative software. They also gave him experience building teams before he needed one of his own.

A company looking for something to build

By February 2009, Tripathy had left Yahoo. He was writing about Indian startups, taking positions with enough force that his blog came with a warning about his opinions. His interests included the quality of engineering teams, practical experience and entrepreneurship in India. The voice was that of a participant who intended to get back to work.

The next venture began as Infinitely Beta, a lab in Pune. Its name allowed for the possibility that nobody was finished. Tripathy put in $300,000 of his own money and joined forces with Baishampayan Ghose. They wanted a place where technically ambitious people could experiment together before the demands of selling and scaling settled the daily agenda.

An early product explored a private, Quora-like question-and-answer service for enterprises. Knowledge management was useful, but the founders came to see customer support as a more pressing need. The work moved towards a broad helpdesk before narrowing again to mobile. The sequence matters: Helpshift emerged through several decisions, rather than arriving fully formed in a flash of founder intuition.

That makes the team unusually central to the origin story. The people preceded the settled product. An idea could be discarded while the group that produced it continued. For an enterprise that would eventually ask customers to trust its infrastructure, the founders first made a substantial bet on their own colleagues.

Please solve the puzzle before applying

The hiring process carried that bet into public view. Helpshift embedded a puzzle in its homepage code. Prospective employees who found and solved it could move forward in recruitment. It was a job advertisement that expected the applicant to look under the bonnet before anyone handed over a key.

Tripathy spoke about the practice at TechSparks Pune in 2013. He welcomed people who could demonstrate ability even without a prestigious academic pedigree. He also liked bringing artists and programmers together, arguing that both cared about refining their work. The appeal was craft: people sufficiently interested in making something better to keep returning to it.

In a separate interview, he described technical hiring that involved a take-home coding exercise and conversations with team members. He placed value on attitude and continuing to learn. His preferred phrase was “always be learning”. It fits the company’s changes of direction rather neatly. An employee who regards yesterday’s solution as sacred may struggle at a company whose useful breakthrough involved throwing a good portion of yesterday away.

“Dare to be different and play to your strength.”

Abinash Tripathy · TechSparks Pune, 2013

Three months to earn Supercell’s trust

A clear product still needed someone willing to put it in front of customers. Tripathy’s account of winning Supercell shows how much patience that could require. A sales colleague persisted in seeking a demonstration. Eventually, the gaming company’s chief operating officer visited Helpshift in San Francisco. Interest became an opportunity to test the product in a newer game.

The arrangement limited the customer’s risk. Supercell already had a support operation and had little reason to replace it on the strength of an enthusiastic presentation. Helpshift had to show that people could get help inside the game and that the experience worked at the scale a gaming company required.

Tripathy said the pilot lasted about three months. After examining the results, Supercell moved its support to Helpshift. Other game companies noticed the provider’s name inside the games. A customer became a demonstration that competitors could encounter for themselves.

This was a slower, more practical kind of persuasion than a grand launch. The founders’ promise had to survive ordinary use. A player looking for an answer does not pause to admire a startup’s market positioning. The button either helps or becomes one more thing to complain about.

A small screen, a large test

The early mobile focus did not make the engineering task small. Gaming brought large audiences and substantial volumes of questions. It offered a demanding place to learn how support software behaved under load, with lessons that could carry into other industries.

In September 2014, Helpshift had announced a $10 million Series A, bringing reported funding to $13.2 million. At that point, Tripathy’s attention extended beyond the established competitors. He worried about a smaller startup moving faster. It was a revealing concern for a founder whose own differentiation had come from identifying something the larger helpdesks had not made central.

By January 2021, a podcast introduction described Helpshift as installed on more than two billion devices, with Microsoft, Xfinity and Zynga among the companies it served. That figure measures software distribution, rather than two billion people making a daily request for assistance. Its significance is the distance travelled from a Pune lab searching for a product to software embedded in services used around the world.

The geographical arrangement supported that ambition. Engineering was rooted in India, while commercial work put the company close to customers in the United States. Tripathy’s stated goal had been to build a technology company with global impact from India. The ambition appeared in the operating arrangement as well as in the speeches.

The chatbot should know its place

Tripathy’s interest in artificial intelligence predates the recent rush to attach it to every product description. At TechSparks in 2016, he described enterprise software moving through stages of digitisation, automation and intelligence. He expected progress to appear through practical functions such as suggestions and predictions. His subject was how software might make itself useful inside an existing business.

By 2019, his discussions of AI included a pointed distinction between demonstrated capabilities and capabilities that existed on a vendor’s roadmap. Customers could hear a sales pitch about tomorrow’s technology and reasonably assume they were buying it today. That gap between presentation and delivery was a problem for anyone trying to sell useful automation.

In a January 2020 conversation, he advocated automating common, frequent support requests first. Helpshift worked on bots for specific tasks, rather than attempting a single bot that understood everything. Rare and complicated cases could remain outside that initial scope. The discipline resembled the earlier mobile pivot: decide what the system can handle, and give that decision consequences.

Messaging also allowed a conversation to continue without requiring both participants to remain available at the same moment. The attraction was ordinary and human. People could ask a question, get on with their day and return to the answer. Customer support had long found elaborate ways to occupy a customer’s time. Tripathy wanted software to give some of it back.

The title changes; the question remains

Tripathy’s own job changed as the company developed. After serving as chief strategy officer, he returned to the CEO role in February 2020. Helpshift paired that appointment with Eric Vermillion’s elevation from chief revenue officer to president. The company described the arrangement as a combination of product and technology experience with operational leadership.

In December 2022, Keywords Studios announced an agreement to acquire Helpshift for up to $75 million. The announced terms included $60 million initially and a further amount tied to performance. Keywords already provided services to the games industry; support automation fitted alongside its player-support work. Helpshift subsequently became part of the group.

Tripathy’s public work now extends beyond the CEO title attached to his older interviews. His LinkedIn profile lists Various Startups, and his public record includes advising Postman. In January 2026, he published an article titled “Bol Bachan AI vs Real AI”. The subject suggests that the distance between a convincing demonstration and a useful product still has his attention.

The pattern across his career is a willingness to stay close to changes in how people communicate, then work through what those changes demand of software. The personal details make that pattern less abstract: code written to pay for evenings out, a team assembled before a settled idea, a puzzle hidden for curious applicants. He has spent years asking what deserves to be built. At Helpshift, one consequential answer arrived when the team decided what to leave out.