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, definitely the technical skills. What you don't have is a clear direction. Every idea you generate feels either too small to matter, too crowded to enter, or too vague to validate. You've read about "finding your niche" and "scratching your own itch," but your own itches are either already solved by existing tools or too idiosyncratic to build a business around.

The stuckness shows up in specific ways:

  • You open a blank notebook or document to brainstorm and close it an hour later with three half-written sentences and a sense of defeat
  • You've built two or three side projects that technically work but nobody uses, including you
  • You spend more time researching "markets" and "trends" than talking to actual people who might pay for something
  • Every promising thread you pull—B2B SaaS for dentists, a tool for freelance designers, a marketplace for local artisans—collapses under five minutes of competitive research
  • You oscillate between "everything's already been built" and "I have no way to know if anyone wants this"

The core problem isn't a lack of ideas. It's that you have no reliable method to separate ideas worth pursuing from ideas that feel exciting for twenty minutes. You're trying to evaluate opportunities using intuition and Google searches, which is like trying to debug production code by reading the repository description.

Why the Usual Fixes Fail

Reading "how I found my SaaS idea" posts. These are survivor bias narratives. The founder retroactively constructs a clean story: "I noticed X problem, built Y solution, got Z customers." They omit the six dead ends, the pivot, the co-founder who quit, the month they almost shut down. You're comparing your messy middle to their polished ending.

Keyword research and market sizing tools. Ahrefs, Semrush, and TAM calculators tell you what people search for, not what they'll pay for. High search volume often means high competition and low urgency. Low search volume might mean a desperate, underserved niche—or it might mean nobody cares. The tool cannot distinguish.

"Scratch your own itch." This works if your itch is shared by thousands of people with budget authority. If you're a developer building a developer tool, you're in the most crowded category on earth. If your itch is highly specific to your workflow, the market size is one. The advice assumes your problems are representative. They usually aren't.

Customer development interviews done wrong. Most people ask "Would you use a tool that does X?" People say yes to be polite. Or they ask "What's your biggest problem?" and get vague complaints like "communication" or "time management" that don't translate to a buildable product. You end up with a list of nice-to-haves, not must-haves.

Waiting for inspiration. The shower moment is a myth. Ideas emerge from contact with reality—specifically, from observing friction in systems where money already changes hands. You don't find opportunities by thinking harder. You find them by looking closer at where value is already being exchanged inefficiently.

Step-by-Step Solution

Phase 1: Map Where Money Moves (Week 1)

Stop looking for "problems." Start looking for transactions.

  1. List 10-15 industries or professional roles you have some access to. Not "industries that seem hot." Industries where you know at least two people willing to take a 20-minute call. Former coworkers, college friends, LinkedIn connections, family members, people you meet at meetups. Access beats interest every time.

  2. For each industry, identify the core revenue loop. How does money enter the system? Who pays whom, for what, and how often? Example: In commercial HVAC maintenance, property managers pay contractors for preventive maintenance contracts (recurring) and emergency repairs (variable). The loop is: equipment runs → degrades → fails or gets maintained → money moves.

  3. Find the friction points in that loop. Where does the transaction slow down, get delayed, require manual work, cause disputes, or fail entirely? In the HVAC example: scheduling is phone-tag heavy, technicians arrive without the right parts, property managers can't verify work was done, invoices sit unpaid for 60 days.

  4. Score each friction point on three dimensions (1-5 scale):

    • Frequency: How often does this friction occur per customer per month?
    • Cost: What's the dollar impact when it happens? (Lost revenue, wasted labor, penalties, churn)
    • Urgency: How actively is the buyer currently trying to solve it? (1 = "someday," 5 = "I have a spreadsheet hack / I'm evaluating vendors this quarter")
  5. Keep only friction points scoring 12+ (out of 15). These are your candidate opportunities. Everything else is a vitamin, not a painkiller.

Phase 2: Validate the Right Way (Weeks 2-3)

Don't pitch. Don't demo. Don't ask hypotheticals.

  1. Recruit 8-12 people per candidate opportunity. Use your access list. Cold DM if needed: "I'm researching how [role] handles [specific friction point]. Not selling anything. 15 minutes, I'll buy you coffee / send a $25 gift card." Pay for their time. It filters for serious respondents and respects the relationship.

  2. Run a structured interview (script below). Record with permission. Take notes. Do not deviate.

The Script:

  • "Walk me through the last time [friction point] happened. What did you do?" (Get the actual workflow, not the idealized one)
  • "What tools or workarounds are you using now?" (Reveals competition: spreadsheets, whiteboards, hiring interns, ignoring it)
  • "What's the hardest part about that workaround?" (The real pain)
  • "Have you looked for a better solution in the last 6 months?" (Proves urgency)
  • "What did you try? Why didn't it work?" (Reveals switching costs and dealbreakers)
  • "If you could wave a magic wand and fix one thing about this process, what would it be?" (The outcome they actually want)
  • "Who else on your team deals with this? Should I talk to them?" (Expands your map)
  1. After each interview, write a 3-sentence summary:

    • The workflow (current state)
    • The blocker (why current tools fail)
    • The evidence of urgency (what they've already tried/spent)
  2. Kill candidates where:

    • Fewer than 3/8 interviewees have actively sought a solution recently
    • The "magic wand" answer varies wildly across respondents (no shared mental model of the solution)
    • The workaround is "we just deal with it" and the cost is abstract ("morale," "efficiency") not concrete ("lost contracts," "overtime pay")

Phase 3: Define the Minimum Viable Test (Week 4)

You don't build yet. You design a test that proves people will pay.

  1. Write a one-page "offer doc" for each surviving candidate. Include:

    • Headline: The specific outcome (not the feature)
    • The mechanism: One paragraph on how it works (no jargon)
    • The price: A specific number or range
    • The commitment: What they do next (pre-pay, deposit, sign LOI, join pilot waitlist with $100 refundable deposit)
  2. Show it to 5 of your interviewees. Say: "Based on our conversation, I'm putting this together. Would you sign this today?" Silence or "maybe later" = no. "Send me the link" or "What's the payment link?" = yes.

  3. Set a threshold: 2/5 committed = build. 1/5 = iterate offer. 0/5 = kill.

  4. If you hit threshold, collect the commitments. Real money or signed LOIs. Not "interest." Not "emails collected." Commitments.

Phase 4: Build the Smallest Thing That Delivers the Outcome (Weeks 5-8)

  1. Strip every feature not directly tied to the committed outcome. No dashboards, no settings, no integrations, no auth system if you can use magic links. No onboarding flow if you can onboard manually.

  2. Build for the 2-3 committed users only. Hardcode their workflows if needed. This is not your product. This is your validation engine.

  3. Deliver in 2-week cycles. Week 1-

Start here

Top comments (0)