Ogment AI - Your AI coworker, in Slack. Just tag @O.

Hey Product Hunt 👋 I'm Teo, CEO and co-founder of Ogment.

Most companies are told to "adopt AI", but in practice that means asking non-technical people to learn new apps, prompt engineering, and workflow builders. There's one thing we've learned over the past two years offering AI to companies: any bit of friction kills adoption. A few power users push through, true, but everyone else gets left behind.

You've probably seen the wave of Slack-native agents shipping lately, Claude Tag included. They're strong for technical teams who want to own the setup. We went the other way: every employee gets their own AI coworker, on any model you choose (including your own local LLM), with zero setup.

We built @O to attack that friction head-on. The bar we set ourselves: using an AI agent should be as easy as tagging a colleague. So that's exactly how it works, you tag @O in Slack, in plain English, and it gets the work done. No new app, no prompt craft, no workflow builder. When the friction drops to zero, adoption is maximized, the whole team starts using AI super naturally, from day one.

Hey PH fam 👋

Super excited to bring Ogment AI to the global tech and startup community today!

Here's a pattern I keep seeing across the AI ecosystem: almost every AI tool is built for one person at a time. One chat window. One context. One user. But real work is a team sport. It happens in threads, channels, and shared projects.

Most AI tools are like giving every employee their own private notebook. Useful, sure. But nothing compounds. @O is the team whiteboard.

It lives natively in Slack, works inside your existing channels and threads, and shares memory and skills across the entire team. When one person teaches it something, everyone benefits. That's the unlock.

My honest take on the competitive landscape: yes, the giants are shipping Slack agents too. Claude Tag is a strong product. But model companies are running many races at once: frontier models, APIs, consumer apps, coding tools. A Slack coworker is one bet among dozens.

For Ogment, it's the only bet. Every sprint, every roadmap call, every support ticket serves this single product. History rewards that kind of maniacal focus. Figma out-obsessed Adobe. Superhuman out-crafted Gmail.

And here's the clever part: Ogment runs on any model you choose, including Claude. So it wins no matter which lab wins the model race. That's smart positioning, not just brave positioning.

What stood out to me:

→ Connects to 1,000+ tools (Gmail, Salesforce, Notion, Linear, Stripe) and actually executes work, not just answers questions
→ Works on any model you choose, including your own local LLM
→ One workspace plan, unlimited Slack users, starting at $50/month. Per-seat AI pricing punishes adoption. This model rewards it.

Big shoutout to Teo and the Ogment team who are all here today and keen to hear from you 🙌

Here's a question I'd love this community's take on: where do AI coworkers ultimately live? Inside the tools we already use every day, like Slack? Or will we all migrate to dedicated agent platforms built from the ground up? Drop your take below 👇

Hello everyone, Flo here, I'm one of the builders at Ogment :)

Really excited to share what we've been hard at work on for the past months. A few more insights into the technical aspects of making an agent in slack run smoothly in production.

The bar we set for this product is extremely high: it needs to be incredibly easy to setup, essentially all integrations should be available to you, it should behave as smoothly as possible in all scenarios that exist in a chat app like Slack, and the hardest part: It should survive and work reliably across a myriad of possible failure modes, errors of all kinds, and deployments - to give people the feeling that "it just works".

First surprise: Slack's API, even their latest one made for agent apps, has an incredible amount of edge cases, error codes and rough edges. Make a tiny mistake, and the entire stream or message your agent is trying to write will simply not be displayed. Getting this right and buttery smooth was an uphill battle of renderers, meticulous testing and bug reports from our alpha testers.

Second surprise: Making agents survive in production still feels like an unsolved problem. Everyone is hand-rolling their own runtime, making agents recoverable when the process crashes, when your LLM provider dies, or when you deploy a new version of your agent and/or its runtime. There's a lot of space to make this simple, or to overengineer it, but one thing is for sure: This is no easy feat (even with the smartest coding agents).

Excited to see what people will delegate to our dear agent O 🚀

Hello Product Hunt!👋

Designer at Ogment here - brand, site, dashboard, launch assets.

The design brief was the same as the product promise: zero friction. If tagging @ O should feel like tagging a colleague, nothing around it gets to feel like software - no new app to open, nothing to learn, nothing in the way.

None of this was designed in a corner - everything we shipped went through the whole team, and half the best cuts came from engineers asking "do we even need this?" Small team, tight loop, that's how it stayed simple 🙌

Don't take my word for it though - just onboard @ O to your Slack and feel the magic ✨

One of my favorite parts? I create O brand assets by tagging our beloved @ O in our #marketing channel, where the whole team can see the process. And when it comes to repetitive revisions... I don't do them anymore. O does.

So excited to finally share this with you all - your thoughts and questions are more than welcome! 💛

Happy to be part of this amazing team and incredibly proud of what we've built.

Exited for this! Congrats team on launching @O!
Tagging on Slack is definitely the best way to interact, that's where team already are. I've been playing quite a lot with ClaudeTag, could you share how you compare to it :)?

This is exactly how AI gets adopted inside companies. No new app to learn, no context switching, just tag @0 where the work already happens. Excited to see where this goes 🚀

Hey Product Hunt 👋

I've always felt that the main challenge with AI is getting it into the hands of non-technical users. You basically have a few options:

1. A capable agent like Claude Code or Codex that requires the user to know what a terminal is and how to set up API keys, MCP, and CLI configs.

2. A basic chat interface where you have to manually bring in all the context from your work.

3. Specialized agents (like the one in Figma) that can't pull in data from other sources.

We wanted to solve this: give non-technical users a general-purpose agent that has access to all the right context without any complex setup. I think we pulled it off 🫡

answering KP's question - I don't think it migrates to a dedicated platform, because the cost being competed against isn't "install a new app," it's "change where my team already collaborates," and that's a much bigger ask than tagging a bot in a place they already live. Slack/Teams/wherever the conversation already happens has a huge structural advantage for that reason alone. the piece I'd push on is the org-level memory layer "curated by an admin" - that's the same promise every internal wiki and knowledge base makes, and those go stale the moment the admin stops actively curating. curious if there's anything automated nudging that curation along, or if it's fully on someone's plate to maintain

Love how you've embedded the AI directly into Slack instead of asking teams to adopt another dashboard. 👏🏻

The ability to tag it like a teammate feels much more natural for day-to-day work. Curious, what's the most popular workflow users are automating with @O so far?

Hey Product Hunt 👋 I'm Amaury, cofounder of Ogment, and I'm super proud to share what we've been building.

We kept seeing the same pattern: people are excited about the AI revolution, they want that full "agentic" experience, but then reality hits. The friction to install and maintain agents a la OpenClaw or Hermes is actually pretty high, esp. for less technical people. Not even mentioning the security or the team collaboration aspect...

So we built O from the ground up for Slack-native teams, where a ton of context already lives. Your conversations, your decisions, your files, your workflows: it's all right there. And the best part? There's zero friction to onboard, just tag @O in Slack.

Here's the thing that surprises people most: we don't really have a dashboard. You can do it all from Slack. Connecting your systems (Gmail, Linear, Stripe), creating a custom skill or sharing it with your team, setting up a recurring job... just ask your agent, like you would a colleague.

And it's proactive. Ogment doesn't just wait for instructions. It constantly spots automation opportunities and surfaces them to you, without you even having to ask.

My personal favorite skill with O? It handles my post-product meetings end to end. It pulls the Granola transcript, reads my backlog in Linear, checks strategy docs in Notion, grabs context from emails, and outputs a clear list of feature requests, bugs, market insights, and a backlog update proposal. What used to take me 45 minutes to do properly is now done in 1 minute.

We're incredibly excited to get this into your hands. Can't wait to see what you build with it!