Turn community pain evidence into testable business hypotheses

Why use this

1. A founder evaluating an idea may encounter repeated complaints that actually come from the same original story or a narrow community. Enthusiastic discussion can also coexist with evidence that users will not change behavior or pay for a solution.

2. An evidence-and-counterevidence map could support a testable hypothesis rather than a confident business claim. The owner could approve the research scope and choose a falsification test before investing in product work or customer outreach.

Why an agent / simpler alternative

Useful judgment

Group related problems, detect shared origins and distinguish reported pain from evidence of demand.

Simpler alternative

Use direct customer interviews when the target audience is already known and accessible.

Unsuitable when

The task requires private-community access, fabricated demand estimates or unapproved outreach.

Proposed inputs

1. Name

   Approved research plan

   Owner

   Business owner

   Minimum scope

   Target users, communities, question scope and collection boundaries

   Quality check

   Confirm approval before any new evidence gathering.

2. Name

   Supplied evidence packet

   Owner

   Research owner

   Minimum scope

   Permitted excerpts, source links and contrary observations

   Quality check

   Preserve origin, date and selection limitations.

Access and setup — proposed or unknown

Proposed minimum

1. Read-only approved evidence and a separate hypothesis draft.

Compatibility unknowns

1. Unknown: exact runtime, community access, evidence-search coverage and current source availability.

External actions requiring approval

1. Expanding research, contacting participants, collecting private data or overwriting existing artifacts.

Expected deliverable and review checks

Proposed artifact

Ranked hypotheses with evidence clusters, contrary evidence and bounded falsification proposals.

Critical checks

1. Repeated reposts are not counted as independent pain reports.

2. Hypotheses distinguish problem occurrence, buyer identity and unproven willingness to pay.

Missing output evidence

No new workflow run or output inspection is performed for this editorial layer. The linked implementation evidence retains the original source-specific outcome and artifact limits.

Failure signals and proposed responses

1. Signal

   Several posts repeat the same original complaint.

   Why it matters

   Apparent recurrence may be overstated.

   Proposed response

   Group them under one origin and qualify breadth.

2. Signal

   Counterevidence is omitted because it weakens the preferred idea.

   Why it matters

   The output becomes advocacy instead of useful research.

   Proposed response

   Retain the contrary case and propose a test that could reject the hypothesis.

Effort and cost — unknown

Setup work

1. Define research boundaries and hypothesis comparison criteria.

Ongoing review

1. Check evidence independence and choose ethical demand tests.

Unknowns

1. Unknown: market size, payment intent, research effort and test costs.

First check — proposed, unexecuted

Status

proposed_unexecuted

Synthetic fixture

Invented evidence includes three reposts of one complaint and a credible account of an adequate existing workaround.

Acceptance checks

1. Reposts remain one origin.

2. The workaround informs a falsification test.

Stop conditions

1. Unapproved collection, outreach or unsupported commercial metrics are needed.

Limits

1. Editorial hypothesis aid; no demand, viability or end-to-end reliability is independently established.