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 time, skills, and maybe even capital—but every idea you generate feels either obvious, saturated, or too small to matter. You've read the "scratch your own itch" advice, but your itches are either already solved or too niche to build a business around. You've tried "talking to customers," but you don't know which customers, what to ask, or how to separate polite encouragement from actual demand.

The stuckness looks like this: you open a blank document to brainstorm, write down three ideas, dismiss two as "already done" and one as "not a real business," then close the laptop. Or you spend weeks researching a market only to realize you've been reading competitor blog posts, not learning what buyers actually struggle with. You're not lacking creativity—you're lacking a reliable process that turns observation into testable opportunity.

Why the Usual Fixes Fail

Scratch your own itch works when your problem is shared by thousands of people willing to pay. Most personal problems aren't. You end up building a tool for yourself that nobody else needs.

Talk to customers assumes you already know who the customer is and what problem space they live in. Cold outreach to random LinkedIn profiles yields low response rates and vague feedback. Surveys get you what people say they want, not what they'll pay for.

Follow trends (AI, Web3, no-code, creator economy) puts you in crowded markets with well-funded incumbents. By the time a trend is visible, the easy opportunities are gone.

Copy competitors leads to feature parity without differentiation. You inherit their positioning, their pricing pressure, and their customer acquisition costs.

Wait for inspiration is not a strategy. It's procrastination with better branding.

These approaches fail because they start with ideas instead of evidence. Opportunity discovery isn't creative writing—it's investigative work.

Step-by-Step Solution

Phase 1: Map Your Access (Week 1)

You can only discover opportunities where you have information advantage. List every group you have genuine access to—not "could email," but "can have a 30-minute conversation with this week."

Do this:

  1. Open a spreadsheet. Columns: Group Name, Your Connection, Size Estimate, Purchase Authority, Conversation Access (Yes/No).
  2. Fill rows for: current/former coworkers, industry Slack/Discord communities, conference acquaintances, newsletter subscribers, clients, vendors, meetup regulars, subreddit moderators, trade association members.
  3. Filter for Conversation Access = Yes. Keep only groups with Purchase Authority = Yes (they control budget or influence buying decisions).
  4. Pick 3 groups. These are your hunting grounds for the next 30 days.

Why this works: Opportunity discovery requires repeated, honest conversations. You get those through trust, not cold DMs.

Phase 2: Run Problem Interviews (Weeks 2-3)

Don't pitch. Don't demo. Don't ask "would you use X?" Ask about their work, their friction, their workarounds.

Interview script (memorize this flow):

  1. "Walk me through the last time you did [relevant workflow]."
  2. "What tools or people were involved?"
  3. "Where did it slow down or break?"
  4. "What did you do when it broke?"
  5. "Have you paid for anything to fix this? What? How much?"
  6. "If you could wave a wand, what would change?"

Rules:

  • 15 interviews minimum per group. Fewer = noise, not signal.
  • Record (with permission) and transcribe. Do not rely on notes.
  • Zero follow-up questions about your idea. Zero.
  • Tag each transcript with: Problem Statement, Current Workaround, Spend Evidence, Urgency (1-5).

Output: A document with 45+ tagged problem statements. Patterns will emerge.

Phase 3: Filter for Evidence, Not Interest (Week 4)

Interest is cheap. Evidence is: money spent, time invested, reputation risked, workflows built around the problem.

Filter criteria (all must be true):

  1. Spend evidence: They've already paid for a tool, consultant, contractor, or internal headcount to address this.
  2. Frequency: The problem occurs weekly or daily. Monthly problems don't sustain SaaS.
  3. Workaround complexity: They've built a spreadsheet, Zapier chain, Notion database, or manual process. This proves the problem is real and they're motivated.
  4. Decision maker access: You can reach the person who signs off on $500-5000/month purchases.
  5. No dominant incumbent: The current solution is homegrown, a generic tool (Excel, email, Slack), or a legacy vendor they complain about.

Score each problem 0-5 on each criterion. Keep only 20+ total score.

Phase 4: Validate Willingness to Pay (Week 5)

You have 3-5 high-score problems. Now test if they'll pay you.

The $500 test:

  1. Write a one-pager for each problem: Problem, Current Cost (time/money), Proposed Solution, Price ($500/mo or $5k one-time), Timeline (8 weeks to MVP).
  2. Send to 5 decision-makers per problem from your interview pool. Subject: "Solving [specific problem] for [their company]."
  3. Ask for a 15-min call to show mockups. On the call: show the one-pager, ask "Does this match what you described?" then "If this existed in 8 weeks at this price, what would stop you from buying?"
  4. Silence their objections. Write them down. Do not defend.
  5. Ask: "Can I follow up in 6 weeks with a working version for a pilot at 50% off?"

Success threshold: 2 of 5 say "yes, follow up" per problem. Fewer = keep interviewing or drop the problem.

Phase 5: Build the Smallest Testable Thing (Weeks 6-9)

Not an MVP. A riskiest-assumption test.

Identify the riskiest assumption: Usually "they'll pay this price" or "we can integrate with their [legacy system]."

Build only what tests that assumption:

  • If price risk: Stripe payment link + Notion onboarding doc. No code.
  • If integration risk: Manual process behind a Typeform. You do the work by hand.
  • If usability risk: Clickable Figma prototype + 5 usability sessions.

Constraints:

  • 3 weeks max build time.
  • Zero features not directly testing the riskiest assumption.
  • One pilot customer committed before you write production code.

Phase 6: Decide (Week 10)

Pilot runs. You have data.

Decision matrix:
| Signal | Continue | Pivot | Kill |
|--------|----------|-------|------|
| Pilot pays full price on time | ✓ | | |
| Pilot uses daily, asks for features | ✓ | | |
| Pilot uses weekly, pays reluctantly | | ✓ (reprice/rescope) | |
| Pilot ghosts, won't schedule feedback | | | ✓ |
| Integration fails technically | | ✓ (different approach) | |

If continue: You have a business. Raise prices. Hire. Systematize.
If pivot: Return to Phase 3 with new insight. You're not starting over—you're 10 weeks smarter.
If kill: Return to Phase 1. Your access map is still valid. Your interview skills are sharper.

Checklist

  • [ ] Access map complete with 3+ groups having conversation access and purchase authority
  • [ ] 15+ problem interviews conducted per group (45+ total), recorded and transcribed
  • [ ] All transcripts tagged: Problem, Workaround, Spend Evidence, Urgency
  • [ ] 3-5 problems scoring 20+ on evidence filter (spend, frequency, workaround, access, no dominant incumbent)
  • [ ] One-pagers written for each high-score problem with specific price and timeline
  • [ ] 5 decision-makers contacted per problem, 2+ "follow up" commitments secured
  • [ ] Riskiest assumption identified and documented
  • [ ] Smallest testable thing built in ≤3 weeks targeting only that assumption
  • [ ] One pilot customer onboarded with payment commitment
  • [ ] Decision matrix applied after pilot period

Closing

This process works because it replaces guessing with evidence at every step. You stop imagining what people want and start documenting what they've already proven they'll pay for. The first time through takes 10 weeks. The second takes 6. The third takes 3. If you're ready to run your first

Start here

Top comments (0)