Software Development Contract Checklist India (14 Points)

A software development contract in India should cover 14 things in writing: scope, fixed price, payment milestones, delivery dates, code ownership, accounts in your name, data, confidentiality, testing, support, exit terms and dispute handling. If your contract is a one- page quote or a WhatsApp message, at least half of these are missing. This software development contract checklist for India shows what to ask for and which wording should worry you.

Written by the Ureka Technologies team [CONFIRM: founder name for byline]. This is a checklist from our side of the table, not legal advice. Have a lawyer read the final contract.

Key takeaways

• Ownership of the code must be assigned to you in writing. Paying for the work does not transfer it automatically.

• Domain, hosting, Play Store and App Store accounts should be registered in your name from day one.

• Tie payments to working builds you can open, not to calendar dates.

• Ask what happens if the developer disappears. The answer should be a handover clause, not "that won't happen".

Why does a software development contract matter for a small business?

A contract matters because software projects fail on misunderstandings, not on code. Most disputes we hear about come from five places: the price grew, the developer vanished, the owner cannot access their own code, the app broke after launch, or nobody agreed what "finished" meant.

A written contract does not stop these. It gives you a document to point at when they happen. It also forces both sides to talk about the awkward parts before any money moves.

You do not need 40 pages. A good project contract for an Indian SMB is usually 3 to 6 pages, plus a scope sheet listing screens and features.

What should a software development contract checklist in India include?

Here are the 14 points, with what to write and what should make you stop. Read the table first, then the notes below it.

How do you make scope and price clear?

Scope is the list of what will be built. Write it as screens and actions, such as "customer uploads a document, admin approves it, customer gets a WhatsApp message" . A sentence like that can be tested."User-friendly dashboard" cannot.

For price, ask for a fixed figure and a change process. Changes are fine, because every project changes. The contract should say that a change is quoted in writing before work starts, and that the original price stands for the original scope. Our own cost guides explain what moves a price: see the app development cost guide for India and the website development cost guide.

Who owns the code when you hire a developer in India?

By default, the developer may own it, not you. Indian copyright law generally treats the person who creates a work as its first owner, with exceptions for employees. A transfer to you must be in writing.

So the contract should say, in plain words, that the code, designs and any trained models are assigned to you once payment is made. It should name the term and the territory (for example, perpetual and worldwide), so no gap is left to be filled by default rules.

Also ask about open-source parts and paid libraries. Open-source software comes with its own licence, and a few licences place conditions on how you can distribute your app. A short list of what is used is enough.

Which accounts should be in your name?

Five accounts decide whether you can walk away from a developer: your domain, your hosting or cloud account, your Google Play Console, your Apple Developer account, and your payment gateway (Razorpay or similar).

Google Play charges US$25 once and Apple charges US$99 per year. These are small amounts. Paying them yourself and adding the developer as a team member costs you almost nothing and removes the biggest lock-in risk. If a developer insists on publishing under their own store account, treat that as a warning.

How should payments be structured?

Link each payment to something you can open and test. A common pattern is a small advance, then payments at working builds, then a final payment on handover. Ask for a GST invoice for each payment, so your accounts stay clean.

Avoid paying the full amount before you see anything. Equally, a developer who asks for nothing upfront and sends no builds is not a good sign either. Regular builds protect both sides.

What happens to your data and users data?

You, as the business, own your customers' data. The contract should say where it is stored, who can access it, how backups work, and that you get a full export on request.

If your app collects personal data from Indian users, the Digital Personal Data Protection (DPDP) Act applies to you as the business, even if the developer built the system. Our note on DPDP compliance for website owners explains what to check. Ask the developer to confirm in writing how they handle personal data during the build and who can see it.

What if the developer disappears halfway?

A good contract answers this before it happens. The two things that matter are access and handover. If your accounts are in your name and the code is in a repository you can log into, a disappearing developer is an inconvenience. If not, it can mean starting again.

Ask for a clause that gives you the current code and documents on request at any point, and a short notice period (say 15 to 30 days) for either side to end the contract.

How do you define "finished" and what about support?

Finished means the acceptance criteria are met. Write down 5 to 10 checks, such as "payment works on UPI and cards" , "admin can export a report", "app opens on an Android phone with 3 GB RAM" . Add a bug-fix period after launch, commonly 30 to 90 days.

After that, support is a separate matter. Software needs updates when phones, browsers and store rules change. Ask what ongoing support costs before signing, not after launch.

Which contract mistakes cost Indian small businesses the most?

The costliest mistakes are the ones that cannot be fixed later. These are the ones we see most when a business comes to us after a bad first experience.

1. Paying in full before any build was shown.

2. Letting the developer register the domain and store accounts.

3. Having no written assignment of the code.

4. Agreeing scope on a call and never writing it down.

5. Not asking who pays for third-party services after launch.

Our comparison of freelancer vs agency vs in-house developers in India shows how these risks differ by hiring model. If you are still choosing a vendor, the 12 questions to ask an app development company in Delhi pair well with this checklist.

How do we handle this at Ureka?

When we start a project, we hold one call and then send a fixed written quote. The client owns the code, domain, store accounts and data from day one, and a working build or link arrives every two weeks. We mention this only so you can compare it with what any vendor offers you. Use the checklist above on us too.

FAQ

Do I need a lawyer to review a software development contract?

For a small project, a lawyer's review of the final draft is worth the cost. You can use this checklist to prepare, so the lawyer spends time on wording and not on discovering what is missing.

Is a quotation or WhatsApp message a valid contract in India?

Written messages can show an agreement, but they rarely cover ownership, exit or support. Treat them as a record of the deal, and still sign a proper agreement.

Does the developer own the code I paid for?

Not automatically. Unless the contract assigns the code to you in writing, the developer may keep ownership. Ask for an assignment clause that applies after payment and states the term and territory.

What should a fixed price software quote include?

It should list scope, price in ₹ with GST, payment milestones, delivery checkpoints, change process, and what is excluded, such as store fees or third-party subscriptions.

Should the contract be on stamp paper?

Stamp duty rules for agreements differ by state. Ask your lawyer which value applies in your state before signing.