Decision catalogueMethod

Platform story, asset check: separate them before you commit

Decision problem

Is this raise underwriting a product path or an unresolved platform science project?

Thesis

Platform breadth is not a substitute for asset-level evidence when the check size and financing narrative assume a product path.

Platform-plus-pipeline structures are common in cell therapy, oligonucleotides, degraders, and delivery technologies. They become decision hazards when platform language absorbs the burden of proof that belongs on the lead asset.

A clean claim map labels platform claims and asset claims separately, then asks what evidence would falsify the asset path even if the platform remains interesting. Use of proceeds should map to claim-resolving gates for the check being asked — not to open-ended platform exploration.

When management cannot state the separation, the partnership is negotiating a category bet while pricing an asset round. The Decision Sprint output makes that mismatch explicit.

Claim map

Must-be-true cuts a Decision Sprint memo would force

  • Platform claims and asset claims are labeled and evidenced separately
  • Asset path has falsifiers independent of platform attractiveness
  • Use of proceeds maps to claim-resolving gates for this check size

Decision triggers

Outputs from the claim test that should change the conversation

  • Asset-sized narrative resting only on platform language
  • No evidence that would kill the asset path while leaving the platform intact
  • Proceeds funding open-ended platform work framed as product progress

Related in the catalogue

Facing this cut on a live $1–10M package?

Scope a Decision Sprint for one opportunity under your deal deadline—claim map, risk register, management questions, and partner briefing.