How to Find Product Opportunities Worth Building

Why Most Solo Founders Pick the Wrong Idea

The Three Discovery Traps

Your first idea is rarely your best idea. But most solo founders never give themselves a chance to discover that — they pick the first idea that excites them and start building.

Here are the three most common discovery traps:

Trap 1: Scratching Your Own Itch — Without Checking If Anyone Else Has It

You hit a problem, think "I could build a tool for this," and open your editor. It feels like a validated idea because you experienced the pain. But you haven't checked whether enough other people share that pain to build a business around it.

A developer frustrated with Jira builds a "simpler Jira." A designer annoyed by Figma's pricing builds a "cheaper Figma." These ideas feel right because they come from personal experience — but personal experience is a sample size of one.

Trap 2: Chasing Shiny Tech

A new model drops. A new framework goes viral. Suddenly every tweet in your timeline is about "building with X." The excitement is real — but the problem you're solving with it might not be.

GPT wrappers in 2023, crypto projects in 2021, VR apps in 2016. The common thread: founders started with the technology and went looking for a problem to attach it to. Technology should serve a problem, not the other way around.

Trap 3: Building for a Market You Don't Know

You read that "the HR tech market is $30B" or "edtech is growing 16% YoY." You've never worked in HR or education, but the numbers are compelling. So you build something for a user whose daily reality you don't understand.

You won't know what to build. You won't know where to find users. You won't know who to talk to. Every step from discovery to launch will be uphill.

What Good Discovery Looks Like

Good discovery isn't about generating brilliant ideas. It's about building a system for collecting and filtering signals.

A signal is evidence that a specific group of people has a specific problem they're actively trying to solve. The goal of discovery is to collect enough signals that patterns emerge, then select the 2-3 directions most worth validating.

The process takes 1-4 weeks and requires no code. Your tools during discovery: a browser, a note-taking app, and curiosity.

---

Where to Find Signals

The Signal-Rich Platforms

Not all platforms are equally useful for discovery. Here are the ones that consistently produce actionable signals:

How to Read Each Platform

Hacker News

Don't just browse the front page. Search for patterns:

• Ask HN: What pains you about...

  — people listing their frustrations

• Ask HN: Is there a tool that...

  — people looking for something that doesn't exist
• Comments on product launches where users say "this is close to what I need but..."

The gold isn't in the posts — it's in the comments. A post with 3 upvotes and 40 comments often has more signal than a post with 300 upvotes and 5 comments.

Reddit

Go to subreddits where your target users complain about their tools. Examples:

• r/Notion, r/ObsidianMD, r/Figma for productivity/tool users
• r/Teachers, r/nursing, r/accounting for professional communities
• r/SaaS, r/startups for founder-focused products

Sort by "New" instead of "Hot." The signal-to-noise ratio is lower, but the signals you find won't already be picked over by everyone else.

Twitter/X

Use search operators:

• "I would pay for"

  + your domain keyword

• "I wish there was a"

  + tool category

• "someone should build"

  + problem area

Follow builders-in-public in adjacent spaces. Their replies section is a goldmine — their audience tells them exactly what they want.

App Store / Chrome Web Store Reviews

The most underrated discovery channel. Find the top 3 products in a space you're interested in, then read their reviews sorted by "Most Critical."

Look for 3-star reviews specifically. 1-star reviews are usually angry and unhelpful. 5-star reviews are too vague. 3-star reviews are people who use the product enough to care but are frustrated enough to write a detailed critique. Every 3-star review is a feature gap someone would pay to fill.

---

How to Filter and Score Directions

The Five-Question Filter

Once you've collected 10-15 signals, group them into candidate directions. For each direction, answer these five questions:

1. Who exactly has this problem? Can you describe a specific person? "Developers" is too broad. "Backend engineers at 20-50 person startups who write internal CLIs" is specific enough.

2. How do they solve it today? If the answer is "they don't," be suspicious. Every real problem has a current solution — even if it's "manually in Excel" or "paying a VA $15/hour." A problem with no current solution is usually a problem nobody actually cares about.

3. How often do they hit this problem? Daily > weekly > monthly > once per quarter. A painful problem that happens once a year is not a business. A mild annoyance that happens three times a day might be.

4. Are they already spending money on adjacent problems? Someone who pays $30/month for Notion is more likely to pay for a Notion-related tool than someone who uses free alternatives. Follow the money.

5. Why you? What do you know about this user or problem that someone random doesn't? If the answer is "nothing special," either learn more before building or pick a different direction.

Scoring Template

Score each direction 1-5 on these dimensions:

Add up the scores. Directions scoring 18+ are worth validating. Directions scoring 12-17 need more signal collection. Directions below 12 should be set aside.

---

Building Your Direction Shortlist

The One-Page Direction Document

For each direction that passes the filter, write a one-page document. Keep it short — if it takes more than 15 minutes to write, you're overthinking it.

Use this template:

Direction: [One-line description]

Who: [Specific user profile — role, company size, context]
Problem: [What they can't do today, or what takes too long]
Current solution: [How they solve it now — even if it's manual]
Why now: [What changed that makes this solvable today? New API? Behavior shift?]
Signal sources: [Links to 3-5 specific posts/comments/reviews]
Revenue model guess: [Subscription? One-time? Usage-based? Rough price range]
Competitive landscape: [2-3 existing products and how they fall short]
My unfair advantage: [Why I'm better positioned than a random developer]

Real example of a completed direction document:

Direction: AI-powered weekly report generator for team leads

Who: Engineering managers at 20-200 person companies who write
     weekly status reports for leadership
Problem: Spending 2-3 hours every Friday compiling updates from
         Slack, Jira, and GitHub into a coherent report
Current solution: Manual copy-paste from multiple tools into a
                  Google Doc template
Why now: LLMs are good enough at summarization to produce useful
         drafts, and managers are already using ChatGPT for this
         (just not in an automated way)
Signal sources:
  - r/EngineeringManagers: "How do you handle weekly reporting?" (34 comments)
  - HN: "Ask HN: Tools for automated status reports?" (18 comments)
  - Twitter: 4 separate "I spend my Fridays writing reports" tweets
    with high engagement
Revenue model guess: $15-30/manager/month subscription
Competitive landscape:
  - Standuply: async standups, not weekly reports
  - Geekbot: focused on standups, weak on cross-tool aggregation
  - Manual ChatGPT: works but requires copy-paste every time
My unfair advantage: I was an EM for 4 years and wrote ~200 weekly
                     reports. I know the format leaders actually want.

Selecting Your Top 2-3

You should end discovery with 2-3 direction documents, not 1. Here's why:

• If validation fails on your first direction (and it often does), you have backups ready
• Having alternatives reduces the emotional attachment to any single idea
• Comparing directions side-by-side reveals which one you're actually excited about

If you can't find 2-3 viable directions after 4 weeks of signal collection, the problem isn't the market — it's your signal sources. Broaden your inputs before concluding there's "nothing to build."

---

Common Discovery Mistakes

Mistake 1: Stopping at One Idea

You find a direction that seems promising and immediately want to start building. This is the most common discovery failure.

The fix: set a rule before you start. "I will document at least 3 directions before I pick one to validate." The rule protects you from your own enthusiasm.

Mistake 2: Confusing "Interesting" with "Viable"

A problem can be intellectually fascinating without being commercially viable. "Decentralized identity verification for Web3 gaming" is interesting. "A tool that helps small restaurant owners schedule staff" is boring — and probably makes more money.

The fix: for each direction, ask "would someone pay for this?" If you hesitate for more than 3 seconds, it's interesting, not viable.

Mistake 3: Researching Forever

Discovery should take 1-4 weeks, not 3 months. At some point you have enough information and need to move to validation. More research won't make the decision easier — it'll just delay the real test.

The fix: set a hard deadline. "By [date 4 weeks from now], I will pick 2-3 directions and move to validation." Put it on your calendar.

Mistake 4: Ignoring Your Own Constraints

A direction that requires $50K in upfront infrastructure isn't a solo founder opportunity. A direction that requires FDA approval isn't a 4-week validation. Be honest about what you can actually execute with your resources.

The fix: add a "feasibility" check to your direction document. Can you build an MVP in under 3 months? Can you reach the target users without a marketing budget? If either answer is no, the direction is for a different kind of company.

Mistake 5: Asking Friends for Direction Feedback

Your friends want you to succeed. They'll say your idea sounds great because they like you, not because they'd pay for it. Their encouragement feels like validation but is actually noise.

The fix: don't ask "what do you think of this idea?" Ask "have you ever had this problem?" If they say yes, ask "how do you solve it today?" If they don't have a current solution, they don't actually have the problem.

---

Exit Checklist

You're ready to move from Discovery to Validation when:

• You have 2-3 completed direction documents, each with a specific user profile
• Each direction is backed by at least 5 independent signals (not 5 signals from the same thread)
• You can articulate why you are well-positioned to solve each problem
• You've eliminated directions that are "interesting but not viable"
• You've set a deadline and haven't exceeded 4 weeks of discovery
• You're equally willing to pursue any of your 2-3 directions into validation

---

Next Step

Once you have your 2-3 directions documented, move to Validation. Pick the highest-scoring direction and test whether real strangers will pay for it — before you write a single line of code.

If you'd rather not spend hours every day manually scanning platforms for signals, Opportunity Scanner monitors 65+ data sources weekly and delivers the patterns in one report.