The Customer Already Wants Something: Rob Snyder’s Practical Search for Product-Market Fit

1. Guest Background

Rob Snyder writes about the difficult passage from a plausible product idea to a business customers actually choose. He is the author of The Power of Pull and the newsletter The Physics of Startups, and his work includes helping startups explore product-market fit. In this conversation, his central subject is the evidence a team needs at each stage: before building, while selling, and after a customer has bought.

Lenny Rachitsky hosts the interview on Lenny’s Podcast. The indexed recording runs 5,147 seconds, approximately 86 minutes, and covers idea discovery, early outreach, sales conversations, closing, onboarding, and repeatable growth. Its scope matters because the proposed framework is followed beyond the first enthusiastic prospect into the harder questions of delivery and continued customer value.

Snyder says the work began with his own struggles as a founder. Friends subsequently drew him into their startups’ zero-to-one problems, and repeated exposure deepened his interest in that stage. Rachitsky introduces him as having helped roughly 50 startups grow from zero to more than $1 million in annual recurring revenue. That figure is the host’s description of his experience; the interview does not establish how much of each company’s outcome was caused by Snyder’s involvement. His contribution here is a practical model assembled from experience, offered for testing against the circumstances of an actual buyer.

2. What the Episode Covers

The episode starts with a demanding definition of pull. Snyder describes a person already trying to accomplish something important, unable to do it with the options available, and therefore ready to pursue help. A fitting product releases an existing blockage. The founder’s first research question becomes who is in that situation, rather than which audience might appreciate a proposed feature.

PULL makes that situation explicit. Project identifies the outcome the customer wants: hiring more employees, for example, rather than purchasing recruitment software. Unavoidable asks why the work must happen now. List of options includes existing staff, tools, outside products, and other ways to proceed. Limitations identifies why those options cannot adequately accomplish the project. Snyder argues that the four conditions must coexist. An unresolved annoyance can remain postponed, while an urgent assignment can be completed internally without buying anything.

The unit of discovery is a person. Selling enterprise software still means understanding the particular individual responsible for a project, rather than assigning a generalized need to a company. In Snyder’s account, that person’s priority exists before the startup arrives. This shifts attention toward the work already underway and the obstacle encountered within it.

Firsthand exposure helps make the hypothesis specific. Snyder describes a friend who explored several small-business industries, shadowed independent physical therapists, and examined a profit-and-loss statement while considering buying a franchise. The friend developed a cost-reduction hypothesis, checked it with one therapist, and then approached five others to see whether it repeated. Snyder cannot remember the cost item. The supported lesson is the progression from observation to a repeatability check, rather than a particular financial intervention.

His proposed presentation is deliberately small: one slide restates the customer’s project, necessity, alternatives, and constraints in their language; another outlines the proposed help and price. Getting permission to have that conversation is a separate task. Short founder outreach should offer something interesting and relevant enough to earn a meeting. His example of family plumbing experience illustrates why a credential familiar to the target audience may be more useful than technology-industry status.

The call itself moves from discovering pull to explaining a conceptual solution. Snyder begins by asking why the prospect accepted, agrees on an agenda, and requests permission to explore context. He recommends reviewing what has been learned after roughly five conversations, without making five a fixed market-rejection threshold. Eventually, the case study factory connects the work: generate conversations, convert suitable prospects, and deliver the result that resolves their blockage. The ambition is to repeat a recognizable customer success. Publishing a written case study for every customer is unnecessary.

3. Core Views: Reasoning, Examples, and Limits

Snyder’s strongest argument concerns the gap between usefulness and priority. He recalls spending two years struggling to sell despite substantial pain, differentiated value, and design partners using his product every day. Those signals were real in his account, but they did not establish that buyers would rearrange their current commitments to purchase. The analytical implication is narrow and useful: recognition of a problem, appreciation of a solution, and actual buying urgency answer different questions. Treating them as interchangeable can keep a team improving an offering whose purchase remains indefinitely deferred.

Jump supplies the clearest example of how circumstances shape urgency. Snyder describes financial advisers who wanted to spend less time recording client meetings and entering notes into their CRMs. Generic AI note-taking tools lacked appropriate integration and had unclear SEC compliance. He also invokes possible imprisonment for failing recording obligations and says Jump searched for approximately 18 months. These remain his account of the case, including its legal-risk framing; the episode does not independently establish a universal legal requirement. The reasoning depends on required work and inadequate alternatives, rather than on accepting every detail as independently verified.

The neighboring insurance-agent scenario sharpens the distinction. Agents also held client meetings and could benefit from saving time, but Snyder says the people in this scenario could simply decline to record them. That option weakened the necessity. A shared workflow or occupational resemblance therefore does not establish an equivalent market. The relevant difference can be whether the customer has to perform the task at all. Excluding inaction from the alternatives would make the opportunity look stronger than the account supports.

Evidence also needs to be separated by strength. Snyder values a prospect actively asking how to proceed over compliments, requests for information, or suggestions of future use. A pharmaceutical executive reportedly offered immediate payment before the product existed. That is a meaningful statement of present interest, but the supplied account does not turn it into a completed payment. Even an actual transaction would leave subsequent delivery and retention unanswered. His emphasis is most useful when it encourages careful observation of what the customer does next, without collapsing several stages of evidence into one declaration of fit.

The same logic challenges abstract claims of product superiority. Snyder discusses Linear and Jira as an interpretation through his framework, not as an independently established explanation of their competition. His own HR-software experience is a more direct caution: he pursued better user experience and found that the buyer did not care. Better UX may remove an important blockage in one setting and barely affect the purchasing decision in another. His hypothetical hundred-times-better home printer makes the point more starkly: performance gains have little purchasing force for someone who is not blocked by printing. A competitor’s success likewise does not explain which customers still need a different solution.

His criticism of free design partnerships concerns how the arrangement changes incentives. Someone helping a founder develop a vision can contribute abundant feedback without urgently needing the outcome. Snyder argues that the relationship can select for that helpfulness and obscure purchasing motivation. He allows that such partnerships might help in some contexts, while saying he has not seen it. The interview supports a warning about interpreting feedback under those conditions, rather than a universal finding that collaboration cannot work.

After the sale, Snyder introduces a fresh test: identify an event X after which leaving would become surprising. Ordinary usage or a high NPS usually does not suffice in his account. For his restaurant employee-retention software, he describes an actionable warning about a potentially preventable employee departure within the first two weeks of purchase. That event connects the software to the customer’s intended result more directly than access or activity alone. It is still a practical hypothesis about retention, requiring observation rather than acceptance as a universal formula.

A horizontal AI-workflow company provides another route to learning. Snyder says freight forwarders kept using one particular workflow, leading the business toward a premium offering for that segment. The surrounding discussion of churn above 90 percent does not establish that company’s exact rate. Persistent users can reveal a promising context, but their existence alone does not establish its size or commercial durability. Snyder’s experience is also predominantly B2B; consumer applicability appears through feedback and anecdotes here. The speakers’ metal-detector metaphor preserves the essential boundary: a better search method cannot guarantee something valuable lies where the team is looking. Snyder explicitly describes the framework as still developing.

4. Learning and Application

A practical application begins with a hypothesis that the team is prepared to disprove. During discovery, ask whether the project could wait and whether the existing team or tools could already handle it adequately. These questions make the absent condition visible. A prospect who acknowledges an inconvenience but can comfortably postpone it should lead to a different next step from someone already attempting a required change. Understanding context before challenging the hypothesis also keeps the exchange useful to the customer, rather than turning it into an interrogation.

When the original proposal produces little response, Snyder’s Hail Mary question opens another route: what current task would the person pay to have removed? He reports that a startup selling an applicant tracking system to government customers uncovered a job-description need and gained its first contract this way. A team applying the idea should treat the answer as a new hypothesis. It still needs to determine whether it can deliver and whether the same situation appears elsewhere. Otherwise, an effective discovery question can become an invitation to accumulate unrelated custom work.

Once a need is sufficiently clear, use the smallest artifact that resolves the next buying question. In the pharmaceutical market-research example, the founder first understood the need, then returned a few days later with a rough mockup. Price can be discussed through the value of finishing the project and the cost of alternatives. The episode’s consultant-cost illustration is a conversation boundary, not a transferable price list. For larger organizations, establish when the internal champion needs results and work backward through procurement and deployment. Individual urgency helps explain the purchase, while organizational steps still have to be completed.

An unfinished platform need not prevent an explicitly described service sale. Snyder allows early delivery through a mixture of manual and automated work, provided the buyer understands what is being offered. The first transactions can establish willingness to transact without settling the optimal price. A separate operating question remains: which delivery tasks recur and can become a product, and which depend on bespoke human work? Snyder acknowledges the risk of remaining a service business. Payment validates a commercial exchange; it does not establish scalable delivery economics.

Personal delivery for the first customers can expose where value actually appears. Observe what the customer accomplishes, where progress stalls, and why leaving remains attractive. Compare the circumstances of customers who stay with those who depart before deciding whether to repair onboarding or narrow the target segment. This requires substantial involvement, and the initial process may not itself be repeatable. Its immediate purpose is to discover what later needs to become repeatable and which customers can benefit from it.

Then use the case study factory to allocate effort. Examine pipeline, sales, and delivery separately, and identify the stage currently preventing the same result from recurring. Snyder’s application of the theory of constraints suggests concentrating resources there before moving to the next bottleneck. The customer case also provides a qualification boundary: prospects needing materially different outcomes may entail an entirely different delivery path. Declining some opportunities can protect the ability to repeat the supported result.

Finally, apply his position on pilots with its explicit exception. Start by discussing a purchase and deployment, but accommodate a pilot when the customer’s procurement process requires one. Entering a pilot should not itself be counted as proof of demand. The useful discipline is to keep the arrangement connected to the buyer’s decision and the promised outcome, while accurately describing what the team can presently deliver.

Source

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