Do you talk to potential users before or after you built your product?

Personally, a bit of both. Before launch, I make sure someone wants it (usually myself). I don't love the idea of derisking too much though. That was popularized by Eric Ries and Steve Blank's book "The Lean Startup", and yet neither of them built a great startup. After launch, I like talking to users because they'll surface ideas for features or even copy (e.g. if all users describe your product as x, maybe you should add that to the homepage's copy). It never ends 😅

I do customer development interview before building up a product. Mostly to understand what they want to buy, what is their pain point. It's easier to sell them what they want to buy then what you produced. ) Because even if you know your idea is bright and your product is useful. They should buy it for themselves. Any change could be made only if there's a wish to change. People don't like changes even if it's for better.

Same here. For Videco we did a long feedback stage to get as much as possible from our potential buyers

Yes! Jupitrr AI's users can schedule a call with @Harris directly. We have added the schedule link at the export page. This helps us to connect with users much better and get feedback.

All the features of Jupitrr AI are based on feedback from the users. So, the answer would be Both! We talk to them before working on any feature and after it is launched. Jupitrr AI's users can schedule a call with Harris directly. We have added the schedule link at the export page. This helps us to connect with users much better and get feedback.

I talk both before and after. But in my experience, the most valuable feedback comes after they've tried the product.

Before, user insights are gold.

Before! You should build a product WITH your Potential users

Talking to potential users both **before** and **after** building your product is crucial for creating a successful product. Here's why engaging with users at both stages is important: ### 1. **Before Building the Product:** - **Understanding the Market Need:** Engaging with potential users before you start building helps you validate the need for your product. This can prevent you from spending time and resources on a product that doesn’t solve a real problem or that no one wants. - **Defining the Problem:** By discussing with users, you can gain deeper insights into the specific problems they face. This allows you to design a solution that directly addresses their pain points. - **Prioritizing Features:** Early user feedback helps in prioritizing features that matter most to your target audience. This ensures that your initial version (MVP) is focused on delivering maximum value. - **Setting Expectations:** Understanding user expectations early on helps you align your product’s vision with what users actually want, which can guide your development process. ### 2. **After Building the Product:** - **User Feedback and Iteration:** Once you have a product, it’s essential to get feedback from users to see how well it meets their needs. This feedback allows you to make necessary improvements, fix bugs, and refine features. - **Validating Product-Market Fit:** After launch, talking to users helps you understand if your product truly fits the market. Are users satisfied? Are they recommending it to others? This can inform future updates and help you pivot if needed. - **Building User Relationships:** Engaging with users after they’ve started using your product helps build a community and fosters loyalty. Users who feel heard are more likely to stick with your product and provide ongoing feedback. - **Marketing Insights:** Post-launch user conversations can provide insights into how to better market your product, including understanding what messaging resonates most with your audience. https://ayatulkursihindi786.com/

Yes, this way I can more accurately identify their challenges.

I try to build awareness even months before launch on social media platforms etc to make the results better on launch day.

It's fascinating how this question really highlights the balance between innovation and user-centered design. While building first can spark creativity and speed up the process, talking to potential users beforehand is crucial for aligning the product with real market needs. I can attest that early conversations with users not only mitigate risks but also often unveil insights that can refine the initial concept in ways you might not anticipate. It’s a strategic move to ensure that what you build is not just innovative, but also truly valuable.

Our team even ran marketing campaigns before launch to build awareness of our product to potential customers, then after the launch, we outreach them through emails or direct contacts. It has provided the best results yet.

We usually talk to potential users before building the product. For example, when designing a drivhus , user feedback helps tailor features to their needs, ensuring the final product aligns with user expectations and practical applications.

Talking about it before even building can help gather investments and even opinions that might improve the product so obviously first.