DEV Community

Alan Descure
Alan Descure

Posted on Originally published at smtm-store.pages.dev

Opportunity Discovery: A Practical Guide for When You're Stuck

Opportunity Discovery: A Practical Guide for When You're Stuck

The Problem in Concrete Terms

You're sitting at your desk with a notebook open, a blank document, or a whiteboard covered in half-erased scribbles. You want to build something—product, service, content business, side project—but every idea feels either obvious and crowded, or vague and untestable. You've read about "finding your niche" and "solving your own problems" and "scratching your own itch," but your itches are either already solved by ten competitors or too weird to build a business around.

The stuckness shows up in specific ways:

  • You maintain a running list of ideas but never move past the "that's interesting" phase
  • You research a market for three weeks, find competitors, and abandon it
  • You build a landing page, get zero signups, and don't know what to change
  • You interview five people, hear "nice to have" instead of "take my money," and freeze
  • You cycle between "everything's taken" and "I have no ideas" without a third option

The core issue isn't creativity. It's that you're treating opportunity discovery as inspiration rather than investigation. You're waiting for a lightning strike instead of running a systematic search process.


Why the Usual Fixes Fail

1. "Solve your own problem"
Works if your problem is shared by thousands of people willing to pay. Fails when your problem is idiosyncratic, already solved, or too small to sustain a business. Most people's personal problems fall into one of these buckets.

2. "Follow your passion"
Passion is a feeling, not a market signal. You can be passionate about underwater basket weaving; that doesn't mean anyone will pay for your course. Passion sustains you after you've found a viable opportunity—it doesn't help you find one.

3. "Look for gaps in the market"
Gaps are invisible until you understand the market structure. Beginners mistake "I don't see a product for X" for "there's a gap," when the reality is usually "X has no budget," "X is solved by a workflow, not a tool," or "X is a feature, not a product."

4. "Validate with a landing page"
A landing page tests interest, not willingness to pay. People click "notify me" for things they'd never buy. False positives waste months. False negatives kill viable ideas because your copy or traffic source was wrong.

5. "Just start building"
Building without a discovered opportunity is expensive prototyping. You learn to code, not whether anyone wants the thing. The feedback loop is 3-6 months instead of 3-6 days.


Step-by-Step Solution: Systematic Opportunity Discovery

This process takes 2-4 weeks part-time. Each step produces a concrete artifact you can review, share, or discard. Do not skip steps. Do not combine steps.

Week 1: Map Your Access Advantages

Goal: Identify where you have unfair access to information, people, or distribution.

Day 1-2: List every professional and social circle you belong to.

  • Current and past employers, clients, contractors
  • Industry associations, Slack/Discord communities, forums
  • Alumni networks, meetups, conference circuits
  • Newsletters you read, podcasts you listen to, creators you follow
  • Hobbies with active communities (not passive consumption)

Day 3: For each circle, answer:

  • What decisions do these people make repeatedly?
  • What tools/workflows do they complain about in private?
  • What budgets do they control or influence?
  • What regulations/constraints shape their work?
  • Who do they trust for recommendations?

Day 4: Score each circle 1-5 on:

  • Access depth (can you DM 10+ people and get replies?)
  • Budget authority (do they spend $100+/month on tools?)
  • Problem frequency (daily/weekly pain vs. quarterly annoyance)
  • Your credibility (do they see you as a peer?)

Artifact: A ranked table of 10-20 circles with scores. Keep the top 3-5.

Week 2: Extract Problem Candidates

Goal: Generate 30+ specific, observed problem statements from your top circles.

Day 5-7: Conduct 15-20 minute conversations (not interviews).
Reach out to 2-3 people per top circle. Script:

"I'm researching how [role/industry] handles [specific workflow]. You've been doing this a while—mind if I ask 3 questions for 15 minutes? No sales pitch."

Questions:

  1. "Walk me through the last time you did [workflow]. Where did it slow down?"
  2. "What's the last tool or process you paid for that disappointed you?"
  3. "If you could wave a wand and fix one recurring headache, what would it be?"

Rules:

  • Record (with permission) or take verbatim notes
  • Do not pitch, suggest, or solve
  • Ask "say more about that" at least 3x per call
  • Stop when you hear the same 3-4 problems across 3+ people

Day 8: Convert notes into problem statements.
Format: [Role] struggles to [specific outcome] because [constraint], resulting in [measurable cost].

Examples:

  • "Marketing managers at Series A startups struggle to attribute pipeline to content because UTM tracking breaks across channels, resulting in 40% of budget allocated by gut feel."
  • "Independent HVAC contractors struggle to schedule emergency calls around planned maintenance because dispatch software assumes fixed routes, resulting in 2-3 lost jobs per week."

Artifact: 30+ problem statements. Deduplicate. Keep 15-20.

Week 3: Filter for Viability

Goal: Reduce to 3-5 testable opportunities with evidence of budget and urgency.

Day 9: Apply the Viability Filter to each problem statement.

Criterion Pass Signal Fail Signal
Budget exists They already pay for a tool/service/workaround "We'd never pay for that" or "We use Excel"
Urgency Problem happens daily/weekly; workarounds cost hours Problem is quarterly; workaround is 15 min
Decision maker accessible You can reach the person who signs the PO Requires committee, procurement, or C-suite
Switching cost manageable Current solution is manual, spreadsheet, or single-tool Deeply embedded in ERP, regulated, or multi-year contract
Market size estimable You can count target users via LinkedIn, directories, lists "Everyone could use this"

Day 10: Score each problem 1-5 on each criterion. Keep only 4s and 5s.

Day 11: For each remaining problem, find 3 pieces of confirming evidence.

  • Job postings mentioning the pain ("must handle X workflow")
  • Forum threads with 10+ replies complaining about it
  • Competitor pricing pages showing people pay for partial solutions
  • RFPs or procurement notices specifying the need
  • Reviews of existing tools citing this exact gap

Artifact: 3-5 opportunity briefs. Each brief = problem statement + viability scores + 3 evidence links + estimated market size (back-of-napkin: target users × annual budget).

Week 4: Pre-Sell the Top 1-2

Goal: Get concrete commitment before building.

Day 12-13: Create a one-pager for each top opportunity.

  • Problem statement (from Week 2)
  • Proposed solution: 3 bullet points, no jargon
  • Price point: specific number ($297/mo, $2,500/yr, $500 setup + $150/mo)
  • Target customer: specific title, company size, tech stack
  • Next step: "15-min demo + 30-day pilot at 50% off" or "Paid discovery workshop: $1,500"

Day 14-18: Reach out to 20-30 decision makers per opportunity.
Use your access circles. Cold email if needed, but warm intros convert 5-10x better.

Script:

"I'm putting together a small pilot for [specific problem]. Based on what you've shared about [their situation], thought you might be a fit. It's [price] for [deliverable] over [timeframe]. Open to a 10-min call to see if it's worth a pilot?"

Day 19-20: Track responses.

  • "Yes, let's talk" → Schedule call, move to discovery
  • "

Start here

Top comments (0)