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 have the capacity to build. You have time, maybe some savings, definitely the technical skills. What you don't have is a clear direction. Every idea you generate feels either too small to matter, too crowded to enter, or too vague to validate. You've read about "finding your niche" and "scratching your own itch," but your own itches are either already solved by excellent existing tools or too idiosyncratic to support a business. You've tried browsing Product Hunt, Indie Hackers, and Reddit for inspiration, but seeing other people's successes mostly makes you feel behind. You've considered B2B SaaS, consumer apps, marketplaces, tools for developers, tools for non-technical people—each path branches into more uncertainty. The result: you keep building half-finished prototypes, or worse, you build nothing at all while waiting for the "right" idea to arrive fully formed.

This isn't a creativity problem. It's a process problem. You're trying to discover opportunities through inspiration instead of investigation.

Why the Usual Fixes Fail

Waiting for inspiration. Ideas don't strike like lightning. They emerge from pattern recognition across many data points. Sitting at your desk hoping for a eureka moment is not a strategy.

Copying successful products. By the time a product is visible enough for you to copy, the market has already priced in its obvious value. You're entering a red ocean with worse distribution and no differentiation.

Building for yourself without checking if others share the problem. Your workflow is weird. Your constraints are specific. Most "scratch your own itch" projects fail because the builder mistakes personal annoyance for market demand.

Relying on keyword research tools. Search volume tells you what people already know to look for. It misses latent needs, workarounds people have normalized, and problems they don't have language for yet.

Asking people "what do you need?" People are bad at predicting their own behavior. They'll describe solutions, not problems. They'll be polite. They'll imagine a world where they have more discipline than they actually do.

Chasing trends. AI wrappers, Web3, no-code tools for X—by the time a trend has a name, the easy opportunities are gone. The remaining ones require deep domain knowledge you don't have.

Step-by-Step Solution

Phase 1: Map Your Access (Week 1)

Opportunity discovery starts with where you can actually reach, not what you think is cool.

List every community you have genuine access to. Not "I could join this Discord." Communities where you already participate, where people recognize your name, where you understand the unwritten rules. Former coworkers. Industry Slacks. Niche subreddits you've commented in for years. Professional associations. Alumni groups. Specialized forums. Conference buddy networks. Your parents' industry contacts. Your partner's coworkers.

For each community, document:

  • What role do you play there? (insider, helpful outsider, silent observer)
  • What's the communication culture? (long-form threads, quick chat, email lists, in-person)
  • What's the purchasing dynamic? (individual buyers, team budgets, enterprise procurement, reimbursement policies)
  • What tools do they already pay for? What do they complain about paying for?

Rank these by access quality, not market size. A community of 200 structural engineers where you're a trusted voice beats 10,000 "entrepreneurs" where you're nobody.

Phase 2: Observe Work, Not Opinions (Weeks 2-3)

Go where the work happens. Watch. Record. Don't interview yet.

Shadow sessions. Ask 3-5 people in your top-ranked community if you can watch them work for 90 minutes. Frame it: "I'm researching how [role] handle [specific workflow]—no product to sell, just learning." Screen share or sit beside them. Watch for:

  • Workarounds: spreadsheets bridging two systems, manual copy-paste, browser extensions they built themselves, sticky notes on monitors
  • Repeated friction: "Every time I have to..." "I always forget to..." "It takes me forever to..."
  • Tool switching: count how many tabs/applications open for one task
  • Handoffs: where work moves between people, teams, or tools—and what gets lost
  • Compliance theater: steps done only to satisfy audit/legal/management that add no value

Take timestamped notes. Not "they seemed frustrated." Instead: "14:23 — copied invoice data from PDF to Excel, then manually entered into NetSuite. Said 'I do this ~15x/day.'"

Collect artifacts. Ask for screenshots of their dashboard, their most-used spreadsheet, their browser bookmark bar, their phone home screen. These reveal more than interviews.

Phase 3: Problem Interviews (Week 4)

Now talk—but only about observed behaviors.

Recruit from shadow sessions plus 5-8 more. Same communities. 30 minutes max. No demos. No solutions.

Script:

  1. "Walk me through the last time you did [observed workflow]."
  2. "What tools did you use? What happened right before and after?"
  3. "What's the worst part? Why?"
  4. "How do you handle it today? What have you tried?"
  5. "What happens if this goes wrong? Give me a recent example."
  6. "Who else is involved? What do they care about?"
  7. "If this were magically better, what would change for you? For your team? For your boss?"

Record and transcribe. Look for:

  • Frequency × Severity: Problems that happen daily and cause real consequences (lost revenue, compliance risk, missed deadlines, reputational damage)
  • Budget evidence: They already pay for partial solutions, or they've built internal tools, or they've hired contractors
  • Decision clarity: You can identify who signs off, what their criteria are, and what timeline they operate on
  • Workaround sophistication: The more elaborate the workaround, the more validated the need

Discard: "Nice to have," "would be cool," "my team might like," problems without budget owners, problems where the workaround is "we just don't do that."

Phase 4: Solution Discovery (Week 5)

You're not building yet. You're testing whether a specific solution fits a specific problem for a specific buyer.

Write a one-pager for each surviving problem:

  • Problem statement (one sentence, their language)
  • Who has it (title, company size, industry, trigger event)
  • Current workaround (tools + time cost)
  • Consequence of inaction (their words)
  • Budget owner + typical approval path
  • Your unfair advantage (access, technical insight, domain knowledge, distribution channel)

Build the smallest testable artifact. Not an MVP. A clickable prototype, a detailed workflow diagram, a fake dashboard screenshot, a 3-minute Loom video walking through the proposed solution. Something you can show in 5 minutes.

Test with 5-8 people from your interview pool. Same script:

  1. "Here's what I heard you describe. Does this match?"
  2. "Here's a rough idea of how it could work. Walk me through your reaction."
  3. "What would stop you from using this?"
  4. "What would need to be true for you to advocate for this internally?"
  5. "If this existed today at $X/month, what's your honest next step?"

Listen for: "Can I get access?" "Who do I talk to about budget?" "Does it integrate with [tool]?" — not "cool idea" or "let me know when it launches."

Phase 5: Commit or Kill (Week 6)

Decision matrix for each opportunity:

Criteria Threshold
3+ interviewees asked for access/pricing Yes/No
Clear budget owner identified Yes/No
You can reach 20+ similar buyers in 30 days Yes/No
Technical feasibility: 80%+ confidence in 90-day build Yes/No
You'd work on this problem for 3+ years Yes/No

If 4/5 yes: Build. Set a 90-day deadline to first paying customer.

If 3/5 yes: Run one more test. Narrow the scope. Re-interview.

If ≤2/5 yes: Kill. Archive the research. Move to next problem.

Document the kill reasoning. You'll forget why you rejected things. Six months later you'll reconsider a dead idea unless you wrote down: "No budget owner—CTO loved it but CFO vetoed every tool over $200/mo."

Checklist

  • [ ] Listed 10+ communities where you

Start here

Top comments (0)