DEV Community

Alan Descure
Alan Descure

Posted on Originally published at smtm-store.pages.dev

Opportunity Discovery: A Field Guide for When You’re Stuck Guessing

Opportunity Discovery: A Field Guide for When You’re Stuck Guessing

The Problem in Concrete Terms

You are not "lacking ideas." You are drowning in noise.

You have a notebook full of "maybe" concepts, a Trello board of half-baked niches, and a browser history littered with "top 10 business ideas for 2024" articles. You’ve validated nothing. You’ve built nothing. You are stuck in the gap between seeing a problem and knowing someone will pay to solve it.

Concretely, the blockage usually looks like one of three things:

  1. The "Solution in Search of a Problem" Trap: You have a cool tech stack (AI wrapper, no-code tool, Rust CLI) and you are desperately trying to retrofit a market onto it. You are building a hammer and walking around hoping to find a nail that looks like a screw.
  2. The "Passive Consumption" Loop: You read Indie Hackers, Hacker News, and Twitter/X threads about "unmet needs." You nod along. You save the posts. You do zero primary research. You mistake reading about discovery for doing discovery.
  3. The "Vague Pain" Paralysis: You hear "people hate expense reports" or "hiring is broken." That’s not a discovery insight; that’s a category. You don’t know which specific workflow step causes the rage, who owns the budget to fix it, or what they’ve already tried and rejected.

You are stuck because you are treating opportunity discovery as a brainstorming exercise. It is not. It is a sales qualification process performed before you have a product.


Why the Usual Fixes Fail

1. "Scratch Your Own Itch"
This works only if your itch is shared by a budget-holding decision-maker in a reachable market. If your itch is "I want a better markdown editor for my blog," the market size is near zero. If your itch is "I spend 10 hours a week manually reconciling Stripe payouts against NetSuite for my 50-person company," that’s a business. Most people confuse personal annoyance with commercial pain.

2. Keyword Research / SEO Tools
Ahrefs and Semrush tell you what people search for, not what they pay for. High volume keywords often indicate informational intent ("how to invoice"), not transactional intent ("best invoicing software for construction subcontractors"). You end up building content sites when you wanted SaaS, or building features nobody buys.

3. "Talk to 100 Customers" (The Cargo Cult Version)
Founders book 15-minute Zoom calls, ask "Would you use a tool that does X?", get polite "Yeah, sounds cool," and call it validation. This is theater. People are terrible at predicting their future behavior. They are excellent at describing their current suffering and current workarounds—if you ask the right way.

4. Trend Surfing (AI, Web3, No-Code)
Building on a trend is not the same as solving a problem with a trend. Adding "AI-powered" to a landing page does not create product-market fit. It just increases your burn rate on API credits.


Step-by-Step Solution: The "Workback" Method

This process requires zero budget, zero code, and zero audience. It requires access to where your target user already talks and the discipline to shut up and listen.

Phase 1: Define the "Who" Before the "What" (Days 1–2)

Stop looking for ideas. Start looking for constraints.

  1. Pick a constraint set. Choose one of the following filters. Do not mix them.
    • Industry Vertical: "Commercial HVAC subcontractors," "Dental labs," "Independent insurance adjusters."
    • Role/Title: "Fractional CFOs," "DevRel leads at Series B startups," "Executive Assistants to C-suite."
    • Workflow Trigger: "People who onboard 5+ contractors/month," "Teams migrating off Heroku," "Agencies managing >20 Google Business Profiles."
  2. Write your "Anti-Persona." Explicitly list who you cannot serve yet.
    • Example: "No enterprise (procurement > 90 days). No pre-revenue startups (no budget). No non-English markets (support load)."
  3. Verify reachability. Can you find 20 of these people on LinkedIn, Slack communities, Reddit, or industry forums right now? If you cannot message them directly, stop. Pick a different constraint. Discovery requires conversation, not broadcast.

Phase 2: Mine "Complaint Exhaust" (Days 3–7)

Go where the constraint group vents. Do not post. Do not survey. Scrape.

Sources to mine manually (copy/paste into a doc):

  • Reddit: r/[industry], r/[role], r/sysadmin, r/freelance, r/smallbusiness. Search: "hate," "sucks," "manual," "spreadsheet," "workaround," "fired," "lost client."
  • Slack/Discord: Join 3–5 communities. Use search: "anyone know a tool," "how do you handle," "spent all day," "error."
  • G2/Capterra/TrustRadius: Filter 2-star and 3-star reviews for the incumbent tools in that space. Ignore 1-star (bugs/rage) and 5-star (fanboys). 2-3 stars are "It works but this specific workflow is killing me."
  • LinkedIn: Search posts by your target role. Look for "Lessons learned," "Day in the life," "Automating X."

Extraction Protocol: For every signal, copy the verbatim quote, the source link, and the context (what triggered the post?).

  • Bad: "Accountants hate data entry."
  • Good: "Every Friday I spend 3 hours copying CSVs from Bill.com into QuickBooks because the sync breaks on partial payments. I’ve tried Zapier but it chokes on the custom fields. [Link to Reddit comment]"

Stop when: You have 50+ verbatim quotes across at least 15 distinct people.

Phase 3: Cluster into "Jobs to Be Done" (Day 8)

Print your quotes (or use a Miro/FigJam board). Group them by workflow step, not by topic.

  • Topic Cluster: "Invoicing" (useless).
  • Workflow Clusters:
    • Cluster A: "Getting the client to approve the estimate" (Pre-sale).
    • Cluster B: "Chasing partial payments / reconciling" (Cash collection).
    • Cluster C: "Formatting the invoice for the client's specific AP portal" (Compliance/Format).

Score each cluster on three axes (1–5):

  1. Frequency: How often does this step happen? (Daily > Monthly).
  2. Pain Intensity: "I want to quit" > "It's annoying."
  3. Workaround Cost: Are they paying humans, buying duct-tape software, or losing revenue right now?

Pick the top cluster. This is your Opportunity Hypothesis. It must be a specific, repeatable workflow step where money or time is actively burning.

Phase 4: The "Switch Interview" (Days 9–14)

You need 5–8 conversations. Not "feedback calls." Switch Interviews. You are investigating a "switch" from a current behavior (workaround) to a new behavior (your future product).

Recruit: DM the people you scraped in Phase 2.

"Saw your comment about [specific pain]. I’m researching that exact workflow for a side project. Not selling anything—just want to understand how you handle it today. 15 mins, I’ll buy you coffee via Venmo."

The Script (Follow this order rigidly):

  1. Timeline: "Walk me through the last time you did [workflow step]. Start from the moment you knew you had to do it."
  2. Tools/Artifacts: "What did you open? Spreadsheet? Email? Portal? Show me if you can (screen share)."
  3. The Struggle: "Where did you hesitate? What did you re-do? What did you copy/paste?"
  4. The Workaround: "How do you handle [edge case X] today? What happens when it breaks?"
  5. The Cost: "If this went perfectly, how long would it take? How long does it actually take?

Start here

Top comments (0)