DEV Community

Alan Descure
Alan Descure

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

Opportunity Discovery: A Field Guide for When You’re Stuck Waiting for a Sign

Opportunity Discovery: A Field Guide for When You’re Stuck Waiting for a Sign

The Problem in Concrete Terms

You are not "lacking ideas." You are drowning in them, or you are paralyzed by the vacuum where they should be. Opportunity discovery—the act of finding a problem worth solving and a market willing to pay for the solution—feels stuck because you are treating it like a lightning strike instead of a supply chain.

Concretely, the stuck state looks like one of three loops:

  1. The Notebook Graveyard: You have 47 concepts in Notion, Obsidian, or a physical Moleskine. None have moved past "cool feature idea" in six months. You confuse ideation with discovery.
  2. The "Scratch Your Own Itch" Trap: You built a tool for a problem you had three years ago. You launched to crickets. You didn't realize your specific workflow was an outlier, not a market segment.
  3. The Research Rabbit Hole: You spend weeks reading Gartner reports, Reddit threads, and competitor pricing pages. You know the landscape perfectly but cannot pick a coordinate to land on. You mistake information gathering for validation.

The common denominator: You are waiting for certainty before you commit to action. Certainty does not exist in discovery. Only evidence does.


Why the Usual Fixes Fail

1. "Just talk to customers."
This advice assumes you know who the customer is and what to ask. If you are stuck, you likely have a vague hypothesis ("Small businesses need better invoicing") but no specific protocol. Cold outreach without a script yields polite non-answers ("Yeah, invoicing is annoying") that feel like validation but aren't.

2. "Build an MVP in a weekend."
This optimizes for building, not learning. If you build the wrong thing fast, you just have garbage code faster. Discovery requires throwing away hypotheses, not committing to them in React.

3. "Follow your passion."
Passion is a retention mechanic for execution, not a discovery mechanism for markets. Markets do not care about your passion. They care about urgent, expensive problems.

4. Keyword Research / SEO Audits.
These tell you what existing demand looks like. They are lagging indicators. Opportunity lives in the gap between what people search for and what they actually do—latent demand that has no keyword yet.


Step-by-Step Solution: The "Evidence Loop"

This process replaces "finding an idea" with "falsifying a hypothesis." It requires zero budget, no code, and no permission. It takes roughly 10–15 hours spread over two weeks.

Phase 1: Constraint Definition (Hours 1–2)

You cannot discover "opportunity" in the abstract. You discover an opportunity for a specific vehicle.

Action: Write your Vehicle Constraints on one page. Answer these four questions explicitly. Do not skip.

  • Capital: How much cash can you lose without lifestyle impact? ($0? $5k? $50k?)
  • Time: How many hours/week can you guarantee for 12 months? (Nights/weekends? 20hrs? Full-time?)
  • Unfair Advantage: What do you know/do/have access to that top 10% practitioners don't? (Network? Domain expertise? Data access? Distribution channel? Specific tech stack mastery?)
  • Anti-Goals: What do you refuse to do? (Sales calls? Manage contractors? Hardware? Regulated industries? Consumer support?)

Output: A filter. Every hypothesis must pass through this. If an idea requires $20k ad spend and you have $0, kill it. If it requires cold calling and you refuse sales, kill it.

Phase 2: Source "Expensive Problems," Not "Ideas" (Hours 3–6)

Ideas are solutions. Problems are opportunities. Go where people complain about money, time, or risk in the context of your constraints.

Action: Execute three distinct sourcing methods. Do not just read; extract verbatim quotes.

Source A: The "Job Switch" Interview (Highest Signal)
Find 3–5 people who recently (last 6 months) switched tools, vendors, or processes in a domain adjacent to your Unfair Advantage.

  • Recruit: "I'm researching how [Role] handles [Workflow]. Can I buy you 15 mins of coffee/Zoom to ask how you made the switch?"
  • Script:
    1. "Walk me through the day you decided the old way wasn't working."
    2. "What did you try first? Why did it fail?"
    3. "What does the new way cost (time/money/political capital)?"
    4. "What would make you switch again tomorrow?"
  • Capture: Exact language describing the Switching Trigger and the Cost of Inaction.

Source B: The "Procurement Trail" (B2B) / "Substitution Audit" (B2C)

  • B2B: Search site:gov "request for proposal" [your domain] or site:linkedin "evaluating vendors" [your domain]. Read the RFPs. The requirements list is the opportunity map. The "Nice to haves" are differentiation; the "Mandatories" are table stakes.
  • B2C: Go to Reddit/Forums. Search "alternative to [market leader]" or "how to [task] without [expensive tool]". Look for people cobbling together Airtable + Zapier + Notion + Sheets. That duct tape is the product spec.

Source C: The "Adjacent User" Shadow
Identify a role adjacent to your target user who feels the pain but lacks the budget/authority to buy current solutions.

  • Example: If targeting Enterprise Sales Directors (buyers), shadow Sales Development Reps (users). SDRs feel the CRM pain daily but can't buy Salesforce. They hack workarounds. Those workarounds reveal the actual workflow gaps the buyer ignores.

Output: A spreadsheet with columns: Source | Verbatim Quote | Stated Problem | Implied Cost (Time/$/Risk) | Current Workaround | Trigger Phrase.

Phase 3: Hypothesis Stacking (Hours 7–8)

Stop looking for The One. Stack 3–5 specific, falsifiable hypotheses derived only from your Phase 2 quotes.

Format: I believe [Specific Persona] experiences [Specific Pain] because [Root Cause from quotes]. They currently [Workaround]. They would pay [Price/Time] for [Specific Outcome] if [Condition].

Example (Bad): "Freelancers need better invoicing."
Example (Good): "I believe junior devs billing via Upwork experience revenue leakage from untracked context switching because Upwork's tracker only captures active window time. They currently manually reconstruct logs in spreadsheets Friday nights. They would pay $30/mo for automated, client-ready time reports if it integrates natively with Upwork's API without manual entry."

Constraint Check: Run each hypothesis against your Phase 1 Vehicle Constraints. Kill 2 immediately.

Phase 4: The "Currency Test" (Hours 9–14)

You do not have a business until someone risks currency (Money, Reputation, Time, Data). Preference is fake. Currency is real.

Test 1: The Problem Validation (Cost: $0, Time: 2 hrs)
Create a One-Pager (Notion page, Google Doc, Carrd). Headline: The specific pain. Subhead: The specific outcome. Body: 3 bullets on how (mechanism agnostic). CTA: "I have this problem. Email me when ready" + "I'd pay $X/mo for this" (radio buttons).

  • Distribution: Post only in the specific communities/Slacks/Discords where your Phase 2 sources live. DM the 5 people you interviewed. "Built a spec based on our chat. Does this match?"
  • Success Metric: 5 emails from strangers (not friends) + 3 "I'd pay" clicks at your target price.

Test 2: The Solution Simulation (Cost: $0–$50, Time: 4–8 hrs)
Do not build software. Build

Start here

Top comments (0)