
Cleo
The AI PM that runs your team
571 followers
The AI PM that runs your team
571 followers
Cleo is the AI product manager for founders and lean teams. It lives in Telegram and Slack - learns your tone, knows your team, and runs the PM work (standups, follow-ups, decisions) while you ship the product. What's different: every fact Cleo learns is transparent - you see the source, the confidence, and can confirm or correct it. No black-box memory. Five trust levels, from observer to operator. Free in Telegram. 1 min setup










What stands out about Cleo is that it doesn't just track tasks — it actually runs sprints autonomously. Curious how it handles prioritization when multiple stakeholders have conflicting requests. Does it have a built-in negotiation framework or just default to whoever shouts loudest?
Cleo
@lakshita_rana1 Cleo doesn't run sprints autonomously yet - it surfaces what's stuck, drafts updates, and chases follow-ups, but humans still call sprint priorities.
On conflict: there's no negotiation engine. Cleo surfaces the conflict explicitly ("PM wants A by Friday, client just asked for B same week — who decides?") with sources for both requests.
Congrats on the launch! Curious, how does Cleo handle situations where the team has conflicting updates or unclear blockers? Does it just surface them or does it actually try to resolve the ambiguity?
Cleo
@campixl Surfaces, doesn't resolve.
When Cleo sees conflicting updates ("Mark says blocked on infra, Sarah's standup says infra is fine") it flags both with sources, side by side, and pings whoever owns the work for clarification. Cleo doesn't try to decide who's right - that's almost always a domain call humans need to make, and getting it wrong silently would be worse than not acting at all.
How do you pull in offline context easily for remote based teams? Ideally something low lift but I would imagine capturing every single meeting would be adding a lot of non-related content.
Cleo
@treeves Good question. Default is off, not on.
Meetings have a per-call toggle ("Cleo joins"). You opt in to the calls that matter (weekly syncs, decision-heavy ones) and skip casual ones. Chat is channel-by-channel, not workspace-wide. Email is label-based. Linear is project-based.
For memory specifically, Cleo only extracts decisions and patterns when signals are strong. Casual conversation doesn't generate clutter. We filter out roughly 80 percent of what flows through.
Lowest lift starting point: connect standup channel plus one weekly meeting. Most teams expand once they see what actually surfaces.
Curious how Cleo handles context across long projects — does it maintain memory between sessions or does each conversation start fresh? The PM bottleneck is real for small teams building fast.
Cleo
@david_marko Yes, memory persists. Every conversation builds on the last one. Cleo holds a model of your team, projects, clients, and decisions across sessions.
Cleo
Hey Product Hunt 👋 Rahman here, Co-Founder of Cleo. I'm 19, building this from the US.
Rahim told you why we started. I'll tell you the line we refused to cross.
Right now there are a hundred tools claiming to be your "AI PM." Be honest - most of them are bullshit. Either it's just another chatbot with a new logo or it's a thin wrapper that "remembers" by dumping everything into a database and praying. No source, no confidence, no way to know if what it's acting on is real or hallucinated. That's not a teammate. That's a liability with a nice landing page.
I've shipped products solo since I was a teenager, and the thing that always broke wasn't the code - it was the coordination. Standups, follow-ups, "wait, what did we decide last week?" That overhead scales worse than any infra problem, and one day you realize you've stopped being the founder and become the PM of your own company.
Every assistant we tried was great at answering and terrible at remembering us. New chat, start over. Re-explain the team, the tone, what matters. By the time you've briefed it, you could've just done the work yourself.
So Cleo doesn't ask you to start over. It lives in your Telegram, Slack, and Linear, learns your team and your voice, and runs the PM work day after day - in your tone, not a robot's.
But here's the part I'd stake the whole product on: an AI that runs your team has no business hiding what it knows. So Cleo doesn't. Every fact it learns shows its source, its confidence, and a button to correct it. Five trust levels, from just watching to fully operating. You decide how much rope it gets - and you can always see exactly what it's working from.
No black-box memory. No "trust me." Just a teammate you can audit.
I'm here all day. Tell me where it still falls short — that's the comment I actually want. 🙏
Try the bot: https://t.me/try_cleo_ai_bot
Cleo
@rahman_bazarov_ Proud to build this with you, brother. The "AI that runs your team has no business hiding what it knows" line is exactly the argument we had at 2am the night we decided to rip out V3. Took a year of bad AI tools to see it that clearly. Glad we both got there.
Healy
We're one of the early agencies using Cleo. The thing that surprised me: it actually learned how my team writes in 7 days. Now it drafts Telegram updates to clients in my voice and I just approve. Saving me 2-in 57 minutes a day on operational stuff.
Cleo
@ecomnazar Honored you trusted us early. The 7-day learning window matched what we hoped for but didn't promise - Telegram is where voice signals are densest, so the model picks up tone fast there. Thanks for sticking through both rewrites in May.
AISA AI Skills Test
interesting that you started from the pain of re-explaining context every session. thats probably the biggest friction with most AI tools right now, they dont remember what matters to your team. curious how Cleo handles conflicting priorities when two people flag something as urgent, does it just surface both or does it actually help triage?
Cleo
@ozandag Yeah, that was the whole reason we built it. On conflicting urgents, Cleo doesn't just dump both on you. It looks at what each one blocks (a client deadline vs. an internal nice-to-have), who's waiting on it and what you've prioritized before. Then tells you which to handle first and why.
You can always override it. Goal is it triages like a COO who actually knows your business, not a notification that makes you decide everything yourself.