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 have the capacity to build. You have time, maybe some savings, possibly technical skills or domain expertise. What you don't have is a clear signal on what to build. Every idea feels either too small to matter, too crowded to enter, or too vague to validate. You've probably:

  • Started a spreadsheet of ideas, then abandoned it because nothing felt "right"
  • Spent weeks researching markets only to conclude everything is saturated
  • Built a prototype for something you weren't convinced about, then lost momentum
  • Watched others launch things that seemed obvious in retrospect, wondering how they saw it
  • Cycled between "I need a big vision" and "I should just scratch my own itch" without committing to either

The stuckness isn't lack of creativity. It's that opportunity discovery is treated as a lightning strike rather than a systematic process. You're waiting for conviction to arrive before you start investigating, but conviction is the output of investigation, not the input.

Why the Usual Fixes Fail

Scratching your own itch works when your problem is shared by enough people who pay for solutions. Most personal itches are either too niche (you're the only one) or already solved (you just haven't found the existing tool). Building for yourself without verifying demand is how you get a portfolio of unused side projects.

Market research reports tell you where the market was, not where it's going. By the time a trend appears in a Gartner quadrant or a "top 10 opportunities for 2024" blog post, the early movers have already established distribution. You're reading the scoreboard after the game.

Competitor analysis leads to feature parity, not opportunity. If you study five competitors and build what they have plus one differentiator, you've built a worse version of their product for a market they already own. The opportunity isn't in the feature gap—it's in the customer segment they're ignoring or the workflow they've normalized that's actually broken.

Brainstorming sessions generate volume, not signal. Without a filter, you end up with 50 ideas and no way to rank them. The filter is the work, not a post-processing step.

Waiting for founder-market fit is backward. You develop founder-market fit by engaging deeply with a problem space, not by introspecting until a match appears. Expertise follows attention.

Step-by-Step Solution

Phase 1: Define Your Constraints (Days 1-2)

Before looking outward, map your actual constraints. Write them down—literally open a document and list:

  • Capital: How many months of runway without revenue? Be precise.
  • Time: Hours per week you can consistently commit for 6+ months.
  • Skills: What can you build well without learning something new? What can you learn in 2-4 weeks?
  • Network: Who do you know in which industries? Who owes you a favor? Who replies to your DMs?
  • Distribution: Do you have an audience, newsletter, community access, or SEO assets? If not, how will you get first users?
  • Risk tolerance: Are you optimizing for learning, cash flow, or equity value?

These aren't preferences—they're hard boundaries. An opportunity requiring $50k upfront is invisible to you if you have $5k. A B2B sales cycle of 6 months is invisible if you need revenue in 3. Most people skip this and waste weeks evaluating ideas they could never execute.

Phase 2: Pick Three Problem Spaces (Days 3-5)

Don't pick ideas. Pick problem spaces—domains where problems exist. Good sources:

  1. Your recent work history: What processes were painful, manual, error-prone, or dependent on tribal knowledge? What did your team complain about in Slack/retrospectives?
  2. Adjacent industries: If you know construction, look at subcontractor coordination, material procurement, or compliance documentation. Don't look at construction SaaS—look at the work.
  3. Communities you're in: Discord servers, subreddits, forums, professional associations. Where do people ask "how do I...?" or "does a tool exist for...?" repeatedly?
  4. Vendor frustration: What software do you or your company pay for that's expensive, clunky, and hard to replace? The switching cost is the moat.
  5. Regulatory/compliance changes: New laws create forced demand. SOC2, GDPR, HIPAA, ASC 606, ESG reporting—each spawned tool categories.

Select three spaces where you have some access to practitioners. Not "I read about this on Twitter." Access means: you can message 5-10 people this week who do this work daily.

For each space, write a one-pager:

  • Who does the work? (Title, company size, seniority)
  • What's the core workflow? (Step by step, current tools at each step)
  • Where does it break? (Time lost, errors, rework, frustration)
  • What triggers spending? (New hire, audit, growth, failure, mandate)
  • Who controls budget? (User, manager, CTO, procurement)

If you can't fill this out, you don't know the space well enough. That's fine—cross it off and pick another.

Phase 3: Run 15 Discovery Calls (Days 6-14)

Not user interviews. Discovery calls. The goal isn't to validate an idea—it's to map the problem landscape. You're not pitching. You're learning.

Recruitment message template:

"Hi [name], I'm researching [specific workflow/problem] for [type of companies]. You came up because [specific reason: you posted about X, you work at Y, mutual connection Z]. Not selling anything—just trying to understand how teams actually handle this today. 20 minutes, I'll share my notes after. Worth a quick call?"

Book 5 calls per problem space. Aim for practitioners, not buyers—practitioners feel the pain; buyers feel the budget. You need both eventually, but practitioners reveal the real workflow.

Call structure (20 minutes):

  1. Context (2 min): "Walk me through your role and where [workflow] fits."
  2. Current workflow (5 min): "Last time you did [specific task], walk me through step by step." Probe for tools, handoffs, exceptions, workarounds.
  3. Pain points (5 min): "What's the worst part? What breaks? What takes too long? What causes errors?" Ask for specific recent examples, not generalizations.
  4. Current solutions (3 min): "What tools/processes do you use now? What do you like/hate? What have you tried and abandoned?"
  5. Buying behavior (3 min): "If something solved [top pain], who decides to buy? What's the process? What budget exists?"
  6. Magic wand (2 min): "If you could wave a wand and fix one thing, what would it be?"

Critical rules:

  • Record (with permission) and transcribe. Don't rely on notes.
  • Zero pitching. If they ask what you're building, say "Still researching—want to make sure I understand the problem first."
  • Ask "why" three times per pain point. "It's slow" → "Why?" → "Manual data entry" → "Why?" → "Systems don't integrate" → "Why?" → "Vendor APIs are limited." That's the real constraint.
  • After each call, write a 5-bullet summary: top pain, current workaround, trigger, budget owner, surprising insight.

Phase 4: Synthesize and Score (Days 15-17)

You now have 15 call transcripts + summaries. Create a matrix:

Problem Space Top 3 Pains (frequency) Workaround Cost (time/$/risk) Buying Trigger Budget Access Your Build Fit (1-5) Your Distribution Fit (1-5)

Build fit: Can you build a v1 in 4-8 weeks with current skills? Distribution fit: Can you reach 10-20 target users in 2 weeks without paid ads?

Score each space 1-5 on:

  • Pain intensity (how badly they need it solved)
  • Pain frequency (daily > weekly > monthly)
  • Workaround cost (high = more willingness to pay)
  • Budget clarity (known budget > "we'd need approval")
  • Build feasibility
  • Distribution feasibility

Multiply pain intensity × frequency × workaround cost × budget clarity = Demand Score. Multiply build × distribution = **Execution Score

Start here

Top comments (0)