IP Licensing Agreement Review for Indian Technology Companies

An Indian technology company may treat an IP licence as a revenue contract, but investors and acquirers treat it as a control document. The core question is whether the company has licensed software, patents, marks, content, designs or know-how in a way that protects ownership, preserves commercial flexibility and avoids hidden restrictions on funding, acquisition or expansion.

For a founder, the licence should convert technology into usable commercial rights. For a VC, PE investor or strategic buyer, it should also show who owns the asset, who can use it, what happens on breach or exit and whether the arrangement can survive diligence.

Why This Matters

An IP licence is only useful if it fits the underlying right. The Indian Contract Act, 1872 supplies the general contract baseline for lawful consideration, capacity, performance, breach and enforceability. The IP statutes then add asset-specific requirements.

For software, product content and creative materials, the Copyright Act, 1957 matters because copyright ownership, assignment and licensing determine whether the company can commercialize code or grant customer rights. For patented technology, the Patents Act, 1970 requires careful review of written assignments, licences, title and register-related steps. For product names, logos and platform brands, the Trade Marks Act, 1999 shapes licensing, quality control, assignment and enforcement risk.

The commercial risk is simple. A company can have strong technology and still lose value if the licence is too narrow, sublicensing is unclear, royalties are badly structured, improvements are trapped with the wrong party or termination cuts off a business-critical product line.

What Counsel Should Review

Start with the asset schedule. The agreement should identify the licensed IP precisely: source code, object code, APIs, documentation, patents, pending applications, trademarks, designs, datasets, product content, confidential know-how and any third-party components. Vague descriptions such as "all platform IP" create diligence problems because they do not show what was actually licensed.

Next, review the licence grant. Counsel should test exclusivity, territory, field of use, duration, sublicensing, transfer, group-company use, contractor access and whether the licence is royalty-bearing, paid-up or bundled into a larger commercial arrangement. If the licensee needs to serve enterprise customers, the sublicensing and hosting language must match that delivery model.

Ownership of improvements is often the highest-value point. The agreement should say who owns modifications, derivative works, trained models, integrations, bug fixes, documentation and product feedback. It should also separate background IP from newly created foreground IP.

Revenue terms need the same discipline. Royalty base, audit rights, tax gross-up, minimum commitments, milestones, usage reporting and non-payment remedies should be practical enough to administer. A beautifully drafted royalty clause is weak if the company cannot measure the revenue event.

Finally, map exit and financing restrictions. Investors should check change-of-control limits, assignment consent, source-code escrow, step-in rights, termination triggers, survival of customer-facing rights and whether a future acquirer can continue using the licensed technology without renegotiation.

Relevant Judicial Guidance

The Supreme Court's official judgment in Nabha Power Limited v. Punjab State Power Corporation Limited is useful for licence drafting because paragraph 41 cautions against rewriting a bargain by implication except within a disciplined business-efficacy analysis. For an IP licence, that means parties should not rely on assumptions about sublicensing, improvements, exclusivity, source-code access or post-termination use. If the right matters to valuation, put it clearly in the agreement.

Typical Timeline and Cost Range

A focused review of one product or software licence can often be completed in 3 to 7 business days if the documents and asset schedule are complete. A deeper investor or acquisition review involving multiple licences, royalty streams, customer-facing sublicences and third-party components may take 2 to 4 weeks.

Costs usually depend on the number of agreements, assets, counterparties and remediation steps. The efficient approach is to separate urgent deal issues from cleanup items that can be handled after signing.

Common Mistakes

1. Licensing rights the company does not clearly own. A licence cannot cure missing founder, employee, contractor or vendor assignments.
2. Leaving improvements and sublicensing ambiguous. These clauses determine whether the business can scale through customers, affiliates and product integrations.
3. Ignoring exit restrictions. Change-of-control, assignment and termination clauses can reduce deal value if a buyer cannot continue the licensed use.

How KAS & Co. Can Help

KAS & Co. helps Indian technology companies, investors and acquirers review IP licensing agreements, asset schedules, ownership evidence, sublicensing rights, improvement clauses, royalty mechanics and deal-readiness issues. For a focused licensing review, contact KAS & Co..

FAQs

1. What should an IP licensing agreement cover first?

It should first identify the licensed IP, the owner, the user, the permitted use, the territory, the term and whether the licence is exclusive or non-exclusive.

2. Can a technology company licence IP before all assignments are complete?

It is risky. The company should confirm ownership or control first, especially for founder-created code, contractor deliverables, open-source components and third-party tools.

3. Why do investors review sublicensing rights?

Sublicensing rights show whether the company can serve customers, affiliates, channel partners or acquirers without breaching the original licence.

4. Should improvement ownership be negotiated separately?

Yes. Improvements, integrations, modifications and product feedback can become valuable assets, so the agreement should allocate them expressly.

Sources

• Indian Contract Act, 1872 - India Code
• Copyright Act, 1957 - India Code
• Patents Act, 1970 - India Code
• Trade Marks Act, 1999 - India Code
• Supreme Court of India - Nabha Power Limited v. Punjab State Power Corporation Limited