Venture Validation Review
Pricing
$20.31 / venture validation review report
Venture Validation Review
Reviews the evidence a venture team has gathered on a concept, assumption by assumption, and checks the most critical claims against public market, competitor and pricing evidence. It grades how strong each piece of evidence is, updates the... Returns HTML, Markdown, JSON, and dataset rows.
Reviews the evidence a venture team has gathered on a concept, assumption by assumption, and checks the most critical claims against public market, competitor and pricing evidence. It grades how strong each piece of evidence is, updates the business-case economics and risks, and tests the concept against gate-readiness criteria. The result is a readiness recommendation to refine the concept, repeat a test, prepare for the portfolio gate, or close, with the next tests to run. It does not make the funding or portfolio decision.
You receive:
- A recommendation with its confidence and the assumptions that decide it
- An assumption-by-assumption assessment with evidence strength, updated economics and a risk register
- Readiness against eight gate criteria and the next validation tests, each with a success threshold and stop signal
It returns a decision report in HTML, Markdown, JSON, and dataset rows.
Runtime
Typical runtime: about 40 minutes.
Summary
For {PARENT_COMPANY}, this review tests whether {VENTURE_CONCEPT} is ready for refinement, another validation test, or preparation for a portfolio gate—not a funding decision. It examines the team’s {VALIDATION_EVIDENCE} assumption by assumption, distinguishing observed or committed behavior from stated intent, estimates, and untested claims.
The review checks relevant claims against public market, competitor, pricing, and parent-company offer evidence. Deliverables include a readiness recommendation with confidence, an assumption assessment, an updated economics view with contribution and break-even analysis, a prioritized risk register, and a matrix covering all eight gate criteria. For concepts needing further validation, it also identifies proposed tests, success thresholds, stop signals, and findings that could change the recommendation.
Methodology
We structure {VENTURE_CONCEPT} into testable assumptions, assign criticality, and link each claim to the relevant items in {VALIDATION_EVIDENCE}. Evidence is assessed for strength, fit, limitations, and threshold results, with observed or committed behavior distinguished from stated intent and estimates. Claims that can be checked publicly are compared with dated market, competitor, pricing, regulatory, and parent-offer sources; customer-specific or operational questions remain dependent on team evidence.
We then assess each assumption, update the economics using evidenced values and bounded estimates where possible, calculate contribution and break-even, and compare key drivers with relevant public benchmarks. Risks are tied to evidence-backed uncertainties and dependencies. The recommendation follows the stated decision logic, while readiness is assessed against eight fixed gate criteria. Proposed tests include advance success thresholds and stop signals; sponsor decisions are kept separate from evidence-based findings for {PARENT_COMPANY}.
Inputs
PARENT_COMPANY(text): Parent Company. The company sponsoring the venture. Example: ENGIEVALIDATION_EVIDENCE(text): Validation Evidence. What you tested, any success thresholds set beforehand, and what happened, with numbers. A line or two is enough; the App researches the rest. Example: 12 site interviews; 3 non-binding pilot LOIs; integration quote EUR 35-55kVENTURE_CONCEPT(text): Venture Concept. The concept in one or two lines: customer, problem, offer and price, and the country or market. Example: flex-as-a-service for Belgian industrial sites, 30% revenue share
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.


