Andy Rachleff — co-founder of Benchmark Capital and founding CEO of Wealthfront — distilled a pattern he observed across hundreds of venture-backed startups into a metaphor that reframed how founders think about go-to-market: the best products are heat-seeking missiles. They don't launch into the void and hope to find a target. They lock onto thermal signatures that already exist — pockets of burning, desperate demand — and fly straight toward them. The alternative — building a product and then cold-calling the world to manufacture interest — is the startup equivalent of firing unguided munitions into fog and calling it strategy.
The distinction sounds semantic. It is not. Cold-calling companies build something they think the market should want, then spend enormous energy convincing customers that the pain exists and that their solution addresses it. The sales cycle is long. The conversion rate is low. Every deal requires education before persuasion, persuasion before negotiation, and negotiation before close. Heat-seeking companies find customers who are already in pain — who have already tried to solve the problem themselves, who are already cobbling together workarounds, who are already spending money on inferior alternatives — and offer them something that makes them say "finally." The sales cycle collapses because the customer was already looking.
Slack didn't market itself into dominance. Stewart Butterfield's team built an internal communication tool during the development of a failed video game, Glitch. When they released it externally in 2013, it spread with a velocity that no marketing budget could have manufactured. Teams were already suffering from email overload, already patching together IRC channels and ad-hoc chat tools, already looking for something better. Slack didn't create the demand. It found the demand. By 2014, Slack was adding $1 million in new annual recurring revenue every eleven days — not because of a brilliant sales team but because the product arrived at the precise coordinates where the heat was already concentrated.
Rachleff's framework draws from his articulation of the Value Hypothesis — the idea that before a startup worries about growth, it must first prove that a meaningful number of users find the product valuable enough to adopt without persuasion. The heat-seeking missile metaphor operationalises the Value Hypothesis: if you have to convince someone they need your product, you haven't found the heat yet. If customers are pulling the product out of your hands before you've finished building it, you've locked onto a thermal signature. The missile is flying.
Dropbox followed the same trajectory. Drew Houston built a file-syncing tool because he kept forgetting his USB drive. He wasn't solving a theoretical problem. He was solving his own burning problem — one shared by millions of knowledge workers who were emailing files to themselves, losing version control, and cobbling together network drives that broke constantly. The famous Dropbox explainer video posted to Hacker News in 2007 generated a waiting list of 75,000 signups overnight. Houston didn't create demand. He dropped a match into a room already filled with fumes.
The inverse is equally instructive. Google Wave, launched in 2009 with enormous internal enthusiasm and engineering talent, attempted to reinvent email, chat, and collaboration simultaneously. It was technically impressive and strategically ambitious. Nobody wanted it. There was no existing pocket of demand that Wave satisfied. Users didn't understand what it was for because they hadn't been looking for it. Google shut it down within a year. The missile had no heat to seek.
Section 2
How to See It
Heat-seeking missiles are visible through a specific diagnostic: the ratio of pull to push. When customers are finding the product rather than being found by the product, demand is pre-existing. When the sales team is dragging customers through the funnel, the company is manufacturing demand — and manufactured demand is fragile, expensive, and non-compounding.
Product
You're seeing Heat-seeking Missiles when a product's waitlist grows faster than the team can onboard users. Superhuman, Rahul Vohra's email client, maintained a controlled waitlist for years — not as a marketing gimmick but because demand genuinely outstripped their capacity to deliver the onboarding experience. Users were referring friends before they'd even received access. The heat was real.
Growth
You're seeing Heat-seeking Missiles when a startup's best-performing acquisition channel is word of mouth, and the team can't explain why growth is accelerating. Figma's early adoption among designers spread without a sales team because designers were already frustrated with the limitations of desktop-only tools and were actively searching for browser-based alternatives. Figma didn't create that frustration. It arrived where the frustration was already burning.
Sales
You're seeing Heat-seeking Missiles when prospects show up to the first sales call already educated on the product, having tried a free tier or watched a demo video unprompted. Zoom's early growth was driven by users who had experienced the pain of clunky enterprise video conferencing — WebEx, Skype for Business, GoToMeeting — and were actively seeking something that simply worked. Eric Yuan built the product he wished existed. Millions of people wished the same thing.
Venture
You're seeing Heat-seeking Missiles when an investor asks a founder "how did your first ten customers find you?" and the answer is "they found us." Marc Andreessen has described this pattern as the single strongest signal of product/market fit: the market pulling the product out of the startup. When the founder has to push, the signal is weak. When the market pulls, the missile has found its heat.
Section 3
How to Use It
The primary application is reorienting the startup building process from "build, then find customers" to "find the heat, then build for it." The secondary application is killing initiatives early when the heat cannot be located — saving months of engineering and millions of dollars that would have been spent building missiles with no target.
Decision filter
"Before investing in building this product, ask: where are the people who are already trying to solve this problem? If I cannot find them — in forums, in support tickets, in competitor reviews, in workaround behaviours — the demand may not exist yet. And creating demand from scratch is a fundamentally different and more expensive bet."
As a founder
Map the thermal signatures before writing a line of code. Search Reddit threads, Hacker News comments, G2 reviews of competitors, Stack Overflow questions, and customer support forums for the specific language of frustration. When people write "I wish there was a tool that..." or "I've been looking for something that..." or "I can't believe nobody has built..." — those are thermal signatures. Your product should fly directly at them.
The Slack origin story is instructive not because Slack was brilliantly designed — it was — but because Butterfield recognised which pain was burning hottest. Internal communication was a problem every team experienced daily, with no satisfying solution. He didn't need to explain the problem. He needed to offer a solution to a problem people were already desperately trying to solve. Find the desperate before you find the investors.
As an investor
The heat-seeking missile framework is a due-diligence filter. Ask founders to describe their first ten customers without mentioning outbound sales. If those customers came through inbound interest, referrals, or organic discovery, the product has likely found pre-existing demand. If the first ten customers all required extensive outbound prospecting, the founder may be manufacturing demand — which can work at sufficient scale and budget but is a fundamentally harder and more capital-intensive path.
Rachleff's heuristic at Benchmark was direct: "a great market pulls product out of the startup." If you have to push the product toward the market, either the product is wrong, the market is wrong, or both. The strength of the pull is the leading indicator of everything that follows.
As a decision-maker
Apply the heat-seeking missile test to internal initiatives, not just external products. Before launching a new process, tool, or programme, ask: is anyone already asking for this? If employees are already building workarounds, sharing informal tools, or requesting the capability in surveys and skip-levels, demand is real. If the initiative is a top-down mandate that nobody asked for, you are cold-calling your own organisation.
Common misapplication: Interpreting survey responses as thermal signatures. Asking potential customers "would you use a product that does X?" and receiving positive answers is not demand discovery — it is demand fabrication. People say yes to hypothetical solutions they will never pay for. The real signal is revealed preference: what are people already doing, already spending money on, already complaining about? Surveys measure intentions. Behaviour measures demand.
Second misapplication: Equating any early traction with heat-seeking success. Some early adoption is driven by novelty, founder networks, or launch-day press rather than genuine pre-existing demand. The diagnostic is retention, not acquisition. If users arrive enthusiastically and disappear within thirty days, the product found curiosity, not heat. Heat-seeking missiles lock onto sustained thermal signatures — problems that persist, frustrations that recur, needs that don't go away after the first week.
Section 4
The Mechanism
Section 5
Founders & Leaders in Action
The founders below didn't just stumble onto demand. They developed instincts — honed through personal frustration, customer observation, or market immersion — for locating pockets of burning need and building products that flew directly toward them. Their competitive advantage was not superior technology. It was superior targeting.
Marc AndreessenCo-founder, Netscape (1994) & Andreessen Horowitz (2009)
Andreessen articulated the canonical formulation: "The product doesn't need to be great; it just has to basically work. And the market doesn't care how good the team is. When a great team meets a lousy market, market wins." His essay "The Only Thing That Matters" (2007) argued that product/market fit — the state where a product meets existing, hungry demand — is the only milestone that determines whether a startup lives or dies. Everything before product/market fit is searching for the heat. Everything after is fuelling the fire.
At Netscape, Andreessen experienced the heat firsthand. The Mosaic browser, developed at the University of Illinois, spread virally because millions of people were already on the internet but lacked a usable way to navigate it. The demand was latent but massive. Netscape shipped into that demand and reached a $2.9 billion valuation within sixteen months. At Andreessen Horowitz, his investment thesis operationalised the same insight: back founders who have found the heat, not founders who are still looking for it.
Lütke built Shopify because he couldn't find a decent way to sell snowboards online. Every existing e-commerce platform in 2004 was either prohibitively expensive, technically hostile to non-developers, or aesthetically frozen in the late 1990s. Lütke's frustration was personal — but it was shared by hundreds of thousands of small merchants who wanted to sell online and couldn't. The thermal signature was enormous: an entire class of businesses locked out of e-commerce by complexity and cost.
Shopify's early growth confirmed the heat. Merchants arrived organically, drawn by the simple promise of a beautiful online store without needing a developer. By the time Shopify went public in 2015, it was powering over 200,000 stores. Lütke didn't create the desire to sell online. He removed the barrier that was preventing it — and the pent-up demand that had been accumulating behind that barrier flooded through the moment the obstacle was removed. Shopify's revenue reached $7.1 billion in 2023, built on the foundation of demand that existed before Lütke wrote a single line of code.
Section 6
Visual Explanation
The diagram captures the two go-to-market orientations. The left column is the default startup path: build what you believe should exist, then spend energy searching for buyers. The right column is Rachleff's prescription: locate the thermal signature first, then build what it demands. The bottom row names the consequence. Push strategies burn capital to manufacture demand that evaporates when the budget stops. Pull strategies compound because each satisfied customer generates the next — the product finds its market through the market's own momentum.
Section 7
Connected Models
Heat-seeking Missiles sits at the intersection of market selection, product design, and go-to-market strategy. It connects to frameworks that describe how demand is validated, how products scale, and how markets select winners. Two models reinforce the logic. Two describe what happens after the heat is found. One introduces the tension that defines the model's boundary.
Reinforces
Product/Market Fit
Product/market fit is the state heat-seeking missiles are trying to achieve. Rachleff's framework provides the method; product/market fit is the destination. When the missile locks on — when the product reaches customers who are already burning with need — product/market fit is the result. The two concepts are inseparable: you cannot achieve product/market fit by cold-calling a market that isn't hot.
Reinforces
Jobs to Be Done
Jobs to Be Done provides the language for identifying thermal signatures. When Clayton Christensen asks "what job is the customer hiring this product to do?" he is mapping the demand that already exists — the functional, emotional, and social needs that customers are already spending money and effort to address. Heat-seeking missiles target those jobs. The stronger the existing job, the hotter the thermal signature.
Leads-to
[Distribution](/mental-models/distribution)
Once the missile finds its heat, distribution determines whether the fire spreads. A product that satisfies pre-existing demand but lacks distribution channels will burn bright and small. Slack's viral distribution — where one team adopting it pulled adjacent teams in — was the distribution mechanism that turned a heat-seeking hit into a $27.7 billion acquisition by Salesforce. Finding the heat is necessary. Distributing the solution is what makes it compound.
Leads-to
Do Things That Don't [Scale](/mental-models/scale)
Section 8
One Key Quote
"If you address a market that really wants your product — if the dogs are eating the dog food — then you can screw up almost everything in the company and you will succeed."
— Andy Rachleff, Co-founder of Benchmark Capital & Wealthfront
Rachleff compressed the entire framework into a single vivid test. The "dogs eating the dog food" image is deliberately unglamorous — it strips away every narrative about team quality, product elegance, and strategic vision to isolate the one variable that determines survival: does anyone want this? The quote's second half is equally important: when demand is genuine, even severe execution mistakes are survivable. Slack had plenty of bugs in its early releases. Dropbox had sync errors that corrupted files. Neither mattered because the demand was so intense that users tolerated imperfections they would have rejected in a product they didn't desperately need.
The corollary is darker: if the dogs aren't eating the dog food, nothing else saves you. No amount of engineering excellence, marketing spend, or team talent can substitute for demand. Google Wave had world-class engineers. It had massive distribution through Google's existing user base. It had press coverage most startups would kill for. It had everything except customers who wanted it. The dogs walked away from the bowl.
Section 9
Analyst's Take
Faster Than Normal — Editorial View
The most common way startups die is not running out of money. It is building something nobody wants. Y Combinator's post-mortem data confirms this repeatedly — the number one cause of startup failure is "no market need." The heat-seeking missile framework is the most actionable antidote to that failure mode because it resequences the startup process: demand discovery before product development, not after.
The pattern I see in the strongest founders is an almost obsessive ability to distinguish real demand from manufactured demand. Real demand leaves traces in behaviour: workarounds, spreadsheet hacks, budget line items for inferior solutions, frustrated forum posts, churning customers on competitor platforms. Manufactured demand exists in slide decks and surveys — it sounds compelling in investor meetings but evaporates the moment the product ships. The founders who build heat-seeking missiles are the ones who spend weeks in forums, on customer calls, and in competitor reviews before they write a single specification. They know the heat is real because they've felt it radiating from the market.
The second pattern worth naming: the best products often emerge from the founder's own pain. Lütke couldn't sell snowboards online. Houston kept forgetting his USB drive. Butterfield's team needed a better way to talk to each other. Craig Newmark wanted a simple email list for San Francisco events. Brian Chesky couldn't afford rent. These aren't sophisticated market analyses. They're personal frustrations that turned out to be shared by millions. The founder's own pain is the first thermal signature — and if the founder is representative of a large population, that signature is predictive.
The failure mode I see most frequently is premature scaling of cold demand. A startup gets a handful of customers through aggressive outbound sales, interprets the revenue as product/market fit, and raises money to scale the sales team. But the customers were dragged over the line, not pulled. Retention is poor. Expansion revenue is nonexistent. The sales team burns cash at an accelerating rate while the product never reaches the organic pull that characterises genuine demand. The company dies slowly, bleeding from a CAC wound that no fundraise can heal, because the fundamental problem was never demand — it was the absence of demand disguised as an early-stage sales challenge.
The limitation worth naming is real: some of the most transformative products in history didn't find demand — they created it. The iPhone, the Model T, the personal computer, the printing press. Rachleff's framework is optimised for the vast majority of startups — those that are better served finding and serving existing demand than attempting to reshape human behaviour. But for the rare founder with the conviction, resources, and taste to create a new category, the heat-seeking approach is insufficient. Steve Jobs didn't seek heat. He lit a fire that the rest of the industry spent a decade trying to find.
Section 10
Test Yourself
The scenarios below test whether you can distinguish genuine heat-seeking — products that find and serve pre-existing demand — from cold-calling disguised as strategy. The critical question in each case: was there observable demand before the product existed?
Is this mental model at work here?
Scenario 1
A B2B startup builds an AI-powered meeting summariser after the founder noticed her team spending hours writing meeting notes. Before writing code, she surveyed fifty enterprise teams and found that 90% expressed interest in 'an AI tool that automatically summarises meetings.' She raises a seed round on the survey data and builds the product. Six months after launch, paid conversion is 2% and monthly churn is 18%.
Scenario 2
A developer notices hundreds of threads on Hacker News and Stack Overflow where engineers complain about the complexity of deploying containerised applications. Many have built custom scripts. Some are paying for overpriced enterprise tools they hate. He builds a simplified deployment tool, posts it on Hacker News, and gets 3,000 GitHub stars in the first week. Within three months, twelve companies are paying for the hosted version without a single outbound sales email.
Scenario 3
A well-funded startup with a strong engineering team builds a social network for pet owners. The product is beautifully designed with advanced features: AI-powered pet health tracking, breed-specific community forums, and a marketplace for pet services. The company spends $5 million on launch marketing, including influencer partnerships and Super Bowl regional ads. First-month downloads hit 200,000. By month six, daily active users have dropped to 8,000.
Section 11
Top Resources
The heat-seeking missile framework draws from venture capital pattern recognition, product strategy, and market analysis. Start with Rachleff for the original framework, move to Andreessen for the market-first thesis, and use the practitioner resources for operational implementation.
Rachleff's most direct articulation of the heat-seeking missile framework: prove the Value Hypothesis before raising capital, find the market that wants your product before scaling it. Includes the "dogs eating the dog food" formulation and the distinction between value creation and value capture that underpins the entire model.
Andreessen's canonical essay on product/market fit, which argues that market quality is the single variable that determines startup outcomes. The essay provides the intellectual foundation for the heat-seeking missile metaphor: if the market is great and the product basically works, the market pulls the product forward regardless of team quality. If the market doesn't exist, nothing else matters.
The most practical guide to distinguishing real demand from polite encouragement. Fitzpatrick's framework teaches founders to ask questions that reveal what customers actually do rather than what they say they would do — the operational equivalent of scanning for thermal signatures rather than listening to hypothetical interest.
Moore's framework describes what happens after the missile finds its initial heat: the challenge of crossing from early adopters (who tolerate imperfection because the pain is acute) to the early majority (who require a complete solution). The "chasm" is the gap between the initial pocket of burning demand and the broader market — where heat-seeking precision must give way to market-building.
Schultz's Stanford lecture on growth includes the most data-rich discussion of how to distinguish organic pull from manufactured traction. His framework for measuring retention curves — the diagnostic tool for determining whether the dogs are eating the dog food — operationalises the heat-seeking missile test with metrics that founders can track from day one.
Heat-seeking Missiles — Cold-calling fires into the void and hopes. Heat-seeking locks onto pre-existing demand and builds for it.
Paul Graham's advice to do things that don't scale is the operational manual for the heat-seeking phase. Before the product scales, founders must manually locate the heat — calling customers, sitting in on workflows, reading support tickets, haunting forums. These unscalable activities are the targeting system. Once the thermal signature is confirmed, the missile locks on and the scalable machinery takes over.
Tension
Iron Law of Market
The Iron Law of Market — that a great market matters more than a great product or great team — both supports and tensions with heat-seeking missiles. It supports the premise: find the hot market first. The tension emerges because the Iron Law implies that any product in a great market will succeed, while the heat-seeking framework requires building the right product for that specific heat. A great market with a poorly targeted product still fails. The market creates the heat. The product must still seek it precisely.
Reinforces
[MVP](/mental-models/mvp)
The minimum viable product is the smallest possible missile. The MVP framework accelerates the heat-seeking process by reducing the cost of each targeting attempt. Build the thinnest version that addresses the core pain, launch it into the pocket of demand, and measure whether the heat is real. If retention is strong and pull is genuine, invest in the full product. If not, retarget. The MVP makes heat-seeking cheap enough to iterate.
For the 99% of founders who are not Steve Jobs, the prescription is clear: find the heat before you build the missile. Talk to a hundred potential customers. Map the workarounds. Read the competitor reviews. Look for the thermal signatures that tell you demand already exists. If you can't find them, either you're looking in the wrong place or the demand isn't there. Both possibilities require a different response than writing more code.
