Software Development Contracts in India: Founder's Guide

A software development contract in India needs eight things to protect a founder: a precise scope with a change-control process, a milestone-based payment schedule, an explicit assignment of intellectual property, confidentiality terms, a warranty and support clause, exit and handover provisions, liability caps, and a stated governing law and dispute mechanism. Get those eight right and most vendor disputes never happen; get them wrong and you are negotiating from weakness after the money has moved.

This guide is written for non-lawyers — founders and SMB owners signing their first serious development agreement. It reflects how contracts actually play out in the Indian market, drawn from both sides of the table: NexaEx signs these agreements with clients every month, and we have inherited enough broken projects to know exactly which missing clauses cause the damage.

Why a purchase order is not enough

Plenty of Indian SMB software deals run on a quotation, a purchase order, and trust. That works until it doesn't. The three failure modes we see repeatedly:

• Scope drift with no referee. The client assumes revisions are free; the vendor bills every conversation. Nothing in writing says who is right.
• IP limbo. The client has paid ₹10 lakh and discovers the copyright in the code legally sits with the vendor (more on this below — it surprises everyone).
• Hostage handover. The engagement sours, and the vendor controls the servers, the domain, and the repository, with no contractual duty to hand anything over.

A contract does not prevent disagreement; it decides disagreements in advance, while everyone is still friendly. Under the Indian Contract Act, 1872, even an email chain can form a binding contract — so the question is not whether you have one, but whether the one you have says what you need.

The eight clauses that actually matter

Let's take the ones founders most often get wrong.

Scope: fixed price, time-and-materials, or milestones?

There are three commercial models, and choosing the wrong one causes more pain than any legal clause:

• Fixed price works when the spec is genuinely frozen — a defined billing system, a marketing site, a well-specified MVP. Typical range for an SMB web platform: ₹4,00,000–₹15,00,000. The risk: every change becomes a negotiation.
• Time and materials (T&M) bills monthly for effort — ₹80,000–₹2,00,000 per developer-month at Indian agency rates in 2026, depending on seniority and stack. Flexible, but you carry the estimation risk.
• Milestone-based hybrid — fixed price per milestone, re-scoped between milestones — is what we recommend for most SMB projects and use ourselves. You get price certainty in the near term and flexibility across the project.

Whatever the model, the contract needs a change-control clause: changes are requested in writing, priced before work starts, and signed off. This single clause eliminates the majority of vendor-client conflict. If you are trying to budget before you negotiate, our project cost calculator gives realistic 2026 ranges by project type.

Who owns the code you paid for?

Here is the part that surprises almost every founder. Under Section 17 of the Copyright Act, 1957, the author of a work is its first owner. The "work for hire" default that Americans assume applies to employees in India — not to independent contractors or agencies. If your contract does not contain an express assignment of copyright, the agency owns the code and you hold, at best, an implied licence to use it.

So the contract must say, in substance: all intellectual property in the deliverables is assigned to the client upon payment of the corresponding fees. Three refinements worth having:

1. Carve out pre-existing IP. Agencies reuse internal libraries and boilerplate. Fair — but the contract should grant you a perpetual, irrevocable, royalty-free licence to that pre-existing IP as embedded in your deliverables.
2. Open-source disclosure. Require a list of open-source components and their licences. A copyleft licence (GPL) in a product you plan to sell is a due-diligence landmine at fundraising time.
3. Assignment on payment, not on completion. If the project terminates at milestone 3 of 6, you should own milestones 1–3 outright.

Any investor's lawyer will check this before a funding round. Fixing it retroactively means chasing a vendor for signatures years later — sometimes with a cheque attached.

Payment schedules that keep both sides honest

The advance exists because vendors get burned too; the holdback exists because clients do. A balanced schedule for a ₹10,00,000 milestone project looks like: 25% advance (₹2,50,000), 20% per milestone × 3 against demonstrated, accepted deliverables (₹6,00,000), and 15% (₹1,50,000) released on completed handover.

Two details make this work:

• Acceptance criteria in writing per milestone. "Client satisfaction" is not a criterion; "the flows in Annexure B pass on staging" is. Add a deemed-acceptance clause (e.g., accepted if no written defects within 10 business days) so the vendor is not held hostage either — you want a contract a good vendor will happily sign.
• GST clarity. Software development services attract 18% GST. State whether quoted figures are inclusive or exclusive, and put both parties' GSTINs on the contract so input tax credit flows cleanly.

The handover holdback is the enforcement mechanism for everything in our software handover checklist — read that piece before you sign, because the handover clause should reference a concrete checklist, not a vague promise of "necessary materials".

What should the exit clause say?

The exit clause is the one you negotiate hoping never to use, and it is the most important clause in the document. Minimum contents:

• Termination for convenience with 30 days' notice, paying for work done to date — so a stalled project can end cleanly instead of festering.
• Handover on any exit: repository with history, credentials, documentation, and data export delivered within a fixed window (7–14 days), with this duty expressly surviving termination.
• No lien on your data. In a fee dispute, the vendor argues about money in arbitration — they do not hold your production database hostage. Ban it in writing.
• Transition assistance at agreed T&M rates for 30–60 days, so a successor team can take over.

On disputes: for SMB-sized contracts, name Indian law and the courts of your city, or arbitration under the Arbitration and Conciliation Act, 1996 with a sole arbitrator. Arbitration is faster than civil court but not cheap — realistic cost ₹1,50,000+ even for a simple matter — which is precisely why well-drafted milestones and acceptance criteria, which prevent disputes, are worth more than a fierce disputes clause.

Data protection: the clause 2026 contracts cannot skip

If your software touches personal data of Indian users — customers, patients, students, borrowers — the Digital Personal Data Protection Act, 2023 makes you the data fiduciary and your development vendor a data processor. Your contract needs a data-processing clause: the vendor processes personal data only on your instructions, applies reasonable security safeguards, reports breaches to you without delay, and deletes personal data on exit. Regulated industries stack further requirements on top — RBI outsourcing norms for NBFC lending platforms (relevant to products like LoanKard), and health-data sensitivity for clinic systems. Our DPDP-ready security checklist turns these obligations into concrete technical controls you can paste into Annexure form.

Negotiating without poisoning the relationship

A contract negotiation is also a vendor test. A professional agency has seen every clause above and will negotiate specifics, not principles. Treat these responses as signal:

• Refuses IP assignment outright → walk away.
• Resists any handover obligation → they are planning to lock you in.
• Pushes for 50%+ advance with no milestone acceptance → cash-flow trouble or worse.
• Offers you their standard contract → fine as a starting point; read it against this guide.

And keep perspective from the other side of the table: clauses that protect the vendor — deemed acceptance, late-payment interest, a liability cap — make it safer for good vendors to work with you, which gets you better vendors. A contract only one side can live with selects for counterparties who do not read contracts. For how the work itself should run once the ink is dry, see Agile explained for non-technical founders.

Talk to us

We are happy to share the contract and handover framework we use with our own clients — it implements everything in this guide. Contact us or WhatsApp +91 97912 97741 (we reply within 24 hours) to discuss your project and see how a well-structured engagement runs. This article is practical guidance, not legal advice; have a lawyer review your final agreement.