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 abstract because most advice treats it like lightning striking. It isn't. It is forensic work.
Concretely, being stuck looks like one of three states:
- The "Shiny Object" Loop: You have five Notion pages, three domain names registered, and zero paying customers. You switch projects every Monday because the previous one "didn't feel right" after you hit the first technical snag or cold email rejection.
- The "Market Research" Trap: You have read 40 industry reports, scraped Crunchbase, and built a competitor matrix in Airtable. You know the TAM, SAM, and SOM for three verticals. You have not spoken to a single human who actually has the problem.
- The "Scratch Your Own Itch" Dead End: You built a tool for a problem you had. You use it daily. You launched on Product Hunt. You got 200 upvotes and 3 signups. Nobody else has the problem quite the way you do, or they solve it with a spreadsheet and don't care enough to switch.
In all three cases, the symptom is the same: You are optimizing for certainty before you have evidence. You are trying to pick the "winner" before you have played the game.
Why the Usual Fixes Fail
1. "Just start talking to customers."
This is the standard Y Combinator advice. It fails because who do you call? If you don't have a hypothesis about a specific person with a specific burning problem, "talking to customers" becomes "having coffee with friendly people who tell you your idea is cool." That is validation theater, not discovery.
2. "Look for problems in communities (Reddit, IndieHackers, Twitter)."
You scroll r/SaaS or r/smallbusiness looking for "pain points." You find complaints like "I hate taxes" or "Hiring is hard." These are categories, not opportunities. They are too broad to build for, too competitive to enter without a wedge, and usually represent problems people complain about but won't pay to solve differently.
3. "Analyze trends and ride the wave."
AI wrappers, Web3, No-code, Remote work tooling. By the time a trend is legible enough for you to spot it in a report or newsletter, the low-hanging fruit is gone. You are entering a red ocean with a plastic spoon.
4. "Build an audience first."
Writing LinkedIn threads for six months to "build trust" before you know what you are selling is a marketing strategy, not a discovery strategy. It delays the moment of truth: does anyone need this badly enough to hand over a credit card?
Step-by-Step Solution: The "Wedge Hunt" Protocol
This process assumes you have zero starting advantages (no audience, no proprietary data, no unfair distribution). It optimizes for speed to evidence, not speed to launch.
Phase 1: Constraint Your Surface Area (Days 1–2)
Do not brainstorm. Filter.
-
Define your "Unfair Advantage" inventory (brutal honesty only).
- List specific technical skills (e.g., "React + Postgres," not "coding").
- List specific domain access (e.g., "My brother runs a 50-truck logistics fleet," not "I know logistics").
- List specific distribution channels you currently control (e.g., "Newsletter with 2k HVAC owners," not "I'm good at Twitter").
- Discard everything generic. If you don't have a specific edge, your edge is speed and pain tolerance. Accept that.
-
Pick one constraint vector to hunt within.
- Vector A: Technical. "I can build complex data pipelines fast." -> Hunt for data-heavy, messy problems in boring industries.
- Vector B: Access. "I have access to dental practice managers." -> Hunt for problems only dental practice managers have.
- Vector C: Capital/Time. "I have 6 months runway and $5k." -> Hunt for problems solvable with a 4-week MVP and $500 ad spend.
- Action: Write your chosen vector at the top of a blank document. Every idea that doesn't fit the vector gets deleted immediately. This prevents the Shiny Object Loop.
Phase 2: The "Expensive Problem" Audit (Days 3–7)
Stop looking for "problems." Look for expensive workflows.
- Identify the target role. Not "SMBs." Not "Marketers." Specific title. "Operations Manager at 20-50 person commercial construction firms."
- Map their "Money Hours." What 3–5 activities consume their week where:
- The output directly touches revenue or compliance (high stakes).
- The process is manual, spreadsheet-based, or involves stitching 3+ tools (high friction).
- Errors are costly (high fear).
- Find the "Shadow IT." Ask (or observe): "What is the ugliest spreadsheet/Access DB/Notion hack you maintain that would get you fired if it broke?"
- That spreadsheet is the spec for your V1.
- Quantify the cost.
- Time cost: Hours/week × Hourly loaded cost.
- Error cost: Frequency × Cost per error (rework, fines, lost client).
- Opportunity cost: What aren't they doing because they are doing this?
- Threshold: If the total annual cost < $10k–$15k per seat, discard. It’s a vitamin, not a painkiller. You need a problem worth $500+/month per user to build a sustainable B2B business without venture scale.
Phase 3: The "Cold Truth" Outreach (Days 8–14)
You need 5 conversations with the exact title you mapped. Not founders. Not friends. The end user or the budget holder.
The Script (Do not pitch. Do not mention your solution).
Subject: Question about [Specific Workflow, e.g., "change order tracking"]
Hi [Name],
I’m researching how [Specific Role, e.g., "Project Managers at commercial GCs"] handle [Specific Workflow] right now. I’m not selling anything—I’m trying to understand if the way I see people doing it (mostly spreadsheets/email) is actually how it works on the ground.
Do you have 10 minutes this week for me to ask 5 specific questions about your current process?
Thanks,
[Your Name]
The 5 Questions (Memorize these. Do not improvise).
- "Walk me through the last time you did [Workflow] start to finish." (Listen for steps, tools, handoffs).
- "Where does it usually break or slow down?" (Listen for emotion: "It's a nightmare," "I hate...").
- "What happens when it breaks? What is the downstream cost?" (Quantify the pain).
- "How are you solving it today? What have you tried buying/building?" (Reveals budget, urgency, competition).
- "If you could wave a magic wand and fix one step instantly, what would it be?" (Reveals the wedge feature).
The Stop Rule:
- If 3/5 say "It's annoying but we manage," Kill the vector. Return to Phase 1.
- If 3/5 describe a specific, costly, active workaround (hiring a temp, paying a consultant, massive spreadsheet), Proceed. You have a wedge.
Phase 4: The "Concierge MVP" (Days 15–30)
Do not write code. Sell the manual service.
- Define the "Done" state. What does the output look like? A report? A clean dataset? A scheduled calendar? A filed compliance doc?
- Price it. Charge 50–75% of the calculated annual cost / 12. If the problem costs them $2k/mo, charge $1k/mo.
- Get 3 Letters of Intent (LOIs) or Pre-payments.
- An LOI is a signed email: "If you build [Specific Output] meeting [Specific Criteria] for $[Price]/mo, we will sign a 12-month contract."
- Pre-payment is better: