I believe that most makers got into computers at an early age and worked in programs that may have already fallen into disrepair, but were crucial for their development and career direction.
Hi hosts! Here's a place to share questions and answers. There are hundreds of us all around the world, some more experienced in hosting events than others. Let's learn from each other. You can view an onboarding video conference I recorded with some meetup hosts around the world here and next steps doc which outlines what you should be doing here
This is probably one of the most debated topics in the startup world: Should you build an audience before you launch, or is it better to launch first and grow your audience afterward? I ve seen both approaches work, but each comes with its own set of challenges and rewards. - Building an audience first means you're creating buzz, validating your idea, and nurturing a community of early adopters who are invested in your success. But it takes time, patience, and a lot of effort to keep the momentum going before you even have a product to show. - Launching first lets you hit the ground running, gather real-world feedback, and iterate quickly. But without an existing audience, you might struggle to get those initial users and traction. So, indulge me: Which approach did you take or are you considering taking (those who haven't launched yet)? - Did you build an audience before launching your product, or did you launch and then focus on growth?
- What worked (or didn't work) for you?
- If you could go back, would you do it differently? Share your story with us so we can all learn from each other. There's someone here who could benefit from your experience. ----- P.S: If you're a growth-stage founder struggling with churn or stagnant customer acquisition (usually because of poor positioning and messaging), I'd love to help. I specialize in crafting impactful marketing strategies tailored specifically to your product so you can start seeing the results you deserve. Connect with me on LinkedIn today. Can't wait to hear from you!
When someone asks for a feature, it's tempting to assume they've already identified the solution to their problem.
But sometimes the request is only one possible way to solve something deeper.
For example, a customer might ask for another dashboard when what they're really struggling with is knowing which information deserves their attention.
