Product Development Agreement (PDA)

Examples

Worked examples

Is an instance
A university engineering lab and a medical device company sign a product development agreement to jointly refine a prototype sensor into a market-ready device. The company funds the engineering work and contributes its regulatory and manufacturing expertise; the university contributes its background patent and faculty inventor time. The agreement sets development milestones (working prototype, verification testing, design freeze), assigns ownership of jointly developed improvements to the company subject to a royalty back to the university on the university's background IP, and includes an option for the company to take an exclusive license to the finished product.
Is an instance
An individual inventor with an early-stage prototype enters a product development agreement with a manufacturer to complete engineering, tooling, and regulatory work needed to bring the product to market. The agreement specifies who owns design changes made during development, splits development costs, and sets a royalty or profit-sharing structure for the eventual commercial product -- distinct from simply licensing the inventor's existing patent, because substantial joint development work still has to happen before there is a sellable product.

Counter-examples

Looks similar, but isn't

Not an instance
A university licenses an already-patented, fully developed compound to a pharmaceutical company for further clinical development and commercialization, with no joint development obligation on the university's part. This is a license agreement, not a product development agreement -- the university's role ends at granting rights to existing IP; it is not jointly performing ongoing development work toward the product under milestone obligations.
Not an instance
A federal laboratory and a private company enter a Cooperative Research and Development Agreement (CRADA) under the Federal Technology Transfer Act, 15 U.S.C. 3710a, to jointly develop a technology, with the lab contributing personnel and facilities and the company contributing funding. This looks structurally similar to a product development agreement, but it is a CRADA specifically because one party is a federal laboratory and the agreement is authorized under that federal statute -- the same collaborative-development concept between a university and a company would be a product development agreement (or a sponsored research agreement with a license option), not a CRADA, because no federal laboratory is involved.

Editorial commentary

A product development agreement is a contract between a company and a university, research institution, or individual inventor to jointly develop a specific product or technology toward a commercial outcome. It sits at the intersection of research collaboration and commercialization: unlike a pure license, it obligates the parties to do further development work together, not just transfer rights to something already finished; and unlike open-ended sponsored research, it is oriented around a defined product, with development milestones and pre-negotiated commercialization terms built in from the start.

What a product development agreement typically covers

Because a PDA spans both the development phase and the eventual commercialization of its output, well-drafted agreements typically address:

Ownership of jointly developed IP. The agreement specifies who owns improvements, modifications, and new inventions created during the joint development effort, as distinct from each party’s pre-existing background IP that it brings into the collaboration. This allocation — sole ownership by one party, joint ownership, or ownership with a license-back to the other party — is usually the most heavily negotiated term in the agreement, since it determines who controls the commercial outcome.
Milestone-based development obligations. Rather than an open-ended research relationship, a PDA typically defines specific technical milestones (prototype completion, testing and verification, design freeze, regulatory submission readiness) with associated timelines, and sometimes funding tied to each milestone. Missing milestones is a common trigger for termination or renegotiation rights.
Contribution and cost-sharing. The agreement allocates who funds the development work, who contributes personnel, facilities, or existing background IP, and how development costs are shared or reimbursed.
Path to commercialization. Because the point of a PDA is a marketable product, the agreement usually specifies what happens once development succeeds — commonly an option or a pre-negotiated license (exclusive or non-exclusive, with defined field of use and royalty terms) for the funding party to bring the finished product to market. See CASRAI’s License Agreement entry for how that downstream license is typically structured.
Publication and confidentiality. As with a sponsored research agreement, a university partner will typically negotiate the right to eventually publish results, subject to a reasonable sponsor review period to protect patentability and confidential information.

How it differs from adjacent agreement types

Product development agreements are frequently confused with three other instruments that share some of the same DNA:

vs. License Agreement. A license agreement grants rights to IP that already exists — the licensor is not obligated to do further development work as part of the deal. A product development agreement, by contrast, is built around ongoing joint development; the product does not yet exist in market-ready form when the agreement is signed. In practice, many real-world deals combine both: a PDA governing the development phase, followed by (or including an option for) a license agreement once the product is ready to commercialize.
vs. Sponsored Research Agreement (SRA). A sponsored research agreement funds a research program, which may or may not be aimed at a specific commercial product — much sponsored research is exploratory or aimed at answering a scientific question rather than delivering a defined deliverable. A product development agreement is narrower and more commercially oriented: it exists specifically to take a technology to a market-ready product, with the milestone and commercialization structure that implies. Some agreements are labeled and function as a hybrid of the two — a development-stage SRA with a built-in license option — which is why the specific obligations in the document matter more than its title.
vs. CRADA (Cooperative Research and Development Agreement). A CRADA is a specific federal-statutory mechanism, authorized under the Federal Technology Transfer Act of 1986 (15 U.S.C. 3710a), available only when one party is a federal laboratory. A CRADA’s IP and licensing conventions — each party takes title to inventions made by its own employees, the non-federal partner commonly gets a first option to negotiate an exclusive license, the government retains a government-use license — are shaped by that statute and by the federal lab’s own template, not freely negotiated the way a university-industry product development agreement’s terms are. A product development agreement between a university and a company, with no federal laboratory involved, is not a CRADA even if it looks structurally similar; it is a general contract governed by ordinary contract law and each institution’s own IP policy.

For a broader look at how universities structure industry collaborations generally, including consortium and affiliates-program models, see CASRAI’s guide to Industry-University Research Partnerships. For the general (non-federal) umbrella contract that governs joint research without necessarily targeting a specific commercial product, see Collaborative Research Agreement (CRA).

IP ownership context: Bayh-Dole and institutional policy

When a university enters a product development agreement funded partly or entirely by federal money, the Bayh-Dole Act governs the university’s right to retain title to resulting inventions and its obligations (such as march-in rights and reporting) once it does. When the agreement is purely industry-funded, Bayh-Dole does not apply, and IP ownership instead defaults to whatever the university’s own internal IP policy and the agreement itself negotiate — there is no federal statutory default answering the ownership question the way Bayh-Dole does for federally funded work.

Machine-readable encodings

Use in your systems

JATS XML <role> element

xml

<role vocab="credit"
      vocab-identifier="https://casrai.org/dictionary/"
      vocab-term="Product Development Agreement"
      vocab-term-identifier="https://casrai.org/dictionary/term/product-development-agreement" />

Schema.org DefinedTerm (JSON-LD)

json

{
  "@context": "https://schema.org",
  "@type": "DefinedTerm",
  "@id": "https://casrai.org/dictionary/term/product-development-agreement",
  "name": "Product Development Agreement",
  "identifier": "https://casrai.org/dictionary/term/product-development-agreement",
  "description": "A product development agreement (PDA) is a contract between a company and a university, research institution, or individual inventor to jointly develop a specific product or technology toward a commercial outcome, combining ongoing development work with pre-negotiated terms for how the resulting IP will be owned and eventually commercialized. An arrangement counts as a product development agreement, rather than one of the adjacent instruments it is routinely confused with, when three elements are present together: (1) the parties jointly perform development work aimed at a defined product or application -- it is not a license of already-existing IP with no development obligation attached, and not open-ended research without a specific commercial product as the target; (2) it sets milestone-based development obligations (technical milestones, timelines, sometimes funding contributions) that both parties are bound to, rather than one party simply performing services for a fee; and (3) it addresses in advance how IP arising from the joint work -- particularly improvements, modifications, or new inventions built on either party's background IP -- will be owned, and how the finished product will ultimately be licensed or otherwise commercialized. A PDA is a general contracting concept, not a term of art created by a specific statute; its content is negotiated case by case, unlike a CRADA, which is a specific federal-laboratory mechanism created by statute.",
  "inDefinedTermSet": "https://casrai.org/dictionary/domain/tech-transfer#set",
  "url": "https://casrai.org/dictionary/term/product-development-agreement",
  "sameAs": [],
  "license": "https://creativecommons.org/licenses/by/4.0/",
  "publisher": {
    "@id": "https://casrai.org/#organization"
  },
  "dateModified": "2026-07-18T08:20:47",
  "inLanguage": "en"
}