Startup IP Assignment Checklist India: Founders, Employees, Contractors, Code and Brand Ownership
If your startup cannot prove who created an asset, who paid for it and who owns it today, the asset may become a diligence problem exactly when the business is raising or selling.
Direct answer
Your startup should be able to trace every important asset from creator to company. That means code, product designs, inventions, brand names, logos, domains, content, datasets, documentation and know-how should each have a clear owner, a signed transfer or licence where needed, and evidence that matches the cap table and contracts.
Use the official IP India portal, the Copyright Office and Startup India IPR guidance as primary reference points. The Best CS Firm In India discipline is to maintain one evidence-backed IP register instead of relying on verbal founder understandings.
Start with an ownership map, not a folder of certificates
| Asset | Likely creator or holder | Proof the company needs |
|---|---|---|
| Source code and models | Founder, employee, freelancer or agency | Signed assignment or licence, repository history and access record |
| Brand, logo and product name | Founder, designer or company | Trademark search/filing, design assignment and brand-use rules |
| Domain, social and app-store accounts | Founder, employee or agency account | Company registrant, administrator list and recovery control |
| Invention or industrial design | Inventor or design team | Invention disclosure, assignment and filing record |
| Content, photos and videos | Employee, creator or studio | Commissioning terms, releases, licences and assignment |
| Data and datasets | Customer, user, partner or public source | Collection purpose, notice/consent, licence and retention record |
1. Fix founder-created IP before the first institutional round
Founders often build the prototype, buy the domain and commission the logo before the company exists. Incorporation does not itself move those assets. Prepare an asset schedule that names the work, creator, creation date, repository or account, and current owner. Then document the transfer or licence to the company and approve it through the appropriate company process.
- List pre-incorporation code, designs, documents, domains and brand assets.
- Check whether a former employer, university, accelerator or client could assert rights.
- Record third-party libraries, templates, stock media and datasets used in the product.
- Move credentials to company-controlled accounts with at least two administrators.
- Keep the executed document, approval and updated register in the data room.
2. Align employment documents with actual product work
An employment template is not enough if the employee is hired by one group entity but builds a product owned by another. Match the employing entity, the repository, the project and the intended IP owner. Cover confidentiality, invention disclosure, assignment, assistance with registrations, return of material and continuing obligations after exit.
Employee file checklist
- Signed offer and employment agreement.
- Confidentiality and intellectual-property terms.
- Role and project allocation where multiple entities are involved.
- Device, repository and access records.
- Exit confirmation, access revocation and return-of-property evidence.
3. Treat contractors and agencies as a separate chain-of-title risk
Payment, a purchase order or a generic “work for hire” label may not resolve every ownership issue. The statement of work should identify deliverables, milestones, acceptance, source files, background IP, third-party components, permitted portfolio use and the rights being assigned or licensed.
| Clause | Founder question | Evidence |
|---|---|---|
| Deliverables | Is the code, design, dataset or document precisely described? | Versioned statement of work |
| Background IP | What remains owned by the contractor? | Schedule and licence terms |
| Assignment | When and how do rights move to the company? | Executed agreement and acceptance |
| Third-party material | What libraries, fonts, images or tools are embedded? | Bill of materials and licences |
| Further assurance | Will the creator support future filings or disputes? | Cooperation obligation |
4. Make brand, domain and account ownership operational
A trademark application does not solve a domain registered in a former employee’s name. Create a brand-control sheet showing marks, classes, applications, domain registrants, social handles, app-store accounts and authorised users. Set renewal reminders and remove personal email addresses from recovery flows.
Free Weekly Newsletter
Subscribe to BSA startup funding alerts
- Every Sunday, all Indian startup funding alerts in one place
- Monthly funding report on the last day of the month
- Free, concise, founder-focused, and easy to unsubscribe
Get the complete Indian startup funding roundup in your inbox, covering deals, sectors, investor moves, and founder readiness notes from the week.
Built for founders, investors, CFOs, and advisors
No spam. Unsubscribe anytime.
5. Review open-source, AI and data inputs
- Maintain a software bill of materials and review licence conditions before enterprise sales.
- Separate company code from code copied from client, employer or public repositories.
- Record the source and permitted use of training, testing and customer data.
- Check generative-AI tool terms before using outputs in core product or brand assets.
- Document security, access and deletion controls for confidential source material.
6. Build the investor-ready IP folder
| Folder | Minimum contents |
|---|---|
| Register | Asset, creator, owner, agreement, filing, renewal and dispute status |
| People | Founder, employee, consultant and agency assignments |
| Registrations | Trademark, patent, design and copyright filings where applicable |
| Technology | Repository ownership, access list, open-source inventory and licences |
| Commercial | Inbound and outbound licences, customer IP terms and partner restrictions |
| Disputes | Notices, oppositions, takedowns, settlements and remediation |
Common mistakes founders should avoid
- Assuming shares given to a founder automatically transfer that founder’s IP.
- Using an agency contract that transfers only final design files but not source files or code.
- Registering domains, cloud accounts and trademarks in personal names without a transfer plan.
- Ignoring previous-employer restrictions or contractor background IP.
- Publishing a product before checking brand conflicts and key domain availability.
- Showing investors an IP schedule that conflicts with employment or customer contracts.
A seven-day IP clean-up sprint
- Day 1: inventory product, brand, content, data and account assets.
- Day 2: map each asset to its creator, current holder and company use.
- Day 3: collect founder, employee, contractor and agency agreements.
- Day 4: review trademark, domain, repository and app-store ownership.
- Day 5: prepare missing assignment, licence or confirmation documents.
- Day 6: update the IP register and access controls.
- Day 7: run a data-room consistency check and escalate unresolved claims.
Founder / Business Takeaway
Investors do not need a startup to own everything in the world. They need a clean, documented right to build, sell and defend the product. Map the chain of title early, fix gaps while creators are cooperative, and keep ownership evidence aligned with how the business actually operates.
Suggested internal links
Official sources
FAQ
Does paying a contractor automatically transfer IP?
Do not assume it does. Use a precise written agreement covering deliverables, background rights, assignment, licences and further assistance.
What about code created before incorporation?
Record the creator and execute a documented transfer or licence to the company.
Should the company own the domain and app-store accounts?
Operational control should sit with company-controlled accounts and named administrators.
What will investors test?
They commonly review chain of title, people agreements, registrations, domains, open-source use, data rights, licences and disputes.
