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're sitting at your desk with a blank document or a half-finished Notion page. You want to build something—maybe a SaaS, a productized service, a content business, a tool. But every idea you write down feels either too small ("who pays for this?"), too crowded ("Stripe/Notion/Linear already owns this"), or too vague ("I'll help creators monetize").

You've read the tweets: "scratch your own itch," "talk to customers," "look for complaints on Reddit." You've tried them. You've scrolled r/SaaS and Indie Hackers until your eyes hurt. You've listed 50 problems you personally have. None of them feel like the one. The ones that excite you seem unsellable. The ones that seem sellable bore you.

Meanwhile, you see people launching things every week. Some are worse builders than you. They're not smarter. They just found something. And you can't figure out how they knew where to look.

The stuckness isn't "I don't have ideas." It's: I have too many half-ideas and no reliable way to filter them. You're missing a process that turns "vague dissatisfaction" into "a specific person with a specific problem they'll pay to solve right now."


Why the Usual Fixes Fail

1. "Scratch your own itch" assumes your itch is representative.

Your problems are idiosyncratic. You're a developer who automates everything. Most people don't want to self-host. They don't want a CLI. They want a button that works. Building for yourself often produces tools only you understand.

2. "Talk to customers" is circular when you don't know who the customer is.

You can't interview "SaaS founders" or "marketers." That's not a person with a problem. That's a demographic. Without a specific context—what are they doing right now when the pain hits?—interviews turn into polite conversations that yield nothing actionable.

3. Mining Reddit/Twitter/Reviews for complaints produces noise, not signal.

People complain about everything. "Jira is slow" isn't an opportunity—it's a fact of life. "I spend 6 hours every Friday manually reconciling Stripe payouts against NetSuite invoices because the CSV export drops metadata" is an opportunity. The second one requires you to know the workflow. The first one doesn't.

4. Frameworks like "Jobs to Be Done" or "Painkiller vs Vitamin" are diagnostic, not generative.

They help you evaluate an opportunity you already have. They don't help you find one. You're trying to use a thermometer to cook dinner.

5. Waiting for "founder-market fit" is a trap.

You don't discover founder-market fit by thinking. You discover it by doing the work in a domain until you see the seams. The fit comes after the exposure, not before.


Step-by-Step Solution

Step 1: Pick Three Adjacent Domains You Can Access

Don't pick "industries." Pick workflows you can observe or participate in this week.

Examples:

  • Your current company's finance close process
  • The agency your friend runs (onboarding clients, reporting, scope creep)
  • The nonprofit board you sit on (grant tracking, volunteer scheduling)
  • Your partner's dental practice (insurance verification, recall campaigns)
  • The Discord community you moderate (onboarding, event coordination, conflict resolution)

Constraint: You must be able to watch the work happen or do the work yourself for at least 4 hours total across the next two weeks. No "I know a guy." You need direct access.

Write down three. Rank them by: (a) how much access you have, (b) how much money flows through the workflow, (c) how much the people involved complain specifically (not generally).

Pick the top one. This is your observation target.


Step 2: Shadow One Complete Cycle

Pick one person who executes the core workflow in your target domain. Ask to shadow them for one full cycle of the work. Not an interview. Shadowing.

  • If it's monthly close: sit with the controller for the 5-day close.
  • If it's client onboarding: watch the PM handle two new clients from signed contract to kickoff call.
  • If it's insurance verification: sit with the front desk for a full morning.

Rules:

  • No questions during the work. Only "what are you doing right now?" and "why that step?"
  • Take timestamped notes: time, action, tool, friction point, workaround, emotion (sigh, curse, pause, duplicate entry).
  • Capture the artifacts: the spreadsheet, the PDF, the email thread, the sticky note, the Slack message.

You are looking for manual bridges—places where a human moves data between two systems, checks something by eye, remembers a rule, or re-does work because the first pass wasn't trusted.

Deliverable: A timeline of the workflow with every manual bridge highlighted. Minimum 15 steps. At least 3 manual bridges.


Step 3: Quantify One Manual Bridge

Pick the manual bridge that:

  • Happens every cycle (daily/weekly/monthly)
  • Takes >30 minutes per cycle
  • Involves a rule set the human knows but the software doesn't
  • Has a clear "done" state (reconciled, verified, sent, approved)

Now quantify it for that specific person:

Metric How to Get It
Time per cycle Stopwatch during shadowing
Cycles per month Ask: "How often do you do this?"
Error rate Ask: "How often do you have to redo it?"
Cost of error Ask: "What happens if this is wrong?"
Current workaround You observed it
Tools involved You observed them

Example output:

"Maria spends 45 minutes every Tuesday reconciling 200 Stripe payouts against NetSuite invoices. The CSV export drops the metadata.customer_id field, so she VLOOKUPs by amount+date, which fails 12% of the time when amounts match. Each failure takes 8 minutes to resolve manually. A mistake means the monthly close is wrong and the CFO escalates. She uses Stripe Dashboard, NetSuite, Excel, and a printed cheat sheet."

That is a quantified problem statement. Not "finance teams struggle with reconciliation." This specific person, this specific time, this specific failure mode.


Step 4: Verify Willingness to Pay—Without Pitching

Do not pitch a solution. Do not say "I'm building X." Instead, ask the person you shadowed (or their boss):

"I noticed you spend ~3 hours/month on [manual bridge]. If that were automated reliably, what would that be worth to you/your team? Not in dollars—what would you do with the time? What risk goes away?"

Listen for:

  • "We'd close two days faster" → speed value
  • "The CFO wouldn't escalate" → risk reduction
  • "Maria could finally work on [higher-value project]" → opportunity cost
  • "We'd stop overpaying vendors" → direct savings

If the answer is "eh, it's annoying but fine," discard this bridge. Go back to Step 3. Pick another.

You need a consequence that someone cares about. Not a complaint. A consequence.


Step 5: Build the Smallest Possible Bridge-Replacer

You are not building a product. You are building a bridge replacement.

Scope it to: one cycle, one user, one manual bridge, zero UI polish.

Options, in order of preference:

  1. Script + shared spreadsheet (Google Apps Script, Python + Sheets API)
  2. Zapier/Make/n8n workflow + a Google Form for trigger
  3. Browser extension that scrapes + writes (if no API)
  4. Macro/shortcut inside their existing tool (Excel VBA, Notion button, Airtable script)

Rules:

  • It runs their data, in their environment, with their permission.
  • You sit with them the first 3 times they use it.
  • You fix every failure in <24 hours.
  • You do not add features. You only make the bridge work.

Success criterion: They use it for 3 consecutive cycles without you present, and the error rate drops to zero.


Step 6: Expand Laterally, Not Vertically

Once the bridge works for one person in one cycle, do not add features.

Start here

Top comments (0)