Buyers assume that paying for software means owning it. In many jurisdictions, that is not automatic. Ownership follows the contract, and a vague or missing clause is expensive to fix once a dispute has started.
This checklist covers the clauses worth negotiating before work begins when you outsource software development, especially to an Indian vendor. It is general information, not legal advice, so have your own counsel review the final contract.
Why the contract matters more than the payment
Under Indian copyright law, the author of a work, or the author's employer, is generally the first owner. That means code written by a vendor's team can belong to the vendor unless the contract transfers it to you. Paying the invoice does not, by itself, move ownership.
The fix is simple, but it must be written down before the work starts.
Clause 1: Assignment, not just a licence
Ask for a written assignment of intellectual property to you, effective on payment, covering source code, designs, databases and documentation. A licence to use is much weaker: it can be limited, revoked or made non-transferable.
Duration and territory deserve special care. Under Indian copyright law (Section 19 of the Copyright Act, 1957), if an assignment does not state its duration or territory, defaults can apply that limit it, for example a shorter period and India only.
State clearly that the assignment is perpetual and worldwide. Ask your counsel whether the agreement needs stamping to be properly enforceable.
Clause 2: Pre-existing tools and vendor IP
Vendors often reuse their own frameworks, libraries and internal tools. That is normal, but the contract should say how it is handled:
- The vendor keeps ownership of genuinely pre-existing tools.
- You receive a perpetual, worldwide, royalty-free licence to use those tools inside your product.
- Anything built specifically for you is assigned to you.
Without this, you can end up unable to run or maintain your own product without the vendor's permission.
Clause 3: Third-party and open-source components
- Require a list of third-party and open-source components with their licences.
- Restrict licences that would force you to publish your own code. Some open-source licences carry that obligation.
- Confirm the vendor has the right to supply every component it delivers.
- Ask for an indemnity if a delivered component infringes someone else's rights.
This protects you from discovering a licensing problem during due diligence for a funding round or sale.
Clause 4: Confidentiality
A mutual NDA should be signed before sensitive material is shared. It should name:
- What counts as confidential
- How long the duty lasts
- How data is returned or destroyed at the end
- Whether subcontractors are bound by the same terms
The subcontractor point matters. Confidentiality only protects you if it covers everyone who touches your material.
Clause 5: Acceptance and payment
- Milestones with written acceptance criteria, so everyone knows when something is done
- Payment tied to acceptance, not to elapsed time
- A defined warranty period during which defects are fixed at no charge
- Change requests priced separately and agreed in writing
This clause also decides who carries risk. Vague acceptance criteria shift that risk to you.
Clause 6: Ownership of accounts and environments
Source repositories, hosting, domains, app store accounts and analytics should be registered in your company name from day one. It costs nothing at the start and removes the most common hostage situation in outsourcing.
If the vendor already holds any of these, ask for a written transfer plan before work continues.
Clause 7: Ending the relationship
Write down what happens on termination:
- Delivery of the latest code and documentation
- A handover period with knowledge transfer
- What is owed for work completed
- Return or destruction of your data
A contract that is silent here gives the vendor leverage at exactly the wrong moment.
Clause 8: Governing law and disputes
Name the governing law and the dispute process, including whether arbitration is used and where it sits. India is a party to the New York Convention, which supports the enforcement of foreign arbitral awards between member countries, subject to conditions and notifications. Ask your counsel how that applies to your jurisdiction and your chosen seat of arbitration.
Also consider a liability cap and an IP indemnity, so the risks of a defect or infringement are allocated deliberately and not by accident.
Quick checklist before you sign
| Area | What to confirm |
| IP assignment | Written, effective on payment, perpetual and worldwide |
| Vendor tools | Licence granted for any pre-existing tools in your product |
| Open source | Component list with licences, no forced-publication licences |
| NDA | Mutual, covers duration, return or destruction, subcontractors |
| Payment | Milestones tied to written acceptance criteria |
| Warranty | Defined period, defects fixed at no charge |
| Accounts | Repos, hosting, domains and stores in your name |
| Exit | Code, documentation, handover and payment for completed work |
| Disputes | Governing law, arbitration and seat stated |
How ORVIA handles ownership
At ORVIA, source code, hosting, domain, Google Ads and analytics accounts are registered in your name and handed over on completion. We sign an NDA before you share anything sensitive, and we also sign your own NDA template if you have one. Every project starts with an approved written scope and a fixed price, with change requests priced separately, and payment is typically split across the start, a review milestone and handover. You can read more on our Security & NDA page.
If you are building custom ERP software or a web application, or you are a US business exploring an Indian partner, see our USA market page. Whoever you choose, hold them to the checklist above.
Frequently asked questions
Do I own the software if I pay for it?
Not automatically. Ownership follows the contract, so you need a written assignment of the intellectual property to you.
What is the difference between an assignment and a licence?
An assignment transfers ownership. A licence only gives permission to use, and it can be limited in time, scope or transferability.
Why must the assignment say perpetual and worldwide?
Under Indian copyright law, an assignment that does not state its duration or territory can be limited by default rules, for example a shorter period and India only.
Is an NDA enough to protect my software?
No. An NDA protects confidential information, but it does not transfer ownership of the code. You need both an NDA and an IP assignment.
What should happen to my code if the relationship ends?
The contract should require delivery of the latest code and documentation, a handover period and settlement for completed work.
Which law and courts apply to disputes?
Whatever the contract names. State the governing law and dispute process explicitly, including whether arbitration is used and where it sits.
Final thoughts
Ownership, confidentiality, acceptance, accounts, exit and disputes are not boilerplate. They decide who controls your product when something goes wrong. Negotiate them before work begins, when both sides are still friendly, and have your counsel review the final contract.
Planning an outsourced build and want a straight conversation about scope and ownership? Talk to ORVIA, call +91 91225 05250 or email hello@orviaerp.com.