Launching today
Yedric.ai
Let users control your SaaS with natural language
692 followers
Let users control your SaaS with natural language
692 followers
Your users shouldn't have to learn where every feature lives. Yedric adds an embeddable AI agent to your SaaS that turns natural-language requests into actions your product already knows how to perform. Users simply say what they want done and Yedric handles the interaction. Instead of building and maintaining your own agent experience, developers can make their existing product AI-native in under 30 minutes.
MESA
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!
@aaroneous Giving users a simple way to control the product makes a lot of sense. What kind of APIs work best with Yedric?
MESA
@rohit62661 Any of the CRUD APIs an app already has are a great place to start. The more a developer exposes, the more freely users can just tell the app what they want to accomplish.
One example I like is combining data from multiple read operations. Instead of exporting everything to Excel and manually putting it together, you can just ask for the result you want directly in the app.
@aaroneous That's a good example. It can save users a lot of time.
What does the integration process look like for an existing SaaS with a large action set?
MESA
@camiladuarte Great q! You don't have to wire up everything at once.
Start with knowledge. Embed Yedric then connect your docs. You'll get useful learnings day one.
Expose actions from your existing API or MCP. Otherwise, point to the endpoints you want to use.
Grow actions from real usage. The conversation dashboard will show you what users are actually asking for so you can prioritize based on that instead of guessing.
We do this ourselves with our own Shopify apps. For example, Infinite Options has ~dozen actions from building custom form fields to setting up complex condition logic and navigating the app's UI.
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 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.
MESA
@erik_v Great questions!
> How does the app interface work technically?
You embed Yedric with one script tag and a small widget element in your app, and Secure Mode lets your server sign the logged-in user's ID so the agent knows exactly who it's talking to. Point it at your help center or docs and it builds a knowledge base it searches before answering, and page prompts give it extra context based on which page the user is on.
> How does the agent act is my SaaS?
Server-side actions run through MCP: you connect an MCP server, import an OpenAPI spec, or point us at your API docs, and the agent can call your API to look up an account, change a setting or start a workflow.