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 you don't know what to build or pursue. Every idea feels either too small, too crowded, or too vague. You've read about "finding your niche" and "scratching your own itch," but your itches are either already solved or not monetizable. You sit down to brainstorm and produce a list of mediocre concepts you don't believe in. Meanwhile, you see others launching products, getting traction, and you can't identify the gap they saw that you missed.

This isn't "writer's block for ideas." It's a process gap. You're trying to generate opportunities from a blank slate instead of extracting them from evidence.

Why the Usual Fixes Fail

Brainstorming sessions produce volume, not quality. Without constraints, your mind defaults to obvious, saturated markets (productivity apps, course platforms, AI wrappers).

Trend-chasing (AI, Web3, no-code) puts you in markets where the cost of entry rises daily. By the time you spot a trend on Twitter, the early movers have 18 months of head start.

"Scratch your own itch" assumes your problems are representative and monetizable. They often aren't. Your problems as a developer/designer/marketer are niche and well-served.

Customer interviews without a hypothesis lead to polite conversations that confirm nothing. People lie about future behavior, overstate pain, and understate switching costs.

Market research reports describe yesterday's opportunities. They're written for investors, not builders.

Step-by-Step Solution

Phase 1: Map Your Asymmetric Advantages (Days 1-2)

List every asset you control that others don't. Be specific. Not "I know Python." Instead: "I've built three internal tools for logistics companies that reduced manual data entry by 60%." Not "I have a network." Instead: "Three former colleagues are now VP Engineering at Series B companies."

Create a four-column spreadsheet:

Asset Type Specific Detail Proof/Artifact Access Level
Technical Built Stripe integration for 12 clients GitHub repos, client refs Direct
Domain Managed $2M ad spend for DTC brands Case studies, dashboards Direct
Network Former boss runs 200-person eng org LinkedIn, last spoke 3 months ago Warm intro
Data Scraped 50K product reviews in pet niche CSV, cleaning scripts Owned

Stop when you have 15-20 rows. This is your unfair advantage inventory. Every opportunity you evaluate must leverage at least two columns.

Phase 2: Collect Observed Friction, Not Ideas (Days 3-7)

Ideas are solutions. Friction is the problem space. Spend one week capturing friction you observe directly—not what people tell you, what you see.

Sources you can access this week:

  1. Your current/previous workplaces: What processes made you or colleagues curse? What spreadsheets run the business? What does the CEO ask for weekly that takes a day to compile?
  2. Communities you're already in: Slack groups, Discords, subreddits, forums. Search for: "how do I," "any tool for," "manually," "spreadsheet," "hate," "annoying," "wish there was."
  3. Support tickets and feature requests: If you have access to any product's feedback (yours, a friend's, open source), tag every request that implies a workaround exists.
  4. Job postings: Search "Excel," "manual," "spreadsheet," "copy-paste" in job descriptions for roles in industries you know. These reveal processes companies pay humans to do badly.
  5. Government and regulatory filings: New compliance requirements (SOC2, GDPR, industry-specific) create mandatory work nobody wants.

Capture format (one row per observation):

Source | Actor | Current Workaround | Frequency | Evidence Quote/Link | Industry
Enter fullscreen mode Exit fullscreen mode

Example:

Reddit r/property management | Property manager | Google Sheets + photos in Drive + calendar reminders | Weekly per unit | "I have 40 units and spend every Sunday updating this nightmare" | Residential PM
Enter fullscreen mode Exit fullscreen mode

Collect 50+ observations. No filtering yet. No "is this a business?" judgment. Just documentation.

Phase 3: Filter for Structural Opportunity (Days 8-10)

Now apply filters. Keep only observations meeting all four criteria:

1. Recurring, not one-off
The friction happens on a schedule (daily, weekly, monthly) or triggers predictably (new hire, new client, month-end). One-time migrations are projects, not products.

2. High-cost workaround
The current solution costs significant time (>5 hrs/week per user), money (>$200/mo in tools/labor), or risk (compliance failure, data loss, customer churn). "Annoying" isn't enough. "Costs us a client per quarter" is.

3. No dominant incumbent
Search the workaround + "software" + "tool" + "platform." If the top 3 results are established companies with >50 employees and clear pricing pages, move on. You want fragmented markets: custom scripts, generic tools (Airtable, Zapier, Notion) stretched past their limits, or nothing.

4. Leverages your advantage inventory
Cross-reference with Phase 1. Can you build the MVP faster, sell to the buyer easier, or integrate deeper because of a specific row in your spreadsheet? If not, you're starting from zero—same as everyone else.

Expect 50 observations → 8-12 survivors.

Phase 4: Validate the Workaround, Not the Idea (Days 11-21)

Don't build. Don't pitch. Replicate the workaround manually for 3-5 real users.

Find the actors from your observations. Message them:

"I'm researching how [role] handles [specific workflow]. I see you're using [workaround]. I built a rough script/template that automates [specific step]. Want me to run it on your data this week? Free, just need your feedback on whether the output matches what you need."

Deliver a partial automation—a script, a Notion template with formulas, a Zapier flow, a Google Sheet with Apps Script. Something that eliminates one painful step in their current process.

Measure:

  • Did they use it without you reminding them?
  • Did they ask for the next step automated?
  • Did they introduce you to a colleague?
  • Would they pay $X to keep it? (Ask: "If this saved you [measured time], what's the max you'd pay monthly?")

Three "yes" signals from different people = proceed. Two or fewer = return to Phase 2 with a new observation set.

Phase 5: Define the Wedge (Days 22-25)

You have a validated friction point. Now define the minimum product that earns the right to expand.

Wedge criteria:

  • Solves one complete sub-workflow end-to-end (not a feature, a flow)
  • Requires <3 weeks to build to "ugly but functional"
  • Has a clear "aha" moment within 10 minutes of first use
  • Generates an artifact the user shows others (report, dashboard, export, client deliverable)
  • Pricing is obvious: per seat, per transaction, per document, per month

Write a one-pager:

Problem: [Specific workflow] costs [actor] [time/money/risk] via [workaround]
Wedge: [Product name] automates [specific step] producing [artifact]
User: [Title] at [company size/type] who currently uses [workaround]
Price: $[X]/[unit] because it saves [Y hours] × [$Z loaded cost]
Build: [Tech stack], [key integration], [hardest part] — 3 weeks
Go-to-market: [Specific channel: cold email template, community, partner, SEO keyword]
Enter fullscreen mode Exit fullscreen mode

If you can't fill this in concretely, the wedge isn't sharp enough. Return to Phase 4.

Phase 6: Build in Public, Sell in Private (Days 26-60)

Week 1-2: Build the wedge. No auth system, no settings, no onboarding flow. Hardcode the first user's config if needed. Deploy to a URL they can bookmark.

Week 3: Onboard your 3-5 validation users. Watch them use it. Record sessions (Loom, with permission). Fix what breaks. Add only what prevents them from completing the workflow.

Week 4-6: Add the minimum to support 10 users: billing (Stripe), auth (Clerk/S

Start here

Top comments (0)