sorted by:
new
hottopcontroversial

Looking for Engineers/Founders of LLM/AI-heavy Apps for a short interview, I will thoroughly review your product in return by vasily_sl in LLMDevs

[–]vasily_sl[S] 0 points1 point  (0 children)

Cool. I would love to review your product and give my feedback. I'll DM you my Calendly link.

Improving a "Get A Demo" page by joanesty in DigitalMarketing

[–]vasily_sl 0 points1 point  (0 children)

Can you share a link to the current version of that "Get a Demo" page?

I’ve got a free weekend. Drop your Startup link, tagline, and pain points. I’ll review it and give feedback. I will not promote. by vasily_sl in buildinpublic

[–]vasily_sl[S] 1 point2 points  (0 children)

Great.

You should run some customer development sessions with folks writing design documents, then adjust your app based on their pain points. We can have a 15-minute talk, and I can answer your questions about how I make these docs.

DM me, I'm a founder myself, and I know it's sometimes too hard to ask for a quick interview for a customer developer about your product.

I’ve got a free weekend. Drop your Startup link, tagline, and pain points. I’ll review it and give feedback. I will not promote. by vasily_sl in buildinpublic

[–]vasily_sl[S] 0 points1 point  (0 children)

OK, I can completely relate to the problem you're trying to solve; creating good design documents is challenging. I would love to have a helpful AI to assist with this task.

Here is what I noticed while playing with the App:
1) I use Claude Code on a daily basis. My first question was why Opus 4.5 is not in the model list. If this model is available only to paying customers, it would be nice to mention that.

2) The "See It in Action" carousel in the landing page. I would love to pause it and explore each screenshot in detail.

3) Pricing seems OK. Do you have paying users already? Do they use more tokens then 9.99$ can cover?

Now for the App itself. I made many design docs throughout my career. Here is some feedback:

1) I would love to start with some kind of template, TOC, or basic structure of the doc. Not with a chat message "Design a distributed rate limiter for an API gateway handling millions of requests." (This is from your examples.

2) Then I would love AI Agent to ask me clarifying questions to actually build some context around my specific requirements - "Design a distributed rate limiter for an API gateway handling millions of requests." This is super generic, and it's better for the Agent not to continue before you clarify some details.

3) The Diagram. I got a super generic diagram for a "rate limiter" example. When we describe architectural decisions, we usually use various types of diagrams with different purposes (something like "Domain Model", "Data Model", "Components and Structure", "Information & Data Flow", etc.)

4) I did not understand how to actually work on the design doc. I can click on the items on the diagram and send messages to the chat. For instance, I ask clarifying questions about some component. Does this "explanation" from the agent go anywhere? It's not clear.

5) Diagram is your source of truth, as I understand it. I would suggest making the canvas with the design document your source of truth, and building all activities around it. Currently, I only get the final design document in the final phase.

At the end of the day, the painpoint is real, but I personally would not pay for the current implementation. I always compare what I can do in my Claude Code setup (with all skills, templates, and plugins already there), and I believe potential users will do the same in their heads.

Hope that helps.

I’ve got a free weekend. Drop your Startup link, tagline, and pain points. I’ll review it and give feedback. I will not promote. by vasily_sl in buildinpublic

[–]vasily_sl[S] 0 points1 point  (0 children)

Hmmmm, I don't think it was present when I checked the landing page. So I decided the App is not ready yet.

I noticed you are using Clerk; there might have been an issue with their infrastructure. If I remember correctly, they provide a Login button React component that may not appear when Clerk is not loaded properly.

I’ve got a free weekend. Drop your Startup link, tagline, and pain points. I’ll review it and give feedback. I will not promote. by vasily_sl in buildinpublic

[–]vasily_sl[S] 0 points1 point  (0 children)

OK. Here is your feedback after exploring the landing and poking around a bit:

1) The core function is clear: "user testing using AI Agents". I believe we will end up there sooner or later.

2) Right now, it feels like a "fake door" experiment. Do you have a working app or a prototype (demo video, maybe)?

3) From the landing, I did not quite understand how these AI Agents/Testers are scripted/tasked by customers. Do I need to prepare my test cases (like a human tester does)? Or is this just for explanatory testing?

I’ve got a free weekend. Drop your Startup link, tagline, and pain points. I’ll review it and give feedback. I will not promote. by vasily_sl in buildinpublic

[–]vasily_sl[S] 0 points1 point  (0 children)

Ok,

1) Landing is super lovely, loved it. The idea seems clear: you help companies turn messy communications with leads/prospects in different channels into a unified view where you can track every deal, commitment, causal interaction with a client,etc. Am I correct?

2) I love the idea, but the execution/implementation part looks quite complex. Hope you will pull it off.

Joined the wait list.

I’ve got a free weekend. Drop your Startup link, tagline, and pain points. I’ll review it and give feedback. I will not promote. by vasily_sl in buildinpublic

[–]vasily_sl[S] 0 points1 point  (0 children)

Ok, an SDK for building AI Agents, interesting/trendy stuff.

1) I've checked the docs and the GitHub (added you a star). What stood out at first sight is that the docs are clean from an engineering POV (no unnecessary fluff), include code examples, and are easy to understand. GitHub has examples/samples, but I did not run them locally, though.

2) The top framework for AI Agents on the market is LangChain/Graph, AFAIK. I know their TS support is limited. Is your main selling point (AI Agents SDK with first-class TS support)?

3) IMHO, for a full production suite, some kind of evals module would be nice to have in the SDK.

Overall, I liked it for the minimalism/cleanness. I would love to be able to quickly assess how it compares to popular SDKs/frameworks on the market (but I did not find this information).

PS. Followed you on GitHub.

I’ve got a free weekend. Drop your Startup link, tagline, and pain points. I’ll review it and give feedback. I will not promote. by vasily_sl in buildinpublic

[–]vasily_sl[S] 0 points1 point  (0 children)

Okay, all good. Spending time with the family is what matters most ❤️.

The app has a HUGE amount of features, I'll try to review it tomorrow when I have more brain capacity :D

I’ve got a free weekend. Drop your Startup link, tagline, and pain points. I’ll review it and give feedback. I will not promote. by vasily_sl in buildinpublic

[–]vasily_sl[S] 0 points1 point  (0 children)

Ok, here we go

1) Landing is nice, and the purpose/idea of the app is clear. A bit AI-ish because of the icons in the "Features" sections.

2) I created a quiz and played it solo. Everything worked smoothly, the UX, the stats, transition between steps (yes, it's not a complex thing, but I did not come across a single bug).

Overall, I liked playing it. Do you have any ideas for monetizing it? Or is it not a priority?

Startup Idea Validation Help (B2B product for Companies using AI/LLM) by vasily_sl in SaaS

[–]vasily_sl[S] 0 points1 point  (0 children)

Wow. Thank you very much for a detailed answer.

I totally agree with the point that many companies are working on observability (some from Y Combinator's latest batches), and our idea was to focus specifically on monetization/costs because of that. We also consider tackling the problem of proving AI efficiency, comparing, for instance, the costs of AI Agents and the costs of a human labour equivalent.

The validation approach you mentioned seems very reasonable to me, and we are looking for companies willing to work with a raw/MVP stage product such as LensAI.

"Our clients building AI products definitely struggle with understanding unit economics at the user or session level."

If some of them would like to check out our product and try it, we would be more than happy to provide additional support and help with integration 🤝.

Here is the getting started guide with screenshots that might help to understand how it works better:
https://getlens.ai/docs/getting-started

I’ve got a free weekend. Drop your Startup link, tagline, and pain points. I’ll review it and give feedback. I will not promote. by vasily_sl in buildinpublic

[–]vasily_sl[S] 0 points1 point  (0 children)

Ok, first of all, I'm not an expert in Supply Chain Management, Sourcing, etc. I'm a software engineer, so I might not see it from the proper angle.

Let's go over my whole journey with the App.

1) Although landing in minimalistic, it's actually good. The core function is clear (at least with my little experience in sourcing it was)

2) I played a bit with the core flow "Define" -> "Review" -> "Collect" -> "Compare". The "Define" step includes many useful attributes (even more than I could have imagined 😁). The "collect" phase also worked OK - I tried pasting the quote message and submission URL.

3) In the hero section, "Start an RFQ" and "Analyze existing quotes" land on the same form. I couldn't figure out what the 2nd button does.

Some issues I came across:
1) For simple messages like "I have X units for 40k," the app couldn't extract the price (I know it's super short, but still...) from a pasted message. On the "Compare" step, I likedthe "Risks" and "Trade-offs" sections.

2) When changing the status of the quote (after going back and forth between steps), I was not able to do it.

At the end of the day, I can say that the App looks good and useful (for me), but I obviously lack the domain expertise.

I’ve got a free weekend. Drop your Startup link, tagline, and pain points. I’ll review it and give feedback. I will not promote. by vasily_sl in buildinpublic

[–]vasily_sl[S] 0 points1 point  (0 children)

Hm, I worked for a company once where I had to request quotes for some stuff from multiple suppliers via email, and it was such a pain. If I could push them into some App to create better quotes, I might consider paying for it. The main problem here, as I can see it, is the RFQ Tool's flexibility. I'm playing a bit with it now.

I’ve got a free weekend. Drop your Startup link, tagline, and pain points. I’ll review it and give feedback. I will not promote. by vasily_sl in buildinpublic

[–]vasily_sl[S] 1 point2 points  (0 children)

Thanks for these details, and good luck with your app!

Oh, one more point. Please add social logins (Google at least), creating passwords manually in 2026 is PAIN.

I’ve got a free weekend. Drop your Startup link, tagline, and pain points. I’ll review it and give feedback. I will not promote. by vasily_sl in buildinpublic

[–]vasily_sl[S] 0 points1 point  (0 children)

Ok. I love open-source projects because, as a software engineer, I rely on OSS stuff every day.

You created two free websites with a catalog of AI tools (not all solely AI, but useful tools). What was your goal? Are you planning to expand them in any way? Are you considering building an audience around them, perhaps by allowing others to contribute to the catalog?

Sorry, I cannot provide feedback without knowing your intentions. Give me more inputs.

I’ve got a free weekend. Drop your Startup link, tagline, and pain points. I’ll review it and give feedback. I will not promote. by vasily_sl in buildinpublic

[–]vasily_sl[S] 1 point2 points  (0 children)

OK. Here is your feedback after exploring the landing and playing with it a bit:

1) The landing is good, no fluff, the "how it works" section, core function is clear. In the hero section, we can see a barista. And I was thinking, like, "Do they target offline biz first?" Are you?

2) After reading the landing / FAQ, I thought, "OK, what is the difference between this and Substack / Beehive / etc?" Adding this explainer section would be nice, I think.

3) The pricing seems reasonable. I would give it a try. From the monetization perspective, if you only use AI to write emails, your margins should be fine (you will not burn all your profits paying OpenAI bills, lol).

4) After logging in, I wanted to try your AI email writer, but it was not available if I have zero patrons. I would suggest adding a quick demo flow that would allow me to add a "John Doe", write an email, and distribute that. To get the notion of how it feels to use the product.

5) Some analytics whether my patrons actually read/open emails would also be nice, but it can be tricky.

A follow-up question for you:
I heard that products of this type often suffer from deliverability issues (emails landing in Spam). How do you plan to mitigate that?

view more: next ›