Have you built a product? Submit it to Inide Need.
There are many useful products being built by indie hackers, but discovering them is not always easy.
That’s why I’m building Inide Need—a place where founders can submit their products and get discovered by people looking for new tools, services, and solutions.
If you have launched a product, even if it is still small or early-stage, you can submit it here:
https://www.indieneed.com/submit
Submitting your product can help you get more visibility, reach potential users, and become part of a growing collection of indie products.
If you are building something, share it below or submit it to Inide Need. I would love to discover what the Indie Hackers community is working on.
The "discovering them is not always easy" line is the real problem, and it cuts both ways — as a maker I recently submitted to a few discovery sites and got a launch-day blip then silence, and as someone looking for tools I rarely go back to a directory after the first visit. The platforms that seem to work build a reason to return (a newsletter, a weekly "best of," alerts) rather than just being a submission form. Is that on your roadmap for IndieNeed, or are you focused on the submission side first?
This is a really thoughtful way to frame it — I agree that a directory without a reason to return quickly becomes a one-time launch channel. IndieNeed is focused on making product submissions useful first, but the longer-term goal is definitely a repeat discovery loop: curated weekly picks, useful alerts, and a reason for makers and early adopters to come back. I’m still validating which format would create the most value rather than adding features for the sake of it. If you were using IndieNeed as a visitor, would a weekly “best new products” digest, personalized alerts, or something else bring you back?
I like the simplicity of the idea. The real value of a product directory comes after there are enough submissions though, when you can actually help visitors filter through everything and find something relevant. Curious what your plan is for discovery once the database gets much larger
That’s exactly the challenge I’m thinking about. The first priority is building a useful base of quality submissions, but once the database grows, a simple chronological directory won’t be enough. I’m planning to make discovery more structured through categories, tags, search, and curated collections around specific problems or use cases — for example, “tools for indie hackers,” “new AI products,” or “products useful for small teams.”
I’d also like to add recurring discovery formats, such as weekly featured products or personalized recommendations, so people have a reason to return rather than browse once and leave. I’m trying to avoid overbuilding before there is enough data to learn from, though. What would be most useful to you in a larger directory: better filters, use-case collections, recommendations, or community-curated lists?