Who Owns the Code in Custom Software Development In India?

INTRODUCTION
In the frantic "move fast and break things" culture of a modern startup, the legal paperwork is usually the last thing on a founder’s mind. There is a common, and very dangerous, assumption in the tech world: "If I paid for it, I own it." In the eyes of the law, especially regarding copyright and trademarks, that assumption is a trap.

For a software startup, the source code is the crown jewel. It is the primary asset that determines the company’s valuation during a seed round or an acquisition. Yet, without a clear, documented "chain of title," a company might be building its entire future on a foundation it doesn't actually own. This article breaks down the practical steps a startup must take to ensure that every line of code whether written in a garage, a coffee shop, or a remote dev-hub legally belongs to the company.

THE "WORK MADE FOR HIRE" MISCONCEPTION

The first thing any legal professional will tell you is that copyright law defaults to the creator. The "Work Made for Hire" doctrine is often cited as a catch-all solution, but it is surprisingly narrow. In many jurisdictions, this doctrine only applies automatically to formal employees.

If your developer is a full-time employee on payroll, you are generally safe. However, many startups survive on a rotating cast of freelancers and independent contractors. For these individuals, the "Work Made for Hire" rule does not apply unless there is a written contract explicitly stating so. Even then, it only covers specific types of work. To be safe, a startup should never rely on the default law; they should always use an express Assignment of Rights clause. This ensures that the moment the code is written, the ownership "leaps" from the creator to the company.

THE FOUNDER’S TRAP: THE "PRE-INCORPORATION" GAP

The messiest IP disputes often happen between the people who started the company. Imagine two founders coding an app for six months before they finally get around to registering their LLC or Corporation. During those six months, the code they wrote belongs to them as individuals, not the non-existent company.

If one of those founders has a falling out and leaves before the IP is formally transferred, they take their "share" of the code with them. This creates a "clouded title" that can kill a VC funding deal instantly. The solution is a Technology Assignment Agreement. Every founder must sign a document that transfers all "prior inventions" related to the company’s business into the corporate entity in exchange for their initial shares. This "cleans" the history of the code and puts everything under one roof.

THE PIIIA: THE GOLD STANDARD FOR DOCUMENTATION

When hiring, whether it’s the first employee or the fiftieth, the Proprietary Information and Inventions Agreement (PIIIA) is non-negotiable. A human-centric approach to this isn't just about "owning" the person's brain; it’s about setting clear boundaries.

A solid PIIIA should include:

• The "Duty to Assist": This requires the creator to help the company register copyrights or patents even after they have left the company.

• Power of Attorney: This is a "break glass in case of emergency" clause. If a former developer disappears or refuses to sign a document needed for a patent, this clause allows the company to sign on their behalf.

• Non-Disclosure: Ensuring that the logic behind the code the "trade secrets" doesn't end up on a competitor's server.

THE CONTRACTOR CONUNDRUM: DEV SHOPS AND FREELANCERS

Many startups outsource their Minimum Viable Product (MVP) to third-party agencies. This is where the documentation gets tricky. Agencies often use their own "boilerplate" code or pre-existing libraries to speed up the process.

If the contract says the startup owns "the work product," does that include the agency's underlying libraries? Probably not. The documentation must distinguish between Deliverables (which the startup should own outright) and Background IP (which the agency owns, but the startup must have a perpetual, royalty-free license to use). Without this distinction, you might find yourself in a position where you own the "house" but the agency owns the "foundation," making it impossible to sell the company later.

OPEN SOURCE: THE SILENT OWNER

Documentation isn't just about what your team writes; it’s about what they "borrow." No one writes 100% original code anymore; we all use Open Source Software (OSS). However, some OSS licenses (like the GPL) are "viral." If you use them incorrectly, they can legally force you to make your entire proprietary codebase public.

Startups need to maintain a Software Bill of Materials (SBOM). This is a living document a list of every third-party library used in the software. Documenting this isn't just a chore; it’s a defense mechanism. During due diligence, an acquirer will scan your code. If you can show them a clean, documented list of every license you use, it proves that the company is professionally managed.

ADMINISTRATIVE HYGIENE: THE DIGITAL PAPER TRAIL

Finally, documentation isn't just about legal contracts; it’s about administrative control.

• Company Accounts: Every developer should commit code using a company email address on a company-owned GitHub or GitLab account.

• The Master Key: The administrative rights to the repository should never be held by a single person’s private email.

• Vesting and IP: Link the ownership of shares to the signing of IP agreements. No signed agreement? No stock. This provides the ultimate leverage to ensure the paperwork actually gets done.

CONCLUSION
At the end of the day, investors don't just buy ideas; they buy assets. If a startup cannot prove, with a clear paper trail, that it owns every piece of its software, it doesn't really have an asset it has a potential lawsuit. By implementing Technology Assignment Agreements for founders, PIIIAs for employees, and clear licensing terms for contractors, a startup can secure its digital borders. Proper documentation might feel like a distraction from "building," but in reality, it is the only way to ensure that what you are building is actually yours to keep.

© 2025. All rights reserved.