When searching for "blocked" demand, it's easy to invent problems from logical first principles (e.g., "all companies want to reduce costs"). This "wish-casting" ignores the customer's actual context and priorities. True pull is never generic; it must be a specific, top-of-mind problem for a user right now.

Related Insights

Real demand isn't a wish list; it's an active struggle. "Coping" customers are fighting a subpar solution right now, while "blocked" customers would act immediately if a viable option existed. Both represent a "spring-loaded" market ready to adopt a new product that solves their problem.

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.

Startups often fail by targeting abstract concepts like 'markets' or 'personas,' neither of which actually buys products. The fundamental unit of demand is a specific project on a single person's to-do list. Solve for one person's tangible need, then see if that need replicates across many others.

True product demand lies in the gap between what customers are currently doing (observable on their calendar) and their ultimate goals (their mental to-do list). A successful product closes this gap, better aligning a customer's actions with their underlying objectives. This mismatch is where "pull" is found.

High-level company initiatives are not real demand. True demand only exists when a specific person has the project on their personal to-do list. Sales efforts are wasted if you cannot find and sell to that individual owner.

A problem can be theoretically urgent or unavoidable, but if it is not the customer's number one priority to solve *right now*, there is no market pull. Demand exists only in the present tense. This reframes the concept of urgency into an immediate, actionable test for founders.

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.

Instead of a generic persona, define your target customer with a 'pull hypothesis': who would be *weird not to buy*? This structured framework forces you to articulate the specific project they're trying to accomplish, why their current options are bad, and why your solution becomes irresistible. It focuses on their demand, not your product's features.

The "Pull Framework" defines demand not by pain, but by observable action. It requires a customer to have an active, unavoidable project, to have already explored existing options, and to find those options insufficient. This is the signal for a product they will eagerly "pull" from your hands, even if it's imperfect.

Instead of asking about generic pain points, use the 'Pull' framework (Project, Unavoidable, Looking, Lacking) during discovery. The goal is to uncover the customer's single most important, blocked priority, which is the only thing they will act on.