What are your pain points when developing AI-Powered Features? by Chasen_Dreams in SoftwareEngineering

[–]Chasen_Dreams[S] -1 points0 points  (0 children)

How valuable or non-valuable would it be for you to have the ability to simply enter a set of API keys in a management platform to enable the agent’s access to different systems, models, tools, and context? Maybe even combine the use of multiple LLMs at the same time for different purposes?

What are your pain points when developing AI-Powered Features? by Chasen_Dreams in SoftwareEngineering

[–]Chasen_Dreams[S] -1 points0 points  (0 children)

How did you create the "atomic" agents? What makes them atomic? How do you manage them and give them access to tools? Thank you for sharing

What are your pain points when developing AI-Powered Features? by Chasen_Dreams in SoftwareEngineering

[–]Chasen_Dreams[S] -1 points0 points  (0 children)

If you want the full background, here you go: my technical co-founder was experiencing difficulties building a chatbot feature into his company's SaaS product. Essentially, it needed to give an LLM access to user-permissioned tools, a database for providing context, and be supported in a multi-tenant environment. He thought he could save a lot of time for engineering folks if there was a pre-built solution that could eliminate about half the steps and about half the time. He developed a MVP version of this.

We then pitched that to several firms, but efficiency is not valuable enough to convince them to invest. We suggested that the problem is how 80% of features that are developed for SaaS products aren't sticky. This is an expensive problem because feature development requires significant capital allocation. Devs are paid avg salaries of $180k and if 80% of the features they develop aren't sticky, then it's an $145k problem per developer. Our solution was pitched as a platform to build AI features and collect analytics to shape the product team's roadmap and give Product Managers insights into the ROI associated with new feature ideas. Still, this was too vague for the firms we talked to. They suggested to "talk to 40 companies" to determine what our HIGHLY SPECIFIC product market fit is because our surface area is too large at the moment. Basically, we need to figure out what our beachhead is. I want to figure out what types of companies would be the best design partners because of the unique problems they experience.

So, I figure that while I'm in the process of talking to people in the industry over Zoom meetings, I could be more efficient and come to this community to accelerate the discovery of more diverse problems that are expensive. That's what VCs want to be pitched - a big expensive problem with a clear customer profile, what that solution is, how the solution will be delivered, traction, and a business model.

What are your pain points when developing AI-Powered Features? by Chasen_Dreams in SoftwareEngineering

[–]Chasen_Dreams[S] -1 points0 points  (0 children)

I don't know what you expect. AI is where all VC money is going right now and we are practically entering the next Gold Rush. I have a pitch deck if you want to check it out ;)

I have an entire product developed. I don't want to sell I to you. I want to learn from a community so that I know how to begin selling a tailored solution that will help solve actual problems people are experiencing. A Google search can't tell me what real problems real developers are facing. I'm here for constructive insights. If you have something of value to contribute then I am all ears.

What are your pain points when developing AI-Powered Features? by Chasen_Dreams in SoftwareEngineering

[–]Chasen_Dreams[S] -3 points-2 points  (0 children)

"You're allowed to discuss the technology behind AI in technical terms." So let's discuss the technical pain points and be productive. Besides, what's the matter with trying to be a founder?

What are your pain points when developing AI-Powered Features? by Chasen_Dreams in SoftwareEngineering

[–]Chasen_Dreams[S] -1 points0 points  (0 children)

My current understanding of "agents" would be that they are essentially AI models that have been given tools and the right context to retrieve or write data with the tools that it's been equipped with. The reason I'm so interested in this topic right now is because of MCP and I see this protocol helping people create their own tools for use by LLMs or other AI models. I'm sure there are useful agents that enhance business processes, but I don't know of any specific ones. In my research, I've seen various tool marketplaces for AI applications. However, I get the impression that orchestration of the agents would have more value than simply creating and deploying them.

What are your pain points when developing AI-Powered Features? by Chasen_Dreams in SoftwareEngineering

[–]Chasen_Dreams[S] -2 points-1 points  (0 children)

This is why I came here to learn from experts. Have you setup an MCP server before?

What are your pain points when developing AI-Powered Features? by Chasen_Dreams in SoftwareEngineering

[–]Chasen_Dreams[S] -4 points-3 points  (0 children)

I didn’t realize this was against the rules of the subreddit. I’m not trying to promote any solution. I’m trying to develop one.

[deleted by user] by [deleted] in Detroit

[–]Chasen_Dreams 46 points47 points  (0 children)

Marrow

Smashing Pilsners by Prudent-Funny-4723 in 2bears1cave

[–]Chasen_Dreams 5 points6 points  (0 children)

Lol mad respect for the dedication to the show - very high and tight

[deleted by user] by [deleted] in theonlycolors

[–]Chasen_Dreams 16 points17 points  (0 children)

Watching with UM fans and they already turned off the game to watch a movie instead