Opportunity Hypothesis Brief avatar

Opportunity Hypothesis Brief

Pricing

$9.38 / opportunity hypothesis brief report

Go to Apify Store
Opportunity Hypothesis Brief

Opportunity Hypothesis Brief

Turns desk evidence into distinct user and problem hypotheses for an Innovation team. It checks public signals and team observations against existing alternatives, counter-evidence and missing proof. The result is a prioritized set of sourced... Returns HTML, Markdown, JSON, and dataset rows.

Pricing

$9.38 / opportunity hypothesis brief report

Rating

0.0

(0)

Developer

FifthRow

FifthRow

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

10 days ago

Last modified

Categories

Features

Limited permissions

Share

Turns desk evidence into distinct user and problem hypotheses for an Innovation team. It checks public signals and team observations against existing alternatives, counter-evidence and missing proof. The result is a prioritized set of sourced hypothesis cards and research questions for the next framing or concept decision.

It returns a decision report in HTML, Markdown, JSON, and dataset rows.

Runtime

Typical runtime: about 29 minutes.

Summary

This brief assesses {OPPORTUNITY_SCOPE} by separating distinct user and problem hypotheses and weighing public observations, current alternatives, contrary evidence, and gaps in proof. It also considers {TEAM_EVIDENCE} as attributed team context—not as representative demand or public fact—and preserves relevant constraints and limits.

For {INTENDED_HANDOFF}, the brief provides a prioritized set of hypothesis cards with confidence, evidence and counter-cases, the observation that could weaken or reverse each priority, and focused questions for the next framing or concept decision. The handoff clarifies which hypotheses merit further Innovation investigation without treating desk evidence as validation or approval to build.

Methodology

The analysis begins by locking the decision and market scope in {OPPORTUNITY_SCOPE}, then distinguishing user groups and problem mechanisms rather than combining unlike populations or outcomes. Public evidence is drawn from relevant, attributable sources; claims retain their dates, links, geography, population, period, and stated limitations. Existing alternatives and credible contrary explanations are considered alongside supportive observations. Figures are included only with a defensible source or explicitly stated basis.

{TEAM_EVIDENCE} is reviewed separately as private, dated team-record evidence, preserving its attribution, sample scope, constraints, contradictions, and missing records. It is not treated as independent public corroboration or representative customer proof; if no team findings are recorded, public evidence remains the basis for assessment. Hypotheses are compared using evidence relevance, plausible significance, counter-evidence, and falsifiable proof questions, then framed for the next decision by {INTENDED_HANDOFF}. No primary research or opportunity validation is implied.

Inputs

  • INTENDED_HANDOFF (text): Intended Handoff. Name the next Innovation decision and what would make a hypothesis useful. Example: Venture Opportunity Framing; prioritize frequent costly problems before proposing solutions.
  • OPPORTUNITY_SCOPE (text): Opportunity Scope. State the user problem, market and geography to explore. Example: cash-flow administration for independent UK cafés; Xero, QuickBooks and Square as public starting points.
  • TEAM_EVIDENCE (text): Team Evidence. Private: Add dated team notes, observations and constraints, or write Not tracked. Example: 6 November discovery notes; owners reconcile card settlements manually each week.

Outputs

Finished runs write files to the Actor key-value store, plus tabular rows in the default dataset.

HTML report (REPORT.html)

A self-contained HTML brief for reading the result in a browser. Use this when you want the formatted decision output, including headings, lists, and cited source links from the App run.

Markdown report (REPORT.md)

A portable markdown document with the same narrative as the HTML report. Use this when you want to paste the output into docs, tickets, or another markdown editor without HTML chrome.

Structured JSON (OUTPUT)

Machine-readable JSON in the key-value store under the OUTPUT key. The object includes:

  • id, status, ready: App run identity and completion state
  • title, catalog_url: display title and FifthRow catalog URL
  • started_at, finished_at, duration_seconds: run timing
  • summary: executive summary text
  • company_impact: implied impact narrative, when the App produced one
  • sections: sectioned App results
  • answers: visible answer objects (title, markdown, sources)
  • questions: Q&A objects produced by the run
  • sources: deduplicated source URLs
  • dataset_items: source rows for the default dataset (oversized dataset writes may omit markdown)
  • report_markdown: full markdown body also stored as REPORT.md

Dataset rows

The default dataset stores rows (run, summary, company_impact, answer, qna) with title, markdown, and sources. Rows that exceed the dataset item size limit are stored with empty markdown.