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

Opportunity Discovery: A Practical Guide for When You're Stuck

The Problem in Concrete Terms

You're sitting at your desk with a notebook full of half-baked ideas, or worse—a blank page. You know you want to build something, start something, or pivot your current work. But every direction feels either obvious and crowded, or vague and risky. You've read about "finding your niche" and "scratching your own itch," but your itches are either too small to sustain a business or too weird to explain to anyone else.

The stuckness shows up in specific ways:

  • You've interviewed five potential users and heard "that's nice" but no one will pre-pay or commit time
  • You've built three MVPs that got zero traction because you were solving problems people didn't actually prioritize
  • You spend weeks researching markets only to talk yourself out of every direction before writing a line of code
  • You have a full-time job and 10 hours a week—you can't afford to chase dead ends
  • You keep seeing other people execute on ideas you had two years ago

The core issue isn't creativity. It's that you're treating opportunity discovery as a lightning-strike event instead of a systematic process with checkpoints.


Why the Usual Fixes Fail

Customer interviews without a hypothesis. Talking to people is good. Talking to people without a specific, falsifiable belief about their behavior is therapy—for you, not them. You'll hear what they say they want, not what they'll pay for.

Keyword research and trend reports. These tell you where the crowd already is. By the time a trend shows up in Ahrefs or Gartner, the low-hanging fruit is gone. You're optimizing for last year's opportunity.

Scratching your own itch without validation. Your problem might be real, but it might also be too niche, too low-urgency, or solved well enough by a spreadsheet. Building for yourself is a starting hypothesis, not a free pass.

Competitor analysis paralysis. Studying competitors teaches you how to build a me-too product. It doesn't teach you where the gaps are—because the gaps are, by definition, what competitors aren't doing.

Waiting for "founder-market fit." This is a retroactive narrative. You discover fit by doing the work, not by meditating on your background.


Step-by-Step Solution

Phase 1: Map Your Constraints (Week 1)

Before looking outward, define your playing field. Write down honest answers to:

Time: How many focused hours per week can you consistently commit for the next 6 months? Not "ideal weeks"—real weeks with sick kids, crunch periods, and low energy.

Capital: How much can you invest without needing it back for 12–18 months? Include tooling, ads, contractors, and your own living expenses if you're quitting.

Skills: What can you actually build, sell, or operate right now? Not what you could learn. What you can ship in 4 weeks.

Network: Who do you know who buys or influences purchases in specific industries? List 20 names with their roles and companies.

Risk tolerance: What's the worst outcome you can absorb? Lost savings? Lost time? Reputation hit?

Unfair advantages: Access to data? Regulatory knowledge? A community? A distribution channel? Be specific.

Output: A one-page constraint document. This kills 80% of ideas before you waste time on them.


Phase 2: Generate Problem Candidates (Weeks 2–3)

Don't brainstorm solutions. Collect problems with evidence. Use these four sources—each requires a different tactic.

Source A: Your Network (Highest Signal)

Message your 20 contacts from Phase 1. Not "what problems do you have?" Ask:

  • "What's the most annoying manual process your team does weekly?"
  • "What spreadsheet is running a critical part of your business?"
  • "What did you try to buy last year but couldn't find?"
  • "What vendor relationship frustrates you most?"

Record verbatim. Look for: frequency (daily/weekly), urgency (blocking revenue or compliance), and workaround cost (hours or dollars spent on duct tape).

Source B: Job Postings (Hidden Demand)

Search LinkedIn/Indeed for roles like "Operations Analyst," "Revenue Operations," "Technical Program Manager" in industries you can access. Read 50+ descriptions. Extract:

  • Tools they're required to use (reveals locked-in ecosystems)
  • Metrics they own (reveals what leadership measures)
  • "Nice to have" skills that appear repeatedly (reveals emerging gaps)

Cross-reference: if 10 companies want someone who can "automate Salesforce-to-Netsuite reconciliation," that's a problem pattern.

Source C: Support Forums & Review Sites (Unfiltered Pain)

Go to G2, Capterra, Reddit, Discord, Slack communities for tools in your target space. Filter for:

  • 2–3 star reviews of market leaders (1-star is usually broken; 5-star is happy; 2–3 is "works but...")
  • Feature requests with high upvotes that are 2+ years old
  • "How do I..." questions that get answered with Zapier/Make/Excel workarounds

Document the workaround. That's your prototype spec.

Source D: Adjacent Tool Ecosystems (Extension Opportunities)

List 10 tools your target users already pay for (CRM, ERP, design, analytics). For each:

  • Browse their marketplace/app store
  • Sort by "most reviewed" and "recently added"
  • Read negative reviews of top add-ons
  • Identify: what does the core tool do poorly that an add-on tries to fix?

Output: 30–50 problem candidates in a spreadsheet with columns: Problem, Evidence Source, Frequency, Urgency, Workaround Cost, Industry, Decision Maker, Your Access Level (0–3).


Phase 3: Score and Filter (Week 4)

Apply a ruthless scoring system. Each criterion 1–5:

Criterion Weight Why
Urgency (blocking revenue/compliance/daily pain) 3x Low urgency = no budget
Frequency (daily > weekly > monthly) 2x Infrequent = hard to build habit
Workaround Cost (hours × hourly rate or direct spend) 2x High cost = budget exists
Decision Maker Access (you can reach them directly) 3x No access = no sales
Build Feasibility (v1 in 4 weeks with your skills) 2x Over-scoping kills momentum
Market Size (TAM > $100M or clear expansion path) 1x Too small = hobby, not business
Competition Gap (no good solution, not "no solution") 2x Crowded = differentiation needed

Multiply score × weight. Top 3 problems advance. Kill the rest. Archive them—don't delete. You'll revisit in 6 months.


Phase 4: Validate with Skin in the Game (Weeks 5–8)

For each of your top 3 problems, run a 2-week validation sprint. Do them sequentially, not in parallel.

Week 1: Problem Confirmation

  • Find 10 people who match your decision-maker profile
  • Book 15-minute calls. Script:
    1. "I'm researching [problem]. Can you walk me through the last time you dealt with it?"
    2. "What did you do? What tools? How long did it take?"
    3. "What would you pay to make that take 10% of the time?"
    4. "If I built a tool that did [specific outcome], what would need to be true for you to try it?"
  • No pitching. No demos. Take notes. Record if permitted.

Pass criteria: 6/10 describe the same workflow, same pain, same workaround. 4/10 give a specific number or process for buying.

Week 2: Solution Simulation

Build the smallest possible demonstration of the core value prop. Not an MVP. A simulation:

  • Clickable Figma prototype for a workflow tool
  • Google Sheet + Apps Script for a data transformation
  • Manual service delivered via Loom video for an automation
  • Notion page + Calendly for a consulting product

Show it to the same 10 people (or 10 new ones). Ask: "This solves [problem] by [mechanism]. Would you pay $X/month for this? If yes, I'll send a Stripe link for a 3-month pilot at 50% off."

Pass criteria: 3/10 pay or sign a LOI with a defined start date.

If zero pass

Start here

Top comments (0)