Most of the productivity software we use every day was designed for a pre-AI world and has spent the last two years having chatbots stapled to its edges. Bhavin Turakhia thinks that’s the wrong way round. The serial entrepreneur — known for building email and collaboration businesses over two decades — has launched Neo, an AI-native work platform, and is backing it with $30 million of his own capital. The pitch is not a smarter assistant inside your inbox. It is a workday rebuilt from the ground up, with agents and automation assumed rather than added.
The launch
According to a YourStory daily roundup (July 2, 2026), Turakhia has committed $30 million of his own money to Neo, positioning it as an AI-native work platform rather than another feature release. That self-funding figure is worth dwelling on: for a founder who has raised and exited before, choosing to write the cheque personally is a statement of both conviction and control.
It is also a familiar arena for him. Turakhia has spent much of his career in the plumbing of how people communicate and collaborate at work — email, domains, and the tooling that sits around them. Neo reads as the logical, and most ambitious, next step: not a point tool bolted onto that stack, but an attempt to own the surface where work actually happens. For a serial founder, it is a bet that the ground beneath the entire productivity category is shifting, and that the incumbents are too invested in their existing architecture to move first.
The specifics of Neo’s product scope are still being verified, and prospective users should treat early framing with appropriate caution. But the shape of the ambition is clear enough: a suite where AI is the operating assumption, not an upsell.
Why AI-native, not AI-added
The distinction Neo is chasing is the most important idea in enterprise software right now. As industry analysis in 2026 has framed it, the market is moving from adding AI features to existing tools toward building AI-native software where agents and automation are the default. The underlying bet is that workflows will be rebuilt rather than retrofitted.
The difference is architectural, not cosmetic. An AI-added product treats the human as the primary operator and the model as a helper you summon — draft this email, summarise this thread, clean up these notes. An AI-native product inverts that relationship. The default expectation is that an agent handles a task end to end, and the human supervises, corrects, or approves. Instead of a person moving data between a calendar, a document, and a CRM, an agent understands the intent and orchestrates the tools.
That is where the real opportunity in the productivity suite lies. Suites have always won because integration beats best-of-breed for most buyers — one login, one bill, data that flows between apps. AI-native design amplifies that logic. The more of your work lives in one coherent system, the more an agent can reason across it and act on your behalf. A collection of separate tools with separate chatbots cannot do this; a suite built for agents from day one, in theory, can. That is the gap Neo is aiming at.
The uphill climb
Believing the thesis is easy. Executing against Google, Microsoft, and Slack is the hard part.
The incumbents are not standing still. Google has woven Gemini across Workspace; Microsoft has pushed Copilot into every corner of Office and Teams; Slack has its own AI layer and the distribution of tens of millions of daily users already inside the product. These companies have the twin advantages Neo lacks: they are already installed, and they already have the enterprise’s data. Switching costs in productivity software are brutal — email history, shared drives, org-wide habits, admin policies, and the simple inertia of “everyone already uses it.”
Neo faces three specific mountains:
- Distribution. A superior product that no one can find loses to a mediocre one that ships to a billion mailboxes. Reaching buyers without an incumbent’s install base is expensive and slow.
- Enterprise trust. Selling to IT and security teams requires compliance, data-residency guarantees, audit trails, and a track record. Agents that act autonomously raise the stakes: a hallucinating chatbot is annoying, but an agent that takes the wrong action is a liability. Neo will have to prove it is safe before it can prove it is useful.
- Measurable gains. “AI-native” is a positioning claim until it produces numbers a CFO recognises — hours saved, headcount avoided, cycle times cut. The burden of proof sits with the challenger, not the incumbent.
None of this is fatal. Category shifts do create openings for challengers precisely because incumbents are constrained by legacy architecture and legacy customers. But the honest read is that being AI-native is necessary and nowhere near sufficient.
The India read
There is a wider story here beyond one founder’s cheque. Neo is an Indian entrepreneur building for the global work stack — not a localised version of a Western tool, but a product intended to compete head-on with the biggest names in software. That ambition is itself a signal about where Indian SaaS is heading.
India has a strong recent history of category-defining productivity software built for the world. What is newer is the appetite to build AI-native rather than AI-adjacent — to treat the current moment as a chance to rewrite the category rather than to slot into it. If that bet pays off even partially, it points to a template for Indian software companies: build for global buyers, design around agents, and compete on architecture rather than price.
The self-funding matters here too. By putting in $30 million of his own capital, Turakhia keeps control of the roadmap and the timeline, and signals conviction to a market that has grown wary of AI hype cycles. Founder-funded also means founder-accountable; there is no venture syndicate to blame if the thesis is wrong. That kind of skin in the game tends to concentrate the mind.
What AI-native SaaS from India could look like is, in a sense, being prototyped in public. The features Neo ships and the customers it wins over the next few quarters will say more than any launch note. But the framing is the right one for the moment: the incumbents are retrofitting; a challenger with capital, category experience, and no legacy code to protect is trying to build the thing fresh. Whether that is enough to move an enterprise off its existing suite is the open question — and one worth watching closely.
