Employee-Created IP Ownership Issues in Indian Startups

Employee-created intellectual property can quietly decide whether a startup is investable. A product may depend on code written by early engineers, UI assets made by a design hire, patentable technical improvements developed by the R&D team, sales collateral created by growth employees or technical documentation built across several product squads. If the company cannot show that these assets sit with the company, investors have to price ownership risk into the deal.

The issue is rarely a simple yes-or-no question. Indian law treats different asset classes differently, and the answer often depends on the employment contract, the role, the scope of work, the timing of creation and whether later assignments or register updates were completed.

Why This Matters

For a VC, PE investor or strategic acquirer, employee-created IP is a chain-of-title problem. The company needs evidence that the asset was created in the course of employment, that the employment terms deal with ownership and assignment, and that any statutory filing reflects the same ownership story.

The Copyright Act, 1957 is central for software code, documentation, product copy, training material and design files. Section 17 starts with the author as first owner, but also contains employer-ownership rules for works made in the course of employment under a contract of service, subject to contrary agreement. Sections 18 and 19 then matter where a written assignment is needed or where the agreement must identify rights, duration and territory.

For inventions, the Patents Act, 1970 requires closer diligence. An employer should not assume that every employee invention automatically appears in the company's title chain. Patent applications, inventor records, declarations, assignment documents and register entries should be reviewed together. Sections 6, 68 and 69 make applicant entitlement, written assignments and registration of title important transaction checks.

The Indian Contract Act, 1872 also matters because employment IP clauses, confidentiality covenants, cooperation duties and post-employment assistance obligations still need enforceable contract architecture. For hardware, product appearance and interface-related assets, the Designs Act, 2000 may also be relevant.

What Counsel Should Review

Start with the employee population that actually created value: founders who later became employees, early engineers, product managers, designers, machine-learning specialists, documentation leads, solution architects and senior sales or implementation staff. The review should map each material asset to a creator, employment period, scope of role and repository or file evidence.

Next, examine employment agreements and offer letters. A strong clause should cover present and future work product, inventions, source code, documentation, product designs, improvements, derivative works, moral-rights waivers where legally relevant, disclosure obligations and cooperation for filings. It should also require employees to disclose prior inventions and third-party restrictions before joining.

Then compare the contract position against actual records. Source-code commits, design tools, ticketing systems, invention disclosure forms, patent filings, trademark or design filings, and board approvals should tell a consistent story. Gaps often appear where an employee created key work before signing an employment contract, after moving from consultant to employee, or while using personal accounts.

For patentable work, counsel should review inventor identity, applicant name, assignment evidence and filing forms. IP India's current patent forms and official fees page is useful because transaction teams can identify whether title-change or assignment filings are expected for the relevant record. For copyright-heavy businesses, the focus is usually the signed employment record, the work's creation context and any later assignment or confirmation deed.

Finally, align deal documents with the evidence. The investment agreement, disclosure schedule and closing conditions should identify any missing employee assignments, former-employee disputes, prior-employer risks, unrecorded patent transfers or repositories controlled by individuals.

Typical Timeline and Cost Range

A focused review for one product line and a small employee group can often be completed in 5 to 10 business days if employment contracts, repository exports, invention records and filing details are ready. A broader review across several product teams, former employees, patent filings and historic contractor-to-employee transitions may take 2 to 4 weeks.

The practical cost driver is not the number of employees alone. It is the number of material assets, missing contracts, legacy filing records and remediation documents required before signing or closing.

Common Mistakes

1. Assuming employment automatically solves every IP issue. Copyright, patents, designs, contracts and registry evidence each need separate review.
2. Ignoring pre-contract and side-project work. Work created before the employment agreement or outside the role may need a separate assignment.
3. Letting patent records drift from the ownership story. Inventor, applicant, assignment and register details should support the company's title claim.

How KAS & Co. Can Help

KAS & Co. helps Indian technology companies, investors and acquirers review employee-created IP ownership, employment IP clauses, invention assignment records, repository evidence, patent title filings and closing remediation. For a focused employee IP review, contact KAS & Co..

FAQs

1. Does an Indian startup own all work created by its employees?

Not automatically in every situation. The answer depends on the asset class, employment terms, creation context and whether any contrary agreement or third-party restriction applies.

2. What employee-created assets should investors check first?

Investors should start with source code, patentable inventions, product designs, technical documentation, architecture diagrams, training material, implementation playbooks and assets created by early senior hires.

3. Can missing employee IP assignments be fixed before closing?

Often yes, if the employee or former employee cooperates and no third-party claim exists. The fix may include confirmatory assignments, patent title filings, warranties and disclosure schedule updates.

4. Why do patent records need separate review?

Patent ownership depends on applicant entitlement, inventor records, written assignment documents and register updates. Employment language alone may not give investors the evidence they need.

Sources

• Copyright Act, 1957 - India Code
• Patents Act, 1970 - India Code
• Indian Contract Act, 1872 - India Code
• Designs Act, 2000 - India Code
• Patent Forms and Official Fees - IP India