Partnerships & Milestones — Glossary¶

← Back to glossary index

Concepts that govern how biopharma companies structure partnerships, get paid by them, and prove the events that trigger payment. These terms come up constantly in any conversation with a biotech CFO or BD lead, especially partnership-heavy small-cap biotechs like Adagene.

Terms covered:

Evidence packet
Milestone payment
Development milestone
Regulatory milestone
Commercial milestone
Discovery / nomination milestone
Strategic investment
Co-development agreement
Option agreement
Royalty stack
In-license / out-license
Joint venture (JV)

Evidence packet¶

Definition. In biopharma partnership agreements, partners pay milestone payments when contractually-defined events occur. An evidence packet is the documented proof that the triggering event has happened, in a form the partner's legal, scientific, and finance teams can validate before authorising payment. It is not one document — it is an assembled bundle that travels from sponsor to partner each time a milestone fires.

In practice. A typical evidence packet contains:

Component	What it is	Where it lives today
Trigger documentation	Proof the contractually-defined event occurred (e.g., "IND filing accepted by FDA on date X" or "10th patient dosed in cohort Y")	Regulatory affairs team's inbox + CTMS
Source data extract	The underlying clinical / preclinical / regulatory data the trigger depends on	EDC, CTMS, eTMF, internal R&D records
Quality attestations	That the source data is reliable — monitoring records, query resolutions, data-lock confirmations	CRO monitoring reports, query-log exports
Regulatory artefacts	Copies of FDA / EMA / NMPA submissions, correspondence, IRB approvals, protocol amendments tied to the milestone	Regulatory affairs file shares
Audit trail	The chain showing how the evidence was generated, who signed off, when	Reconstructed from system logs, emails, sign-off records
Contract cross-reference	Linkage to the specific clause(s) in the collaboration agreement being triggered	Legal team's contract management system

Worked example — Exelixis $3M milestone (Adagene, 2026). Exelixis paid Adagene $3M on the nomination of a second SAFEbody-derived masked antibody-drug conjugate. The evidence packet would have included: nomination committee minutes, preclinical data supporting the candidate, cross-reference to the relevant clause in the 2021 Exelixis–Adagene collaboration agreement, GLP/quality attestations on the underlying preclinical data, and a sign-off chain from scientific lead → EVP Clinical Development → CEO → legal → out to Exelixis.

Why it matters. Three reasons evidence-packet assembly takes weeks of effort:

Source data is scattered. CRO Oracle CTMS holds operational data; sponsor Veeva holds the eTMF; EDC holds clinical data; partner data-share folders hold what's already been shared. Hand-pulling from each is the dominant cost.
Quality and audit trails are reconstructed retrospectively. Nobody captures evidence-readiness as the trial runs — it's retrofitted when a milestone fires.
Each partner wants a different format. The same underlying evidence gets re-shaped per partner.

The downstream cost is cash-cycle drag — every week between trigger-event and packet-delivery is a week the partner can't process the payment. At Sanofi/Exelixis/Merck milestone scales (typically $3-25M per event), that's material.

Where Flusso fits. Continuous evidence capture rather than retrospective assembly. As source systems produce data, Flusso ingests it and tags it by milestone-relevance using the Knowledge Area / source-document linkage model. Pre-configured milestone templates define the evidence "slots" in advance. When a trigger fires, the slots are already populated — what was a 3-week scramble becomes a 1-day curation pass. Audit trail is automatic. Partner-specific export formats are standardised once, then reused.

Related: Milestone payment · eTMF · CDISC

Milestone payment¶

Definition. A contractually-defined payment from one party to another in a biopharma partnership, triggered when a specific event occurs. Milestone payments are the dominant economic structure of upstream biotech collaborations, sitting alongside (or replacing) upfront payments and downstream royalties.

In practice. A typical biotech-pharma deal might include:

An upfront payment ($10-100M+) on signing
A series of development milestones tied to clinical progress (FPI of Phase 1, Phase 2 readout, pivotal Phase 3 initiation)
A series of regulatory milestones tied to filings and approvals (IND acceptance, BLA filing, FDA approval, EMA approval, NMPA approval)
A series of commercial milestones tied to sales thresholds ($100M, $500M, $1B annual sales)
Tiered royalty payments on net sales

Adagene's Sanofi deal is illustrative: a $25M strategic investment plus undisclosed downstream milestone potential across the muzastotug Phase 1/2 in 100+ patients, plus a separate option for a third SAFEbody program.

Why it matters. Milestone-driven economics mean cash flow into a small-cap biotech is event-driven, not time-driven. A biotech with a $25M milestone landing in Q2 vs Q3 has a materially different cash position. Speed of milestone realisation = direct runway extension. This is why evidence packet assembly speed is a CFO-level concern, not just a clinical-ops concern.

Where Flusso fits. By compressing evidence-packet cycle time from weeks to days, Flusso compresses the milestone-realisation timeline. At a $5-25M milestone scale, two weeks saved is a measurable cash-cycle benefit per event.

Development milestone¶

Definition. A category of milestone payment tied to clinical-development progression — typically the most numerous milestones in a deal.

In practice. Common development milestones, in roughly chronological order:

IND acceptance — FDA accepts the Investigational New Drug application
First Patient In (FPI) — first patient dosed in a clinical trial
Cohort completion — completion of a dose-escalation cohort or expansion cohort
Phase transition — moving from Phase 1 → Phase 2 → Phase 3
Pivotal trial initiation — start of a registrational study
Last Patient In (LPI) — final patient enrolled in a pivotal trial
Top-line data readout — primary endpoint analysis available
Database lock — clinical trial database locked for analysis

Each is contractually defined in the collaboration agreement with explicit triggering criteria.

Why it matters. Development milestones are the most operationally-controlled — meeting them is largely a function of trial execution speed and quality. Slow site activation, slow enrolment, or protocol deviations directly delay milestone payments and therefore cash inflow.

Where Flusso fits. Real-time visibility on enrolment velocity, site activation, and trial-status milestones means the operations team detects slip earlier and the finance team forecasts cash inflow more accurately.

Related: Milestone payment · Enrolment velocity

Regulatory milestone¶

Definition. A category of milestone payment tied to regulatory filings or approvals — typically larger individual payments than development milestones because they de-risk the asset substantially.

In practice. Common regulatory milestones:

IND / CTA acceptance in the first major market (US, EU, China)
Priority Review designation or Breakthrough Therapy designation
BLA / NDA / MAA filing acceptance
FDA Advisory Committee positive vote
First approval in a major market (FDA, EMA, NMPA, PMDA)
Approval in second / third major market
Label expansion approval (new indication added)

Regulatory milestone payments often exceed $50M each and can exceed $100M for first-major-market approval.

Why it matters. Regulatory milestones are gating events for the commercial phase of an asset's life and therefore for the much larger commercial milestones and royalties downstream. A delayed regulatory milestone often delays everything that follows.

Where Flusso fits. Indirect — Flusso supports the regulatory submission process by providing audit-trail evidence and CDISC-aligned data exports, but the regulatory decision itself sits outside the platform.

Related: Milestone payment · IND / NDA / BLA / MAA

Commercial milestone¶

Definition. A category of milestone payment tied to post-launch commercial performance, typically structured as one-time payments when annual or cumulative sales cross specific thresholds.

In practice. Common commercial milestone tiers:

First commercial sale in major market
Annual net sales thresholds: $100M, $250M, $500M, $1B, sometimes $2B+
Cumulative net sales thresholds: $500M, $1B, $5B

Commercial milestones can run into the hundreds of millions and dominate the long-tail value of a successful asset.

Why it matters. Commercial milestones realise only after launch and depend on commercial execution by the partner who licensed the asset (typically the larger pharma in the relationship). They're the "blockbuster bet" portion of the deal economics.

Where Flusso fits. Out of scope — Flusso operates in the development and trial-execution phase, not post-launch commercial.

Related: Milestone payment

Discovery / nomination milestone¶

Definition. Smaller milestone payments tied to events upstream of clinical development — typically the selection of a development candidate or the nomination of a novel program against a target.

In practice. Common discovery / nomination triggers:

Target nomination — identification of a validated target for a partnered program
Lead candidate selection — selection of a specific molecule to advance into IND-enabling studies
Development candidate (DC) nomination — formal nomination of the candidate for IND-enabling work
IND-enabling study completion — successful completion of IND-enabling tox/pharm

The Exelixis-Adagene $3M milestone (2026) on second SAFEbody nomination is a typical example.

Why it matters. Discovery milestones are typically smaller ($1-10M) but more frequent than development milestones, and they require evidence packets too. For a discovery-platform biotech (like Adagene with SAFEbody), nomination milestones across multiple partners can aggregate to material annual revenue.

Where Flusso fits. The same evidence packet compression logic applies — discovery milestones often require even more cross-system evidence assembly than development milestones because the supporting data lives in lab notebooks, internal R&D systems, and external CRO reports rather than structured trial systems.

Related: Evidence packet · Milestone payment

Strategic investment¶

Definition. An equity investment by a partner (typically large pharma) into a biotech, structured alongside or in lieu of an upfront partnership payment. Sometimes at a premium to market price; sometimes with rights attached (board observer seats, future-round participation rights, ROFR on subsequent licensing).

In practice. The Sanofi $25M strategic investment in Adagene (2026, alongside the muzastotug 100-patient combination program) is a textbook example. The investment serves several purposes simultaneously:

Provides non-dilutive (from the biotech's perspective) deal economics
Aligns the partner's interest with the biotech's long-term success
Signals partner confidence to the market (and to other potential partners)
Often comes with information rights or governance rights

Why it matters. Strategic investments are often the cleanest signal of real partner conviction. Pharma writes equity cheques carefully — a $25M strategic investment from Sanofi tells the market that Sanofi believes muzastotug is a real asset.

Where Flusso fits. Out of scope as an instrument, but the operational visibility Flusso provides directly supports the information rights that strategic investors typically negotiate. Partners with board observer or information rights want clean operational reporting — Flusso provides it on demand.

Co-development agreement¶

Definition. A partnership structure where two parties (typically a biotech and a pharma, or two pharma companies) jointly develop an asset, sharing both costs and downstream economics. Distinct from a pure licensing deal where one party transfers rights to the other in exchange for milestones and royalties.

In practice. Co-development agreements typically include:

A cost-share ratio (e.g., 50/50, 60/40, 80/20)
Joint governance through a Joint Steering Committee (JSC) and operational committees
Cost-true-up reconciliations (typically quarterly)
Profit-share ratio post-launch (often distinct from cost-share ratio)
Defined operational responsibilities (one party usually leads clinical operations; the other contributes specific expertise or assets)

Why it matters. Co-development is operationally heavier than licensing — both parties' clinical, regulatory, and commercial teams interact across the program. The coordination overhead is real and recurring.

Where Flusso fits. Co-development relationships are exactly where the Flusso orchestration value compounds. Both parties need decision-ready operational views; cost-true-up reconciliations need clean trial-cost attribution; JSC packs need consolidated multi-party views. Flusso reduces the meeting-prep overhead that dominates co-development governance.

Option agreement¶

Definition. A partnership structure where one party pays for the right (but not the obligation) to license an asset, an additional program, or rights in additional indications/territories at a future date. Common in early-stage discovery deals and platform partnerships.

In practice. A typical option deal might include:

Upfront payment for the option itself (e.g., $5-20M)
Option exercise fee (paid only if option exercised, e.g., $20-100M)
Downstream milestones and royalties triggered on option exercise
Defined option exercise window (e.g., post-Phase-1 data readout)

The Sanofi-Adagene relationship includes an option for a third SAFEbody discovery program — illustrating the platform-extension pattern.

Why it matters. Options give the partner cheap optionality on platform-derived assets while providing the biotech with non-dilutive funding. The biotech bears the data-generation cost; the partner pays only if the data warrants it.

Where Flusso fits. Option exercise decisions depend heavily on data quality and timeliness. A clean evidence base presented to the partner during the option window can mean the difference between option exercise and option expiry.

Related: Strategic investment · Evidence packet

Royalty stack¶

Definition. The cumulative royalty obligations on a single asset from multiple upstream licensors, technology providers, or partners. When an asset incorporates IP from multiple sources, royalties to each source "stack" on top of each other and reduce the launching company's net economics.

In practice. Royalty stacks often include:

Royalties to the original biotech that out-licensed the asset
Royalties to platform technology providers (e.g., antibody discovery platforms, ADC linker chemistry providers)
Royalties to academic institutions whose patents underpin the asset
Royalties to manufacturing technology providers

A typical royalty stack might total 15-30% of net sales — sometimes higher.

Why it matters. A heavy royalty stack constrains the commercial value of an asset and can affect deal-making conversations (partners model net economics, not gross). Adagene's SAFEbody licensees inherit the SAFEbody royalty obligation.

Where Flusso fits. Out of scope — royalty calculation is a finance/legal function downstream of clinical operations.

Related: In-license / out-license

In-license / out-license¶

Definition. The two sides of a licensing transaction. In-licensing is acquiring rights to an asset or technology from another party (you become the licensee). Out-licensing is granting rights in your asset or technology to another party (you become the licensor).

In practice. Most biotech business development conversations are about one or both:

A small biotech out-licenses an asset to large pharma (Adagene out-licensing ADG104 to Sanjin in China is an example)
A large pharma in-licenses a discovery program from a biotech to fill a pipeline gap (Sanofi in-licensing access to muzastotug for the combination program)
A biotech in-licenses enabling technology (linker chemistry, antibody scaffold) to enable its own discovery work

Why it matters. Licensing is the dominant deal structure in biotech — a typical pharma pipeline is heavily licensed-in, and a typical biotech revenue line is heavily licensing-driven. The terms of in/out-licensing transactions define the long-term economics of a program.

Where Flusso fits. Out of scope as a financial instrument. However, the operational visibility Flusso provides supports the information sharing obligations typical in licensing relationships.

Related: Royalty stack · Milestone payment

Joint venture (JV)¶

Definition. A separate legal entity created by two or more parties to develop and commercialise a specific asset or technology together. Distinct from a co-development agreement (which is a contractual relationship without forming a new entity).

In practice. JVs are less common than co-development agreements in biotech but appear in:

Region-specific commercialisation (e.g., a JV to commercialise an asset in China)
Platform technology vehicles (a JV to develop a discovery platform jointly)
High-risk, high-cost programs where neither party wants to bear the full cost on its own balance sheet

Why it matters. JVs have their own governance, their own financials, and their own operational structure — they create more entities to coordinate, not fewer.

Where Flusso fits. A JV-led trial is operationally similar to any other multi-party trial — Flusso's coalition / cross-institutional model handles the multi-party governance natively.

Related: Co-development agreement

← Back to glossary index