Software IP Assignment Issues in Indian Technology Companies

An Indian technology company may present itself as a software owner while its core product contains code written by founders before incorporation, freelance developers, agencies, former employees or an overseas affiliate. Investors and acquirers need more than repository access and a warranty. They need a provable chain of title and a usable licence position for every material product component.

The business risk is straightforward: a company unable to demonstrate control of its software may not control the asset on which its valuation is based.

The Statutory Starting Point

Software ownership analysis in India begins with the Copyright Act, 1957. The Act addresses works in which copyright subsists, the meaning of copyright, first ownership, assignment and the mode of assignment. Sections 17, 18 and 19 are central to an investor review of who initially owned relevant rights, whether they were transferred and whether the transfer is sufficiently documented.

The commercial mistake is to assume that payment for development necessarily gives the company full ownership of source code and derivative rights. The underlying engagement, employment relationship and written assignment terms need examination. A licence may support use of a component without giving the company the ownership or transfer rights assumed in a funding or sale process.

Where Assignment Gaps Commonly Arise

Founder code is a recurring issue. A founder may begin building the product before incorporation, use personal repositories and later assume the company owns all rights automatically. The diligence file should include a clear assignment of relevant pre-incorporation software and related materials to the company.

Contractor and agency development requires equal care. Statements of work often describe deliverables and payment while failing to transfer rights clearly, define background materials or address future modifications. The company may receive executable deliverables while lacking sufficient rights to alter, sublicense or transfer parts of its own platform.

Employment documents should be reviewed against actual contributors and development history. Gaps arise where early employees signed no agreement, worked through a different group entity, or developed material modules before joining. Joint development, accelerator arrangements, university involvement and outsourced product work can introduce further ownership or licence constraints.

Finally, code bases often contain open-source and commercial third-party components. These are not necessarily defects; they require an accurate inventory and compliance review so an investor understands licences, notice obligations, distribution implications and any effect on proprietary elements.

What An Investor Should Request

Start with a product-and-repository map identifying material modules, mobile or web applications, infrastructure scripts, application programming interfaces, documentation and key development contributors. Obtain founder assignments, employment and consulting agreements, agency contracts, affiliate development arrangements, commercial licences, open-source inventory and records of any dispute or claim.

For each material component, counsel should classify the position: owned by the investee, validly licensed on acceptable terms, requiring remediation or uncertain pending further evidence. That analysis should be mapped to revenue-generating products and transaction objectives rather than treated as a paperwork inventory.

Where gaps exist, remediation may include assignments, confirmatory deeds, expanded licences, replacement of a component, warranties backed by specific disclosure, escrow or closing conditions. A missing signature affecting a core platform should not be postponed casually until after funds are released.

Assignment Terms Need Precision

An assignment document should identify the relevant work or category of works, the rights conveyed, territory, duration, permitted exploitation and consideration or other required commercial terms, with treatment of future development and background materials appropriate to the arrangement. The statutory framework makes this precision more than drafting neatness: it is part of establishing an enforceable transfer record.

For investor reporting, the company should maintain executed assignments and licences centrally, link them to contributors and product modules, and require review before external developers begin material work.

Typical Timeline and Cost Range

A focused audit of ownership documents for one principal product and a small contributor group can commonly be performed within 1 to 2 weeks after repository and contract records are supplied. A review spanning several products, group entities, acquired code bases or extensive third-party components may require 2 to 4 weeks or staged remediation.

Costs depend on the number of contributors, agreements, products and identified gaps. Investors commonly benefit from a red-flag phase first, followed by targeted assignments or licence remediation for components that affect value.

Common Mistakes

1. Assuming paid development means ownership. Payment and possession of code do not replace a defensible written rights analysis.
2. Reviewing contracts without mapping them to the product. An assignment is valuable only if it covers the code and contributor relevant to the business.
3. Treating remediation as a post-closing formality. A core ownership gap can directly affect valuation, control and exit readiness.

How KAS & Co. Can Help

KAS & Co. assists investors and Indian technology companies with software ownership audits, assignment remediation, licence review and transaction protections tied to product value. To review an IP chain of title before financing or acquisition, contact KAS & Co..

FAQs

1. Does a company automatically own software written by its founder before incorporation?

That should not be assumed. Investors should request written transfer documentation covering relevant pre-incorporation work and related rights.

2. Is a contractor invoice sufficient evidence that software rights transferred?

Usually not as a diligence answer. The engagement and written rights terms should be reviewed for ownership, licence scope, background materials and transferability.

3. Do open-source components make a software company uninvestable?

No. They require identification and licence analysis so the company can demonstrate compliance and understand any obligations affecting distribution or proprietary strategy.

4. Can ownership gaps be fixed during a financing round?

Many can be addressed through confirmatory assignments or licences, but material gaps should be identified early and reflected in closing conditions or investment protections where appropriate.

Sources

• The Copyright Act, 1957 - India Code