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. You have a Notion page, a Trello board, or a notes app folder labeled "Ideas" that contains 47 entries ranging from "Uber for dog walking" to "B2B SaaS for dental supply chain logistics." None of them feel right.
The stuckness isn't confusion. It’s selection paralysis masked as discovery.
You sit down to "find an opportunity." You open Google Trends. You scroll Twitter/X for "pain points." You read Indie Hackers posts titled "How I made $10k MRR in 30 days." You feel productive. You are not. You are consuming other people’s finished movies while trying to write your own script.
Concretely, the problem looks like this:
- The Filter is Broken: You evaluate ideas against vague criteria ("big market," "passive income," "exciting") instead of hard constraints ("I can build this in 6 weeks," "I know 10 buyers," "Margin > 70%").
- The Source is Wrong: You look outward for signals (markets, trends, keywords) instead of inward for assets (access, skills, unfair advantages, specific annoyances you personally endure).
- The Stakes are Imaginary: You treat every idea like a lifelong marriage decision. You try to validate the business before you’ve validated the problem. You build landing pages for problems nobody has, or worse, problems you can’t actually solve.
You are stuck because you are playing "Entrepreneur Simulator" instead of doing the grunt work of finding a specific person with a specific bleeding neck wound you can reach and treat.
Why the Usual Fixes Fail
1. "Scratch Your Own Itch" (Without the Second Half)
The advice is usually "build what you need." The failure mode: you build a tool for a problem you used to have, or a problem you have now but only because of your specific weird workflow. You lack the distribution channel to reach others like you. You end up with a custom script, not a product.
2. Keyword Research / SEO Gap Analysis
This finds demand, not opportunity. It tells you what people search for. It does not tell you what they will pay for, what they are frustrated by, or if you can actually deliver the solution. High volume, low difficulty keywords are often low intent or dominated by aggregators you cannot beat.
3. "Talk to Customers" (Generic Edition)
You book 15 calls. You ask: "What's your biggest challenge?" They say: "Time management." You build a to-do list app. They don't buy.
Why? Because "talking to customers" without a hypothesis and a specific profile is just socializing. You need to talk to one specific type of person about one specific workflow where money is already changing hands or time is actively being wasted.
4. Trend Surfing (AI, Web3, No-Code, etc.)
By the time a trend is a hashtag, the alpha is gone. Building on a platform trend (e.g., "GPT wrapper for X") makes you a feature, not a business. Platform risk eats your lunch. You are competing with the platform vendor and 10,000 other wrappers.
5. The "Idea Validation" Theater
Building a landing page, running $50 in cold traffic, getting 3 emails, and calling it "validated." This validates curiosity, not willingness to pay. It wastes 2 weeks you could have spent finding a real lead.
Step-by-Step Solution: The Asset-Led Discovery Loop
Stop looking for ideas. Start auditing assets. An opportunity is just an intersection between what you uniquely control and what someone urgently needs.
Phase 1: The Asset Audit (Days 1–2)
Do not brainstorm. Inventory. Open a spreadsheet. Create four tabs.
Tab A: Access (Who trusts you?)
List every person you can message right now who would reply within 24 hours.
- Former coworkers (group by industry/role).
- Past clients.
- Niche community mods/admins you know.
- Friends in specific verticals (construction, logistics, dental, B2B sales, etc.).
- Constraint: Only list people where you know what they do daily. "My friend works in tech" is useless. "Sarah, VP Ops at 200-person logistics co" is gold.
Tab B: Competence (What can you build/do fast?)
List specific technical or operational capabilities you can execute without learning a new framework.
- "Python data pipelines," not "AI."
- "Webflow + Airtable + Make," not "No-code."
- "Cold email infrastructure setup," not "Sales."
- "Technical SEO audits," not "Marketing."
- Be ruthless. If it takes 2 weeks to ramp, cross it off.
Tab C: Domain Scars (Where have you bled?)
List specific, painful, repetitive workflows you have personally executed or watched up close for > 6 months.
- Not "HR is hard." → "Onboarding 50 seasonal warehouse workers using Google Forms and a shared drive is a nightmare of compliance errors."
- Not "DevOps is annoying." → "Managing secrets rotation across 12 microservices on AWS ECS with manual Terraform runs."
Tab D: Capital/Time Constraints (Your Real Boundaries)
- Cash you can burn: $____
- Hours/week you can actually commit: ____
- Runway before you must have revenue: ____
- Skills you refuse to learn (e.g., "I will not do video sales," "I will not manage contractors").
Phase 2: Intersection Mapping (Day 3)
Cross-reference Tabs A, B, and C. You are looking for: Access + Competence + Scar.
- Example: You know Sarah (VP Ops, Logistics) [Tab A]. You build Webflow/Airtable tools fast [Tab B]. You watched a freight brokerage drown in manual rate confirmation emails [Tab C].
- Intersection: Automated rate confirmation parsing + Airtable dashboard for Sarah’s team.
Discard any intersection missing a leg.
- Access + Competence, no Scar? Solution looking for a problem.
- Competence + Scar, no Access? You can build it, but can’t sell it. (Cold outreach is a different skill; do not assume you have it).
- Access + Scar, no Competence? You’re a consultant, not a product founder. (Valid path, but different guide).
Pick three intersections max. Rank them by: Severity of Scar × Speed to MVP × Access Warmth.
Phase 3: The "Ugly First Draft" Validation (Days 4–10)
Do not build. Do not make a landing page. Sell the workflow.
Step 3.1: Write the "Pain Hypothesis" Doc (1 page).
For your top intersection, write:
- Persona: Specific title, company size, tech stack (e.g., "Freight Brokerage Ops Manager, 10–50 employees, using Gmail + Rose Rocket TMS").
- Current Workflow: Step-by-step, screenshots if possible. Where does the human touch the keyboard unnecessarily?
- The Cost: Time * Hourly Rate + Error Rate * Cost of Error. (e.g., "3 hrs/day × $30/hr × 5 people = $2,250/mo wasted + 2% error rate on $1M revenue = $20k risk").
- Proposed Workflow: What changes specifically? "Email parser dumps structured JSON → Airtable → One-click 'Confirm' button → Auto-reply to carrier."
- Price Anchor: "We charge $X/mo per seat / per transaction." Pick a number. Defend it.
Step 3.2: The "Concierge" Pitch (Send to Tab A contacts).
Message your 3–5 best contacts from Tab A individually. No mass DMs.
*"Hey [Name], I’m building a very specific internal tool for [Persona] to automate [Specific Painful Step]. It’s ugly, manual on my end right now (I run the script, you get the result), but it cuts [Time/Cost] by [X%]. I need 3 design partners to use it free for 30 days in exchange for brutal feedback. You’re the exact person I had in mind. Open to a
Top comments (0)