Skip to main content
Back to all page templates

Page template

Evidence-led venture story template

A venture page that leads with beneficiary, current evidence, mechanism and next test.

Pattern ID

evidence-led-venture-story

Implementation

Reusable component specimen

Live examples

7

Where this page type is used and why

Use when one venture needs enough story to be understood without becoming a sales promise.

/intentions/ventures/berleytrails

Inspect the Map Your Fish venture as a dogfood experiment with bounded evidence.

Inspect BerleyTrails without mistaking the venture page for validated proof.

Proof signal: A reader can tell what is being tested, what remains unproved, and where the business-plan evidence lives.

Open live page · Implementation source

/intentions/ventures/betterpractice

Inspect Better Practice as a coaching and practice-loop venture hypothesis.

Inspect Better Practice without mistaking the venture page for validated proof.

Proof signal: A reader can distinguish the coaching promise, evidence boundary, and next proof route.

Open live page · Implementation source

/intentions/ventures/howzus

Inspect Howzus as an AI-native open-market holiday-planning hypothesis.

Inspect Howzus without mistaking the venture page for validated proof.

Proof signal: A reader can name the traveller job, market response loop, and unproved demand.

Open live page · Implementation source

/intentions/ventures/prettymint

Inspect PrettyMint as a platform-dependent venture experiment with business-plan evidence.

Inspect PrettyMint without mistaking the venture page for validated proof.

Proof signal: A reader can tell what platform dependency is being tested and where the assumptions sit.

Open live page · Implementation source

/intentions/ventures/southernhagen

Inspect Southernhagen as a Copenhagen–Aotearoa experiment proposal, not institutional proof.

Inspect Southernhagen without mistaking the venture page for validated proof.

Proof signal: A reader can name the reciprocal table, evidence boundary, and smallest responsible test.

Open live page · Implementation source

/intentions/ventures/stackmates

Inspect Stackmates as the coordination-substrate venture experiment.

Inspect Stackmates without mistaking the venture page for validated proof.

Proof signal: A reader can name the infrastructure promise, dogfood boundary, and next proof route.

Open live page · Implementation source

/intentions/ventures/touchforfun

Inspect Touch For Fun as an experiment record with explicit evidence limits.

Inspect Touch For Fun without mistaking the venture page for validated proof.

Proof signal: A reader can name the proposed beneficiary, uncertainty, and next test.

Open live page · Implementation source

Components used to assemble the UI pattern

  • VentureHero
  • VentureCollectionLink
  • venture-specific sections
  • Score and metric displays

Public page contract registry · Primary implementation example

Rendered specimen

The specimen uses public-safe fixture copy. It proves rendering shape only; it does not prove beneficiary value or authorise work.

Open specimen in a full page

Presentation considerations

  • Lead with evidence boundary before persuasion.
  • Use public-safe venture copy only; do not import private strategy as public warrant.
  • Keep next test bounded and human-owned.

Alternative design choices