DEV Community

Alan Descure
Alan Descure

Posted on Originally published at smtm-store.pages.dev

opportunity-discovery: a practical guide

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 problem worth solving. Every idea feels either too small (a vitamin, not a painkiller), too crowded (ten funded competitors), or too vague ("people need better productivity"). You sit down to research and end up doom-scrolling Product Hunt or reading market reports that tell you the TAM is $50B but nothing about what to build on Monday.

The stuckness shows up in three ways:

  1. Idea paralysis: You generate concepts but kill them before validation because you "know" they won't work.
  2. Research rabbit holes: You spend weeks mapping competitive landscapes for markets you have no intention of entering.
  3. False starts: You build an MVP for a problem nobody actually has, then wonder why signups flatline.

The common thread: you are trying to find an opportunity instead of earning the right to see one.


Why the Usual Fixes Fail

Market research reports tell you where money was spent last year. They are lagging indicators wrapped in consultant language. By the time a trend appears in Gartner or CB Insights, the early-mover advantage is gone.

Keyword tools and SEO research reveal search volume, not willingness to pay. People search for "free CRM" and "how to lose weight fast"—neither indicates a viable B2B SaaS or sustainable consumer business.

Competitor analysis teaches you what existing companies do. It does not teach you what customers hate about those companies. The opportunity lives in the gap between what competitors deliver and what users tolerate.

Brainstorming sessions produce ideas filtered through your own biases. You default to problems you personally experience (developer tools, productivity apps) because they are visible to you. The highest-leverage opportunities are usually invisible to you—until you go look.

Waiting for inspiration is not a strategy. It is procrastination with better branding.


Step-by-Step Solution

Phase 1: Pick a Surface Area (Days 1–2)

You cannot discover opportunities in "business" or "tech." You need a specific domain where you have access—not expertise, access. Access means you can reach 10–20 practitioners this week without cold emailing strangers.

List every domain where you have access:

  • Current or former industry (you know the workflows, the jargon, the people)
  • Hobbies where you participate in communities (Discord, forums, local meetups)
  • Adjacent roles in your company (talk to sales, support, ops, finance)
  • Friends' and family's professions (ask for 15-minute walkthroughs)

Pick one. Commit to it for two weeks. If it yields nothing, move to the next. Do not parallelize.

Phase 2: Run Contextual Interviews (Days 3–10)

Schedule 10–15 conversations, 30 minutes each. Not "customer discovery calls"—that framing makes people perform. Call them "workflow walkthroughs" or "day-in-the-life chats."

Recruitment script:

"I'm trying to understand how [role] actually works day to day. Not the happy path—the messy middle. 30 minutes, no sales pitch, I'll buy you coffee/lunch/send a $20 gift card."

Interview structure (do not send questions ahead):

  1. Context (5 min): "Walk me through last Tuesday. What did you do from 9 to 5?"
  2. Tools & workarounds (10 min): "What tools do you use? What do you hate about them? What spreadsheets/Notion docs/scripts have you built yourself?"
  3. Pain ranking (10 min): "If you could wave a wand and fix one thing about your workflow, what would it be? What's the second? Third?"
  4. Budget & authority (5 min): "Who decides on new tools? What's the last tool your team bought? How did that decision happen?"

Critical rules:

  • Record (with permission) and transcribe. Do not rely on notes.
  • Ask "then what?" and "say more about that" more than any other question.
  • Never pitch. Never say "would you use a tool that..."
  • Listen for workarounds—they are the clearest signal of unmet needs. A shared spreadsheet passed around via Slack is a product waiting to happen.

Phase 3: Cluster and Rank Problems (Days 11–12)

Take your transcripts. Highlight every distinct problem mentioned. Write each on a sticky note (physical or Miro/FigJam). Group duplicates.

For each cluster, score 1–5 on four dimensions:

Dimension 1 5
Frequency Mentioned by 1 person Mentioned by 8+ people
Intensity "Annoying" "Costs us deals / causes compliance risk / makes me stay late"
Workaround existence No workaround Custom script, spreadsheet, or paid consultant
Budget accessibility No budget, no authority Team bought something similar last quarter

Sum scores. Keep clusters scoring 14+. Discard the rest. You should have 2–4 problem clusters left.

Phase 4: Validate Willingness to Pay (Days 13–17)

For each remaining problem, find 3–5 people from your interviews (or new ones in the same role) and run a problem-solution fit test.

Create a one-pager (Notion page, PDF, Google Doc) per problem:

  • Problem statement in their language (quote them directly)
  • Current workaround described
  • Proposed solution: 3 bullet points, no features—outcomes only
  • Price anchor: "Teams like yours typically pay $X/seat/month for this"
  • CTA: "I'm building this for 5 design partners. 50% off for life, weekly feedback calls. In or out?"

Send personally:

"Based on our chat, I put this together. Honest feedback—would you put this on your team's radar? No pressure."

Track responses:

  • Strong signal: "Send me the contract" or "Can I show this to my manager?"
  • Weak signal: "Interesting, keep me posted"
  • Noise: "Cool idea!" with no follow-up

You need 2 strong signals per problem to proceed. If zero problems hit this threshold, return to Phase 1 with a new surface area.

Phase 5: Define the First Slice (Days 18–21)

Pick the problem with the strongest signals. Do not build an MVP. Build a manual-first delivery.

Map the workflow end-to-end. Identify the single highest-value step you can do for the customer without code. Examples:

  • They need competitor pricing intelligence → You deliver a weekly curated report
  • They need compliant contract review → You review 5 contracts/week with a checklist
  • They need candidate screening → You screen 20 resumes against their rubric

Charge from day one. Even $100/month. Payment is the only validation that matters.

Set a 4-week deadline: deliver manually, collect feedback, document every edge case. Only then decide what to automate.


Checklist

  • [ ] Listed 5+ domains where I have direct access to practitioners
  • [ ] Picked one domain and committed to 2 weeks
  • [ ] Conducted 10+ workflow walkthroughs (recorded, transcribed)
  • [ ] Extracted and clustered problems from transcripts
  • [ ] Scored each cluster on frequency, intensity, workaround, budget
  • [ ] Kept only clusters scoring 14+
  • [ ] Created one-pagers for each remaining problem
  • [ ] Got 2+ strong buying signals per problem
  • [ ] Selected one problem and defined a manual-first delivery
  • [ ] Secured first paying design partner before writing code

Closing

Opportunity discovery is not a creative exercise—it is a sales exercise. You earn the right to build by proving someone will pay for the outcome. The steps above replace guesswork with evidence, and they work whether you are a solo founder, a PM exploring a new vertical, or an engineer tired of building things nobody uses. If you want a structured workbook that walks through each phase with templates, scripts, and scoring sheets, start here.

Top comments (0)