IP Ownership Clauses in Technology Services Contracts in India

IP ownership is an under-negotiated line in a technology services contract. A startup may hire a development partner assuming that payment buys ownership of the output. If the contract does not clearly separate pre-existing tools from new deliverables, and licences from assignments, the company may end up paying for work it cannot fully control.

The question is whether the contract gives the company the rights it needs.

Why This Matters

In Indian technology businesses, value often sits in source code, product documentation and workflow logic built during a services engagement. If the contract is vague, the service provider may later argue that reusable modules or parts of the stack remain its property, while the customer believed it had bought the outcome.

The statutory framework should shape the drafting. The Indian Contract Act, 1872 governs whether the agreed allocation is enforceable as part of a valid bargain. The Copyright Act, 1957 is central because section 17 addresses first ownership, section 18 permits assignment, and section 19 requires a valid assignment to be in writing and to specify the rights being assigned. Where a services engagement may generate patentable outputs, the Patents Act, 1970 also matters. If the contract is signed through digital workflows, the Information Technology Act, 2000 supports contracts formed through electronic means.

What Counsel Should Review

Start with the ownership architecture, not the boilerplate label. The contract should define background IP, provider tools, deliverables and improvements separately. Without those distinctions, an assignment clause may still leave room for dispute about what was actually transferred.

Next, match the commercial model to the legal transfer mechanism. If the customer needs exclusive control of custom code or invention rights, the contract should use present-tense assignment language and describe the rights with enough precision to satisfy the Copyright Act. If the provider is meant to retain its platform or accelerators, that should be stated expressly.

Then test invention capture. Services contracts often address copyright and forget patentable improvements. If engineers, founders or subcontractors may create patentable subject matter during the engagement, the paper set should deal with disclosure obligations, filing support and execution of further documents.

Review subcontracting and post-termination rights with the same care. A prime vendor cannot transfer more rights than it controls, so the customer should ask whether affiliates, freelancers or subcontractors have signed back-to-back assignments. The company should also secure source-code access, handover of repositories and return of credentials early.

Relevant Judicial Guidance

In Nabha Power Limited v. Punjab State Power Corporation Limited, Civil Appeal No. 8478 of 2014, reported as 2024 INSC 833, the Supreme Court explained in paragraph 41 of the official judgment that the business-efficacy test cannot override an express contractual term and is relevant only where the contract is not explicit and clear.

That principle matters here because parties regularly assume a court will later infer the commercially obvious answer on ownership. If the contract is imprecise on whether code is assigned, whether provider tools are excluded, or whether future inventions must be transferred, the signed text may control the outcome.

Typical Timeline and Cost Range

A focused review of one master services agreement, statement of work and IP schedule can often be completed within 3 to 5 business days once the full document set is available. A broader cleanup across multiple vendor templates or legacy development arrangements usually takes 1 to 2 weeks.

Fees are usually best scoped by document volume and remediation depth. Often, the efficient approach is to review one live services deal and convert that position into a standard clause set.

Common Mistakes

1. Using one broad assignment sentence for every type of output. Code, documentation, inventions, provider tools and pre-existing libraries usually need separate treatment.
2. Ignoring the vendor's subcontracting chain. If subcontractors or freelancers created the work without back-to-back assignments, the customer's title can still be incomplete.
3. Leaving transition rights for later. Repository access, build materials, credentials and further-assurance obligations are hardest to negotiate after the relationship sours.

How KAS & Co. Can Help

KAS & Co. advises founders, investors and deal teams on technology services contracts, IP chain-of-title risk and contract cleanup before fundraising, acquisition or scale. To review a live services agreement or legacy development paper set, contact KAS & Co..

FAQs

1. Does paying a vendor automatically mean the customer owns the code?

No. Payment alone does not replace clear contractual drafting on ownership, assignment and retained provider rights.

2. Why are background IP and foreground IP definitions so important?

They separate what the provider already owned before the engagement from what is newly created during the work, reducing later disputes about reuse and exclusivity.

3. Should a services contract address patentable inventions as well as copyright?

Yes. If the engagement may create patentable outputs, the contract should cover disclosure, assignment support and filing cooperation rather than treating everything as ordinary software deliverables.

4. What documents should investors ask for during diligence?

Investors should ask for the master services agreement, statements of work, subcontractor terms, invention or assignment deeds and repository-control evidence.

Sources

• The Indian Contract Act, 1872 - India Code
• Section 17, Copyright Act, 1957 - India Code
• Section 18, Copyright Act, 1957 - India Code
• Section 19, Copyright Act, 1957 - India Code
• The Patents Act, 1970 - India Code
• Section 10A, Information Technology Act, 2000 - India Code
• Nabha Power Limited v. Punjab State Power Corporation Limited - Supreme Court judgment dated 5 November 2024