Lenny's PodcastAn 86-minute guide to finding PMF | Rob Snyder (Author, The Power of Pull)
CHAPTERS
- 0:00 – 1:16
Cold open: What a sales call should feel like when there’s real pull
Rob frames the central idea: if genuine pull exists, customers should feel like they’re trying to “rip the product out of your hands.” He teases a specific sales-call structure that starts with discovery and transitions into a pitch only when pull is present.
- •A sales call works best when the buyer is pulling, not when the founder is pushing
- •Discovery is the core of the call; pitching comes after pull is surfaced
- •Rob uses “pull” as the litmus test for whether selling should feel easy
- 1:16 – 4:00
Rob’s origin story: Getting “punched in the face” at zero-to-one
Lenny introduces Rob’s book and newsletter and shares community feedback that his work is unusually practical for early-stage founders. Rob explains his obsession with zero-to-one came from struggling as a founder, then repeatedly helping others through the same stage.
- •Rob didn’t plan to write; his lessons came from firsthand founder pain
- •Friends began pulling him in to help their startups go zero-to-one
- •He focuses on what’s uniquely weird and hard about the zero-to-one stage
- •Lenny shares quotes about how Rob’s work normalizes how painful PMF search can be
- 4:00 – 9:56
The PULL framework: Priorities, not pain points, drive buying
Rob defines pull as a situation where it would feel “weird not to buy.” He explains why classic startup guidance (pain points, value props, differentiation) can still fail: people may agree it’s valuable but won’t drop priorities to act now.
- •Pull means a person is a “coiled spring” trying to get something done now but stuck
- •Rob’s earlier startup had pain points, value, and daily usage—yet sales failed
- •The difference is whether the problem is an active priority right now
- •PULL acronym: Project, Unavoidable, List of options, Limitations of those options
- 9:56 – 13:53
Case study: How Jump found pull with financial advisors (and where it failed)
Rob walks through Jump’s discovery that financial advisors had a compliance-driven reason they had to capture meeting notes and log them. He contrasts that with insurance agents, who shared the “project” but lacked the “unavoidable” force, making “do nothing” a viable option.
- •Jump’s customer project: minimize time spent taking notes and entering them into CRMs
- •Unavoidable driver: failure to log notes could have severe consequences, so it must happen
- •Existing options failed due to CRM integration and compliance uncertainty
- •Insurance agents had the project but not the unavoidable pressure, so they didn’t pull
- •Rob clarifies a “project” can be an intention within an existing workflow, not a written to-do item
- 13:53 – 17:13
Pull is discovered (not created) and lives in a person, not a company
Rob describes how liberating it was to realize pull exists independent of the founder—so the job is to find it, not convince people to want it. He emphasizes that even in enterprise, pull belongs to a specific individual with a project, not an abstract company segment.
- •Trying to convince the market is a common trap; finding pull is the real work
- •Conversations with pull sound like: “How do we get started? Does it exist yet?”
- •Enthusiasm without urgency is not pull
- •A common mistake is saying “we sell to X companies” instead of identifying the person and their project
- •Selling is to a specific stakeholder (e.g., a functional leader) who is blocked on a priority
- 17:13 – 23:57
Finding startup ideas: Earned secrets through firsthand experience
Rob argues idea quality can’t be judged by brainstorming; instead, form a pull hypothesis about a specific person who’s stuck and test it. He strongly prefers founders get direct exposure—shadowing, embedding, or doing the job—to uncover what interviews and whiteboards often miss.
- •Use PULL upstream of product ideas: hypothesize who has pull, then test it
- •Rob believes this stage isn’t taken seriously enough; founders should “go all out”
- •Example: a founder shadowed multiple industries, then embedded with physical therapists until he found something real
- •Firsthand experience helps founders make the thousands of downstream product decisions
- •Rob estimates most successful ideas he’s seen came from firsthand experience rather than the founder’s prior job
- 23:57 – 27:25
Testing your pull hypothesis with two slides (and what “real intent” looks like)
Rob recommends validating pull with a simple two-slide approach: first reflect back the customer’s situation; then show a conceptual way you could help. The signal isn’t compliments—it’s a “pull-shaped action,” where they try to buy and push for next steps now.
- •Slide 1: confirm the customer’s Project, why it’s Unavoidable, Options considered, and their Limitations
- •Slide 2: a conceptual overview of how you could help (not a full product vision)
- •The goal is to hear: “Yes, that’s exactly it,” followed by concrete next-step pressure
- •Real pull shows up as urgency and attempts to transact, not “maybe in Q4”
- •Rob suggests some teams fill the framework live during calls to identify missing elements
- 27:25 – 30:59
When solving your own problem works—and the “Hail Mary” pivot question
Rob distinguishes between problems you truly would pay to solve versus things you merely think should exist. When conversations are lukewarm, he suggests a direct question that can surface a higher-priority project and sometimes triggers a successful pivot.
- •Solving your own problem works when you honestly would have paid for a solution
- •It fails when the founder wants something to exist but lacks true willingness to buy
- •The Hail Mary question: “Is there anything on your to-do list you would pay me to do right now?”
- •Rob has seen startups pivot successfully after this question reveals a more urgent project
- •Reframing sales as “seeing if they need help” reduces the pressure to convince
- 30:59 – 34:38
Common traps: Building too early and relying on design partners
Rob calls out two brutal anti-patterns: hiding from reality by building before talking to customers, and recruiting “design partners” who provide feedback but don’t buy. He argues true pull customers want the outcome, not a role in shaping your product vision.
- •Don’t delay customer conversations by going heads-down to build first
- •Rob says founders should face the “cold wind of reality” early
- •He’s skeptical of design partners: they often “buy into the vision” and never purchase
- •Design-partner feedback can become customers “playing Steve Jobs” instead of trying to get a job done
- •People with real pull typically want the project solved now, not to co-design tooling
- 34:38 – 41:37
Landing first customer conversations: ‘Founder magic’ outreach and benchmarks
Rob shares a cold outreach approach focused on being interesting enough to earn a conversation, not pitching a value prop. He provides practical activity targets and diagnostics for what’s broken when acceptance or reply rates are low.
- •Outreach goal is to start conversations; pull already exists (or doesn’t) independent of your message
- •Avoid templated “pain points + game-changing solution” pitches
- •Use short “founder magic” messages (e.g., a surprising personal hook)
- •LinkedIn approach: add 100–150 people/week; connect ~20/day and message after acceptance
- •Benchmarks: 30–40% connection acceptance; 30–50% reply rate; diagnose profile vs message issues if below
- 41:37 – 54:06
How to run the first sales call: agenda, discovery, and lean-back posture
Rob outlines a sales call as two phases: pull discovery, then a conceptual pitch if pull is present. He recommends starting by asking why they took the call, earning the right to ask questions, and using the framework to determine urgency and blockedness.
- •Rob enters calls expecting the buyer to “convince him to let them buy” if pull exists
- •Open with: “Why did you take the call with me today?” to surface context quickly
- •Set an agenda using what they said, then ask permission to ask discovery questions
- •Typical call length: 30 minutes; demos may be minimal or delayed depending on stage
- •Key discovery checks include urgency (“why now?”) and whether alternatives are good enough
- 54:06 – 1:00:57
From interest to commitment: simple pitches, 10x debates, and closing mechanics
Rob explains that when pull exists, the pitch becomes smaller and simpler—reflecting back what they’re trying to do and how you unblock it. He challenges the “10x better” heuristic and instead focuses on whether the customer is truly blocked, then describes how to close with a plan and manage internal steps.
- •A good pitch mirrors the customer’s pull: what they’re trying to do and what’s blocking them
- •Rob rejects “10x” as a universal rule; being “infinitely better” can mean simply unblocking the job
- •If the buyer can do it themselves or with an existing tool, pull is absent
- •Closing can start with a fast follow-up mock-up and a clear plan for next steps
- •For larger orgs, work backward from when results must show to drive the sales-process timeline
- 1:00:57 – 1:06:54
Pricing with PULL and avoiding self-sabotage (pilots, freebies, and service-shaped offers)
Rob shows how the framework sets pricing bounds by referencing either the value of completing the project or the cost of current alternatives. He warns against proactively offering pilots or free arrangements, and suggests early “service-shaped” delivery to meet pull without overpromising a finished platform.
- •Pricing bounds can come from project value or the costs of alternative options
- •Early on, Rob prioritizes willingness to transact over perfect pricing precision
- •A pricing tactic: share a range of what others have paid and ask the buyer to react
- •Don’t proactively offer pilots/POCs/design partnerships; only do them if the buyer requires it
- •Service-shaped early delivery can validate pull while the product is built behind the scenes
- 1:06:54 – 1:11:34
Onboarding and retention: finding the moment it becomes ‘weird to churn’
Rob argues post-sale delivery is about designing a “bullet train” to the moment where churn becomes unlikely. He recommends identifying the leading indicator that predicts retention and shaping onboarding so every customer reaches that value quickly, then using churn to sharpen who your ideal customer really is.
- •Assume every customer will churn until they reach a specific retention threshold
- •Find the leading indicator that predicts retention (Rob references an example from Slack)
- •Rob shares an example from his startup: a specific early success moment made customers rave and stay
- •If churn is high, it’s critical to learn whether the issue is delivery or customer fit
- •Churn can reveal a narrow segment that retains, enabling a focus or pivot to that segment
- 1:11:34 – 1:21:34
Building a repeatable ‘case study factory’—and applying PULL inside established companies
Rob introduces a mental model: a startup is a machine that repeats one successful case study at scale. He breaks the “factory” into pipeline, sales, and delivery, then suggests using bottlenecks to choose what to focus on; he also explains how founders and product leaders inside existing companies can apply the same approach to new products.
- •A scalable company repeats one core case study, not many unrelated stories
- •The factory stages: pipeline (conversations), sales (conversion), delivery (retention)
- •Use bottleneck thinking to focus: pipeline vs close rate vs retention constraints
- •Case studies become a qualification tool: “Is this outcome relevant to you?”
- •In established companies, successful new products often come from sales-call pull signals rather than whiteboarding; founders can sell features before building them
- 1:21:34 – 1:25:47
Lightning round: influences, favorites, and a ‘tar pit’ warning
Rob shares a few personal recommendations and preferences, then closes with a caution about common idea traps. He flags a recurring failure mode: entering a space with a clear winner without a credible theory for being meaningfully different for a specific customer with pull.
- •Book recommendation: Christopher Alexander’s Nature of Order series
- •Favorite movies: a recent Pride and Prejudice and Penguins of Madagascar
- •AI product mention: Muse
- •Life motto: “Life is what you make of it”
- •Tar pit category: copying a proven winner without a pull-based differentiation theory
