I try really hard to be the kind of founder that listens to users. The whole idea of building something people want is that you're supposed to be paying attention to them, not building in a vacuum.
But every time I've followed the loudest requests, I've ended up building things almost nobody else wanted. One vocal customer asks for a feature, it feels urgent because they're right in front of me, and three weeks later it's sitting there barely used.
I spent nearly four years on one idea before I finally pivoted to what I'm building now (@Basedash: AI data analyst). What mostly bothers me isn't that I was wrong, it's that I still can't tell you the exact signal that should've made me quit two years earlier.
At the time everything felt like progress. We had users, we had encouraging conversations, we had the occasional good week that convinced me the next one would be better. None of it was a clear "stop."
This feels like a hard balance, especially for products that need a bit of context.
If the landing page explains too much, it can start to feel heavy. If it explains too little, people may sign up without really understanding the problem, the use case, or why the product matters.
I ve seen products where the tool itself is good, but the first reaction is still: I don t get it yet.
For makers here, what do you try to make clear before signup, and what do you leave for users to discover inside the product?