Clade - AI COO that runs your team in tools you already use
by•
Clade is your AI COO for teams. It lives in Telegram, Slack, and iMessage, so there's no new dashboard to babysit - you message it like a teammate. Clade chases status updates, keeps client and project work moving, drafts the follow-ups, and flags what's slipping before it becomes a fire. The web app is your cockpit when you want the full picture. Built for teams who'd rather ship than manage.
Replies
This is interesting. How does it avoid duplicate syncing when the same project runs across Slack and iMessage?
@dhiraj_patel5 Good question. The trick is that channels aren't separate stores, they're just different doors into one memory.
Slack and iMessage don't each hold their own copy of the project. They both read and write to the same underlying model of your team and work. So a project isn't "synced" between them, it just exists once and every channel points at it.
When the same fact arrives from two places, we dedupe on the entity, not the message. We resolve who and what it's about, check it against what's already there, and either confirm the existing fact or flag a conflict if they disagree. Same input twice doesn't create two records, it just raises confidence on the one that's there.
Building around trust instead of just memory feels like the right call - especially with sources and confidence visible.
Curious what happens if two channels create slightly different versions of the same fact. Does Clade try to resolve that, or just surface it?
Congrats on the launch!
Transparent memory is a smart move. Most AI tools "remember," and you never know what they are actually storing.
Curious though, how do the five trust levels work in practice? Does "observer" watch, and "operator" take action?
Asking because for a COO-type tool, the line between helpful and intrusive is thin. 😅
Congrats on the launch.
congrats on the launch!
Congrats team, clean execution across three platforms!
The "no black-box memory — every fact shows source, confidence, and a button to fix it" is the part that would decide it for me, because an ops agent acting on a wrong assumption is worse than no agent. Concretely: if Clade learns something wrong and drafts a follow-up on it before I catch it, does a correction just update the fact, or does it also walk back actions already taken at the "operator" trust level? I'd want to know the blast radius of one bad fact before handing it standups and client follow-ups.
Rahim, the part I keep thinking about is being able to see what it has picked up about your team and correct it. That kind of openness is rare, and it makes the whole thing far easier to trust.