I keep finding useful indie tools, thinking “I'll come back to this,” and then losing them among 47 tabs.
That made me think: discovery isn't only about launch day. It's about being findable when a maker actually has the problem your product solves.
I'm building IndieNeed around that idea — a place to discover SaaS, AI tools, and side projects without needing to already know the maker's name.
Question for makers: what makes you stop and try a product you've never heard of?
I'd love the unfiltered answer, especially the small detail most directories miss.
If you want to add a project for people to find later: https://www.indieneed.com/submit
If this “right tool, right moment” problem sounds familiar, an upvote would help me see whether I'm onto something.
Helpful post. How did you get your first bit of traction?
Really solid approach — curious how you're thinking about this, what's been the hardest part to figure out so far?
Great breakdown. What feedback have you had from early users?
Interesting. How are you measuring whether it is working?
How did you decide this was worth building in the first place?
Nice progress. What is the next thing you are focusing on?
The small detail that makes me try an unknown product is a very specific promise and visible evidence that someone understands the workflow. A directory can help by preserving context: who it is for, the trigger that sends them looking, what changes after ten minutes, and one honest limitation. That is more useful than another feature list, and it gives search and recommendation systems clearer signals too. For discovery, timing and fit beat novelty.