A customer-support queue is a small theatre of helplessness. Music plays. Minutes acquire weight. A simple question grows a beard. In 2015, that ordinary frustration sat near the beginning of Yellow.ai: its founders wanted customers to handle routine enquiries and complaints in chat instead of waiting on a telephone line. Rashid Khan did not arrive through a recruiter or a meticulously planned startup courtship. He met Raghu Ravinutala and Jaya Kishore Reddy at a hackathon at his college, NIT Warangal, where their problem statement caught his attention.
Khan was finishing a computer science and engineering degree. He had followed Y Combinator and Hacker News in college, and he wanted to build something in chat partly because good code might earn him a look from WhatsApp or Google. The CV project had other ideas. He began helping the Yellow Messenger team on the side, took an IoT engineering job at EdgeVerve after graduation, then left it after roughly four months to join the young company. A line intended for a résumé became the work of a decade.
This origin is useful because it has no grand prophecy in it. There is a queue, a hackathon and a young programmer scratching at an interesting problem. Nine months after the product's soft launch, about 50,000 people had interacted with it. The team soon moved from an early consumer app toward software that businesses could use for voice and chat. The problem survived the pivot: make communication between a customer and a company less punishing.
The apprentice who published the manuals
Before Yellow.ai, Khan contributed to Tomboy Notes at the GNOME Foundation, working on its macOS version and library. At EdgeVerve, he built backends for connected devices. Those details place him in a recognizable species of early founder: the person close enough to the machinery to know which promises will survive contact with it.
He also wrote the manuals. Learning IoT Using Particle Photon and Electron, co-authored during his early engineering period, covered devices, cloud services, firmware and even an autonomous car project. Then came Build Better Chatbots with Anik Das, published by Apress in late 2017. Its 109 pages moved from development environments and bot design through analytics and monetization. The sequence is almost comically neat: connected objects, conversational interfaces, then a company devoted to automating conversations. Careers usually look coherent only after an editor has cleaned them up. This one supplied its own table of contents.
At Yellow.ai, Khan says the original application layer used Node.js and MongoDB, with Python handling natural-language processing and machine learning. He built the core platform alongside the company's technical co-founder. After the Series A, his remit widened: as chief product officer, he built and led product and design teams. A programmer had crossed the first internal border.
A product chief walks into the sales meeting
The fashionable account of company-building treats specialization as maturity. Engineering builds. Product prioritizes. Sales sells. Marketing narrates. Khan's career at Yellow.ai has behaved more like a visitor who ignores the velvet ropes.
In 2022 and 2023 he took responsibility for markets outside the United States while retaining the product brief. His own account credits that period with more than $8 million in annual recurring revenue added over three quarters. The number matters, but the more revealing detail is the direction of travel. Many product leaders speak reverently about proximity to customers. Khan temporarily moved his desk, figuratively and sometimes geographically, to the other side of the promise.
He had reasons to do so. Yellow.ai was expanding across India, Southeast Asia and the Middle East while establishing a North American base. Enterprise buyers were adding languages, channels and use cases. Voice had joined chat. Selling this kind of system is less like passing over a box and more like arranging a marriage between software stacks, security rules and human habits. A product decision can become a sales objection by lunchtime.
When generative AI began to redraw the category, Khan returned his focus to product. His site describes a 2024-onward assignment leading the transformation and adding go-to-market engineering. Yellow.ai's current leadership page now lists him as chief marketing officer, head of investor relations and co-founder. The title is new; the pattern is not. He goes where the translation problem is most acute, whether that means translating models into products, products into revenue or a decade of company-building into a story investors can understand.
Three rules, no ornament
Khan has offered a compact belief system: persistence, showing up every day and curiosity. The three would fit comfortably on Post-it notes above a monitor. Each matches the long, unphotogenic middle of his story. Persistence is staying with the same customer problem while the company changes names and architectures. Showing up is moving from the glamorous abstraction of strategy into a difficult market. Curiosity is being willing to become a beginner in the next function.
There is ambition here, certainly, but it is practical in texture. He calls himself a “full-stack entrepreneur,” defining the phrase as the ability to build and sell, write software and close customers. The conventional full-stack developer covers layers of technology. Khan's version covers layers of an institution. It is also a mild rebellion against the founder as ceremonial figurehead. He seems happiest near the seam where one discipline misunderstands another.
Recognition arrived in 2022, when Forbes India and Forbes Asia both named him to their 30 Under 30 lists in enterprise technology. By then Yellow Messenger had become Yellow.ai, reflecting its move beyond text chat. Khan had helped launch voice AI and was arguing for low-code and no-code tools that customers could modify. The trophy is easy to print. The continuous revision behind it is the more interesting achievement.
From languages in software to language in policy
A customer speaking to a machine brings language down from theory. Accent, noise, local vocabulary and urgency all arrive at once. Khan's recent writing about voice systems insists that they must work on a street corner, not only in a quiet demo room. His broader work has carried that interest into public policy. He identifies himself as an active member of UNESCO's Coalition for Linguistic Diversity in AI, focused on frameworks that prevent languages and their communities from being left behind.
In July 2026, Khan co-chaired a cluster on “AI Opportunities and Implications” at the inaugural UN Global Dialogue on AI Governance in Geneva. His opening request to governments, industry, academia and civil society was brisk: bring specifics, not positions. After the session, he distilled the discussion into four ideas.
- Access is only a beginning; countries also need the capacity to use AI.
- Enablement, literacy and distribution matter more than a symbolic compute race.
- Local models, languages and user-owned data can coexist with frontier systems.
- Measure success in better public outcomes, not in the number of models deployed.
The argument connects neatly to his product life. A model answering a question is different from a system resolving the problem behind it. Resolution requires context, integrations and permission to act. In policy, access to a model is likewise different from the capacity to create prosperity with it. The engineer's impatience with a merely impressive demo has become the operator's impatience with a merely impressive declaration.
A public chapter, still in draft
In August 2026, Yellow.ai and Bluerock Acquisition Corp. announced a definitive business combination agreement intended to take Yellow.ai public on Nasdaq under the ticker YAI. The transaction has not closed and remains subject to approvals and other conditions. Its filings describe hundreds of enterprise customers and billions of annual conversations. For Khan, now carrying investor relations alongside marketing, the proposal makes his newest border crossing unusually literal: private company to public market.
It also returns the story to communication. A public company must explain itself repeatedly, under rules less forgiving than a product launch. The person who once translated code into a usable interface is now helping translate the company into an investable account of itself. There is an irony worthy of a smile: the engineer who hoped a chatbot might improve his CV now has a decade of work that resists fitting on one page.
Khan is still building side projects with AI coding tools. He has created experiments for searching saved posts and keeping AI-generated interfaces consistent. He has started a long-form publication, The Product Brew, and says he wants to return to a steady writing practice. These are modest clues about the next phase. Even after a company absorbs most of adult life, curiosity keeps a small workbench at home.
The easy moral would be “do everything.” That would be exhausting and, for most people, foolish. Khan's career suggests something narrower: learn enough of the neighboring craft to follow an important problem across the boundary. The title may change when the company needs a different view. The queue remains. Somewhere, a customer is still waiting for a simple answer.