Deep domain expertise; the founder has direct, extended experience within a specific industry (dental office administration) and has observed a recurring workflow problem (patient recall coordination) that people in this industry already struggle with, matching this lesson’s description of domain expertise as a reliable idea source.

Solution looking for a problem; the founder started from excitement about a specific technology (the AI capability) and is now searching for a problem to retroactively justify it, rather than starting from an actual, observed problem first, which this lesson identifies as a common trap that often causes later validation struggles.

A vitamin; since users aren’t currently actively spending resources trying to solve this problem (no urgent, acute pain driving them to seek a solution), this matches the vitamin category, which this lesson identifies as much harder to get people to pay for, especially before they’ve tried the product.

A painkiller; firms are already actively spending time and experiencing worry/urgency around this problem (avoiding penalties, meeting deadlines), matching this lesson’s description of a painkiller as something people are already trying to solve, making it easier to justify switching to a better solution.

Because a founder who has directly experienced the problem already understands its nuances, urgency, and the specific frustrations involved from the inside, rather than needing to learn all of this secondhand from others; this existing understanding allows the founder to more quickly recognize whether early user feedback reflects a genuine, familiar pain point or a tangential concern, and to iterate on solutions more efficiently since they already grasp the problem’s real shape rather than starting from a more abstract, external understanding.

Not necessarily automatically dismissed; while this lesson identifies personal pain and domain expertise as the two most reliable sources, it doesn’t claim these are the only possible valid sources – a genuine painkiller-level problem identified through other means (observation, research) could still be worth pursuing, though the founder might need to work harder to develop the empathy and nuanced understanding that direct personal experience or domain expertise would have provided more readily, according to this lesson’s reasoning.

This broad framing spans multiple very different buyer types (freelancers, small agencies, enterprise teams) with likely very different specific needs and workflows, which raises a concern about whether this idea reflects a genuinely specific, deeply understood problem (as domain expertise or personal pain would provide) or a more general, less-specific idea; this concern about narrowing to one specific buyer and problem is exactly what the following lesson addresses in more depth.

This memory demonstrates genuine painkiller-level pain: the founder didn’t just imagine this problem was annoying, they actually spent significant real money ($500) to solve it through a manual workaround, which is exactly the kind of “already spending money, time, or workarounds on it” evidence this lesson identifies as characterizing a painkiller rather than a vitamin.

Because validation processes like customer interviews are specifically designed to surface whether real people have a genuine, pre-existing problem and are already trying to solve it; an idea that started from technology-first thinking (rather than an observed problem) may struggle to find real people who actually recognize and feel urgency about the invented problem, since the problem was constructed to justify the solution rather than discovered independently in the world, meaning validation conversations may repeatedly reveal a lack of genuine, existing pain no matter how impressive the underlying technology is.

Not necessarily less valid; this lesson presents personal pain and domain expertise as two separate, both-reliable sources, rather than ranking one above the other – domain expertise specifically allows a founder to identify problems observed extensively within an industry even without directly, personally experiencing that exact problem themselves, which this lesson treats as an equally legitimate path to a strong idea.

Painkiller/vitamin status appears to matter more for fundamental commercial viability specifically, since this lesson ties this distinction directly to willingness to pay (“switching to something better is relatively easy to justify” for a painkiller, versus a vitamin being “much harder to get someone to pay for”); domain expertise is presented as valuable for execution and empathy (helping identify and understand the problem, and iterate effectively), but doesn’t by itself change whether the underlying problem is one people will actually pay to solve, suggesting the painkiller quality is a more fundamental viability factor even though domain expertise remains valuable for other reasons.

These address genuinely different questions: idea source concerns how well-positioned the founder is to understand and execute on the problem (through direct experience or domain knowledge), while idea quality (painkiller versus vitamin) concerns whether the underlying problem itself is one people are actually motivated to pay to solve; an idea could come from a strong source (deep personal pain) while still being a vitamin-level problem with weak commercial pull, or could be a strong painkiller-level problem discovered through a less personal source – since both dimensions independently affect an idea’s prospects, evaluating idea source alone wouldn’t be sufficient without also separately assessing whether the underlying problem itself has genuine painkiller-level urgency.