Why IP assignment matters before fundraising

A startup can have users, revenue and a strong pitch deck, and still fail IP diligence. The reason is simple: investors do not invest only in the founder’s talent. They invest in a company that should own or validly use the assets that create business value. If the code sits in a founder’s personal GitHub, the logo was made by a freelancer without assignment language, the domain is in a co-founder’s personal email, the product uses untracked open-source code, or the first prototype was built before incorporation and never transferred, the company has a title problem.

IP cleanup is not only for deep-tech or patent-heavy startups. It matters for SaaS, AI, D2C, edtech, fintech, marketplaces, content businesses, healthtech, climate-tech and B2B services. A brand name, source code, UI design, training dataset, product documentation, domain name, app-store account, customer-facing copy, technical architecture or proprietary process can all become diligence questions.

The right approach is not to collect generic IP clauses at the last minute. The right approach is to create an IP chain-of-title file. That file should show who created each asset, under which agreement, whether the company owns it or only licenses it, where the source files are, whether third-party material is used, and whether the company has control of the relevant accounts.

Indian law source map founders should know

Startup IP ownership is spread across copyright, patents, trademarks, contracts, designs, data rights and account control. The following points matter most in practical founder diligence:

• Copyright Act, 1957, section 17: the author is generally the first owner, but employee-created work in the course of employment can vest in the employer unless there is an agreement to the contrary. This does not remove the need for clear contracts, especially for founders, consultants and pre-incorporation work.
• Copyright Act, sections 18 and 19: copyright can be assigned wholly or partially, but assignment must be in writing and signed. The assignment should identify the work, rights assigned, duration, territory and consideration. If duration or territory is missing, default rules can create unpleasant surprises.
• Patents Act, 1970, section 68: assignment, mortgage, licence or other interest in a patent must be in writing and duly executed. Patent rights should not be left to oral founder understanding.
• Patents Act, section 69: registration of assignment, transmission or other interest in patents should be handled with the Controller where applicable.
• Trade Marks Act, 1999, sections 37-45: registered and unregistered trademarks can be assigned or transmitted, subject to the Act. Trademark assignment can raise goodwill, partial assignment, associated mark and registration issues.
• Contract law: founder agreements, employment agreements, consulting contracts, agency contracts and acquisition documents should identify what is being transferred, when, for what consideration and with what warranties.

The practical lesson is that payment is not a complete ownership strategy. A company can pay a designer and still lack source files. It can pay a developer and still not own reusable code libraries. It can file a trademark and still have the domain controlled by an individual. It can employ engineers and still leave invention assignment unclear for side projects, prior inventions or open-source contributions.

The startup IP asset map

Founder IP: pre-incorporation work and co-founder exits

Most startups begin before incorporation. Founders pick a name, buy a domain, write code, create a prototype, design a pitch deck, build a landing page, speak to early customers or prepare technical diagrams. Once the company is incorporated, that early work should be transferred to the company if it belongs to the business.

A founder IP assignment deed should cover:

• the founder’s name and the company name;
• clear identification of assets being assigned;
• copyright, know-how, inventions, designs, documentation and brand assets where relevant;
• future cooperation for filings and signatures;
• warranty that the founder has not knowingly copied third-party work;
• disclosure of prior inventions or excluded personal IP;
• consideration, even if nominal or linked to shareholding/founder role;
• handover of repositories, domains, files and passwords through secure company-controlled processes.

This becomes critical when a co-founder exits. If the departing founder wrote the first code, bought the domain or designed the brand, the company should not wait until the exit dispute to ask who owns what. Founder separation documents should include IP reaffirmation, credential handover, deletion/return of company materials, confidentiality, non-use of brand assets and assistance with future filings.

Employee IP and invention assignment

Indian copyright law gives helpful rules for works created in the course of employment, but founders should not rely on assumptions. Employment agreements should still contain IP assignment, confidentiality, invention disclosure, prior invention carve-outs, moral-right waiver where appropriate, return of property, data handling and post-exit cooperation clauses.

The employment IP clause should be broad enough to cover code, documentation, designs, product ideas, discoveries, improvements, configurations, scripts, workflows, models, datasets, customer materials, inventions, training material, written content and works created using company resources. It should also tell employees how to disclose prior inventions or side projects so that later disputes do not become personal.

For technical teams, add an operational control: important work should be committed to company repositories, not personal accounts. If employees use local laptops, personal Git accounts, external storage or personal cloud tools, the company needs a clean handover process when they leave.

Contractor, freelancer and agency IP

Contractor IP is where many Indian startups get hurt. A freelancer is not the same as an employee. A design agency, developer, marketing consultant, photographer, videographer or no-code builder may own parts of the deliverable unless the agreement clearly transfers ownership or grants the company a sufficient licence.

A contractor agreement should answer these questions:

• What exactly is being delivered?
• Does the company own only the final output or also editable source files?
• When does ownership transfer: on creation, on delivery, or after full payment?
• Can the contractor reuse libraries, templates, design systems or generic know-how?
• Are third-party fonts, images, plugins, stock files or code libraries used?
• Who is responsible for third-party licences?
• Can the contractor display the work in a portfolio?
• What warranties and indemnities are given for infringement claims?
• What happens if invoices are disputed or partly unpaid?

For startups, the practical fix is simple: use assignment language before work starts, collect source files at each milestone, pay through company bank account, keep invoices, and close every major project with a handover note.

Copyright assignment: the clause should not be lazy

Section 19 of the Copyright Act is specific. The assignment should identify the work, specify rights assigned, duration, territorial extent and consideration. If a startup uses a one-line clause saying “all IP belongs to the company” but never identifies the deliverables, rights, territory or source files, diligence counsel may ask for clarification.

For software, design, content and media assets, the agreement should specify whether the company receives:

• source code and object code;
• editable design files;
• documentation and technical specifications;
• right to reproduce, modify, adapt, translate, distribute, host, display, commercialise and sub-license;
• worldwide rights for the full term of copyright where intended;
• right to create derivative works;
• right to use in existing and future formats, platforms and media;
• waiver or non-enforcement of moral rights to the extent legally permitted;
• third-party asset list and licence scope.

This sounds detailed because it should be. Startup IP is often reused across product, website, sales deck, app, APIs, customer documentation, investor deck and acquisition diligence. A weak assignment clause can create uncertainty across all of those surfaces.

Patents, designs and trade secrets

Patentable inventions need a different discipline from copyright. The company should keep invention disclosure forms, inventor names, lab notebooks or technical evidence, employment or consultant assignment provisions, proof of right for filing, filing documents, prosecution records and assignment/registration records where applicable. Section 68 of the Patents Act makes writing and execution central for assignments or creation of interests in patents.

Founders should also protect trade secrets. Not every valuable technical asset is patented. Algorithms, model architecture, manufacturing know-how, formulae, process settings, pricing logic, internal scripts and customer segmentation may be protected through confidentiality, access control and contractual restrictions. If a startup discloses trade secrets casually to vendors, pilots or prospective partners, the value can disappear before a patent or commercial deal is ready.

For industrial designs, check whether product shape, configuration, pattern or ornamentation should be registered separately. For hardware, D2C and manufacturing startups, design files and CAD ownership can matter as much as brand ownership.

Brand, trademarks, domains and handles

Trademark ownership is not only a legal filing. It is also practical control. The company should know who owns the brand name, logo, tagline, packaging artwork, domain, social media handles, marketplace seller account, app-store account and ad accounts. The Trade Marks Act permits assignment and transmission of registered and unregistered marks, but founders should avoid title confusion from the first day.

For brand assets, maintain:

• name-clearance search and trademark filing records;
• logo/design assignment from designer or agency;
• domain registrar account under company email;
• social handles under company-controlled admin access;
• brand guidelines and source design files;
• evidence of first use;
• co-founder exit confirmation if a founder was associated with the brand creation;
• assignment deed if brand was originally held by an individual or another entity.

Domain names and social handles may not always behave like statutory IP rights, but investors care deeply about control. If the company loses access to its domain or app-store account, the legal theory will not comfort customers.

Open-source and third-party asset diligence

Open-source is not a problem by default. Undocumented open-source use is the problem. A commercial software startup should know which libraries it uses, what licences apply, whether any copyleft obligations are triggered, whether notices are required, whether source disclosure obligations exist, and whether a component is safe for the company’s distribution model.

Keep an open-source register with:

• package name and version;
• licence type;
• where it is used;
• notice obligations;
• approval owner;
• security or vulnerability review status;
• replacement plan for risky components.

Also track stock images, icons, fonts, templates, themes, plugins, no-code components, APIs, SDKs, datasets, sound files, video footage and outsourced copy. A paid download is not always a commercial licence. Some assets prohibit resale, sublicensing, app embedding, logo use, merchandise or AI training.

AI, datasets and model terms

AI startups should treat data rights as part of IP diligence. If the product uses scraped data, customer data, licensed datasets, employee-generated annotations, model outputs, synthetic data, third-party APIs or fine-tuning material, the company needs a data-source register. This is not only a privacy issue. It is also an ownership, licence, confidentiality, contractual and product-risk issue.

The data register should state source, permission basis, licence terms, restrictions, retention period, whether personal data is involved, whether customer confidential information is included, whether data can be used for training, and whether outputs can be commercialised. Customer contracts should not silently permit training if the customer never agreed. Vendor AI tools should be checked for output ownership, input retention and model-training settings.

IP data-room pack for fundraising

Before fundraising, create an IP folder that can be shared under diligence. It should include:

Practical 7-day cleanup plan

Common mistakes to avoid

• Assuming founder shareholding automatically transfers founder-created IP.
• Believing payment to a freelancer is enough without assignment wording.
• Forgetting pre-incorporation code, decks, prototypes and brand work.
• Letting one founder control the only domain, repository or cloud admin account.
• Using agency-created logos without source-file and copyright assignment.
• Failing to list third-party fonts, themes, plugins, stock assets and code libraries.
• Ignoring open-source licence obligations until investor diligence.
• Using customer data for AI training without contractual permission.
• Not preserving invention disclosure and proof-of-right documents for patent filings.
• Signing co-founder exit documents without IP reaffirmation and credential handover.

Sources reviewed

• Copyright Office, Copyright Act, 1957, Chapter IV: https://copyright.gov.in/Copyright_Act_1957/chapter_iv.html
• India Code, Copyright Act, 1957: https://www.indiacode.nic.in/bitstream/123456789/15356/1/the_copyright_act%2C_1957.pdf
• IP India, Patents Act, 1970: https://ipindia.gov.in/frontend/pdf/patents/1_113_1_The_Patents_Act__1970___incorporating_all_amendments_till_1-08-2024.pdf
• India Code, Trade Marks Act, 1999: https://www.indiacode.nic.in/bitstream/123456789/15427/1/the_trade_marks_act%2C_1999.pdf
• IP India official portal: https://ipindia.gov.in/
• Indian Contract Act, 1872 on India Code: https://www.indiacode.nic.in/bitstream/123456789/2187/2/A187209.pdf

FAQ Section

Founder / Business Takeaway

IP assignment is not a paperwork afterthought. It is how a startup proves that the product, brand, code, data and inventions belong to the company rather than to scattered individuals and vendors. Founders who clean this early save themselves from hard diligence questions later.

Before a fundraise, customer security review or co-founder exit, prepare the IP asset schedule, execute missing assignments, move accounts to company control and write down open risks honestly. Clean IP records make the company easier to invest in, acquire and operate.