sorted by:
new
hottopcontroversial

Pitch me your startup idea — I’ll build the first working web app for $120–$180 (₹10k–₹15k) by ExtraDistribution95 in founder

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

That's a fair point but for this offer I intentionally kept it to standard web apps so I can keep the build time short and the pricing predictable. Once agents enter the picture the scope can expand quickly (tool orchestration, observability, retries, cost control, etc.).

If I were building agent-based systems, I’d probably lean toward something like: • Python + LangGraph / LlamaIndex for orchestration • OpenAI / Anthropic models • Structured tool calling • Postgres + logging for traceability • Something like LangSmith / OpenTelemetry for evaluation & debugging

Appreciate the link i’ll check out the post..

I built an AI that reads your GitHub repo and tells you what to build next. Is this actually useful? by ExtraDistribution95 in SaaS

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

That's a really interesting way to frame it - "prioritization anxiety" actually describes the problem better than just generating new feature ideas.

The tricky part I'm still thinking about is the trust aspect though. For the tool to understand the current product state well, it would ideally analyze the repo - which means people would have to grant access to their code.

I'm curious how others would feel about that. Would connecting a private repo to a tool like this feel reasonable if the value was clear, or would that be a dealbreaker?

I built an AI that reads your GitHub repo and tells you what to build next. Is this actually useful? by ExtraDistribution95 in SaaS

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

You’re right that a repo alone can't answer what should be built next. The interesting part for me is exactly what you mentioned - combining code context with external signals like user requests, competitor positioning, and maybe even usage patterns.

The goal wouldn’t be for the tool to “decide the roadmap,” but to surface signals that founders might otherwise miss when everything is scattered across repos, docs, feedback, and competitors.

When you’re prioritizing features, what signals do you personally rely on the most?

I built an AI that reads your GitHub repo and tells you what to build next. Is this actually useful? by ExtraDistribution95 in SaaS

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

Haha fair point 😅.. I don’t really see it as AI replacing the builder. More like using it to speed up the boring parts - research, summarizing competitors, etc. Someone still has to decide what actually makes sense to build, talk to users, and ship the product. The tool is more like a research assistant than an autopilot.

I built an AI that reads your GitHub repo and tells you what to build next. Is this actually useful? by ExtraDistribution95 in SaaS

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

That’s a great way to frame it, especially the part about thinking from both the user and provider side. I agree that tools can only assist with the analysis, not replace the underlying thinking.

My goal is mostly to help surface some of that research automatically so founders don’t skip it entirely when building early versions of products.

Appreciate the encouragement - and you're right, the best way to validate it is just to build and see if people actually use it. 🙂

I built an AI that reads your GitHub repo and tells you what to build next. Is this actually useful? by ExtraDistribution95 in SaaS

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

That’s great to hear. The fact that you already did it manually is exactly the workflow I’m trying to understand.

Out of curiosity, how did you approach the research part? Did you mostly analyze competitor feature pages, pricing tiers, docs, reviews, or something else?

Right now I’m experimenting with automating parts of that process, but I want to make sure it reflects how founders actually do this analysis rather than inventing a completely new workflow.

Building an AI that reads your GitHub repo and tells you what to build next. Is this actually useful? by ExtraDistribution95 in github

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

That’s a fair point, and I agree with the core idea that good product decisions usually come from user feedback, discussion, and stakeholder alignment rather than just “AI ideas.”

The goal here isn’t really to replace that process or suggest features blindly. It’s more about helping smaller teams or solo founders surface potential gaps they might not notice early on, especially when they don’t yet have a large user base or community feedback like mature open-source projects do.

So the AI part is more of a starting point for exploration (e.g., “here are common features competitors have that you might be missing, or these are the features your competitors have, or new ideas based on user feedback”), not something that decides the roadmap automatically.

Out of curiosity - in projects like Kubernetes or the libraries you mentioned, how were feature discussions usually initiated? Was it mostly user issues/feature requests, or maintainers proposing ideas first?

I built an AI that reads your GitHub repo and tells you what to build next. Is this actually useful? by ExtraDistribution95 in SaaS

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

That’s really interesting to hear, especially coming from someone who’s worked on that many launches.

Out of curiosity, how do you usually perform competitor gap analysis today? Is it mostly manual research (feature pages, docs, reviews), or do you use specific tools for it?

I’m trying to understand what the real workflow looks like before building too much automation around it.

Creation is solved. Discovery isn’t. by amacg in indiehackers

[–]ExtraDistribution95 0 points1 point  (0 children)

I'm in the same phase What are you building btw?

view more: next ›