1const e=`## What the valuation engine does 2 3xPharma produces a risk-adjusted net present value for each asset, alongside the ranges and sensitivities that buyers and suppliers actually need to negotiate against the same numbers. The output is not a single point estimate â it's a range, plus a clear view of which assumptions move the deal. 4 5## What you'll see 6 7For every published asset, the valuation surfaces: 8 9- A **P10 / P50 / P90 NPV range** so you can see optimistic, expected, and pessimistic scenarios at once. 10- A **probability-of-success view** that decomposes risk across scientific, clinical, regulatory, and commercial layers. 11- A **sensitivity breakdown** showing which assumptions move NPV the most â usually peak penetration, pricing, transition probabilities, and discount rate. 12- A **comparable deals view** so the valuation is anchored to real, published transactions rather than abstract math. 13 14## Why a range, not a single number 15 16Biotech assets are option-like: at every stage gate the holder can choose to continue, pause, or out-license. A single NPV number hides that optionality and systematically undervalues programs with asymmetric upside. 17 18xPharma's engine treats each future stage as a decision, runs many simulated outcomes, and reports the resulting distribution. That gives you a defensible view of the asset's value at a P50 â and a clear sense of how wide the bands are around it. 19 20## Where the assumptions come from 21 22Inputs draw from the asset's own profile (target, mechanism, stage, indication), industry-standard transition probabilities by indication and modality, and a curated set of comparable deals. Suppliers can adjust assumptions for their own asset; buyers see the same inputs surfaced as part of the valuation. 23 24The goal is not to replace a buyer's diligence model, but to give both sides a shared starting point that is grounded in real data rather than slide-deck math. 25`;export{e as default};
Line numbers count LF bytes from the start of the resource, as the search results do. Vendor segments are library code the classifier recognised; they are stored but not indexed. Bytes are shown as Latin1 characters, one per byte.