Joint Development Agreement IP Risks in Indian Technology Ventures
A joint development agreement can create the most valuable asset in a young technology business—and the hardest asset to sell or finance. A startup may collaborate with an enterprise customer, hardware vendor, university lab or implementation partner to build code, models, interfaces or device improvements. If the contract labels everything “joint IP” without allocating rights precisely, a later investor or buyer may find that the target cannot license, modify or transfer the technology it believes it owns.
For an India-linked venture, the agreement should work alongside the parties’ existing employment, contractor, patent and copyright records. The commercial objective is straightforward: preserve each party’s pre-existing technology, give the venture practical freedom to commercialise the project output, and avoid a co-owner becoming an unplanned veto-holder during a financing or exit.
Start with an asset map, not a generic ownership clause
Define background IP before the work begins. This includes source code, libraries, patents, know-how, documentation, designs, brands and development tools already controlled by each participant. Attach a schedule with version identifiers, repositories, patent application numbers and permitted dependencies. A bare statement that background IP “remains owned” is not enough if the project needs an irrevocable licence to use, adapt or combine it after the collaboration ends.
Then define foreground IP by deliverable. Separate new code, inventions, designs, documentation, training materials and improvements to a party’s background IP. This matters because ownership can differ by asset. The Copyright Act addresses first ownership and requires a written assignment identifying the work, rights, duration and territorial extent. The Patents Act contains its own entitlement and assignment framework. Deal teams should ensure that the agreement, employee inventions documents and contractor assignments point to the same owner.
Make commercial rights usable after the relationship ends
The central question for an investor is not only who owns a deliverable on signing day; it is who may use it after a dispute, termination, change of control or product pivot. If ownership stays with the customer or partner, negotiate a licence that is express, perpetual where commercially justified, worldwide if the business needs it, transferable to an acquirer, and capable of sublicensing to hosting, distribution and group-company providers.
Where the parties truly share ownership, spell out whether either may commercialise independently, license third parties, bring infringement claims, register rights, or assign its interest. Do not assume “joint ownership” supplies those answers. If an exit requires the collaborator’s consent, price and timetable, the technology is not exit-ready.
The contract should also address improvements. A product team often builds on a collaborator’s API, reference design or dataset, then later develops a distinct platform. Decide whether an improvement is owned by the improver, assigned to one party, or licensed back. Include a clean procedure for disclosure, acceptance testing and an assignment instrument executed when the relevant work is created.
Three common mistakes
- Calling all output “joint IP.” This obscures whether either party can continue selling, licensing or transferring the technology without a second signature.
- Ignoring the human chain of title. A company cannot promise rights that its employees, consultants or subcontractors have not validly assigned or licensed.
- Leaving exit rights to a future negotiation. A buyer will discount value when a collaborator can block assignment, access to repositories or use of essential background technology.
A diligence checklist for investors and acquirers
Ask for the signed agreement, all statements of work, delivery acceptance records and the background-IP schedule. Trace each significant repository, invention disclosure and design file to a person or entity with written obligations. Review licence scope, sublicensing, assignment, change-of-control and termination language. Finally, compare the agreement against the cap table, planned transaction structure and product roadmap: a minority investor may tolerate a narrow customer licence, but an acquirer usually needs durable control or a clearly transferable licence.
The Indian Contract Act provides the baseline for a binding agreement, while IP-specific statutes govern the relevant proprietary rights. That is why copied development templates are risky: they can be commercially clear yet still fail to document the assignment or licence needed for the asset at issue. A short amendment before a funding round is usually cheaper than reconstructing provenance during exclusivity.
If you are preparing a financing, acquisition or strategic collaboration, contact KAS & Co. for a focused review of the IP allocation, transferability and execution record.
FAQs
Can a startup own code developed jointly with a customer?
Yes, if the agreement and the contributor documents allocate or assign the relevant rights clearly. If the customer retains ownership, the startup should secure the licence scope needed for its planned products and transaction path.
Does a joint development agreement need a separate IP assignment?
Often it should include one or require short-form assignments at defined milestones. The right approach depends on the asset, contributors and intended owner, but the written documentation must be specific enough for the applicable statutory framework.
Can a buyer acquire a business if its collaborator owns key background IP?
Yes, but the buyer must test whether the licence survives the acquisition, permits continued use and modification, and can be transferred or sublicensed as the post-closing business requires.
What should investors request before signing a term sheet?
Request the joint development agreement, schedules, amendments, contributor agreements, deliverable acceptance evidence, repository access rules and a concise matrix showing background and foreground rights.
Sources
Topics
Need legal advice on this topic?
KAS & Co. provides strategic legal counsel across technology law, data privacy, IP and commercial advisory.
Schedule a Consultation