A startup founder receives an encouraging email from a potential enterprise customer. The company is interested in adopting the startup’s software across several departments, subject to its legal, security and procurement review.

The commercial team begins discussing pricing. The technical team prepares a demonstration. The founders start estimating the revenue the contract could generate.

Then the customer’s legal team asks a different set of questions.

Who owns the software? Were the developers’ rights transferred to the company? Can the startup legally license the product to customers? Does the code include third-party components, and are those components being used under appropriate licences?

The founder has an invoice from the development agency, access to the source-code repository and a signed agreement for software development. Yet the agreement does not clearly establish whether the company owns all the rights it intends to commercialise.

This is a hypothetical scenario, but it reflects a practical distinction that growing businesses need to understand: having a product available for sale does not necessarily establish that the company owns every intellectual property right needed to sell it.

For founders searching for an IP assignment agreement startup India solution, the commercial question is not simply whether a contract exists. It is whether the company can demonstrate a coherent legal basis for developing, modifying, licensing and distributing its product.

Intellectual property ownership becomes especially relevant when a business begins serving larger customers, entering strategic partnerships or preparing for an investment or acquisition. These transactions may require the company to explain the rights supporting the product rather than rely on assumptions made during its early development.

Why a large customer may ask who owns your product

An enterprise customer is not necessarily trying to acquire the startup’s intellectual property. It may only want a licence to use the software.

Even so, the customer has a commercial reason to understand the supplier’s rights.

Suppose a company integrates a startup’s software into its customer-support operations. It trains employees, migrates internal processes and connects the product to several existing systems. If a dispute later prevents the startup from licensing or maintaining the software, the customer could face operational disruption.

A legal review may therefore ask whether the startup has sufficient rights to provide the promised service and whether any third-party restrictions could interfere with that arrangement.

The scope of the review depends on the transaction. A customer buying a limited subscription may raise different questions from a customer commissioning customised software, demanding extensive modification rights or requiring a white-label product.

In some situations, the customer may ask the startup to confirm that it owns the relevant software. In others, it may request representations about the company’s rights to use and license third-party components. The precise requirements depend on the contract and the parties’ risk allocation.

This is where an IP assignment agreement becomes commercially relevant.

The startup needs to establish whether the rights it received from founders, employees, freelancers and agencies support the rights it now intends to grant to a customer. An agreement adequate for an internal prototype may not answer every question concerning a commercially distributed product.

The objective is not necessarily to transfer ownership of the entire product to the customer. It is to ensure that the startup has the legal rights required to make the contractual promises it offers.

The difference between owning the software and being able to use it

Founders sometimes treat ownership, access and permission to use software as though they were the same thing.

They are different questions.

A company may possess the source code without owning the copyright in it. It may own original code while relying on a third-party licence for an essential library. It may have permission to use a component internally but lack the rights needed to redistribute or sublicense it.

These arrangements are not automatically defective. The problem arises when the founder cannot distinguish between them.

Consider a hypothetical SaaS company that hired an agency to build its initial product. The agency provided the application, documentation and repository access. The startup paid the agreed price and began selling subscriptions.

Later, an enterprise customer requests a customised version that can be deployed within its own environment. The founder assumes that the startup can supply the customised code because it has always operated the product.

However, the agency agreement does not clearly establish the scope of copyright transferred to the company. It also does not distinguish newly created code from the agency’s pre-existing tools.

The fact that the startup possesses the code does not resolve those questions.

Under Section 17 of the Copyright Act, 1957, the author is generally the first owner of copyright, subject to the Act’s exceptions. Section 18 permits copyright to be assigned wholly or partly and subject to limitations. Section 19 prescribes formal requirements for copyright assignments.

The starting point is therefore to establish who owns the relevant work and what rights have been transferred. A licence may be sufficient for some components, while an assignment may be appropriate for rights the startup intends to acquire from a contributor.

The business should not promise an enterprise customer rights that it has not established a legal basis to grant.

The founder-built product that never formally became a company asset

A different problem can arise when the product existed before the company.

Many startups begin with a founder building a prototype, testing a business idea or developing software outside a formal corporate structure. Once the company is incorporated, the product is moved into the business and used to attract customers.

From a commercial perspective, the transition may feel complete. The founders operate the company, pay expenses and own shares in it.

The legal position requires a separate examination.

A company is a distinct legal person from its shareholders and directors. A founder’s shareholding does not, by itself, document a transfer of personally owned intellectual property to the company.

Suppose a founder developed a scheduling tool before incorporation. The company now sells subscriptions to that tool, and an enterprise customer wants the right to integrate it with its internal systems.

The company should establish whether the founder transferred the relevant rights to it, whether it has a licence or whether another arrangement governs the use.

If the founder still owns the relevant rights, an appropriate assignment may be needed to establish company ownership. The specific position depends on the facts, existing agreements and applicable law.

This issue is particularly relevant when the original product has become the main source of revenue. A company should not assume that years of commercial use will, by themselves, answer every question about the original ownership of the code.

The same consideration applies to founder-created technical documentation, product artwork and other assets that existed before the business was incorporated.

An enterprise transaction may bring this history into focus because the customer wants to understand whether the company can lawfully continue providing the product and granting the rights set out in its contract.

Paying a freelancer does not answer every ownership question

Outsourcing is a rational choice for many startups. A small business may need a working product before it can afford to hire an internal engineering team.

The founder agrees on a price, reviews progress and pays when the deliverables are completed. The relationship appears straightforward until the startup needs to establish precisely which rights were transferred.

Under Indian copyright law, payment is not a universal substitute for a valid assignment.

Section 17(c) of the Copyright Act generally provides that an employer is the first owner of copyright in a qualifying work created in the course of employment under a contract of service or apprenticeship, subject to statutory exceptions and agreements to the contrary.

That provision should not be assumed to govern every independent contractor engagement. Section 17(b) also contains a specific rule for certain commissioned works, including specified photographs, paintings or portraits, engravings and cinematograph films. It is not a general rule that paying for every commissioned work transfers copyright to the customer.

A software development agreement should therefore address the rights intended to pass from the developer or agency to the startup. The agreement should also make clear which deliverables are covered.

Where the agency uses subcontractors, the company should consider whether the agency has obtained the rights necessary to make the promised transfer.

This matters to enterprise customers because the startup may need to grant rights in the work that has been delivered. If the agency has not secured all the relevant rights, the startup may need additional documentation or another arrangement before it can safely make certain contractual commitments.

The correct response is not to assume that every agency contract is inadequate. It is to examine whether the company has the rights required for the specific product and transaction.

The third-party software problem that can survive an assignment

Even a well-drafted assignment cannot transfer rights that the assignor does not own.

A startup’s software may incorporate open-source libraries, commercial frameworks, reusable tools, licensed design material and third-party services. Some components may be essential to the operation of the product despite not being owned by the company.

Suppose an agency develops a payment-management platform. It assigns its rights in the new code to the startup, but the platform also uses a third-party library subject to a separate licence.

The startup may own its original code while continuing to rely on that library under the applicable licence.

That arrangement can be commercially workable. However, the licence must permit the company’s intended use. If the startup promises an enterprise customer that it can redistribute or sublicense the complete product, the third-party component’s terms may need closer examination.

Open-source software should not be treated as a single category with identical conditions. The startup needs to identify the components it uses and assess the applicable licence requirements, including conditions relevant to modification and distribution.

The same principle applies to an agency’s background intellectual property. A contributor may retain ownership of pre-existing tools and give the startup a licence to use them within the product. The startup should understand the scope of that licence before promising rights to customers.

This is one reason why a contractual statement that “all intellectual property belongs to the company” is not enough on its own. The company needs to understand what the assignor owns, what third-party rights exist and what permissions are required to operate the business.

Why the words in the assignment matter

Copyright assignments are not merely commercial statements of intent. Section 19 of the Copyright Act sets out particular requirements.

A copyright assignment must be in writing and signed by the assignor or a duly authorised agent. It must identify the work and specify the rights assigned, the duration and territorial extent. It must also specify the amount of royalty and any other consideration payable to the author or legal heirs during the assignment, where applicable under the statutory provision.

The Act also provides defaults where the assignment period or territorial extent is not specified.

If the period is unspecified, Section 19(5) provides a five-year default. If territorial extent is unspecified, Section 19(6) presumes that the assignment extends within India. Section 19(4) addresses non-exercise: if the assignee does not exercise the assigned rights within one year, the assignment of those rights is deemed to have lapsed after that period unless otherwise specified in the assignment.

These statutory defaults should not be treated as recommended drafting choices. A startup intending to license software over the long term, including to customers outside India, should not leave such matters to assumptions.

Section 18 also provides that assignment of copyright in a future work takes effect only when that work comes into existence. A development contract may address future deliverables, but the actual work and the contractual terms still need to be assessed.

The commercial purpose is to establish that the rights being promised to a customer are supported by the assignment and any necessary licences.

Patents and trade marks need their own treatment

An enterprise customer may also want to understand the startup’s rights in technology, a registered brand or another protected asset.

These questions cannot always be answered by a copyright assignment alone.

Section 68 of the Patents Act, 1970 requires specified assignments and other interests in patents to be in writing and duly executed. Section 69 separately addresses registration of title or interests. Where a patent or patent application forms part of the startup’s product or commercial offering, the relevant ownership documents and records should be examined under the applicable framework.

Trade mark assignments raise different considerations. Section 45 of the Trade Marks Act, 1999 addresses registration of an assignee’s title to a registered trade mark. Other provisions address assignability, assignments without goodwill and associated trade marks, subject to their respective conditions.

For example, a founder might have registered the startup’s principal brand in an individual name while the company uses it across its products and commercial agreements. The company should establish how its rights were obtained and whether the relevant ownership records and transfer formalities have been addressed.

The purpose is not to suggest that every startup must register every asset or complete the same paperwork. The requirements depend on the rights involved. A patent, a registered trade mark and software copyright should not be treated as interchangeable forms of property.

What enterprise customers may ask during legal review

The precise review will depend on the customer’s industry, the software being supplied and the contract under negotiation. Some transactions involve a limited subscription, while others include extensive customisation, system integration or rights to distribute a product further.

The customer may ask who created the core software and whether the startup has the rights required to license it. It may seek confirmation that the founders transferred relevant pre-incorporation assets, that employee and contractor arrangements address ownership, and that any third-party components can be used in the manner contemplated by the agreement.

Registered rights may also require attention where a brand, patent or design is relevant to the product. In technology-heavy arrangements, the parties may separately address access to source code, maintenance, confidentiality and the treatment of customer-specific modifications.

These questions concern different legal and commercial issues. Ownership documents do not automatically establish that every third-party component is compliant, just as control of a repository does not necessarily prove ownership of copyright.

An unclear ownership position does not automatically prevent a commercial deal. It may, however, require further explanation, additional documentation, a revised licence arrangement or specific risk allocation in the contract.

The significance depends on the asset and transaction. A customer’s ability to continue using a core platform may present a different risk from ownership of a secondary visual asset.

For the founder, the practical objective is to understand these issues before making representations the company may be unable to substantiate.

Build the commercial relationship on rights the company can actually grant

The best time to clarify ownership is when the relevant work is commissioned or created, rather than when a customer’s legal team asks for evidence.

A startup should understand the origin of the material assets supporting its product, the agreements under which they were created and any third-party rights that affect their use. It should also understand the difference between rights it owns and rights it holds under licence.

That understanding can help the company negotiate commercial contracts more accurately. If a customer needs a licence, the startup can identify the rights it can grant and any restrictions that must be preserved. If the company needs to acquire rights from a founder or contractor, the appropriate transfer can be considered before the transaction depends on it.

The process does not need to become a bureaucratic exercise. The scope of review should reflect the business, the importance of the assets and the commitments the startup intends to make.

What matters is that the company does not confuse payment with ownership, access with title or a broad contractual phrase with compliance across every category of intellectual property.

The SALT Legal: startup IP ownership and commercial readiness

A startup’s intellectual property arrangements should support the way it actually operates and the rights it intends to grant to customers.

The SALT Legal’s Startup Legal Advisory offering can help founders examine existing assignments, founder-created work, software development agreements, employee and contractor arrangements, licences and relevant ownership records.

The appropriate review depends on the company’s product, development history and commercial plans. It may identify questions about ownership, third-party licences or registered rights that need to be addressed before a major customer contract, investment or acquisition.

For founders preparing to sign an enterprise agreement, reviewing the company’s IP ownership position can help clarify what the business owns, what it uses under licence and what rights it can responsibly promise to its customers.

Legal disclaimer: This article is for general informational purposes and does not constitute legal advice. Intellectual property ownership depends on the relevant facts, agreements and applicable law. Obtain advice from a qualified Indian lawyer before acting on a specific matter.

Frequently asked questions

1. What is an IP assignment agreement for a startup in India?

An IP assignment agreement documents the transfer of specified intellectual property rights from a rights holder to a startup. Depending on the asset, it may cover copyright in software, technical documentation, eligible patent rights or other intellectual property. Its legal effect depends on ownership, the wording of the agreement and the statutory requirements that apply.

2. Why might an enterprise customer ask a startup to prove IP ownership?

The customer may need to understand whether the startup has the rights required to license, maintain or supply its product. The review may examine founder-created assets, development agreements, employee and contractor arrangements, third-party licences and registered ownership records. The scope varies by transaction.

3. Does paying a software development agency transfer copyright?

Payment alone does not necessarily establish copyright ownership. The applicable legal rules, working relationship and contract need to be examined to determine whether the relevant rights have been transferred. A startup should also consider whether the agency used subcontractors or third-party components.

4. Can a startup assign rights in software that has not yet been created?

Section 18 of the Copyright Act permits assignments of copyright in future works, but the assignment takes effect only when the work comes into existence. The agreement should still be assessed for the deliverables, rights and statutory requirements involved.

5. Does an IP assignment cover open-source components?

An assignment cannot transfer ownership of third-party components that the assignor does not own. The startup should identify the applicable licences and determine whether its intended use, modification and distribution of those components are permitted.

6. Is a copyright assignment enough for patents and trade marks?

No. Copyright, patent and trade mark rights have different statutory frameworks. Patent assignments are addressed by Sections 68 and 69 of the Patents Act, 1970, while Section 45 of the Trade Marks Act, 1999 addresses registration of an assignee’s title to a registered trade mark, subject to the Act.

7. Should a startup review its IP agreements before signing an enterprise contract?

It is sensible to review the relevant ownership position before making contractual promises about the product. The appropriate scope depends on the rights being licensed or transferred, the product’s development history and any third-party restrictions.