Huy Dinh and the Problem With Waiting for Coffee

Huy Dinh wanted his coffee without the queue. In Melbourne in 2016, he and his co-founder Lee were tired of waiting for their usual lattes each day. They began thinking about a way to place an order ahead of time through messages. The idea became BotStar, which reached the public the following year. A perfectly ordinary inconvenience had acquired a software development budget.

There is something pleasingly specific about that beginning. A latte has a customer, an order, a preparation time and a handover. A message can carry the order before the customer reaches the counter. The attraction is easy to understand without a diagram of the future of computing. Someone would like a coffee. Someone else would like to sell one. The queue gets a smaller part in the proceedings.

Dinh is now the co-founder and CEO of Chative.IO, a business messaging platform. Between the coffee idea and the shared inbox sits a sustained interest in the machinery of conversation: how to design it, connect it to other tools and let people step in when software needs help. The connection is an editorial reading of his work, rather than a claim that every subsequent decision began at the same café.

That distinction matters. A good origin story can become a souvenir, polished until it explains everything. Here, the coffee queue explains a starting point. The products that followed had to deal with a much larger collection of questions than whether the milk was ready. Orders, customer information, handovers and messages from different channels all needed somewhere to go.

Da Nang, Melbourne, and a generalist’s route

Dinh describes himself as a generalist. He was born and raised in Da Nang, and his education includes Swinburne University of Technology, with attendance listed from 2005 to 2009. His professional profile places him in Ho Chi Minh City. Those places belong to different parts of the story: childhood, study, a later professional base. They should not be collapsed into the location of a company registration.

His earlier work includes software engineering and product development roles. The career record names Effective Measure, SMSGlobal and JMango, followed by engineering management at Asian Tech and delivery work at FPT Software. It is a route through building software, organizing its development and delivering it to clients. The dates for those individual jobs are less useful here than the range of responsibilities.

A project on his profile gives that range a concrete shape. From August 2012 to June 2013, he worked on an SMS platform with new functionality and an interface designed from the ground up. Messaging was already part of his work before the latte problem. The emphasis on a smoother user experience also predates the later chatbot products.

Calling yourself a generalist leaves room for an untidy résumé. It can also be an accurate description of the work involved in a messaging product. The interface, the underlying systems, the people operating them and the customer at the other end each impose their own demands. Dinh’s career has included responsibilities on several sides of that arrangement. His own label is more illuminating than assigning him a personality from a photograph.

A conversation you could draw

BotStar approached chatbots through a visual editor. Its public proposition was to let users design, develop and train bots visually, making a conversation easier to see and maintain. The product appeared on BetaList in July 2018, with Dinh among its makers. The premise was practical: a conversation becomes easier to work on when its branches can be inspected.

Think of the difference between a shop’s opening hours and a customer’s actual question. Opening hours fit neatly on a page. A question can lead to a second question, a choice, an order or a request for assistance. A visual conversation editor provides a way to lay out those routes. That is an explanation of the design approach, rather than a report of any particular customer’s experience.

The appeal of drawing a flow is that someone can review the decisions before customers encounter them. Where does this answer send the visitor? Which information is collected? At what point should a person take over? Those are editorial questions for an automated conversation as much as engineering questions. An attractive greeting offers little consolation if the next step leads nowhere.

Dinh’s BotStar ambitions extended beyond a single bot. He described wanting an ecosystem comparable to WordPress for website building. It was an aspiration about who could create and maintain conversational tools. The comparison made the intended scale of the idea legible: a tool that other people could use to build their own work. It also left the difficult part, making that tool useful across many businesses, firmly on the table.

The useful exit marked “human”

In March 2019, Dinh announced BotStar’s support for Zapier. The integration connected chatbot activity with other applications. His explanation included five supported triggers, covering new records, subscribers, changes to user attributes, tags and requests for a human operator. The list reads like ordinary administrative plumbing. That is precisely why it deserves attention.

A chatbot can produce a tidy answer while leaving a business with an untidy task. Someone still needs to transfer information, update a record or pass a request to a colleague. Connecting the conversation to another application addresses that second layer of work. The exchange becomes part of a process that continues after the chat window stops blinking.

The human takeover trigger is especially revealing as a product detail. It explicitly makes room for a user asking to contact an operator. Automation has an exit. Nothing in that feature proves how Dinh behaves in every business situation, but it does show that a person entering the conversation was part of the system’s design, rather than an interruption outside it.

There is a modest kind of wit in the phrase “human takeover.” In this setting, the person arriving is likely to handle a customer’s question, rather than reclaim civilization. Yet the language points to a serious responsibility: someone must inherit the conversation. A handover that preserves context gives that person a chance to help without asking the customer to start the story again.

Two friends, one shared inbox

Chative was founded in 2021 by two Australian-Vietnamese best friends, registered in Singapore, with employees based in Da Nang. Its 2022 startup presentation named Dinh as CEO and founder of both Chative and BotStar. Vu Nguyen appeared as VP of Growth. The business had a cross-border structure, while its engineering work remained connected to the city where Dinh grew up.

The distinction between a chatbot builder and a shared messaging workspace helps explain this chapter. A builder organizes the routes inside an automated conversation. An inbox organizes the conversations arriving at a business. Chative’s proposition brings channels together so a team can work with them in one place. The scope includes the staff answering messages alongside the software helping them.

Picture a hypothetical shop receiving questions on its website and social accounts. A customer may care about a product, a delivery or an existing order. The team needs both the message and the surrounding information. Chative’s current offering includes an omnichannel inbox, e-commerce messaging, customer information and AI assistance. Its advertised tools connect that exchange with the work of selling and supporting an order.

The company says more than 10,000 businesses use its platform. That is a company-reported figure, not a count of Dinh’s personal customers or a measure of his wealth. More interesting for this story is the continuity of the problem. A message should help the next action happen. The café pre-order and the shop inbox are different products, but each makes waiting part of the design brief.

A detour through the winter

Dinh’s interests also reached GameFi. In a March 2023 essay, he discussed working with the Rune Seeker team and questioned the durability of blockchain-game economics. The argument examined incentives, gameplay and whether a game actually needed blockchain. It belongs to his record as a generalist, alongside the more sustained messaging work.

His position was pointed. A game had to be good regardless of the technology used to build it, and the blockchain component needed a meaningful role. The essay presented his views about design and incentives; it was not proof that a proposed economic model had succeeded. Keeping that distinction preserves the interesting part of the detour: a software founder willing to ask what an extra layer of technology was doing for the user.

“The point of utility is not about the token or the NFT itself,” he wrote. The observation sits comfortably beside the earlier product questions. What happens because this tool exists? Who gets something done? That connection is an interpretation of two bodies of work, rather than a philosophy Dinh has packaged under a convenient slogan.

“The point of utility is not about the token or the NFT itself.”

Huy Dinh · March 2023

Return to the coffee queue and the biography has a useful ending without pretending the career is finished. The first problem was small enough to describe in a sentence. The later work asks businesses to organize many such exchanges at once. Dinh’s route runs through interfaces, integrations, colleagues and customers. Somewhere at the beginning, two friends simply wanted their usual lattes sooner. It is a respectable amount of ambition to find at the bottom of a coffee cup.