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 time, skills, and maybe even capital—but every idea you generate feels either obvious, saturated, or too small to matter. You've read the "scratch your own itch" advice, but your itches are either already solved or too niche to build a business around. You've tried "talking to customers," but you don't know which customers, what to ask, or how to separate polite encouragement from actual demand.

The stuckness shows up in specific ways:

  • Idea paralysis: You maintain a Notion page of 47 concepts but haven't committed to one in six months
  • Validation theater: You run surveys, post in communities, get "great idea!" replies, then hear crickets when you ask for pre-orders
  • Market confusion: You can't tell if a space is "crowded but growing" or "saturated and dying"
  • Scope creep before launch: Every idea expands into a platform before you've validated a single feature
  • Founder-market fit blindness: You chase opportunities that look good on paper but require skills, networks, or risk tolerance you don't have

The core issue isn't creativity—it's that you lack a repeatable process for finding and filtering opportunities that match your specific constraints.


Why the Usual Fixes Fail

1. "Scratch your own itch"
Works if your itch is shared by thousands of people with budget and urgency. Fails when your problems are idiosyncratic (you need a better way to organize your stamp collection) or already solved (you want a simpler project management tool).

2. "Talk to 50 customers"
Without a hypothesis about who and what problem, conversations become unfocused. People are polite. They'll say "I'd use that" to be nice. You need a framework to distinguish curiosity from commitment before you schedule calls.

3. "Look for problems in communities"
Reddit, Discord, and forums surface complaints, but complaints ≠ paying demand. People complain about things they'll never pay to fix. You need a way to filter signal from noise.

4. "Follow trends" (AI, Web3, no-code, etc.)
By the time a trend is visible in TechCrunch, the low-hanging fruit is gone. Trend-chasing also ignores your unique advantages—you're competing with everyone else who read the same article.

5. "Build an audience first"
Audience-building is a valid strategy, but it's a distribution strategy, not a discovery strategy. You still need something worth distributing. Many creators build audiences then realize they have nothing to sell them.

6. "Copy what works"
Cloning a successful product without understanding why it works (distribution channel, timing, founder leverage, network effects) leads to zombie products—functional but unprofitable.


Step-by-Step Solution

Phase 1: Define Your Constraint Box (Days 1-2)

Before looking outward, map your inward reality. Opportunities only matter if you can execute them.

Write down honest answers to:

Constraint Your Answer
Capital available $_____ (personal + accessible)
Runway _____ months before revenue required
Technical depth What can you build alone in 4 weeks?
Domain expertise Industries where you have insider knowledge or credibility
Network access Who can you call for intros, feedback, or first customers?
Risk tolerance What's the worst outcome you can absorb?
Time commitment Hours/week realistically available
Distribution leverage Existing audience, SEO assets, partnerships, cold email skill

Filter rule: Any opportunity requiring resources outside this box is discarded now, not later. This prevents the "I'll learn React/raise money/hire sales" fantasy loop.


Phase 2: Generate Candidate Problem Spaces (Days 3-7)

Don't generate ideas. Generate problem spaces—areas where money moves and friction exists.

Source 1: Your work history (highest signal)
List every role, project, client engagement. For each, identify:

  • Manual processes people complained about
  • Spreadsheets acting as makeshift software
  • Expensive consultants hired for repeatable work
  • Tools that were "good enough but annoying"
  • Budget line items that made finance wince

Source 2: Adjacent industries
Take your domain expertise and look one step sideways.

  • If you know B2B SaaS sales → look at sales enablement, RevOps, commission tracking
  • If you know construction → look at subcontractor scheduling, material procurement, compliance docs
  • If you know healthcare → look at prior auth, referral management, credentialing

Source 3: B2B marketplaces & aggregators
Browse G2, Capterra, Software Advice. Filter by:

  • Categories with 50+ competitors (proves budget exists)
  • Low average ratings (proves dissatisfaction)
  • High "most reviewed" counts (proves active buying)
  • Recent funding announcements in the space (proves growth)

Source 4: Government & regulatory filings

  • SEC 10-K "Risk Factors" sections for public companies in your domain
  • State licensing board complaint databases
  • RFP databases (SAM.gov, state portals) — what are agencies buying?

Source 5: Job postings as demand signals
Search LinkedIn/Indeed for roles like "Salesforce Admin," "HubSpot Specialist," "NetSuite Consultant," "QuickBooks Cleanup." High volume + high salary = companies paying to work around software gaps.

Output: A list of 15-20 problem spaces. Format each as:

[Problem Space] — [Who has it] — [Current workaround] — [Budget evidence] — [My access/advantage]

Example:

Subcontractor insurance compliance tracking — GCs and subs — Shared spreadsheets + email reminders — $12K/yr per GC in admin + fines — I managed subs for 3 years, know 5 GCs


Phase 3: Rapid Filter (Days 8-10)

Apply hard filters to your 15-20 candidates. Kill ruthlessly.

Filter 1: Urgency test
Can the buyer not solve this today without losing money, legal exposure, or competitive position?

  • "Nice to have" → kill
  • "We'll get to it next quarter" → kill
  • "We're getting fined $5K/month until this is fixed" → keep

Filter 2: Budget owner accessibility
Can you reach the person who signs the check without a 6-month enterprise sales cycle?

  • Individual contributor user ≠ budget owner
  • Department head with $10K discretionary → accessible
  • Procurement committee → kill (unless you have enterprise experience)

Filter 3: Founder-market fit
Does this leverage something in your Constraint Box?

  • Requires cold calling but you hate phones → kill
  • Requires deep ML but you're a frontend dev → kill
  • Uses your network of 5 GCs → keep

Filter 4: Market structure

  • 3-10 competitors doing $1M-$10M ARR → healthy market, room for niche
  • 0 competitors → either no market or you're early (dangerous for first-time founders)
  • 1 dominant player (80%+ share) → kill unless you have structural wedge

Filter 5: Expansion path
If you win this wedge, can you expand to adjacent problems without rewriting the product?

  • Single feature tool → risky
  • Platform play from day one → risky
  • Wedge → adjacent workflow → platform → keep

Target: 3-5 problem spaces survive.


Phase 4: Micro-Validation (Days 11-21)

For each surviving problem space, run one validation experiment. Not surveys. Not landing pages. Commitment tests.

Test A: The $100 deposit
Create a one-pager (Notion page, Carrd, PDF) describing:

  • The specific problem
  • The proposed solution (1-2 sentences)
  • Price (monthly or annual)
  • "Reserve your spot with $100 fully refundable deposit — first 10 get 50% off lifetime"

Send to 20-30 target buyers (from your network, cold email, warm intros). Track:

  • Who clicks
  • Who replies
  • Who pays

Threshold: 3+ deposits from strangers (not friends) = signal. 0-1 = kill or pivot problem space.

Test B: The manual service
Sell the outcome before the software.

  • "I'll manually compile your subcont

Start here

Top comments (0)