Demand Research
Answer one question: is there enough credible demand evidence to make this
product bet now? Keep the result small enough to paste into Product Bet.
First decide whether research earns its cost
Skip research when any applies:
- The ticket is a child contribution; inherit the epic's demand case.
- The work is mandated, compliance-driven, or parity work.
- A cheap reversible experiment can test the assumption more directly.
- The demand claim would not change scope, priority, or the build/no-build call.
When skipping, state the reason in one sentence. Do not manufacture a research
appendix to make the plan look complete.
Research loop
- Frame the single decision neutrally so either outcome is acceptable, and name
the demand claim that could change it. Do not frame the task as proving demand.
- Start with first-party evidence: customer requests, usage, sales/support
records, interviews, or the user's supplied material.
- Fill only meaningful gaps with current external sources. Prefer primary
sources and record the date checked.
- Grade evidence by sacrifice: behavior, money, time, or switching cost beats
stated interest. Separate direct evidence from inference.
- Run a disconfirmation pass: seek the strongest evidence against demand,
including non-adoption, abandonment, unwillingness to pay, and contradictory
usage. Report supporting and contradicting evidence together, name the
strongest alternative explanation, and say what would change the verdict.
When the evidence permits competing interpretations, state the ambiguity
instead of resolving it in the sponsor's favor. Missing negative evidence is
unknown, not support.
- Stop when the decision can be made or the cheapest next validation is clear.
Output
Return exactly these four compact parts:
- Verdict — PRESENT, WEAK, ABSENT, or UNAVAILABLE: one sentence tied to the
decision, not a market-size claim.
- Strongest evidence: up to three dated bullets with links or local evidence
identities; label inferences.
- Gaps: only unknowns that could reverse the verdict.
- Cheapest validation: one concrete next test, or
none when evidence is
already sufficient.
ABSENT and UNAVAILABLE are evidence states, not approval blockers. Do not
invent evidence or upgrade demand strength when sources are unavailable.
Update Problem / Why now with the verdict and strongest decision-bearing
evidence. Do not add a separate research document unless the evidence itself is
too large to cite compactly.
1---2name: demand-research3description: Tests whether a proposed product bet has credible demand. Use when Why now depends on an unresolved, decision-critical demand claim or when the user explicitly asks for demand research. Do NOT use for child features, mandated work, parity work, or when a cheaper experiment can answer the question before research.4---56# Demand Research78Answer one question: **is there enough credible demand evidence to make this9product bet now?** Keep the result small enough to paste into Product Bet.1011## First decide whether research earns its cost1213Skip research when any applies:1415- The ticket is a child contribution; inherit the epic's demand case.16- The work is mandated, compliance-driven, or parity work.17- A cheap reversible experiment can test the assumption more directly.18- The demand claim would not change scope, priority, or the build/no-build call.1920When skipping, state the reason in one sentence. Do not manufacture a research21appendix to make the plan look complete.2223## Research loop24251. Frame the single decision neutrally so either outcome is acceptable, and name26 the demand claim that could change it. Do not frame the task as proving demand.272. Start with first-party evidence: customer requests, usage, sales/support28 records, interviews, or the user's supplied material.293. Fill only meaningful gaps with current external sources. Prefer primary30 sources and record the date checked.314. Grade evidence by sacrifice: behavior, money, time, or switching cost beats32 stated interest. Separate direct evidence from inference.335. Run a disconfirmation pass: seek the strongest evidence against demand,34 including non-adoption, abandonment, unwillingness to pay, and contradictory35 usage. Report supporting and contradicting evidence together, name the36 strongest alternative explanation, and say what would change the verdict.37 When the evidence permits competing interpretations, state the ambiguity38 instead of resolving it in the sponsor's favor. Missing negative evidence is39 unknown, not support.406. Stop when the decision can be made or the cheapest next validation is clear.4142## Output4344Return exactly these four compact parts:4546- **Verdict — PRESENT, WEAK, ABSENT, or UNAVAILABLE:** one sentence tied to the47 decision, not a market-size claim.48- **Strongest evidence:** up to three dated bullets with links or local evidence49 identities; label inferences.50- **Gaps:** only unknowns that could reverse the verdict.51- **Cheapest validation:** one concrete next test, or `none` when evidence is52 already sufficient.5354`ABSENT` and `UNAVAILABLE` are evidence states, not approval blockers. Do not55invent evidence or upgrade demand strength when sources are unavailable.5657Update **Problem / Why now** with the verdict and strongest decision-bearing58evidence. Do not add a separate research document unless the evidence itself is59too large to cite compactly.