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 Looking for Problems Worth Solving

Opportunity Discovery: A Practical Guide for When You're Stuck Looking for Problems Worth Solving

The Problem in Concrete Terms

You're not "waiting for inspiration." You're staring at a blank page, a half-full notebook, or a Trello board full of ideas that all feel either too small, too crowded, or too vague to pursue. You've read the advice: "scratch your own itch," "talk to customers," "look for complaints on Reddit." You've tried them. The itch you have is either already solved or too niche. Customer conversations devolve into polite feature requests for things that already exist. Reddit threads are noise—people complaining about pricing, not missing solutions.

The concrete reality: you have limited time, limited capital, and a need to pick a direction this month. You don't need more ideas. You need a filter that tells you which ideas are worth the next 90 days of your life. You're stuck because every framework you've found either produces too many candidates (paralysis) or filters out everything (despair).


Why the Usual Fixes Fail

1. "Scratch your own itch" assumes your problems are representative. They rarely are. Your workflow, budget, and tolerance for friction are outliers. Building for yourself often produces a tool you love that 47 other people need.

2. "Talk to 50 customers" without a hypothesis wastes everyone's time. You ask open-ended questions. People give polite, unfocused answers. You hear "it would be nice if..." and mistake it for "I'll pay for..." You leave with 50 feature requests and zero conviction.

3. Mining forums for complaints surfaces symptoms, not root causes. A thread about "Jira is slow" doesn't tell you whether the opportunity is a faster Jira, a lighter alternative, a plugin, or a workflow change. You build a painkiller for a symptom that disappears when the underlying process changes.

4. Trend-chasing (AI, Web3, no-code) confuses market motion with opportunity. A rising tide lifts all boats, but it also drowns the ones with holes. Jumping on a trend without a specific, defensible wedge means you're competing on hype cycles, not value.

5. Idea validation checklists (landing pages, waitlists, smoke tests) test interest, not viability. People click "notify me" for free things they'll never pay for. A 10% conversion on a free waitlist predicts nothing about a $200/month B2B tool.


Step-by-Step Solution: The Opportunity Filter

This process takes 2–3 weeks part-time. It produces 1–3 opportunities you can validate with real money, not emails. Do each step in order. Skip nothing.

Week 1: Define Your Constraints First (Days 1–3)

Before looking outward, lock down your inward reality. Write answers to these. No aspirational answers—only what's true today.

Constraint Your Answer
Capital available (cash you can lose without lifestyle change) $______
Time available per week (consistent, uninterrupted hours) ______ hrs
Technical skills you can apply *without learning new stacks* List: ______
Distribution advantages (audience, network, platform access, SEO assets) List: ______
Minimum viable revenue to continue at 3 months $______/mo
Deal-breakers (industries you won't touch, business models you hate, team requirements) List: ______

Why this works: Most people filter ideas after generating them. Filtering before eliminates 80% of dead ends instantly. If you have $2k, 10 hrs/week, no audience, and need $5k/mo in 90 days, you cannot pursue enterprise sales, hardware, or content plays. That clarity is worth more than 100 brainstorming sessions.

Output: A one-page "Constraint Card." Keep it visible. Every idea must pass it.


Week 1–2: Source Candidates from Structured Observation (Days 4–10)

Don't brainstorm. Observe. Use these three sources only. Each produces a different type of opportunity.

Source A: Workflow Shadows (B2B/Prosumer)

Pick 3–5 roles you can access (friends, former colleagues, LinkedIn 2nd-degree). Ask for a 45-minute screen share: "Show me the most annoying 30 minutes of your typical week. Narrate what you're doing and why it sucks."

Rules:

  • No questions about "problems" or "tools." Watch the work.
  • Note every: manual copy-paste, spreadsheet bridge, screenshot-to-email, "I export to CSV then...", "I check three dashboards to...", "I ask someone in Slack for..."
  • Record the frequency (daily/weekly/monthly) and stakes (what breaks if this goes wrong?).

Output: 15–25 observed friction points. Tag each: [High Freq + High Stakes], [High Freq + Low Stakes], [Low Freq + High Stakes]. Discard Low/Low.

Source B: Purchase Decision Autopsies (B2B/B2C)

Find 5–10 people who recently bought a tool in a category you understand (CRM, design, devops, finance, fitness, learning). Ask: "Walk me through the day you decided to buy. What happened that morning?"

Rules:

  • Focus on the trigger event, not the evaluation.
  • Note: what broke, what changed, what deadline appeared, what boss/client demanded.
  • Ask: "What did you try first that didn't work?" (free tier, spreadsheet, competitor, hiring).

Output: 5–10 trigger patterns. Group by trigger type: [Compliance/Regulatory], [Scale Break], [New Role/Team], [Tool Death/Sunset], [Budget Unlock].

Source C: Adjacent Market Gaps (Platform/Extension)

List 3–5 platforms you know well (Shopify, Salesforce, Notion, Figma, AWS, Webflow, HubSpot, Jira). For each, search the marketplace/app store for:

  • Categories with >50 listings but <5 reviews average (underserved, fragmented)
  • Categories with 1–2 dominant players charging >$200/mo and >30% negative reviews mentioning the same missing feature
  • "Free" tools with 10k+ installs and no paid upgrade path (monetization gap)

Output: 3–5 platform-specific wedges with evidence of demand and weak incumbents.


Week 2: Apply the Viability Filter (Days 11–14)

Take every candidate from Sources A, B, C. Run each through this filter. Be ruthless. Kill 90%.

Filter Question Pass Criteria Evidence Required
Does it fit my Constraint Card? Yes on all 6 constraints Direct mapping
Is the trigger urgent and recurring? Trigger happens ≥monthly, stakes = revenue loss / compliance risk / customer churn Source B autopsy or Source A frequency+stakes tag
Is the current workaround painful and expensive? Workaround costs ≥10 hrs/mo OR ≥$200/mo in labor/tools Source A observation + rough calc
Can I reach the buyer without cold outreach? You have 1st/2nd-degree access to ≥10 buyers OR SEO/keyword path with <30 KD LinkedIn search + Ahrefs/SEMrush trial
Is the wedge narrow enough to build in 6 weeks? Core value = 1 workflow, ≤3 screens, ≤2 integrations Technical sketch
Can I charge ≥$50/mo (B2B) or ≥$15/mo (B2C) for the wedge alone? Comparable tools charge this for less scope Pricing page screenshots

Scoring: Each candidate gets 0–6. Keep only score ≥5. You'll have 1–3 left. If zero, repeat Week 1–2 with new sources. Do not lower the bar.


Week 3: Pre-Sell the Wedge (Days 15–21)

For each surviving candidate, do this before writing code.

1. Write the One-Pager

One page. Sections:

  • Trigger: "When [role] experiences [trigger event]..."
  • Current Workaround: "They currently [manual

Start here

Top comments (0)