An 86-minute guide to finding PMF | Rob Snyder (Author, The Power of Pull)

The podcast discusses the "Pull" framework for achieving product-market fit, emphasizing that successful adoption occurs when a customer has a pressing, urgent problem they are actively trying to solve - so compelling that not buying the solution would be "weird." This "pull" comes from individual users, not companies, and is rooted in real, unavoidable needs rather than hypothetical pain points. Founders are advised to avoid common pitfalls like building based on assumed demand, relying on design partners, or pushing products through persuasion, and instead focus on discovering where genuine pull already exists.

The framework is broken down into key components - identifying a specific project (P), its urgency (U), the list of existing solutions (L), and their limitations (L) - which together create a situation where the customer feels "stuck" and open to a new solution. Validation involves direct customer engagement, using simple pitches or even mockups to test interest and observe reactions like urgency or excitement. The discussion also covers pricing based on the cost of inaction, the importance of retention, and the need to systemize success through repeatable case studies. Ultimately, the approach encourages founders to validate demand early, stay focused on real problems, and build only when there's clear evidence of pull.

• What if you tested demand for your product idea by asking a "Hail Mary" question on your next 5 sales calls?

  • Move: Before pitching, ask: "Is there anything on your to-do list you'd pay me to solve right now?" in your next 5 customer discovery calls. Take notes on responses and look for urgency, specific projects, and limitations in current tools.
  • Why Now?: Early-stage uncertainty is expensive - delaying validation increases the risk of building something no one urgently needs. This low-effort move surfaces real pull before writing code.
  • Expected Upside: You'll either uncover a high-pull use case to build around or eliminate a weak hypothesis early, saving months of development time and increasing odds of product-market fit.

• What if you reframed your outreach to attract only "Hell Yes" customers - those who are already stuck and actively seeking a solution?

  • Move: Rewrite your LinkedIn or cold email template to highlight a specific problem (e.g., "Helping financial advisors automate compliant meeting notes without wasting 10+ hours/week"). Avoid generic value props; focus on a narrow, urgent project someone is blocked on.
  • Why Now?: Broad messaging attracts lukewarm interest. The faster you filter for individuals with unavoidable problems and failed alternatives, the sooner you find pull.
  • Expected Upside: Higher reply and meeting conversion rates, plus stronger signals of intent (e.g., "How do we get started?"), leading to faster first sales and clearer product direction.

• What if you validated retention risk on day one by designing onboarding around a "can't live without it" moment?

  • Move: For your next new customer, manually deliver the core outcome (e.g., processed AI notes into their CRM) and observe when they react with relief or dependency. Document the exact action or result that made churning feel "weird."
  • Why Now?: Acquisition without retention is wasted effort. Knowing the "X moment" (e.g., first automated SEC-compliant note) early lets you design the product and onboarding to guarantee it.
  • Expected Upside: You'll identify a leading indicator of retention, reduce early churn, and create a repeatable onboarding playbook that scales with product automation.

• Identify and target specific individuals (not companies) who have an urgent, unavoidable problem your product can solve - validate this by asking, "Is there anything on your to-do list you'd pay me to do right now?"
• Before building, test demand using a simple two-slide pitch: one outlining the customer's project, urgency, and failed alternatives, and another showing your conceptual solution - only proceed if customers ask, "How do we get started?"
• Replace design partners and pilots with direct sales attempts; sell a service-shaped version of your product manually to validate willingness to pay and refine the offering before automating.
• Conduct batches of 5 sales calls to test your hypothesis - if no one shows urgency or excitement, refine your idea or target audience instead of pushing forward.
• Systemize early success by turning your first "Hell Yes" customer into a repeatable case study, then build your sales, onboarding, and delivery process around replicating that exact outcome.