Sign inStart
Demonstration data

Example idea brief · no signup required

A research brief that keeps every source attached

See how a few source passages can lead to a small product hypothesis and a concrete test. This example is authored demonstration data, not evidence of real customer demand.

Research a real problem Inspect the example quotes

The problem to investigate

Small product teams preparing stakeholder or client reviews

Research summaries lose the links behind their findings. The example reviewers copy links into separate documents or reopen their raw notes before a presentation.

ev-1042ev-1089ev-1117ev-1194

Four authored passages illustrate the problem. The audience and proposed product are hypotheses to test.

A focused first version

MVP hypothesis

A small tool that attaches an exact quote and source link to each finding could make a research handoff easier to check.

  • Save a source link and an exact quote beside a finding.
  • Group a few findings into one shareable research brief.
  • Export the brief with each quote and source link intact.

Start without automatic scraping, trend dashboards, or a full research repository.

Inspect the exact passages

These are fixed example records. Highlighted words are exact spans from the authored passage; no quotes were collected from real people for this page.

ev-1042

Example forum

Demonstration data
Our team reviews product research every Friday. I copy every source link into a separate document because our research summaries lose their references. We want to spend that time deciding what to build.

Exact span: 48–151 · authored record

ev-1089

Example review

Demonstration data
Our team reviews product research every Friday. I need to click from a finding straight to the original discussion when stakeholders ask where it came from. We want to spend that time deciding what to build.

Exact span: 48–156 · authored record

ev-1117

Example community

Demonstration data
Our team reviews product research every Friday. Before every client presentation I recheck the raw notes because I cannot audit the synthesis. We want to spend that time deciding what to build.

Exact span: 48–142 · authored record

ev-1194

Example forum

Demonstration data
Our team reviews product research every Friday. Please let me export recommendations with the source records still attached. We want to spend that time deciding what to build.

Exact span: 48–124 · authored record

Validate before building

A proposed experiment, not a forecast.

  1. 01

    Ask about a recent handoff

    Interview five people who prepare product research reviews. Ask them to show the last brief they shared and how they checked its sources.

  2. 02

    Try a manual version

    With permission, turn an existing brief into a document with linked quotes. Ask two interviewees to use it in a real review and observe what still gets in the way.

  3. 03

    Decide whether to build

    Look for a recurring problem, use in another review, and a concrete commitment to try or pay for a prototype. If these are missing, revise the audience or problem before expanding the product.

What this brief cannot tell you

  • How often real teams encounter this problem and how much time it costs.
  • Whether their existing document or research tool already solves it.
  • Who would buy the tool and whether they would pay for it.
An evidence ranking helps you choose what to investigate. It does not establish market size, revenue, or product-market fit.

Find a problem in an audience you know.

Start a free research preview and explore a question of your own, with the source evidence attached.

Start free preview