A balanced approach might work best. You could start by creating a small, targeted audience while developing the product, making sure you’re gathering feedback and interest throughout the process. This way, you’re not only building the product but also shaping your marketing strategy.
It’s a tough call, right? On one hand, launching first lets you test your product in real-world conditions and get immediate feedback, which can be super valuable for tweaking things quickly. On the other hand, building an audience beforehand can create buzz and ensure you have people ready to jump in when the product drops. Personally, I think a mix of both works well—start building some hype early, even if it's just a small, engaged group, and then launch with a bit of momentum behind you. That way, you get the best of both worlds—real feedback and an eager user base right off the bat!
Honestly, I think it depends on the product and your goals. If you're testing something super new or niche, launching early with a small group of users can give you valuable feedback to refine the product—kind of like a 'soft launch.' But if you're aiming for something bigger or more competitive, building an audience first can create buzz and make sure you hit the ground running. Personally, I lean toward the 'build an audience first' approach because it feels less risky and gives you a community to support you from day one.
p/general
p/ama
p/introduce-yourself
p/self-promotion
p/thoughts-5
p/zencoder
p/producthunt
p/wisprflow
p/kraftful
p/screaming-frog-seo-spider
p/xnapper
p/google-chrome
p/fine
p/openai-api
p/bolt-new
p/elevenlabs
Replies
A balanced approach might work best. You could start by creating a small, targeted audience while developing the product, making sure you’re gathering feedback and interest throughout the process. This way, you’re not only building the product but also shaping your marketing strategy.
It’s a tough call, right? On one hand, launching first lets you test your product in real-world conditions and get immediate feedback, which can be super valuable for tweaking things quickly. On the other hand, building an audience beforehand can create buzz and ensure you have people ready to jump in when the product drops. Personally, I think a mix of both works well—start building some hype early, even if it's just a small, engaged group, and then launch with a bit of momentum behind you. That way, you get the best of both worlds—real feedback and an eager user base right off the bat!
Honestly, I think it depends on the product and your goals. If you're testing something super new or niche, launching early with a small group of users can give you valuable feedback to refine the product—kind of like a 'soft launch.' But if you're aiming for something bigger or more competitive, building an audience first can create buzz and make sure you hit the ground running. Personally, I lean toward the 'build an audience first' approach because it feels less risky and gives you a community to support you from day one.