# Opportunity Hypothesis Brief (`fifthrow/innovation-opportunity-decision-briefing`) Actor

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.

- **URL**: https://apify.com/fifthrow/innovation-opportunity-decision-briefing.md
- **Developed by:** [FifthRow](https://apify.com/fifthrow) (community)
- **Categories:** AI
- **Features:** Limited permissions
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

$9.38 / opportunity hypothesis brief report

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event

## What's an Apify Actor?

An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.

Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md.

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.

Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run.

For examples already wired to this Actor's own input schema, see the [API](#api) section below.

Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`).

# README

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.

# Changelog

This Actor's version history is a separate document: https://apify.com/fifthrow/innovation-opportunity-decision-briefing/changelog.md

# Actor input Schema

## `INTENDED_HANDOFF` (type: `string`):

Name the next Innovation decision and what would make a hypothesis useful. Example: Venture Opportunity Framing; prioritize frequent costly problems before proposing solutions. Suggested examples: Venture Opportunity Framing; Customer problem prioritization; Concept investigation decision. Other clear text values are also accepted.

## `OPPORTUNITY_SCOPE` (type: `string`):

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. Suggested examples: UK café cash flow; US rural broadband access; German home energy billing. Other clear text values are also accepted.

## `TEAM_EVIDENCE` (type: `string`):

Private: Add dated team notes, observations and constraints, or write Not tracked. Example: 6 November discovery notes; owners reconcile card settlements manually each week. Suggested examples: Not tracked; 6 November discovery notes; Weekly settlement reconciliation. Other clear text values are also accepted.

## Actor input object example

```json
{
  "INTENDED_HANDOFF": "Venture Opportunity Framing",
  "OPPORTUNITY_SCOPE": "UK café cash flow",
  "TEAM_EVIDENCE": "Not tracked"
}
```

# Actor output Schema

## `OUTPUT` (type: `string`):

Complete structured JSON result stored as KVS OUTPUT.

## `markdown` (type: `string`):

Portable markdown report stored as KVS REPORT.md.

## `overview` (type: `string`):

Run overview plus summary, company impact, answers, and Q\&A as default dataset items.

## `report` (type: `string`):

Self-contained HTML report stored as KVS REPORT.html.

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {
    "INTENDED_HANDOFF": "Venture Opportunity Framing",
    "OPPORTUNITY_SCOPE": "UK café cash flow",
    "TEAM_EVIDENCE": "Not tracked"
};

// Run the Actor and wait for it to finish
const run = await client.actor("fifthrow/innovation-opportunity-decision-briefing").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = {
    "INTENDED_HANDOFF": "Venture Opportunity Framing",
    "OPPORTUNITY_SCOPE": "UK café cash flow",
    "TEAM_EVIDENCE": "Not tracked",
}

# Run the Actor and wait for it to finish
run = client.actor("fifthrow/innovation-opportunity-decision-briefing").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{
  "INTENDED_HANDOFF": "Venture Opportunity Framing",
  "OPPORTUNITY_SCOPE": "UK café cash flow",
  "TEAM_EVIDENCE": "Not tracked"
}' |
apify call fifthrow/innovation-opportunity-decision-briefing --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,fifthrow/innovation-opportunity-decision-briefing"
        }
    }
}
```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/zTXgnm9znmcPS982R/builds/f4lROSPyLLRSrSqTx/openapi.json
