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 skills to build things. You have time (or you're making time). But every idea you come up with feels either too small to matter, too crowded to enter, or too vague to start. You've read about "finding problems worth solving" but when you sit down to actually do it, you stare at a blank page.

This isn't writer's block. It's a process gap.

Concrete symptoms:

  • You maintain a notes app with 47 half-baked ideas, none developed past a sentence
  • You've built three side projects that nobody uses because you didn't verify demand first
  • You spend hours on Product Hunt, Indie Hackers, or Reddit "looking for inspiration" but leave feeling more paralyzed
  • You can't articulate who specifically would pay for your idea, how much, or why they'd switch from what they're doing now
  • You oscillate between "this is too competitive" and "nobody's doing this so maybe it's not a real problem"

The core issue: you're treating opportunity discovery as a creative act instead of a research discipline. You're waiting for a lightning strike instead of running a systematic search.


Why the Usual Fixes Fail

1. "Scratch your own itch"
Works only if your itch is shared by enough people with budget to solve it. Most personal itches are either too niche (you're the only one) or already solved (you just haven't found the solution). Building for yourself without validating the market size is a hobby, not a business.

2. "Talk to customers"
Generic advice. Talk to which customers? About what? Cold outreach to strangers without a specific hypothesis gets you polite non-answers. People lie about future behavior. They overstate pain. They understate switching costs. Without a structured interview framework, you collect noise, not signal.

3. "Look for complaints on Reddit/Twitter/forums"
You find complaints, not opportunities. A complaint is a symptom. The opportunity is the underlying workflow break, the budget owner, the switching trigger. Most complaints are about free tools, minor annoyances, or problems the complainer won't pay to fix. You waste weeks mining signal from noise.

4. "Follow trends" (AI, Web3, no-code, etc.)
By the time a trend is visible, the easy opportunities are taken. You're competing with funded teams and experienced founders. Trend-chasing also produces me-too products with no defensible position.

5. "Build an audience first"
Audience-building is a separate skill set from product discovery. You can spend 12 months growing a newsletter only to realize your subscribers are hobbyists with no budget. The audience becomes a constraint—you build what they'll cheer for, not what they'll pay for.


Step-by-Step Solution

Phase 1: Define Your Search Space (Week 1)

1.1 List your unfair advantages
Write down every asset you bring: technical domains (e.g., "distributed systems," "computer vision"), industry knowledge (e.g., "dental practice workflows," "freight forwarding"), network access (e.g., "I know 15 VP Engineers," "my spouse runs a logistics company"), audience (even 500 engaged followers counts), capital, time, location, certifications. Be specific. "I know Python" is useless. "I've built three production RAG systems for legal document review" is an advantage.

1.2 Define your constraints
Minimum viable revenue target? Hours per week? Runway? Team or solo? Willingness to do sales? Technical complexity ceiling? Regulatory tolerance? Write these down. They filter opportunities faster than any framework.

1.3 Pick 3-5 verticals to investigate
Cross-reference advantages with constraints. If you know dental software and have 10 hours/week, don't investigate enterprise security compliance (long sales cycles, high complexity). Do investigate: dental lab communication tools, insurance claim automation for small practices, patient retention systems for multi-location groups.

Output: A one-page document with advantages, constraints, and 3-5 verticals. This is your search mandate.


Phase 2: Map the Workflow, Not the Market (Weeks 2-3)

For each vertical, do this:

2.1 Find 5-10 practitioners
Not founders. Not buyers. The people doing the work daily. Use LinkedIn Sales Navigator, Apollo, or manual search. Title examples: "Senior Dental Hygienist," "Freight Operations Manager," "Clinical Trial Coordinator." Message template:

"Hi [Name], I'm researching how [specific role] handle [specific workflow, e.g., 'insurance claim denials' or 'vendor onboarding']. Not selling anything—just 15 minutes to understand your actual process. Happy to share what I learn across the 10 people I'm talking to."

Book 5 calls per vertical. Pay for their time if needed ($50-100 gift card).

2.2 Run structured workflow interviews
Do not ask about problems. Ask about the workflow. Use this script:

  1. "Walk me through [workflow] from start to finish. What tools, people, and steps are involved?"
  2. "Where does the work pile up? Where do things break, get delayed, or require manual cleanup?"
  3. "When that break happens, what do you do today? Workaround? Spreadsheet? Phone call?"
  4. "Who feels the pain of that break? Who gets blamed? Who loses money?"
  5. "Has anyone tried to fix this? What happened?"
  6. "If this break disappeared tomorrow, what would change for you? For your boss? For the company?"

Record. Transcribe (Otter, Fireflies). Take notes on: frequency of break, cost of break (time, money, risk), current workaround, budget owner, decision maker.

2.3 Build a workflow map per vertical
One diagram per vertical. Boxes = steps. Arrows = handoffs. Red stars = breaks. Annotate each break with: frequency, cost, current workaround, who cares, budget owner.


Phase 3: Score and Filter (Week 4)

3.1 Score each break on 5 dimensions (1-5 scale)

Dimension 1 3 5
Frequency Monthly Weekly Daily/hourly
Cost per occurrence <$10 $10-100 >$100
Workaround pain Minor annoyance Significant time sink Blocks critical path
Budget clarity No owner / no budget Owner exists, budget unclear Clear owner, recurring budget
Switching trigger "Nice to have" "We're evaluating" "Contract up / crisis / mandate"

3.2 Apply your constraint filter
Eliminate any break that violates your constraints (e.g., requires 6-month sales cycle when you have 3 months runway).

3.3 Select top 2-3 opportunities
You should now have 2-3 specific breaks with scores, workflow context, and identified budget owners. Each should be describable in one sentence: "Dental practices lose $3-5K/month on denied claims because hygienists document procedures in language that doesn't map to CDT codes, and the office manager spends 15 hrs/week rewriting notes before submission."


Phase 4: Validate Willingness to Pay (Weeks 5-6)

4.1 Create a one-pager per opportunity
Not a pitch deck. A problem statement document:

  • The break (specific, quantified)
  • Current workaround and its cost
  • Who owns the budget
  • Your proposed solution concept (2-3 sentences)
  • Price anchor (e.g., "$200/month per location")
  • Ask: "Would you commit to a pilot at this price if we solve [specific break]?"

4.2 Get 5 commitments per opportunity
Return to your interviewees + 5 new prospects per opportunity. Send the one-pager. Book 15-minute calls. Ask directly: "If this existed today at $X, would you sign a 3-month pilot?" Track: hard yes (will sign LOI), soft yes (interested, needs approval), no (and why).

4.3 Decision rule
Proceed only if: ≥3 hard yes OR ≥2 hard yes + ≥2 soft yes with clear path to approval. Otherwise, return to Phase 2 with a new vertical or deeper workflow mapping.


Phase 5: Build the Smallest Testable System (Weeks 7-10)

5.1 Define the minimum viable workflow
Not MVP. The smallest slice that eliminates the break for one user in one context. For the dental claims example: a Chrome extension that sits on the claim submission page, suggests CDT codes based on procedure

Start here

Top comments (0)