The common advice to conduct unbiased discovery interviews sounds logical but often fails. The truest way to validate an idea and understand customer needs is through the act of selling. This forces a concrete value exchange and reveals genuine demand in a way that hypothetical conversations cannot.
Related Insights
Customers, like founders, have a gap between their stated beliefs and actual behaviors. Instead of relying on discovery interviews, watch them work. Observing their actions reveals their true operating philosophy—what they genuinely value—which is a more reliable guide for product development than what they say.
Standard discovery questions about 'pain points' are too broad. Instead, focus on concrete 'projects on their to-do list.' This reveals their immediate priorities, existing attempts, and the specific 'pull' that will drive a purchase, allowing you to align your solution perfectly.
A potential customer can logically agree with your framing of their problem yet have no intent to buy. True demand isn't intellectual agreement; it's a palpable force. You must sense the pressure of them actively pushing against a wall. A customer leaning back and nodding is a red flag.
Validate business ideas by creating a fake prototype or wireframe and selling it to customers first. This confirms demand and secures revenue before you invest time and money into development, which the speaker identifies as the hardest part of validation.
Most problems customers describe are "pain points" they won't act on. You can't distinguish these from real, actionable demand ("pull") through interviews alone. The only true test is presenting a viable solution and attempting to sell it. Their reaction—whether they try to pull it from you—is the only reliable signal.
Founders often create complex plans and documents to avoid the simple, hard, and uncomfortable task of selling. Just as getting stronger requires consistently lifting heavier weights, finding product-market fit requires consistently doing the core work of talking to customers and trying to sell.
Structure customer validation across two meetings. The first is framed as a request for help to validate an idea, building rapport without sales pressure. The second presents the honed solution based on their feedback, creating a natural and easier transition into a sales conversation with a trusted partner.
Replace speculative feedback from discovery calls with a process that would be "weird if it didn't work." First, get strangers to pre-pay for a solution. Then, deliver it manually. This confirms real demand (payment) and validates the solution's value (retention) before writing code.
To truly validate their idea, Moonshot AI's founders deliberately sought negative feedback. This approach of "trying to get the no's" ensures honest market signals, helping them avoid the trap of false positive validation from contacts who are just being polite.
