Launching today
Cleo
The AI PM that runs your team
175 followers
The AI PM that runs your team
175 followers
Cleo is the AI product manager for founders and lean teams. It lives in Telegram and Slack - earns 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
Cleo
Cleo
@rahimwws Happy to launch with you mate
Big congrats on the launch! The transparency model (source + confidence + fix button on every fact) is the right instinct, but I'd push further: there's a failure mode where an auditable AI quietly becomes a verification queue. If I'm confirming and correcting facts to keep Cleo accurate, I've just swapped standup overhead for memory-maintenance overhead. What's the design that keeps the audit asymmetric, where I only look when something's wrong, not to keep it right? Does Cleo surface only low-confidence facts for review, act silently on high-confidence ones, and shrink the queue as it learns my corrections?
Cleo
@ferdi_sigona Sharp catch. This is the failure mode we feared most and explicitly designed against. Three things keep the audit asymmetric:
1. Confidence determines visibility, not just labeling. High-confidence facts (>85%) act silently — Cleo uses them, doesn't ping you. Mid-confidence (60-85%) gets surfaced only when about to be used in a consequential action. Low-confidence (<60%) goes to a review queue. You're not approving facts — you're approving the small subset where Cleo isn't sure yet.
2. Confirmations compound, corrections decay. A fact you confirm once moves up the confidence ladder. A fact that survives 30 days without contradiction or correction graduates to "settled" — invisible in normal flow. You converge to a state where most of memory operates without you.
3. Corrections become rules, not patches. When you fix a fact, Cleo extracts the pattern ("Mark doesn't own ingestion anymore, Sarah does — and ownership transitions happen in #eng-leads channel"). The next 100 facts of that type don't need correcting.
The math we watch: confirmation-events per active user per week. If that number doesn't drop month over month, the design is failing. Right now it drops ~40% from week 2 to week 6 for active users. That's the signal we'd kill the product over if it inverted.
Nice launch! Quick q - is Cleo built specifically for agencies, or would it work for a small SaaS team too? Most of my "PM" pain is internal standups and follow-ups, not client stuff.
Cleo
@ahmetaz Yes - works for small SaaS teams. Agencies are the wedge because the tool stack is consistent and the pain is acute, but the operational primitives (memory, learned rules, integrations) generalize.
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.
the confidence scoring model is the right approach. most AI tools just act on everything with the same certainty and you only find out it was wrong after it already sent the message. curious how the 30 day correction window works in practice when the team structure changes fast
Cleo
@tina_chhabra Static decay breaks for fast-moving teams — by the time a fact ages out, the org chart has changed twice. So decay is event-driven, not time-driven.
Facts have a type that determines how they age. Structural facts (ownership, roles) decay fast on contradiction -one Slack message saying "Sarah's taking over from Mark" drops the old fact's confidence below threshold and queues both for confirmation.
30 days is the fallback for facts with no contradicting signal. For active teams, most facts get refreshed or contradicted long before that.
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.
Cleo
@louislecat The endgame is bigger than a PM tool.
We're building toward agents that operate as employees - not assistants. They sit in your meetings. Execute across every integration your team uses (50 native, 500+ through Composio). Run entire functions of the company under your judgment.
Cleo today is the operational layer. The architecture (memory + provenance + learned rules + integrations) generalizes - same primitives that draft a client follow-up today will run the entire client-success function tomorrow.
An AI workforce that operates under human judgment, with auditable memory and trust gates. Not "AI that helps you." AI that does the work.