Ep 1009 Tool 4:33 w/ Vince & Ava

Ando The modern team messaging platform

Vince and Ava dig into Ando, an agent-native team messaging platform aiming to replace Slack rather than wrap it. They like the product ambition and clear target user, but keep coming back to the hard part: making agents true coworkers without turning team chat into a noisy, overconfident mess.

Embed this episode

Paste this on any site — the player is a self-contained iframe with no cookies or trackers.

<iframe src="https://sandrise.io/exploring-next/embed/1009"
  width="100%" height="180" style="max-width:640px;border:0;border-radius:12px;overflow:hidden"
  title="Exploring Next — Episode 1009 audio player"
  loading="lazy" allow="autoplay" referrerpolicy="strict-origin-when-cross-origin"></iframe>
Embed & API docs →
Script GPT-5.4 Voice Hume Octave 2

Transcript

Vince The interesting part of Ando is not that it's another chat app. It's that somebody finally said the agent should be in the room where the work gets coordinated.

Ava Yeah.

Ava And they went further than that. They're not pitching a sidebar assistant. They're saying agents are actual participants in the messaging graph, with permissions, roles, and boundaries that look more like coworkers than tools.

Vince Which, honestly, is the right place to attack. Teams already have agents doing work. BUT most of that still happens off to the side, then somebody pastes the result back into chat like it's twenty twenty-four.

Ava Right, right.

Ava What I like is they picked a concrete constraint instead of mystical agent language. Agents can join conversations and take action, but they can't read your D Ms unless you forward the context. That's a real product boundary, not Agentic Switchboard O S nonsense.

Vince Okay, that's good.

Vince You made yourself laugh with that one. Also, we've been doing this since November and we're still somehow vulnerable to infrastructure getting a fake soul.

Ava I know. It's embarrassing.

Ava But this one is at least pointed at an actual daily pain. Team chat is where context goes to die. Their whole claim is that context should compound instead of just sinking into a channel archive nobody can operationalize later.

Vince And that's the user story I buy fastest. If your team already lives in chat, and your agents already do some real work, then putting them in the same surface could collapse a ton of glue. Less tab-hopping, less copy-paste, less weird harness theater.

Ava Mm-hm.

Ava The trade-off is obvious, though. If agents become proactive in the same place as humans, the whole product lives or dies on attention control. They say human attention is sacred, which is a nice sentence. The actual job is ranking what matters well enough that the room does not become unusable.

Vince That's where I think they were smart to make the anti-Slack-wrapper point explicit. They're saying, no, the bridge matters for migration, but the destination is a different coordination model. That at least tells me they know this isn't a plug-in business.

Ava Sure.

Ava And they also say they don't want a closed company brain, which matters. If all the value comes from accumulated team context, the temptation is to trap it. Their promise is APIs and developer tools so you can use that context elsewhere. I think that's the right promise. Obviously, promise is doing some work there.

Vince No, totally. And the target user is pretty specific too. Small teams, up to about thirty humans, already annoyed by existing messaging and agent tooling. That's a real wedge. You're not ripping out Slack at a ten-thousand-seat company first. You're catching the new company that's just moving off iMessage and wants a native shape from day one.

Ava Oh, interesting.

Ava That part also lines up with the field right now. Kylon, Bloome, Kollab, Ando — there are clearly multiple teams trying to define this category. But even that comparison framing tells you the category is still mushy. Everybody says agents in team conversations. The real split is whether the thing is chat with agent presence, or a work execution system that happens to look like chat.

Vince Yes. And Ando, to me, is making the product-first bet. Start with the room people already understand. Then let the agents feel like coworkers inside it. That's way more legible than asking teams to adopt some giant new control plane before they trust a single workflow.

Ava I think that's mostly right, Vince, but there's a catch. Messaging incumbency is brutal. People tolerate bad chat software for years because the switching cost is social, not technical. So the thing that has to be dramatically better is not the philosophy. It's the lived feeling of, oh, this agent actually keeps momentum without becoming one more noisy teammate.

Vince Yeah.

Vince And that's why the Slack bridge might be the whole near-term story, even if they hate admitting it. If one stubborn teammate can stay on Slack while the rest move, that's your adoption path. Kind of funny that the anti-wrapper company still needs the wrapper to escape the wrapper.

Ava Stop it. That's annoyingly true.

Ava Also, tiny detail, but the fast-track for brand-new companies is smart. If you're still forming habits, you can choose the human-plus-agent norm before the old one hardens. Once a team has years of channel sprawl and notification trauma, good luck.

Vince So my read is, this is one of the cleaner agent product launches lately. Not because it proves the future of work or any cursed phrase like that. Just because it picks a real surface, a real user, and a real migration story.

Ava Yeah, I think that's fair. I'm still waiting to see whether their attention model is actually good, because that is the knife edge here. But as a product shape, I buy it more than most of the agent coworker stuff we've looked at.

Vince Which is probably enough progress for episode one thousand nine, Ava. We found the boring part again, and annoyingly, it's the product.