Yedric.ai

@aaroneous Giving users a simple way to control the product makes a lot of sense. What kind of APIs work best with Yedric?

The conversations dashboard is the gem of this whole thing, in my opinion. Being able to quickly see structured data with real insights into where customers are driving conversations makes life much easier when it comes to identifying painpoints and documentation gaps. Nothing slips through the cracks.

Building my own in-app assistant for a field-sales app taught me the hard part isn't understanding the request, it's deciding what the agent is allowed to do without asking. Reading data is easy, but deleting a customer or changing a contract is not. How do you handle confirmation for destructive actions? Is that set per action by the developer?

the idea of making ai agents feel more natural is really interesting especially when they can actually handle task instead of just chatting

Nice approach, letting users just say what they want instead of hunting through menus is where most SaaS products lose people. Does the embedded agent map requests onto existing actions you define, or does it try to infer new ones?

How does the app interface work technically? How does the agent act is my SaaS?

Do you see it as a replacement for traditional navigation or more as another way to access it?

Do you see it as a replacement for traditional navigation or more as another way to access it?

Does it ask follow up questions or try to infer the intended action?

The embeddable approach caught my attention. Being able to add this without building a whole agent experience from scratch could save a lot of development time.

What does the integration process look like for an existing SaaS with a large action set?

Hey Product Hunt! 👋I've spent more than two decades building SaaS products, and the basic interaction model has barely changed: we decide what the software can do, organize those capabilities into an interface, and then expect users to figure out how it works. Every new capability means more for users to learn. AI gives us an opportunity to flip that model around. Instead of making users learn how our software works, what if they could simply tell it what they want to accomplish?That's what we built Yedric to do. Yedric is an embeddable AI agent that turns what your app can already do into things users can simply ask for. You give Yedric access to your product knowledge, user context, and APIs, and he can actually get things done inside your app.We originally built this technology for our own Shopify apps. We wanted users to be able to say things like "turn off email notifications" or "fix my broken integration" and have the app handle it for them instead of sending them through docs, support, or a maze of settings.Then something unexpected happened.Those conversations became one of our best sources of product insight. When users asked for something our apps couldn't do, we could see exactly what they were trying to accomplish, in their own words, at the moment they were trying to do it. In one month, a single app surfaced more than 80 distinct feature requests this way.That's when we realized this shouldn't just be something we built for ourselves.We've tried to make adding this kind of AI to an existing SaaS product ridiculously easy. Most developers can have Yedric running in under 30 minutes, and it's free (you bring your own LLM key).We're still early, and that's a big part of why we're launching here. I'm curious whether other SaaS builders are seeing the same shift: five years from now, how much software will still make users navigate an interface vs. letting them simply ask for what they want?Thanks for checking out Yedric. I'll be here all day answering questions and would love your feedback!