If I'm being completely honest, I have built a successful resume maker tool but I'm not passionate at all about resumes. Although it is really rewarding to help people in something as important as their job search, what I am really passionate about is building cool things online and the potential of building a lifestyle business that would allow me to be a time millionaire. But I always wonder how it would feel when both boxes are checked- when you are passionate about the problem you are solving AND passionate about building your own business. Sometimes what you're passionate about is not economically feasible- I would love to develop video games but the market is already saturated. Although having a successful business could leave room for me to use my free time to follow my passion. Then the line can get blurry- am I passionate about the problem my product is trying to solve or passionate about the result of solving that problem? I don't actually care about resumes but I work on it with passion because of the possible outcome ... what is the difference then? I'm sure there are plenty of people on this forum who have had a great money-making idea and went for it. But that's not necessarily in niche that you feel passionate about. What do you think is the extent to which a business can be hindered when the founder(s) have no passion for the problem the business is solving? Do you think it even matters?
What do you think is the best way to make your newsletter subscribers grow? Maybe offering some kind of free resource? Or by advertisement? What worked better for you?
My instinct is always to polish. I want the first thing someone sees to be good, because I figure you only get one first impression and an embarrassing v1 sticks to you. But almost every product I actually respect started out rough. The early versions were janky and half-broken, and the founders shipped anyway because real users teach you things a year of polishing never will. So I go back and forth on this constantly. The case for shipping ugly is that you stop guessing. You find out what people actually care about instead of perfecting features nobody asked for. The case for waiting is that a bad first experience can kill momentum before it ever gets a chance to stick, and you don't always get told why people left. I think the answer depends on how reversible the launch is. A small audience that forgives you is very different from a big public moment you can't take back. But I'm probably biased toward polishing longer than I should, and I've definitely buried good ideas thinking they were not ready yet. Where do you land: ship the ugly version and learn, or hold it until you're proud of it?
I ve been on Product Hunt for over 1,000 days, and honestly, when I first started, I had no strategy.
I knew I wanted to grow, but I didn t have a clear plan. I simply liked the platform, and that was enough motivation to spend time here. That time helped me recognise certain ways to build a personal brand on Product Hunt.
I am possibly preparing for marketing my own tool (a Chrome extension) and collect the activities I can use for future visibility and possible purchases. Right now, I am thinking about basics:
SEO within the plugin (name, description, description in the Chrome Store + visuals)
Listings in directories
Reddit mentions
Building in public
I am aware that it is not sufficient, and there will be much more work.
Everyone has their favourite routine to perform at their best.
Some are advocates for the Pomodoro technique (25 minutes of intensive work, with a 5-minute short break), others love time-blocking, a few plan the entire week on Sunday, and there are even people who say ice-cold showers la Wim Hof help them focus.
