Venture Opportunity Framing
Pricing
$14.06 / venture opportunity framing report
Venture Opportunity Framing
Finds the new-business spaces where market signals meet a company's own assets and recommends which one to take into concept development. It maps the company's relevant assets and existing initiatives alongside customer problems, market shifts and... Returns HTML, Markdown, JSON, and dataset rows.
Finds the new-business spaces where market signals meet a company's own assets and recommends which one to take into concept development. It maps the company's relevant assets and existing initiatives alongside customer problems, market shifts and active players, then defines bounded spaces and rates each on customer need, attractiveness, crowding, feasibility, parent fit, novelty for the company and the stated venture ambition. The result is a ranked set of opportunity spaces with a recommended pick, the evidence behind it, route options and the first questions concept work must answer. It does not design the venture concept or business model.
You receive:
- A recommended opportunity space, with a runner-up and what would change the call
- A ranked table of every screened space with ratings and evidence confidence
- Space cards with customer problem, parent fit and build, partner or buy options
It returns a decision report in HTML, Markdown, JSON, and dataset rows.
Runtime
Typical runtime: about 1 hour 7 minutes.
Summary
Evaluate where market signals and {SIGNALS_AND_ASSETS} align to create new-business opportunities for {COMPANY} in {TARGET_GEOGRAPHY}, within the boundaries of {VENTURE_MANDATE}. The analysis examines customer problems, market shifts, active competitors, parent-company assets and existing initiatives to frame distinct opportunity spaces and identify potential overlap.
Receive a ranked opportunity table with evidence confidence, bounded space profiles, route options, and a recommendation on which space to advance into concept development. The decision brief compares the leading space with its runner-up, explains the whitespace and size of prize against the mandate, and identifies the key questions concept work must resolve. This gives venture leaders and sponsors a grounded basis for prioritizing where to focus next.
Methodology
First, establish the scope using {COMPANY}, {SIGNALS_AND_ASSETS}, {TARGET_GEOGRAPHY}, and {VENTURE_MANDATE}. Review the company’s current assets, initiatives, published priorities, and ownership status, then map relevant customer problems, market shifts, and active players in the target geography. Use dated sources and distinguish evidence that directly measures a space from adjacent or broader-market context.
Frame distinct candidate spaces around customer segment, problem, use context, and boundary. For each, assess demand and willingness to pay, competitive crowding and whitespace, parent fit, existing-initiative overlap, and possible build, partner, or acquisition routes. Compare sourced revenue ranges with the mandate, rate each dimension on consistent qualitative scales, and calibrate confidence to evidence quality and scope. Apply mandate exclusions and reconcile conflicting facts before making the comparative assessment.
Inputs
COMPANY(text): Company. The parent company that would own the new venture, with its website. Example: ENGIE (engie.com)SIGNALS_AND_ASSETS(text): Signals And Assets. Where to look: the market signal or company asset area to explore, in a line or two; the App researches the assets and the evidence. Example: Flexibility assets at customer sites plus rising B2B demand for energy-as-a-serviceTARGET_GEOGRAPHY(text): Target Geography. Countries or regions where the venture would start. Example: France, Belgium, the Netherlands and GermanyVENTURE_MANDATE(text): Venture Mandate. What the venture must achieve for the parent and what is off-limits. A line or two is enough; the App researches the rest. Example: EUR 50M revenue in 5 years, no residential retail
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 statetitle,catalog_url: display title and FifthRow catalog URLstarted_at,finished_at,duration_seconds: run timingsummary: executive summary textcompany_impact: implied impact narrative, when the App produced onesections: sectioned App resultsanswers: visible answer objects (title, markdown, sources)questions: Q&A objects produced by the runsources: deduplicated source URLsdataset_items: source rows for the default dataset (oversized dataset writes may omit markdown)report_markdown: full markdown body also stored asREPORT.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.


