A commercial collaboration frequently rests on a simple premise: one party contributes technology, the other contributes expertise, and together they develop something neither could produce alone. The premise tends to hold until the resulting technology acquires commercial value, at which point questions that appeared academic at signing take on considerable consequence.
Two concepts sit at the centre of those questions. Background IP refers broadly to the intellectual property each party brings to the collaboration or develops outside it. Foreground IP refers to the intellectual property the collaboration itself produces. The distinction appears straightforward in principle, yet in practice it governs who owns the product, who may commercialise it and who may continue to use it once the relationship ends.
KEY IP CONSIDERATIONS
- Defining the boundary between background and foreground IP: Parties rarely stop developing their own technology when a collaboration begins. Where a party refines its platform in parallel with the project, or incorporates existing tools into a deliverable, it becomes uncertain whether a given development belongs to that party alone or to the project. The answer often turns on drafting choices made at the outset, and those choices interact with ownership and assignment provisions elsewhere in the agreement in ways that are not always apparent.
- Ownership of what is created: No default rule allocates foreground IP in a manner that reliably reflects the commercial bargain. Several ownership models are available, and each carries different consequences for funding, commercialisation and enforcement. Joint ownership, often adopted as a compromise, can produce outcomes the parties did not anticipate, as the rights of co-owners vary with the type of IP and the governing law.
- Improvements to background IP: Where the collaboration does not simply create something new, but improves one party’s existing technology, the parties may hold irreconcilable views on whether the enhancement is an improvement to background IP or a new asset arising from the project. This is resolved based on how exploitation rights are allocated between the parties.
- Licensing and Access Rights: Owning foreground IP does not of itself confer the ability to exploit it, as commercial use may depend on continuing access to the other party’s background IP. A licence drafted too narrowly may leave a party unable to sell its own product, while one drafted too broadly may grant the counterparty considerably more than the arrangement warrants. The allocation should reflect the commercial objectives of the parties.
- Third Party IP: Background IP may incorporate open-source code, licensed datasets, third-party software or materials held under technology transfer arrangements. A party may therefore commit to granting rights it does not hold and cannot extend, a deficiency that tends to surface only during diligence for a financing or acquisition.
- Confidentiality is materially different: Confidentiality obligations restrict disclosure and misuse, but they do not determine ownership or confer rights of use. Agreements that rely on confidentiality clauses to perform the work of IP provisions leave significant gaps that the parties may discover only when a dispute arises.
- Post-termination rights: Commercialisation often continues long after development activities end. Without a considered framework, termination may disrupt access to the tools and technology required to exploit the deliverables and leave uncertain which licences survive and what each party must do with the materials in its possession.
CONCLUSION
Disputes in joint development arrangements seldom arise because the parties overlooked intellectual property altogether. They arise because the agreement did not anticipate how existing and newly created IP would interact. The appropriate treatment of each issue above depends on the technology involved, the commercial objectives of each party and the applicable law, and these questions are considerably easier and less costly to resolve at the drafting stage than after the collaboration has produced something of value.
Authors: Shantanu Mukherjee, Maitreyi Ramdas
