Home/r/indiehackers/2025-07-24/#build-first-or-talk-to-users-first
12

Build first or talk to users first? What's your process?

r/indiehackers
7/23/2025

Content Summary

The post asks the fundamental question faced by many SaaS entrepreneurs: should you build a product first or talk to users first? The discussion features diverse perspectives, with most commenters advocating for talking to users first to understand real pain points before building. However, some suggest building for personal pain points when domain knowledge is strong. Several users share tools they've built to help with this process including interview analysis tools (YakStak.app), MVP development services (MVPFaster.dev), feedback marketplaces (FeedPlain, MobileAppDev.Reviews), and personal automation projects (TezNewz). The conversation explores practical challenges like how to conduct effective user interviews, where to find users, and how to translate user feedback into actual product development. Several commenters emphasize that users often don't know what they want until they see it, suggesting entrepreneurs should focus on understanding problems rather than taking feature requests at face value.

Opinion Analysis

The discussion reveals several distinct viewpoints:

  1. User Research First Advocates - The majority opinion represented by u/Immediate_Swimmer_70, u/SlothEng, and others who strongly advocate for talking to users first to understand real pain points before building anything. They emphasize that building without validation is risky and likely to result in wasted effort.

  2. Build for Personal Pain Supporters - Represented by u/JeorJo and u/Character-Roll-5689 who argue that building for your own pain point can be more effective, especially when you have deep domain knowledge. They acknowledge the importance of user research but suggest it shouldn't dictate exact feature sets.

  3. Hybrid Approach Proponents - Commenters like u/PhrulerApp, u/Kooky_Increase9228, and u/dgunseli who suggest a parallel approach of talking to users while building, or building an MVP first then validating with users.

  4. Tools Builders - Founders like u/SlothEng (YakStak.app), u/webmasterleo (MVPFaster.dev), and u/dgunseli (FeedPlain) who have created tools specifically to help with the validation process, indicating this is a common pain point for entrepreneurs.

  5. Process Skeptics - A minority view represented by u/Hungry_General_679 who suggests just building with a dev partner and figuring things out as you go, though this seems more of a practical approach for those comfortable with the process.

The most significant debate centers around the value of user feedback. While most agree it's essential, there's discussion about how to interpret it - with u/Reasonable-Total7327 and u/akhil1234mara emphasizing that you shouldn't build exactly what users ask for, but instead understand the underlying problems they describe.

SAAS TOOLS

SaaSURLCategoryFeatures/Notes
YakStak.apphttps://yakstak.appInterview Analysis ToolHelps organize user interview notes, provides next step recommendations, integrates LLM for guidance during interviews and enhanced analysis
MVPFaster.devhttps://mvpfaster.devMVP DevelopmentHelps founders build MVPs fast (7-14 days) to test and validate ideas
FeedPlainhttps://www.feedplain.comFeedback MarketplaceMarketplace for paid feedback requests to help validate product ideas
MobileAppDev.Reviewshttps://mobileappdev.reviewsApp Testing & FeedbackGuarantees 28+ testers per month who install, test, and provide feedback
TezNewzhttps://teznewz.comFinancial News AnalysisScores and filters financial news and Reddit discussions, streams data to Discord and website

USER NEEDS

Pain Points:

  • Difficulty knowing whether to build first or talk to users first
  • Not knowing how to start deep conversations with users
  • Struggling with self-doubt after building an MVP
  • Difficulty validating product ideas before development
  • Lack of user feedback channels
  • Not knowing where to find users or how to approach them
  • Users often don't know what they want until they see it

Problems to Solve:

  • How to validate product ideas before investing time in development
  • How to effectively communicate with potential users
  • How to overcome social anxiety when approaching users
  • How to translate user feedback into actual product development
  • How to determine which pain points are worth solving
  • How to identify and reach target customer segments

Potential Solutions:

  • Conduct user interviews to understand real pain points before building
  • Build for personal pain points where domain knowledge is strong
  • Use tools like YakStak.app to organize and analyze interview insights
  • Create MVPs quickly to test with real users
  • Leverage communities like Ollin or Reddit to get early feedback
  • Use feedback marketplaces like FeedPlain to get paid user insights
  • Pre-sell or get prepayment as ultimate validation of demand

GROWTH FACTORS

Effective Strategies:

  • Combining user research with building in parallel
  • Starting with waitlists to build initial user base
  • Using A/B testing to optimize value proposition and messaging
  • Building for personal pain points with deep domain expertise
  • Using negative reviews of existing products to identify improvement opportunities
  • Creating feedback loops with early users to guide development

Marketing & Acquisition:

  • Finding users where they already congregate online (Reddit, Discord, niche forums)
  • Offering free premium access as incentive for early adoption
  • Using paid ads targeting specific user segments
  • Leveraging communities for idea validation and early feedback
  • Using social proof through user testimonials and case studies
  • Building in public to generate interest and feedback

Monetization & Product:

  • Focusing on problems users would actually pay to solve
  • Starting with free tier to acquire users, then upselling premium features
  • Pricing based on value delivered rather than just features
  • Building only what solves real problems rather than hypothetical needs
  • Using analytics tools (Mixpanel, Posthog) to understand actual user behavior

User Engagement:

  • Creating Discord communities for ongoing user interaction
  • Involving users in the development process through feedback loops
  • Providing tools to help users help each other (feedback marketplace)
  • Using LLM integration to enhance user interviews and analysis
  • Gamifying feedback through credit systems (give feedback to get feedback)
  • Regularly sharing product roadmap and development progress with users