The common startup process of interviewing many users, cataloging pain points in a spreadsheet, and force-ranking them feels scientific but is deeply flawed. It identifies common annoyances, not urgent, purchase-driving priorities. True market pull often emerges from a single, unplanned conversation where a customer reveals an immediate, unsolvable need.

Founders instinctively view the world through a "supply lens," where their product is a central feature. This biases perception, making it impossible to see the pre-existing struggles (demand) that drive purchases. To see clearly, you must mentally remove your product and yourself from your view of the world.

A common founder mistake is believing they must create demand for their new product. In reality, demand is an independent force—a person struggling to achieve something. Your job isn't to create this force, but to find where it's currently blocked and offer a solution that enables what already 'wants to happen'.

Pitching supply concepts without understanding underlying pull rarely connects with a customer's latent project by chance. Presenting ideas this way usually elicits pleasant, polite validation rather than true customer commitment or active demand.

The strongest companies are built by founders who have personally and painfully experienced the problem they're solving. This visceral understanding is non-negotiable. Without it, founders can't know what to build or how to achieve third-party validation, wasting immense time and resources.

Contrary to the "always listen to the customer" mantra, a startup is deeply personal. Founders should build something that emotionally moves them. If you're obsessed enough to work on it every waking hour, you'll inevitably find customers who share that same obsession.

Pull isn't just a problem; it's a state of active struggle. Think of it as physics: the customer is applying force toward a project, but their existing options are applying a counter-force. Your product's role is to unblock this potential energy, which is often invisible until a viable new solution is presented.

When customers use your product in surprising ways, don't just build features for the new use case. Apply the "demand lens" by rewinding time. Investigate what struggle or "pull" existed in their world *before* they discovered your product to understand the core, pre-existing demand that is driving their behavior.

Since "blocked" demand is unobservable, you must ask questions that reveal it indirectly. Asking "If I spent $100M to build something for you, what problem would it solve?" forces customers to consider their most critical, unaddressed needs, bypassing their current behaviors and revealing latent demand.