Successful startups are born from noticing urgent problems in domains where you have expertise, rather than by trying to 'think up' clever ideas.
Don't try to "think of" startup ideas; instead, look for specific, painful problems—preferably those you personally experience—while living at the leading edge of a rapidly changing field.
This is for the aspiring founder paralyzed by "blank page" syndrome—the inability to come up with a viable business idea. It solves the problem of "forced" innovation, where founders invent things nobody wants. After reading this, you will be able to shift your mindset from imagining products to noticing gaps, and you'll have a systematic toolkit for identifying high-demand niches that others are overlooking.
The central thesis is that successful startups grow naturally from external stimuli hitting a prepared mind ("organic" ideas) rather than being forced inventions. Most people fail because they try to manufacture ideas from thin air, leading to "sitcom" ideas: things that sound plausible (like a social network for pet owners) but lack urgent demand.
To succeed, you must identify a Well. While a "Crater" (like Google) has immense volume, it is often too large for a startup to excavate initially. A "Well" is narrow but deep—a small number of people want something urgently. Depth of need is the requirement; narrowness is merely a byproduct of optimizing for speed and depth.
By becoming the sort of person who notices these gaps—by living in the future, pursuing expertise, and turning off psychological filters like the "schlep" (the avoidance of laborious tasks)—you position yourself to notice what is truly missing before anyone else does.
The verb you want to be using with respect to startup ideas is not "think up" but "notice." Instead of trying to generate ideas on demand, you should look for things that chafe or annoy you in your daily life. Why it matters — Forced ideas often do not feel like inspirations; they are usually mediocre because everyone makes up the same ones. Organic ideas discovered by noticing what is truly missing while working in a field are far more likely to succeed. In the book — Graham argues that "The way to get startup ideas is not to try to think of startup ideas. It's to look for problems, preferably problems you have yourself."
A "Crater" represents a product hundreds of millions of people need a lot; a "Well" represents a niche where a small number of people want something urgently. Why it matters — You can build something a small number of people want a large amount. Depth is the requirement; narrowness is a byproduct of optimizing for depth and speed. In the book — The author uses a graph model where X-axis is volume (number of people) and Y-axis is intensity of need, advising founders to choose the "Well."
A good idea must have an urgent demand such that users will use it even in a crude state. Why it matters — If your friends say they "could see" using a product but don't want it now, you have a sitcom idea, not a startup idea. In the book — Ask: "Who wants this so much that they'll use it even when it's a crappy version one made by a two-person startup they've never heard of?"
The "Schlep Filter" is a subconscious avoidance of ideas involving "schleps"—painful, laborious tasks like dealing with messy payment systems or tedious logistics. Why it matters — Successful startups are laborious regardless (investors, hiring, firing). Avoiding the schlep is often an illusion/self-indulgence that prevents you from solving real problems. In the book — Stripe initially avoided payments because they shrank from the schlep of dealing with payment systems; turning off this filter was key to their success.
You should only look for ideas in areas where you already have deep expertise. Why it matters — Without expertise, you cannot trust your judgment in a domain. People often give themselves a "pass" in domains where they lack expertise (the Dunning-Kruger Pass), leading to bad ideas. In the book — A database expert should not build a chat app for teenagers (unless they are also a teenager) because they cannot trust their judgment in that domain.
To notice what is missing, you must get to the leading edge of a rapidly changing field as a user or builder. Why it matters — This allows you to "live in the future" and see the gaps before they become obvious to everyone else. In the book — Graham suggests ratcheting yourself into the future and studying unrelated fields (e.g., a CS major taking genetics) to find software problems in new domains.
Use this to vet any idea you notice:
If you cannot notice an idea organically, use these systematic prompts:
This week
Ongoing
Reflection questions
Flashcards Q: What is the difference between a "Well" and a "Crater"? A: A Well is narrow but deep (high intensity of need); a Crater has immense volume (huge number of people) but may lack initial urgency. Q: What is the "Schlep Filter"? A: The subconscious avoidance of ideas involving laborious, painful tasks (like payment systems). Q: What is the "Urgency Test"? A: Asking: "Who wants this so much that they'll use it even when it's a crappy version one made by a two-person startup they've never heard of?" Q: Why should you avoid trying to "think up" ideas? A: Forced ideas often do not feel like inspirations and are usually mediocre because everyone makes up the same ones. Q: What is the "Expertise Rule"? A: Only look for ideas in areas where you have expertise, otherwise you cannot trust your judgment on what constitutes a real problem. Q: How can you "live in the future" to find ideas? A: Get to the leading edge of a rapidly changing field as a user or builder to notice what is missing before others do.
Confidence: High. This summary is grounded strictly in the provided notes from Paul Graham's material. I am certain about the "Well vs. Crater" model, the "Schlep Filter," and the "Notice vs. Think" distinction. The specific "Plan B Recipes" were extracted directly from the text. There is no outside information included.