Validate problem frequency and monetization potential before building
When evaluating ideas from friends or observations, ask critical qualifying questions: How frequent is the problem? Can you build something better? Can you monetize it? Can you find clients? Only start building if you can answer yes to all questions. Problem frequency indicates market size; monetization and distribution potential indicate viability.
When to use
When evaluating ideas that come from observing others' problems rather than your own pain points
Don't do this
Building solutions for interesting problems without validating frequency, monetization, or distribution
3 Founders Who Did This
Asked real estate agent friends validation questions: 'You have this problem but when? How frequent? Am I able to do better? Am I able to monetize it and to find clients?' Only started after yes to all
Built a peer-to-peer musical gear rental marketplace targeting independent musicians with a small commission model without validating frequency or monetization potential
Targeted young streamer fans who lacked disposable income for $500-$1000 experiences without validating willingness to pay