Ando Exits Stealth With $20 Million and an Agent-First Rival to Slack and Teams
TechCrunch first reported the launch, and Ando confirmed the money in its own announcement. According to TechCrunch, Ando said it has raised $20 million in pre-seed and seed funding from investors including Accel, Index Ventures and Emergence. The company's press release calls the round seed funding and names one more backer. It describes Ando as backed by Accel, Index Ventures, Emergence Capital, and Contrary Capital. Accel's portfolio page lists Ando as a business messaging platform for collaboration between people and AI agents, with Du as founder and an initial seed investment in 2025. That confirms Accel's stake and when it began. The $20 million total comes from the company's own announcement.
Du has built a company before. The release says she previously founded enterprise API platform Alloy Automation and is a Thiel Fellow. Du told TechCrunch the new money will go toward hiring more people and "burn through more tokens," which is a candid admission that agents reading every channel cost real compute.
Accel partner Ivan Zhou summed up the investor thesis in the release: agents "aren't simply another feature inside existing workplace software." That is the bet everything else in this story tests. Is a purpose-built messaging app worth leaving Slack or Teams for, given that both incumbents already host agents?
Why Sara Du Blames the "Meat Proxy" on Slack's and Teams' Design
The idea came from integration work. When Sara Du was helping companies build MCP servers in 2025, people kept asking her how they could use AI agents from within Slack itself. But there were a bunch of technical hurdles in the way: moving messages back and forth and getting agents the right context, all without burning through token budgets. MCP stands for Model Context Protocol, a standard way to connect AI models to outside tools and data. Those hurdles, getting messages into an agent, giving it enough history, and keeping token costs down, are the everyday problems of bolting an agent onto a chat system that was designed for people.
Du decided the real problem was the architecture. "The deeper I went, the more I felt Slack and Teams were built for a world that was starting to pass us by," Du told TechCrunch. "Agents were treated as apps you install even as they were becoming participants in the team."
Her name for the result is the meat proxy: the person who ends up relaying an agent's output to everyone else. As she put it, "The human effectively becomes the messenger between the agent and the rest of the company." In Du's version, agents instead sit in the shared conversations where work gets coordinated. There they can follow why a decision was made, ask a colleague a question, build on another agent's work, and pull in a human when judgment is needed.
Anyone who has pasted a Copilot or ChatGPT summary into a Teams thread will recognize the complaint. Whether the fix has to be a new messaging platform is still an open question. Microsoft and Slack are betting that it doesn't.
Agents With Inboxes: What Ando's App Actually Does
The human-facing features are the familiar ones. Du told TechCrunch the app has channels, DMs, group conversations, and live calls that agents can transcribe and review. Ando's App Store listing, published under the developer name Asari, Inc., adds threads with real-time sync, video and audio calls with live transcription and searchable recordings, file sharing, reactions, mentions, full-text search across the workspace, and desktop, web and mobile apps. The iPhone app requires iOS 16.4 or later. Version 1.0 appeared on July 21, and version 1.7.0 shipped two days before the launch. The listing has only four ratings, so it tells you nothing about adoption.
The agent behavior is where Ando breaks from convention. According to TechCrunch, agents can browse channels, pick which ones to join, and can even join conversations without being tagged. If a company's agent thinks a human worker needs to be notified of something, it can message them on its own rather than waiting for approvals. The App Store listing says that when you mention an agent in a thread, the agent sees the whole channel, and that agents can decide which channels to join and how to react with emoji.
Ando's website sets one boundary on that autonomy. Agents join conversations and take action like human teammates, but they can't read your DMs unless you forward the context yourself. The site lays out three principles:
- Agents are true participants in the workspace, with defined roles, rather than platform features.
- The context built up by past conversations should be reused so agents become more useful over time.
- More proactive agents must not mean more noise, so the system should get better at predicting what deserves a person's attention.
Du gave TechCrunch one example of what this looks like in use. An agent spotted two conversations in different channels about the same problem. Without being asked, it pulled everyone into a group chat, explained the context, and suggested a decision. "I felt agents could better manage people than humans can because they can process a lot more messages than a human can in a shorter span of time," she said. This is the founder's anecdote. TechCrunch's report includes no customer data on how often this happens or how accurate those suggestions are.
Microsoft Teams Already Hosts Agents, Under Copilot Licensing and Preview Rules
TechCrunch's report grants that Du's idea is not unique. Most of the major players in the workplace collaboration space have already built in support for AI agents — Slack, for instance, has turned its native bot into an AI agent, and Microsoft has gone to great lengths to integrate Copilot into Teams. For Microsoft 365 shops, the real comparison is with specific Teams features, and those come with clear limits.
The feature closest to Ando is Microsoft's Channel Agent for Teams channels, and Microsoft's support documentation says it is in public preview with features likely to change. Each Teams channel can get its own agent that draws on that channel's conversations and meetings. According to Microsoft, Channel Agent can draft and share status reports for team review, use meeting transcripts as knowledge sources, schedule meetings with suggested agendas and invite lists, create tasks and send reminders, and draft and send emails without switching to Outlook. It answers questions in the channel and in group chats and meetings it has been invited to, using channel messages, meeting transcripts, and web search if the organization's IT admin allows it. Microsoft's support pages also cover managing tasks in Jira, Asana or GitHub through the agent.
Access is gated in ways Ando's pitch is not. To create, use, or manage Channel Agent, a user needs a Microsoft Copilot subscription assigned to them, membership in the channel where the agent was created, and IT admin permission to use apps in Teams. Channel members without Copilot can see the agent's responses and other people's interactions with it, but they can't interact with it themselves. When the agent is added to another group chat or meeting, only members of its home channel can ask it questions. Everyone else just watches. On mobile, creating, removing, and configuring the agent must be done in the desktop or web version of Teams. The mobile apps need Teams 7.11.0 or later on iOS, or 1416/1.0.0.2025100000 or later on Android.
Microsoft separately documents adding Copilot agents and bots to Teams group chats, and says that workflow does not need a Copilot license. That is a different feature from Channel Agent and has different rules, so don't assume one set of requirements covers both.
Put side by side, the two products share a goal and differ in who holds the reins. Both put agents inside team conversations. In Teams, agents live in a channel, answer the people who are licensed and allowed to use them, and work inside Microsoft's identity and admin model. Ando, as described to TechCrunch, gives agents their own inbox, lets them choose where to be, and lets them message people without asking first. How that autonomy works out in practice is something neither Ando nor any outside tester has published data on yet.
Ando's Waitlist and 30-Person Ceiling Frame the Replacement Pitch
TechCrunch describes Ando as a full replacement for Slack or any other messaging platform that agent-heavy companies might use. The company's own website is more modest about where it stands. It says it is out of stealth but still working through a waitlist. New companies moving off iMessage get fast-tracked, with onboarding promised in under 24 hours. The site says Ando currently works best for teams of up to 30 humans plus their agents, and that it hasn't pushed much beyond that size.
Customers so far fit that profile. Du told TechCrunch that Ando works with customers in software, real estate, and finance across 15 countries, and that many of those teams are small. TechCrunch named no customers and gave no user counts or retention numbers. Du was also frank that the product didn't impress at first. "A lot of people we showed it to early on were understandably unimpressed. It was, in many respects, just a jankier messaging platform," she said. What convinced the team, she said, was customers sticking with it longer.
Ando's plan for migration is gradual. The website promises to keep a working connection to Slack "for as long as you have teammates who refuse to leave," while calling Slack a bridge, not the destination. The site says Ando will support agents built by the company, by customers, or by anyone else. It also says its APIs and developer tools should make it easy to use workspace context elsewhere, so customer data doesn't end up locked in a closed "company brain." There is no mention of a Teams bridge. For Microsoft 365 organizations, Ando would today be a separate workspace running alongside Teams, not something connected to it.
The broader field suggests the idea is catching on. TechCrunch notes that Jack Dorsey, co-founder of Twitter and Block, recently announced Buzz, another app that puts people and AI agents in one messaging product, though Buzz is aimed more at developers.
Governance Questions IT Should Put to Ando Before a Pilot
Autonomous agents make governance the main thing to evaluate. An agent that joins channels uninvited, reads call transcripts, and messages employees on its own touches data classification, records retention, and acceptable-use policy in ways a bot you summon on demand does not. Microsoft's documentation for Channel Agent at least spells out who can use it, the admin gate on Teams apps, and whether web search is on.
Ando has published a security page. It says the company completed SOC 2 Type I in July 2026, that its SOC 2 Type II observation period is underway, and that data is encrypted in transit and at rest. SOC 2 is an independent audit of a company's security controls. Type I checks that the controls are designed properly at one point in time, and Type II checks that they actually operated over a period. Those claims come from Ando itself.
What Ando has not published is how administrators control agents. None of the public material covers organization-level limits on which channels agents may join, audit logs of agent actions, retention and eDiscovery, data residency, or how an agent's permissions relate to those of the people who deploy it. The "no DMs without forwarded context" rule is the only access boundary Ando states. Any regulated organization or Microsoft 365 tenant considering a pilot should get written answers on those points first.
What this means for you
Most Microsoft 365 organizations can watch Ando without acting on it. Small, agent-heavy teams that are frustrated with how agents work in Teams or Slack are the ones for whom a waitlist signup makes sense. Ando's own guidance puts its sweet spot at 30 people or fewer, and it has no Teams bridge. For an enterprise running Teams under Entra identity and Purview compliance policies, a switch would mean parallel infrastructure, not a swap. If what you want is a channel-level agent inside Teams, Microsoft's Channel Agent preview is the obvious place to test. Budget for Copilot licenses and expect features to change during the preview.
- Ando launched on September 24, 2026 with $20 million from Accel, Index Ventures, Emergence Capital and Contrary Capital, and new customers still come in through a waitlist.
- Ando agents have their own identities and inboxes, can join channels without being tagged, and can message people unprompted, but cannot read DMs unless a user forwards the context.
- By Ando's own account, it works best for teams of up to 30 people, keeps a Slack bridge for gradual migration, and does not mention any Teams integration.
- Microsoft's Channel Agent for Teams is in public preview, requires an assigned Copilot subscription and IT permission to use Teams apps, and lets unlicensed members see its output but not interact with it.
- Adding Copilot agents to Teams group chats is a separate workflow that Microsoft says does not need a Copilot license, so check requirements feature by feature.
- Before piloting Ando, get written answers on admin controls, audit logging, retention and data residency, because its public material covers SOC 2 progress and encryption but not those controls.
Ando's bet is that agents will be trusted to act on their own before Microsoft and Slack loosen their permission models. For a 20-person startup, that trade may be easy to make. For a Teams tenant with compliance obligations, the deciding factors are Ando's SOC 2 Type II report and whatever admin controls it publishes as it grows beyond 30-person teams. Until then, Microsoft's slower, licensed, admin-gated approach to agents in Teams remains the default for most organizations.