Opportunity Discovery: A Practical Guide for When You're Stuck
The Problem in Concrete Terms
You have time, skills, and maybe even capital—but you cannot point to a specific, validated problem worth solving. Every idea feels either too small (a vitamin, not a painkiller), too crowded (ten funded competitors), or too vague ("people struggle with productivity"). You sit down to brainstorm and walk away with a list of features, not opportunities. The longer this goes on, the more you convince yourself that all the good problems are taken, or that you lack the "founder insight" everyone talks about.
This isn't writer's block. It's a process gap. You're trying to have ideas instead of finding them.
Why the Usual Fixes Fail
1. "Scratch your own itch" works only if your itch is shared by a reachable market willing to pay. Most personal itches are either too niche (you're the only one) or too generic (everyone has a todo app).
2. "Talk to customers" fails when you don't know who the customer is or what to ask. Cold outreach without a hypothesis gets ignored. Conversations without structure produce noise, not signal.
3. "Look at trending topics" (Product Hunt, Hacker News, Twitter) shows you what launched, not what works. Survivorship bias hides the graveyard. By the time a trend is visible, the low-hanging fruit is gone.
4. "Pick a big market and find a wedge" sounds strategic but usually leads to analysis paralysis. You spend weeks modeling TAM/SAM/SOM for markets you don't understand, then pick a wedge based on guesswork.
5. "Wait for inspiration" is not a strategy. It's procrastination dressed in mystique.
Step-by-Step Solution
Phase 1: Define Your Constraints (Day 1)
Before hunting, decide what you're actually willing to build. Constraints focus search; freedom paralyzes it.
Write down your non-negotiables:
- Time horizon: How long before you need revenue? (3 months? 12? 36?)
- Capital: Bootstrapped? Savings runway? Willing to raise?
- Team: Solo? Co-founder? Can you hire contractors?
- Technical depth: Code yourself? No-code? Need to hire devs?
- Domain interest: Industries you'll enjoy for 3+ years. Industries you'll hate.
- Distribution advantage: Existing audience? Network in a vertical? SEO skills? Paid ads experience?
Example constraint set: "Solo founder, 6 months runway, can code React/Node, no audience, prefer B2B SaaS, hate consumer apps, have network in logistics from previous job."
Keep this visible. Every opportunity gets filtered through it.
Phase 2: Map Your Access Vectors (Days 2–3)
Opportunities are discovered through people. You find problems by talking to people who have them. List every vector you have to reach potential buyers.
Create a spreadsheet with columns:
| Vector | Specific Contacts | Access Level | Vertical/Role | Last Contact |
|--------|-------------------|--------------|---------------|--------------|
| Former coworkers | 12 people | Direct Slack/email | Logistics, ops, engineering | 2023 |
| LinkedIn 2nd-degree | ~200 | Warm intro possible | Supply chain, warehousing | Never |
| Industry Slack/Discord | 3 communities | Member | Freight tech, 3PL | Active |
| Conference contacts | 8 people | Email | WMS vendors, shippers | 2022 |
| Cold email list | 0 | None | Need to build | N/A |
Action: Pick the top 3 vectors by access level × relevance to constraints. Ignore the rest for now.
Phase 3: Run Structured Discovery Conversations (Days 4–20)
Don't "chat." Run 20-minute interviews with a fixed script. Goal: find a recurring, urgent, expensive problem your constraints can address.
The Script (memorize this flow):
- Context (2 min): "What's your role? Walk me through a typical week."
- Current workflow (5 min): "Show me how you handle [process relevant to vertical] today. What tools? What people?"
- Pain isolation (8 min): "What's the most frustrating part? How often does it happen? What happens when it breaks? What have you tried to fix it? How much does it cost you—time, money, reputation?"
- Buying signal (3 min): "If a tool solved [specific pain], what would need to be true for you to pay for it? Who else signs off? What's your budget process?"
- Referral (2 min): "Who else should I talk to who feels this acutely?"
Rules:
- Record (with permission). Take notes after, not during.
- Zero pitching. Zero feature ideas. You are a journalist.
- Stop when you hear the same specific pain from 3+ people who don't know each other.
- If 5 conversations yield no recurring pain, change your vector or vertical. Pivot the search, not the idea.
Output after each call: One-line problem statement in the interviewee's words. Example: "We lose $40k/quarter because our WMS can't auto-split shipments across 3PLs when inventory is fragmented."
Phase 4: Validate Willingness to Pay (Days 21–35)
A problem isn't an opportunity until someone commits resources to solve it.
Step 1: The "Concierge" Test
Pick the top 2 problem statements. For each, design a manual service that solves it. No code. Spreadsheets, Zapier, phone calls, you doing the work.
Step 2: Price It
Charge 10–20% of the stated cost of the problem. If they say "we lose $40k/quarter," charge $1k–2k/month.
Step 3: Sell to Your Interviewees
Email the 3+ people who described the problem:
"I'm building a done-for-you service that handles [specific pain]. It costs $X/mo, saves ~$Y. I'm taking 3 pilot clients this month. Interested in a 15-min walkthrough?"
Step 4: Collect Commitments
- Strong signal: Signed agreement + payment (even $100 deposit).
- Medium signal: "Yes, send contract" + intro to decision-maker.
- Weak signal: "Sounds interesting, keep me posted."
- Noise: "Cool idea!" with no next step.
Decision rule: 2+ strong signals = build the product. 2+ medium = run another 5 discovery calls on same problem. Else = discard, return to Phase 3.
Phase 5: Build the Minimum Sellable Product (Days 36–60)
You have paying pilot customers. Now automate only what they use daily.
Scope ruthlessly:
- List every manual step in your concierge delivery.
- Mark each: "Automate now" (used daily, high error risk) vs. "Keep manual" (weekly, judgment-heavy, low volume).
- Build only "Automate now" items.
- Ship to pilots weekly. Get feedback on workflow fit, not features.
Do not build: Admin dashboards, settings pages, onboarding flows, integrations "for later," multi-tenant architecture.
Do build: The core logic that replaces your manual work. A way for pilots to trigger it. Basic logging so you see failures.
Phase 6: Expand From Pilots to Market (Days 61–90)
Week 1–2: Onboard 3–5 more customers from referral chain. Same price. Same manual+automated mix.
Week 3–4: Raise price 20–50% for new customers. Test resistance.
Week 5–6: Document the exact onboarding steps that worked. Turn into a checklist. This becomes your sales process.
Week 7–8: Build only the feature that unblocks the next 3 deals. Ignore everything else.
Week 9–10: Write 3 case studies with numbers. "Client X reduced split-shipment errors from 12% to 0.8%, saving $38k/qtr." Use these in cold outreach.
Checklist
- [ ] Constraints document written and visible
- [ ] Access vector spreadsheet completed, top 3 selected
- [ ] 15+ discovery calls conducted
Top comments (0)