Skip to main content

Venture Marketplace Index

Which venture deserves the next unit of attention?

A venture marketplace index helps a reader choose what to inspect, back, join, or kill next. It connects the Tight Five to a portfolio surface: purpose sets the bet, performance ranks the opportunity, platform names what exists, process gives the next action, and people choose the role they can play.

Job​

The index causes comparison toward commitment. It is not a brochure wall.

Use it when a portfolio has enough opportunities that equal-weight cards would hide the real choice. The page must make the best next action easier than wandering through every venture.

Decision Surfaces​

Each card needs these surfaces before it earns a place in the index:

  • Stage — concept, validating, early-stage, or proven.
  • Model — service, SaaS, protocol, community, platform, marketplace, or hybrid.
  • Proof state — REALITY, DREAM, or CONSUMED.
  • Composite score — a comparison score with a visible caveat that it measures conviction, not truth.
  • Revenue target — rounded yearly target, labelled as a target or projection.
  • Kill signal — the condition that stops the bet.
  • Next action — the verb the reader should take now.

The card can still be beautiful. But beauty is subordinate to comparison.

Proof States​

Use one honest state per capability claim:

  • REALITY — built, proven, and measurable.
  • DREAM — needed and plausible, but not proven.
  • CONSUMED — delegated to a provider, partner, or existing platform.

Do not let one card mix these states without labels. A single proven workflow does not make the whole venture proven.

Chooser Rules​

The page should offer visible controls:

  • Sort by composite score, revenue target, stage, and newest.
  • Filter by stage and model.
  • Show the result count after every change.
  • Keep a reset path for empty results.
  • Make the whole card scannable before the click.

The default view should answer: "Which opportunity deserves attention first, and why?"

CTA Verbs​

Generic "view" actions waste the tension the card created. Match the call to action to the venture state:

  • Proven — See the proof.
  • Validating — Watch it prove out.
  • Early stage — Get in early.
  • Concept — Pressure-test this.

If the verb cannot be made specific, the card probably lacks a clear next action.

Trust Layer​

A venture marketplace earns trust by making downside visible.

  • Use yearly targets instead of oddly precise weekly math.
  • Label projected numbers as projected.
  • Show kill dates when available.
  • Recover common slug drift with redirects or route-recovery pages.
  • Make a venture-like 404 point back to the marketplace.
  • Use data attributes or structured data for stage, model, score, target, proof state, kill date, and next action.

Human trust and agent readability are the same work here: the surface must expose the decision structure it asks the reader to use.

Source Trail​

  • Stripe, "Marketplaces vs platforms" — supports the distinction between a transaction-oriented marketplace and a broader platform. Interpretation: a venture index should behave like a comparison and commitment surface when it presents multiple opportunities.

Procedure​

  1. List every venture in the portfolio.
  2. Assign each venture one stage and one primary model.
  3. Name the current proof state for the core claim.
  4. Add the composite score and the caveat behind it.
  5. Round the revenue target to a yearly number.
  6. Write one kill signal with a date or review cadence.
  7. Choose the stage-aware CTA verb.
  8. Add sort and filter controls only after the fields above are complete.
  9. Run a cold-reader chooser test: can the reader pick one next action in under two minutes?

Kill Signal​

If cold readers cannot explain why one card is higher priority than another, the index is still a gallery. Rebuild the comparison surfaces before adding more ventures.

Failure Modes​

  • Gallery drift — cards look distinct but expose no comparison logic.
  • False precision — weekly revenue math looks exact while the venture is still projected.
  • Proof blur — a DREAM capability inherits trust from one unrelated REALITY proof.
  • Dead route — natural slug guesses or old shared links end in a cold 404.
  • Generic action — every card asks the reader to "view" instead of resolving its stage-specific tension.

Context​

Questions​

Which comparison field would change the next commitment if it were wrong?

  • Which card should a founder inspect first, and what field made that obvious?
  • Which venture should an operator ignore for now, and what kill signal protects that decision?
  • Which missing field would stop an engineer from building the chooser without guessing?