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 too small to matter, too crowded to enter, or too vague to act on. 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 turn their complaints into something buildable.

The stuckness shows up in specific ways:

  • You maintain a running list of ideas that never progresses past the "interesting" column
  • You can't distinguish between a real market gap and a feature request for an existing product
  • You spend weeks researching a space only to find the economics don't work
  • You default to building tools for developers because that's what you know, even when the market is saturated
  • You feel like everyone else has a secret map you weren't given

The core issue isn't creativity—it's that you're trying to invent opportunities instead of discovering them. Opportunities aren't ideas; they're structural mismatches between what people need and what's available. You find them by looking at systems, not by brainstorming.


Why the Usual Fixes Fail

Brainstorming sessions produce ideas, not opportunities. Ideas are solutions in search of problems. Opportunities are problems with constraints that make them solvable by you specifically.

"Talk to 50 customers" fails when you don't know who the customers are or what problem space to explore. You end up with 50 polite conversations and zero signal because you asked "would you use this?" instead of investigating how they currently solve the problem.

Trend reports and market research describe where the puck was. By the time a trend appears in a report, the structural opportunity has been exploited. The remaining opportunities are execution plays, not discovery plays.

Competitor analysis teaches you what's already been built. It doesn't reveal what's missing—only what's been tried. The gaps between competitors are often mirages: they exist because the economics don't work, not because nobody thought of them.

Scratching your own itch works only if your itch is shared by enough people with budget to matter. Most developer itches are either too niche (a better dotfile manager) or too competitive (another project management tool).


Step-by-Step Solution

Phase 1: Map Your Asymmetric Advantages (Week 1)

Before looking outward, inventory what you bring that others don't. This isn't "skills"—it's structural advantages that lower your cost of discovery or execution.

Do this:

  1. List every domain you have insider access to. Not "I know Python." Instead: "I worked in procurement at a mid-sized food distributor for three years." "My spouse runs a dental practice." "I managed inventory for a seasonal e-commerce brand." Access beats expertise. Access means you see the workflow, the exceptions, the workarounds, and the budget owner.

  2. List every constraint you can operate within that others can't. Examples: "I can build and launch in 4 weeks without external approval." "I have $15k I can risk without investor permission." "I have direct access to 200 independent insurance agents through a former colleague." "I can operate in a regulated space because I hold the license."

  3. List every recurring problem you've seen professionals pay to solve badly. Not "they complain about X." Instead: "They pay $200/month for a tool they hate because the alternative is a spreadsheet that breaks monthly." "They hire a part-time contractor at $3k/month to manually reconcile data between System A and System B."

Output: A one-page document with three columns: Access, Constraints, Observed Paid Workarounds. This is your search space. Everything outside it is noise.


Phase 2: Study Workflows, Not Pain Points (Weeks 2-3)

Pain points are symptoms. Workflows are systems. You discover opportunities by finding the steps in a workflow where value leaks—time, money, accuracy, compliance risk, or decision latency.

Do this:

  1. Pick one domain from your Access column. Ideally one where you can observe the actual work happening, not just hear about it.

  2. Shadow the work for 2-3 full cycles. If it's monthly close, sit with the controller for the full close. If it's patient intake, sit at the front desk for three mornings. If it's freight booking, watch the broker for a week. Take timestamped notes: What triggers this step? What tools are used? Where does the person pause, sigh, switch tabs, re-enter data, call someone, or check a spreadsheet?

  3. Map the workflow as a value stream. For each step, record:

    • Time consumed
    • Tools/systems involved
    • Handoffs to other people
    • Error rate (ask: "How often does this come back wrong?")
    • Cost of error (ask: "What happens when this is wrong?")
    • Frequency
    • Who owns the budget for this step
  4. Identify the "shadow workflows." These are the spreadsheets, Notion pages, Slack threads, email chains, and manual checks that exist around the official software. Every shadow workflow is a candidate opportunity. The official software vendor doesn't see them. The buyer doesn't budget for them. But they consume real hours and create real risk.

Output: A workflow map with shadow workflows highlighted. Rank shadow workflows by: (frequency × time × cost of error × budget owner accessibility).


Phase 3: Validate the Economics Before Building (Week 4)

Most builders skip this. They assume "if I build it better, they'll switch." They won't—switching costs are real, and "better" is subjective. You need to prove the math works for the buyer.

Do this:

  1. Calculate the current cost of the shadow workflow. Include: labor hours × loaded cost, error remediation cost, opportunity cost (what else could that person do), tool costs (even free tools have time costs), compliance/risk exposure.

  2. Define the maximum viable price. This is not "what would you pay?" It's: What fraction of the current cost can I capture while leaving the buyer a clear ROI? If the shadow workflow costs $8k/month in labor and errors, and you charge $2k/month, the buyer nets $6k/month. That's a 3:1 ROI. At $5k/month, it's 1.6:1—harder to sell. At $7k/month, it's not worth switching.

  3. Identify the budget owner and buying process. Who signs? What's their threshold for approval without committee? What's the procurement cycle? If the budget owner is a VP who needs board approval for anything over $5k/month, and your price is $6k, you've added 3 months to the sale. Adjust price or target accordingly.

  4. Run a "concierge test" with 3-5 real prospects. Don't build. Don't show mockups. Say: "I'm exploring building a tool that does [specific shadow workflow step]. It would cost roughly $X/month and save ~Y hours. If I had a working version today, what would stop you from using it?" Record objections verbatim. Objections are your feature roadmap and your pricing validation.

Output: A one-pager per candidate: Current Cost, Max Viable Price, Budget Owner, Buying Process, Top 3 Objections. Kill any candidate where objections are structural (e.g., "we can't move data off-prem" and you're SaaS) or where Max Viable Price < your floor for sustainability.


Phase 4: Build the Thinnest Slice That Proves the Math (Weeks 5-8)

You are not building a product. You are building a proof that the shadow workflow can be replaced at the target price.

Do this:

  1. Scope to one high-value step. Not the whole workflow. The step with the highest (frequency × cost of error × time) that you can automate or streamline end-to-end.

  2. Build for the concierge test participants only. Hardcode their data formats. Skip auth, settings, onboarding, billing, multi-tenancy. If they use CSV exports from System A, your tool ingests that exact CSV. If they need a PDF output, generate that exact PDF.

  3. Measure what matters: Time to complete the step. Error rate. Number of manual interventions. Whether they actually use it when you're not watching.

  4. Charge from day one. Even if it's a "pilot price." Free users give

Start here

Top comments (0)