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 listing problems you encounter daily, but they're either trivial (better coffee cup lids) or massive systemic issues you can't touch (healthcare costs).

The stuckness shows up in specific ways:

  • You maintain a Notion page of "ideas" that hasn't yielded a single viable candidate in months
  • You can argue both sides of any opportunity: "too competitive" vs. "validated market," "too niche" vs. "focused beachhead"
  • You've built three MVPs that nobody used because the problem wasn't urgent enough
  • You spend more time researching markets than talking to potential customers
  • Every framework (Jobs-to-be-Done, Wardley Mapping, Blue Ocean) feels useful in the abstract but paralyzing in practice

The core issue isn't creativity—it's that you're trying to find opportunities instead of discovering them through a repeatable process that produces evidence, not just hypotheses.


Why the Usual Fixes Fail

1. "Scratch your own itch" assumes your itches are representative. They rarely are. Your problems as a developer/designer/marketer are idiosyncratic. The market doesn't care about your workflow optimization.

2. "Look for complaints on Reddit/Twitter" surfaces noise, not demand. People complain about everything. Complaints ≠ willingness to pay. The loudest voices are often the least representative buyers.

3. "Analyze competitors and find gaps" leads to feature-chasing. You end up building "X but with Y feature" which is a positioning statement, not an opportunity. Competitors' customers are already satisfied enough not to switch for a single feature.

4. "Trend surfing" (AI, Web3, no-code) confuses waves with tides. Trends are visible to everyone. By the time you spot a trend in TechCrunch, the easy opportunities are gone. You're competing with funded teams who started six months earlier.

5. "Customer interviews" without a hypothesis waste everyone's time. Asking "what problems do you have?" gets you wishlists and vague frustrations. You need a specific enough hypothesis to recognize signal when you hear it.

6. Frameworks become procrastination tools. Wardley Mapping, Value Proposition Canvas, JTBD—they're analysis tools, not discovery tools. They organize what you already know. They don't generate new knowledge.


Step-by-Step Solution

Phase 1: Define Your Constraints (Days 1-2)

Before looking outward, define the box you're playing in. Write down non-negotiables:

Capital constraints: How much can you invest before revenue? $0? $5k? $50k? This eliminates entire categories (hardware, regulated industries, long sales cycles).

Time constraints: How many hours/week can you commit? 10? 40? This determines whether you can do enterprise sales (months) or need self-serve (days).

Skill constraints: What can you actually build, sell, and operate? Not "what could I learn." What can you ship in 4-6 weeks?

Distribution constraints: Do you have an audience, network, or channel advantage? If not, you need product-led growth or paid acquisition budget.

Outcome constraints: What does "worth it" look like? $5k/mo side project? $100k/yr lifestyle business? Venture-scale? Each requires different opportunity shapes.

Output: A one-page constraint document. Refer to it every time you evaluate an idea.


Phase 2: Hunt Where Evidence Lives (Days 3-14)

Stop brainstorming. Start collecting evidence of unmet demand. Focus on three sources:

A. Procurement Data (B2B)

If you're targeting businesses, find where money already flows:

  • Government contracts: USAspending.gov, SAM.gov, state procurement portals. Filter by NAICS code, award size, recency. Look for: recurring contracts, multiple vendors for same category, complaints in award justifications.
  • Corporate vendor lists: Many enterprises publish approved vendor directories. Cross-reference with job postings mentioning specific tools—they're paying for those tools.
  • RFP databases: BidNet, FindRFP, or industry-specific portals. Read the requirements. The gaps between what's requested and what's available = opportunity.

B. Workflow Observation (B2B/B2C)

Shadow 5-10 people in a target role for 2-3 hours each. Don't interview. Watch.

  • Record (with permission) their screen and narration
  • Note every: copy-paste between tools, manual spreadsheet, "I wish this...", workarounds, dropped tasks, complaints to colleagues
  • Pay attention to frequency and consequence. A daily 15-minute manual task with revenue impact > a weekly annoyance

C. Behavioral Exhaust (Digital)

Where people leave traces of unsolved problems:

  • Support forums: Zendesk, Intercom, GitHub Issues, Discourse. Search for: "workaround," "feature request," "how do I," "is there a way to." Filter by upvotes/engagement.
  • Marketplace reviews: G2, Capterra, Chrome Web Store, Shopify App Store, Heroku Elements. 2-3 star reviews of market leaders are gold—people paying but unhappy.
  • Freelance job boards: Upwork, Toptal, Gun.io. Recurring requests for custom scripts/integrations = productizable service = potential product.
  • API documentation changelogs: New endpoints often signal emerging use cases companies are building internally.

Output: A spreadsheet with columns: Source | Specific Problem | Frequency Observed | Evidence Quote/Link | Current Workaround | Willingness-to-Pay Signals | Your Constraint Fit (Y/N)


Phase 3: Filter Ruthlessly (Days 15-18)

Apply your constraint document. Kill anything that doesn't fit. Then apply these filters:

Urgency Filter: Is the problem active right now? "I'll need this next quarter" = not urgent. "I'm manually doing this today and it costs me $X/week" = urgent.

Frequency Filter: Daily > Weekly > Monthly. High frequency = habit formation potential = lower churn.

Consequence Filter: What happens if this isn't solved? Lost revenue? Compliance risk? Customer churn? Employee turnover? "Annoyance" is not a consequence.

Budget Filter: Who pays? Can you name the budget line item? "Marketing tools" > "productivity." If you can't identify the budget owner and line item, you don't have a B2B opportunity.

Switching Cost Filter: What's the cost to adopt your solution? Data migration? Retraining? Integration? If switching cost > 3x monthly price, you need a wedge strategy.

Your Advantage Filter: Why you? Distribution access? Technical capability? Domain expertise? Unique insight? If the answer is "I'll work harder," discard.

Output: 3-5 opportunities that survive all filters. Rank by: Urgency × Frequency × Consequence × Budget Clarity × Your Advantage.


Phase 4: Validate with Skin in the Game (Days 19-35)

Don't interview. Sell. Or at minimum, get concrete commitment.

For B2B:

  1. Build a one-pager: Problem, Solution, Price, Timeline, ROI calculator
  2. Identify 20-30 decision-makers (not users—budget holders)
  3. Cold email/LinkedIn: "I'm building X for [specific role]. It solves [specific problem] saving ~$Y/mo. Open to a 15-min call to show a mockup?"
  4. On the call: Show mockup, ask "If this existed at $Z/mo starting [date], would you put it on your team's budget?" Get a yes/no/timeline
  5. Threshold: 3/10 say "yes, here's my card/email for pilot" → proceed. 1-2 → iterate positioning. 0 → kill.

For B2C/Prosumer:

  1. Build a landing page with price, clear value prop, email capture
  2. Spend $100-300 on targeted ads (Meta/Google/Reddit) to your ICP
  3. Threshold: 3-5% email capture rate + >$0.50/email cost → proceed. Lower → iterate offer or kill.

For Productized Service (fastest path):

  1. Define a fixed-scope, fixed-price service solving the problem manually
  2. Sell 3

Start here

Top comments (0)