The 'Thousand People Framework' prioritizes customer clarity over product development. It forces founders to define a hyper-specific ICP of 1,000 people, identify a problem they'd pay annually to solve, and map out how to reach them. This extreme focus on a small, defined market is presented as the true driver of a startup's success.

Successful startups tap into organic customer needs that already exist—a 'pull' from the market. In contrast, 'conjuring demand' involves a founder trying to convince a market of a new worldview without prior evidence. This is a much harder and less reliable path to building a business.

Founders mistakenly treat their product idea as fixed while searching for customers. The correct mindset is the reverse: customer needs are a fixed reality. Your product is the variable you must shape to fit that reality, not the other way around.

The process of building a business must start with identifying the ideal customer. The product, offer, messaging, and channels should all be reverse-engineered from that initial choice. Delaying this decision limits leverage and leads to wasted effort on a mismatched offer.

Many businesses fail by creating an offer and then searching for a customer. The correct sequence is to first deeply understand and select your ideal customer segment. Only then can you reverse-engineer an offer that resonates perfectly.

This reframes the fundamental goal of a startup away from a supply-side focus (building) to a demand-side focus (discovery). The market's unmet need is the force that pulls a company and its product into existence, not the other way around.

For deep tech startups aiming for commercialization, validating market pull isn't a downstream activity—it's a prerequisite. Spending years in a lab without first identifying a specific customer group and the critical goal they are blocked from achieving is an enormous, avoidable risk.

Believing you must *convince* the market leads to a dangerous product strategy: building a feature-rich platform to persuade buyers. This delays sales, burns capital, and prevents learning. A "buyer pull" approach focuses on building the minimum product needed to solve one pre-existing problem.

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.