Building a Startup on Trust? Where Founders Need Legal Protection Instead

A startup can spend months developing a product, pay a freelancer for its code, hire an agency for its branding and still discover that its intellectual property position is less secure than its founders assumed.

The problem often begins with a simple misunderstanding: paying for work, receiving the files and owning the underlying intellectual property are not necessarily the same thing.

For founders seeking startup legal advisory in India, this distinction matters long before a dispute arises. It can affect whether a company can modify its software, transfer its technology, appoint a replacement developer, license its product or demonstrate ownership during an investment or acquisition process.

The solution is not to distrust every freelancer or turn every conversation into a legal negotiation. It is to document the relationship clearly enough that both sides understand what is being created, who owns it, what may be reused and what happens when the engagement ends.

This guide explains how intellectual property ownership works under Indian law, what founders should check in contractor agreements, and how to address ownership gaps before they become commercial problems.

Who owns intellectual property created by a freelancer or developer?

In India, a startup does not automatically own every copyright-protected work simply because it paid a freelancer or developer to create it. Under section 17 of the Copyright Act, 1957, the author is generally the first owner of copyright, subject to statutory exceptions. Employment arrangements and certain commissioned works have specific rules, but those exceptions do not create a universal ownership rule for every freelance software or design project.

A written agreement should therefore clearly establish whether the creator assigns the relevant intellectual property to the startup or grants the startup a licence to use it. The exact result depends on the work, the parties' relationship, the agreement and the applicable law.

For example, consider a startup that pays an independent developer to build a customer dashboard. The developer delivers the application, and the founder pays the final invoice. If the contract addresses delivery and payment but says nothing clear about intellectual property, the founder may have evidence of a commercial transaction without having adequately documented ownership of every relevant right.

That does not mean the startup necessarily has no rights. The contract, applicable statutory provisions and facts must be examined. It means the startup should not assume that payment alone settles the issue.

The first practical question is not simply, “Did we pay for it?”

It is: “What rights did we acquire, from whom, in which work, and under what written terms?”

What Indian copyright law says about ownership

The author is generally the first owner

Section 17 of the Copyright Act establishes the general rule that the author of a work is its first copyright owner, subject to the exceptions set out in the Act.

Those exceptions matter. For example, the Act provides for employer ownership in certain works created in the course of employment under a contract of service, subject to the statutory wording and any agreement to the contrary. It also provides a specific rule for certain commissioned photographs, paintings, portraits, engravings and cinematograph films made for valuable consideration at another person's instance.

These provisions should not be casually extended to every work commissioned by a business. A startup hiring an independent developer should not assume that the statutory rule for a commissioned photograph automatically determines ownership of custom software.

The relevant provisions are available in the Copyright Act, 1957, Chapter IV.

What counts as copyright-protected work?

Copyright may protect original expression in different forms, including literary and artistic works and computer programs, subject to the Act's requirements.

For a startup, relevant assets may include:

• Source code and object code.
• Website copy and technical documentation.
• Original illustrations, icons and graphics.
• Interface artwork and certain visual assets.
• Marketing photographs, videos and written content.
• Original training materials, manuals and reports.

Not everything valuable to a startup is protected by copyright in the same way. A business idea, general method or commercial objective is not automatically protected as a copyright work merely because it is valuable. A particular expression of an idea may be protected, while the underlying concept may require a different legal or commercial protection strategy.

A product can also contain several layers of rights. Its source code may raise copyright issues, its brand may raise trademark issues, and a technical invention may require a separate patentability assessment.

Practical lesson: identify the asset before deciding how to protect or transfer it.

Why the type of asset changes the legal analysis

Founders often use “IP” as if it were one indivisible asset. In practice, a startup may need several different arrangements to secure its product.

Software and source code

A software project can contain original code written for the startup, libraries developed earlier by the contractor, third-party dependencies, open-source software and components supplied by the startup itself.

An agreement that merely says “the developer will deliver the application” does not clearly answer whether the startup owns all newly created code, receives a licence to the developer's existing tools, or may continue using the application if the developer relationship ends.

A useful contract distinguishes between:

1. Project-specific work: the code, documentation and other deliverables created for the defined project.
2. Background technology: tools, frameworks, reusable modules and materials the developer owned or developed independently before the engagement.
3. Third-party components: software, libraries, assets or services subject to another party's licence.
4. Startup materials: specifications, datasets, designs, credentials and other materials supplied by the company.

The agreement should state the intended rights for each category.

Logos, branding and visual assets

A designer may create a logo, brand illustrations, a website layout and social media templates in the same engagement. These deliverables should not be treated as interchangeable.

The founder should establish which original works are included in the transaction, whether editable files are part of the delivery, whether the designer may display the work in a portfolio and whether third-party fonts, stock graphics or templates are included.

Trademark ownership is a separate question from copyright ownership in a logo. A company may need to consider the trademark application, the identity of the applicant and the proper documentation of any transfer. Sections 37–45 of the Trade Marks Act, 1999 address assignment and transmission, including registration requirements for assignments of registered marks.

See the official Trade Marks Act, 1999.

Technical inventions and product designs

A startup developing a novel technical product may need to consider patents, while a product's visual appearance may raise design-registration questions.

Patent ownership and assignment have their own statutory requirements. Section 68 of the Patents Act, 1970 requires an assignment or other specified interest in a patent to be in writing and duly executed. Section 69 deals with registration of title or interests.

The Designs Act, 2000 separately defines the proprietor of a new or original design. Its rules should be checked for the particular design and transaction.

A founder should not assume that a copyright assignment alone transfers every patent or registered design right associated with a product.

Official references:

• Patents Act, section 68
• Patents Act, section 69
• Designs Act, section 2(j)

Assignment or licence: what should a startup obtain?

One of the most important decisions in a contractor agreement is whether the startup needs an assignment of intellectual property, a licence to use it, or a combination of both.

What is an assignment?

An assignment transfers the specified rights from one party to another, to the extent permitted by law and the agreement.

For example, a startup may want ownership of the custom source code developed specifically for its product so it can maintain, modify, commercialise or transfer the software without having to negotiate a new licence every time its business changes.

A copyright assignment is governed by sections 18 and 19 of the Copyright Act, 1957. Section 19 requires a written assignment signed by the assignor or an authorised agent, identification of the work, specification of the rights assigned, duration and territorial extent, and consideration-related particulars.

The Act also provides default rules where the duration or territory is not specified, subject to its provisions. Those defaults are not a sensible substitute for carefully drafted terms.

See the Copyright Act, Chapter IV.

What is a licence?

A licence grants permission to use intellectual property under specified terms without necessarily transferring ownership.

This may be appropriate where a developer uses a pre-existing software library that they need for other projects, or where a startup uses a third-party platform under a commercial licence.

Section 30 of the Copyright Act addresses written licences by copyright owners. Section 30A applies section 19, with necessary adaptations and modifications, to licences under section 30.

A licence should be reviewed for its scope, duration, territory, permitted users, sublicensing, modification, commercialisation and termination terms, as relevant to the work.

Why the distinction matters

Suppose a developer uses a reusable reporting engine in several client projects but builds a custom analytics module for a startup.

The parties might agree that the startup owns the custom module while receiving a sufficiently broad licence to use the reporting engine as part of its product. That arrangement may preserve the developer's reusable technology while protecting the startup's ability to operate its business.

The precise drafting depends on the technical architecture, the applicable rights and the commercial arrangement.

The objective is not to demand ownership of everything a contractor has ever created. It is to make sure the startup has the rights it needs to operate, develop and commercialise its product.

The overlooked risk: the person signing may not own everything

An agreement is only as useful as the rights the person signing it can actually transfer.

A freelancer may have subcontracted part of the work. A development agency may have engaged individual programmers. A designer may have incorporated an illustration purchased from a third-party marketplace. A founder may have used code written by a former colleague before the company existed.

In each situation, the startup needs to identify the source of the relevant rights.

Ask who actually created the work

A company should identify the individuals or entities that contributed to important deliverables and check whether the contractual arrangements establish the necessary rights.

If an agency promises that it owns all project deliverables but cannot demonstrate that its subcontractors have granted the required rights, a gap may remain.

Useful contractual protections may include obligations to obtain appropriate assignments or licences from contributors, disclose subcontractors, identify third-party materials and provide reasonable supporting documentation.

These are risk-management measures, not a guarantee that a dispute can never arise.

Check pre-existing work

A contractor may reuse their own libraries, templates or development tools. That is not automatically improper. The problem arises when the startup cannot determine what it owns and what it is merely permitted to use.

Ask the contractor to identify material that:

• Existed before the engagement.
• Is owned by another party.
• Is licensed under open-source or other third-party terms.
• Requires continuing access to a third-party service.
• Cannot legally be assigned to the startup.

A clear schedule of excluded or licensed materials can prevent disagreements later.

Do not rely solely on a warranty

A contractor's warranty that the deliverables do not infringe third-party rights can be useful. However, a warranty does not itself transfer ownership of material that belongs to someone else.

If the contract includes indemnities, review their scope, exclusions, procedure and practical enforceability. The commercial value of a promise depends partly on whether the party making it can honour it.

A founder-specific problem: the work began before incorporation

Early-stage startups frequently begin as projects between individuals. A founder pays a developer personally, a designer helps create the brand, or a technical co-founder writes the first version of the product before the company is incorporated.

Later, the founders register a company and assume that all the earlier work now belongs to it.

That assumption should be checked.

Why the timeline matters

The company may not have existed when the contract was signed. The original contracting party might have been a founder personally, a partnership or another entity. The deliverables may have been created at different times, under different arrangements.

The relevant questions include:

• Who commissioned the work?
• Who entered into the agreement?
• Who was intended to receive the rights?
• Did the agreement identify a future company or permit transfer to it?
• Was a subsequent assignment or other appropriate transfer executed?
• Are the original creator's rights adequately documented?

The correct solution depends on the original documents and the nature of the rights.

How to close the gap

The startup should assemble the original agreements, invoices, delivery records and correspondence, then obtain advice on the appropriate confirmatory assignment, licence, novation or other document where needed.

A new document should not be backdated to create an appearance that an earlier transfer occurred when it did not. The parties should document the actual transaction accurately.

This is a good example of why corporate legal advisory can be valuable before fundraising: the company may need to establish that the assets essential to its business are held by the correct legal entity.

The hidden cost of vague intellectual property clauses

Consider a hypothetical startup that has paid for an application over twelve months. Its developer agreement says:

“The developer will deliver the completed software upon payment of the agreed fees.”

The application works. The company has the files. The founder is satisfied.

A year later, the company wants to replace the developer and appoint another team to modify the application. The original developer claims that the agreement covered delivery and use, not a complete transfer of ownership.

The startup now needs to examine the agreement, the parties' conduct, the relevant statutory rules and the work actually delivered. The outcome cannot be predicted from the invoice alone.

The practical costs may include:

• Legal review of the original agreement and communications.
• Technical review to identify the disputed components.
• Negotiation of a confirmatory assignment or licence.
• Delays while access and rights are clarified.
• Additional payment if a negotiated settlement is appropriate.
• Further documentation for investors or a purchaser.

Not every ambiguity leads to litigation. Many can be resolved commercially. But the time to clarify ownership is usually before the parties disagree about it.

What should a startup's IP agreement cover?

A well-designed agreement should reflect the actual work, the parties and the intended commercial outcome. It should not rely on a generic sentence about “all rights” without defining the deliverables or addressing exclusions.

The following issues deserve attention.

A. Identify the contracting parties

Use the correct legal name of the company or individual entering the agreement. If the startup is incorporated, confirm that the agreement identifies the intended company rather than relying on an informal project name.

For an overseas contractor, check the contractor's legal identity, country of establishment and authority to sign.

B. Define the deliverables

List the work covered by the arrangement as precisely as practical.

For software, this might include source code, object code, documentation, configuration files, deployment scripts and project-specific materials. For branding, it might include final artwork, editable files and specified design assets.

The list should reflect what the startup actually needs, not an unrealistic promise to transfer every tool or asset used during development.

C. State the intended ownership position

The agreement should distinguish between project-specific intellectual property that is to be assigned and pre-existing or third-party material that is to remain subject to separate terms.

Where copyright is assigned, ensure that the written instrument addresses the statutory requirements in section 19. Where a patent or registered mark is involved, consider the additional rules governing those rights.

D. Explain the treatment of background technology

A developer may retain ownership of pre-existing tools while granting the startup rights necessary to use the deliverables.

The licence should be broad enough for the intended product lifecycle, where commercially agreed. Consider whether the startup needs rights to modify, maintain, distribute, commercialise or sublicense the relevant component.

A clause that permits use only within a narrow project context may be inadequate if the startup intends to license the product to customers.

E. Address third-party and open-source components

Require appropriate disclosure of components that are material to the project, subject to the scope and risk of the engagement.

The startup should understand applicable licence conditions, attribution obligations, redistribution rules and any restrictions that could affect commercial distribution. Open-source software is not inherently unsafe or unsuitable for a commercial product; the issue is whether its licence terms are compatible with the intended use.

F. Document payment and transfer mechanics

The agreement should state how fees relate to the assignment or licence, when the relevant obligations take effect and whether any agreed milestone or payment condition applies.

Avoid assuming that a transfer has occurred merely because a final invoice was paid. The parties should expressly document the intended result.

G. Cover confidentiality and access

A contractor may need access to source repositories, customer information, credentials or product plans. Confidentiality obligations should identify the protected information and permitted uses, with appropriate exceptions and return or deletion arrangements.

Access should be limited to what the contractor needs. Use company-controlled accounts where practicable and avoid sharing a single founder's personal credentials.

H. Plan for exit and handover

The agreement should explain what happens when the engagement ends, including delivery of agreed materials, transfer of administrative access, return of confidential information, removal of unnecessary access and reasonable transition assistance.

This reduces dependence on a single individual and makes it easier to appoint another developer.

I. Address representations and remedies

Depending on the engagement, the startup may request representations concerning authority, originality to the extent appropriate, disclosed third-party materials and the contractor's ability to grant the agreed rights.

Indemnities and liability provisions should be proportionate to the transaction. No clause can eliminate every infringement risk, and enforceability depends on the contract and applicable law.

J. Keep an evidence trail

Retain the signed agreement, amendments, invoices, delivery records, relevant approvals, repository history and any assignment documents.

Section 10A of the Information Technology Act, 2000 provides that a contract is not unenforceable solely because electronic means were used in its formation. That does not mean every email exchange necessarily proves every disputed term. Preserve reliable records of the agreement and the parties' acceptance.

The official provision is available through India Code's legislation resources.

International developers: does an Indian agreement solve everything?

Not necessarily.

An Indian startup may hire a developer in another country, engage a foreign agency or license its product internationally. The legal analysis can then involve several jurisdictions.

Questions may include:

• Which law governs the contract?
• Which courts or dispute-resolution forum have jurisdiction?
• What is the contractor's legal status and who employs or supervises the actual creators?
• Does local law impose formalities or restrictions on intellectual property assignments?
• Are there moral rights or other creator rights that cannot be waived in the same way?
• Are separate assignments or recordals required in countries where patents or trademarks are registered?
• Does the third-party software licence permit the planned commercial use?

A governing-law clause is important, but it does not automatically settle every issue involving registered intellectual property or mandatory local law.

The startup should assess the jurisdictions relevant to the transaction rather than assuming that a clause selecting Indian law resolves all cross-border questions.

For a modest engagement, a targeted legal review may be sufficient. For core technology, a strategically important invention or a major international development contract, specialist cross-border advice may be warranted.

What if the startup has already paid the freelancer?

An incomplete agreement does not necessarily mean the startup has no rights or no practical remedy. It means the existing position must be assessed before further assumptions are made.

A sensible process is:

Step 1: Collect the documents. Find the proposal, contract, invoices, messages, specifications, change requests and delivery records.

Step 2: Identify the work. Separate the original code or design from third-party components, background tools and later modifications.

Step 3: Establish the ownership chain. Identify who created the work, who contracted for it, whether subcontractors were involved and what rights were actually granted.

Step 4: Review the legal position. A lawyer should consider the agreement and the relevant statutory provisions before advising whether the startup has ownership, a licence or another enforceable right.

Step 5: Discuss a documented solution. Where the parties agree that additional rights should be transferred, they can consider a properly drafted assignment, licence or confirmatory instrument. Any additional consideration should be negotiated transparently.

Step 6: Preserve business continuity. Secure lawful access to the code and relevant systems, maintain backups and document the handover. Avoid unauthorised access to a contractor's personal accounts or unrelated systems.

Step 7: Escalate disputes proportionately. If the contractor refuses to cooperate or threatens to restrict critical access, obtain legal advice on the available contractual and legal options before taking action.

The right response depends on the documents and facts. A founder should not assume either that the startup automatically owns everything or that the contractor necessarily owns everything.

Why intellectual property ownership matters to investors

A startup's intellectual property position can become relevant when it raises capital, enters a strategic partnership, licenses its technology or negotiates an acquisition.

A prospective investor may ask whether the company owns or has adequate rights to the assets central to its business. The precise scope of diligence varies by investor, transaction and risk profile.

An incomplete ownership record can generate questions:

• Was the source code assigned to the company?
• Are founders' earlier contributions documented?
• Do contractor agreements cover the relevant deliverables?
• Are important third-party components disclosed?
• Can the company lawfully modify and commercialise the product?
• Are trademark or patent applications held by the correct entity?
• Are any rights subject to termination or restricted licences?

A startup can maintain an intellectual property register that records each material asset, its creator, the date of creation, the relevant agreement, the current owner or licensee, third-party dependencies and the location of supporting documents.

This is useful even when no investment is imminent. It gives the founders a clearer picture of the assets they rely on and the work needed to correct gaps.

When does a startup need legal advisory?

Not every design task requires a lengthy legal engagement. The appropriate level of review depends on the asset's value, the business's reliance on it and the complexity of the arrangement.

A focused review is especially worth considering when:

• A freelancer is developing the startup's core product or platform.
• The company intends to commercialise or license custom software.
• A founder created important assets before incorporation.
• Several developers or agencies contributed to the same product.
• A contractor is located outside India.
• A patent, registered design or important brand asset is involved.
• The startup is preparing for investment, acquisition or a major commercial partnership.
• The parties disagree about ownership, permitted use or handover.

Startup legal advisory in India can help founders identify the relevant assets, assess the existing contracts, distinguish assignment from licensing, document contributor rights and plan for future commercial use.

Legal advisory for businesses should be proportionate. A straightforward freelance engagement may need a clear, short agreement; a complex product with several contributors and international distribution may require a more detailed intellectual property and commercial review.

The objective is not to add paperwork for its own sake. It is to ensure that the company's commercial plans are supported by rights it can actually demonstrate.

Conclusion: trust your team, but document the rights

Trust is valuable in a startup. It helps founders work quickly, collaborate with specialists and build products without unnecessary friction.

But trust should not be asked to answer questions that the contract leaves unresolved.

For an Indian startup, the central task is to identify the intellectual property it depends on, establish who owns or controls it, document the rights needed for the business and preserve the evidence that supports those rights.

A signed agreement is not a magic solution. It must cover the right work, be executed by the right parties and reflect the applicable law. But a clear agreement, supported by a reliable handover and ownership record, gives founders a much better starting point than an invoice and an assumption.

If your startup relies on freelancer-created software, branding, designs or other commercially important assets, The Salt Legal can help assess the relevant contractual and intellectual property questions and identify practical next steps. The appropriate advice will depend on the documents, the type of work and the jurisdictions involved.

FAQ section

1. Does a startup own software after paying a developer?

Not automatically in every case. Payment proves a commercial transaction, but ownership depends on the applicable law, the parties' relationship and the contract. Review the written terms to establish whether the startup received an assignment, a licence or another set of rights.

2. Who owns copyright in work created by a freelancer in India?

The author is generally the first copyright owner under section 17 of the Copyright Act, 1957, subject to statutory exceptions. The legal position depends on the type of work, the creator's status and the specific circumstances. An appropriate written assignment or licence can document the rights agreed between the parties.

3. Is an email agreement enough to transfer intellectual property?

An electronic contract is not unenforceable solely because electronic means were used, under section 10A of the Information Technology Act, 2000. However, copyright assignments must satisfy the applicable written-assignment requirements, including section 19 of the Copyright Act. Whether a particular email exchange meets those requirements depends on its contents, authentication and circumstances.

4. Should a startup use an IP assignment or a licence?

An assignment transfers specified rights, whereas a licence permits use under agreed conditions without necessarily transferring ownership. The appropriate arrangement depends on whether the startup needs ownership of custom work, permission to use background technology or a combination of both.

5. Who owns code written before a startup was incorporated?

The answer depends on who commissioned the work, who created it, the original agreement and whether the relevant rights were subsequently transferred. Incorporating a company does not, by itself, resolve every ownership question relating to earlier work. The startup should review the original documents and obtain advice on any necessary transfer.

6. Can a developer reuse code created for a startup?

It depends on the code, the rights involved, the agreement and any third-party restrictions. A contract can distinguish the startup's project-specific code from the developer's pre-existing tools and reusable components. The parties should clarify these categories rather than assume that either party owns every component.

7. Does a freelancer agreement need an intellectual property clause?

A written agreement is a practical way to document ownership, licensing, confidentiality, deliverables and handover responsibilities. Where copyright is assigned, the agreement should satisfy the relevant statutory requirements. The precise terms should reflect the project and the rights the business needs.

8. When should a founder consult a business lawyer about intellectual property?

Consider legal advice when a freelancer develops core technology, ownership terms are unclear, several contributors are involved, a founder created assets before incorporation, an international contractor is engaged, or an investment or acquisition is approaching. A lawyer can review the existing documents and advise on the appropriate steps based on the facts.