Case Study: Product Discovery Pipeline

The hardest question in product development isn't "can we build this?"; it's "should we?"

Solo operators and small teams face this problem acutely. Without a research department, a sales team feeding back market signals, or an advisory board to challenge assumptions, product decisions default to intuition. Intuition is fast, but it's biased toward what the builder finds interesting rather than what the market actually needs.

We needed a system that could surface real pain (not hypothetical pain, not "wouldn't it be cool if" pain, but people describing specific frustrations in their own words) and then score, filter, and stress-test those signals into a prioritized portfolio of product opportunities.

The pipeline starts where practitioners actually complain: professional subreddits.

We built a mining system that scans targeted communities across 12 professional verticals: from CPAs and veterinarians to eCommerce sellers and recruiters. The system uses Perplexity's Sonar model as a semantic search layer to find contextually relevant pain point posts, then scores each result locally using a weighted formula that combines engagement signals (upvotes, comment depth) with keyword pattern matching across 80+ signal categories.

The signal categories aren't generic sentiment analysis. They're organized by the type of pain being expressed: wish/desire patterns ("I wish there was..."), tool-seeking behavior ("what do you use for..."), frustration signals ("drives me crazy"), process problems ("manual process," "spreadsheet," "duct tape"), time and cost complaints, and specific software grievances. Each category carries different weight because they indicate different levels of actionable demand.

The output is a scored, dated report organized by vertical. Each run produces a snapshot of what's hurting practitioners right now, not what was hurting them when a market report was published six months ago.

Raw pain signals aren't product opportunities. A post scoring 917 in r/accounting might be venting about Big 4 burnout, real pain, but not something a software product solves. The pipeline's second stage filters and contextualizes.

Tier 1 identification. Posts are clustered by theme within each vertical. Clusters with multiple high-scoring posts across different subreddits indicate systemic pain rather than individual frustration. From an initial scan of 200+ matches, 16 clusters cleared the threshold for deeper investigation.

Competitive research. For each Tier 1 cluster, we mapped the existing competitive landscape: incumbents, pricing, recent M&A, market sizing, and, most importantly, the specific gap between what exists and what practitioners are asking for.

Scoring model. Each opportunity was scored across multiple dimensions: pain severity, market size, competitive gap, technical feasibility, time to revenue, and capital requirements. The weights were calibrated to favor opportunities with high pain, low capital requirements, and fast time-to-revenue, reflecting the constraints of a solo operator with $5K in starting capital.

The result was a ranked portfolio of 16 validated opportunities with documented evidence trails: not hunches, not brainstorms, but scored assessments backed by real practitioner language.

A ranked list of opportunities isn't a strategy. Choosing which to pursue, and in what order, requires weighing tradeoffs that a scoring model can't capture: seasonal timing, shared infrastructure potential, cross-sell paths, and the sequencing constraints of a single operator.

Solo product development creates a specific risk: decisions go unchallenged. Without a team to push back, confirmation bias compounds. The builder gravitates toward what's exciting rather than what's strategically sound.

To address this, we developed a structured debate methodology where AI agents simulate distinct executive perspectives: CEO (commercial viability and cash flow), CMO (go-to-market and positioning), CPO (product scope and technical feasibility), and a mandatory Contrarian role whose job is to challenge emerging consensus before it becomes groupthink. Domain experts are added as needed.

The pipeline produced a three-phase launch strategy:

Phase 1 targets the opportunity with the lowest capital requirement and fastest time-to-revenue, chosen not because it scored highest on pain, but because it was the only product feasible at $5K starting capital. Revenue from Phase 1 funds Phase 2.

Phase 2 targets the highest-pain opportunity (score: 452), timed to a seasonal window when the target buyers are receptive. Phase 1 and Phase 2 share infrastructure, reducing build cost.

Phase 3 targets higher contract values in a different vertical, with a longer sales cycle that requires Phase 1+2 revenue to sustain operations during the ramp.

Each phase has defined success triggers and kill thresholds. The portfolio isn't a wishlist; it's a sequenced plan with explicit criteria for when to advance and when to stop.

Real pain signals beat market reports. A practitioner writing "I spend 3 hours a day on customer emails and it's killing me" at 2am is a more reliable signal than a market sizing report that estimates TAM at $27B. The mining system surfaces the former; competitive research contextualizes it with the latter. Both matter, but the signal comes first.

Structured AI debate is a bridge, not a destination. The methodology catches obvious blind spots and forces explicit tradeoff analysis. It doesn't replace the generative friction of real disagreement between people with different experiences. The Contrarian role is the most valuable; it's the closest approximation to genuine pushback that a solo operator can get.

Kill criteria are the most important output. The natural instinct is to define success metrics. But for a capital-constrained solo operator, knowing when to stop is more valuable than knowing when to celebrate. Every product in the portfolio has a specific, measurable kill threshold.

The pipeline is reusable. The mining scripts, scoring model, and debate methodology aren't specific to eCommerce or CPAs. They work on any vertical where practitioners gather online and complain about their tools. The system produces a new snapshot every time it runs.