Last updated: 12 October 2026 · 14 min read
Every business runs on promises. A customer promises to pay, a supplier promises to deliver, a co-founder promises to build, an employee promises to keep your plans confidential. In the early days, most of these promises are made informally: over a call, in a chat message, or with a handshake after a good meeting. That works perfectly well while everyone remembers the same thing and wants the same outcome.
The difficulty is that businesses change. People leave, plans shift, money gets tight, and memories of "what we agreed" quietly drift apart. A contract is how you fix those promises in place before that happens. This guide is a plain-language overview of business contracts for founders and small business owners in India: why written agreements matter, what the law generally requires for a contract to be enforceable, the agreements most growing businesses encounter, a closer look at non-disclosure agreements (NDAs), and the mistakes that cause the most trouble later.
A common belief among first-time founders is that contracts are for big companies, or for relationships where trust is low. In practice, the opposite is often true. Contracts matter most in exactly the relationships founders care about: with co-founders, early employees, key suppliers and first customers. These are the relationships where a misunderstanding causes the most damage.
Many verbal agreements can be legally valid in India; a contract does not always have to be written down to exist. The real problem is evidence. If a dispute arises, each side will remember the conversation differently, and it can be very difficult to establish what was actually agreed, when, and on what terms. Messages and emails help, but scattered informal messages rarely cover everything that matters, such as what happens if a deliverable is late or who owns the work produced. Some kinds of agreements also carry their own formality requirements, which an informal arrangement may not meet.
One of the most underrated benefits of a written contract is the process of preparing it. Putting an agreement on paper forces both sides to answer questions they might otherwise avoid: What exactly is being delivered? What if payment is late? Who owns the result? How can either side walk away? Having those conversations at the start, while relations are good, is far easier than having them in the middle of a disagreement.
Well-organised agreements also make a business more credible and more valuable. When investors, lenders or acquirers look at a company, they typically review its key contracts as part of due diligence: founder arrangements, employment and consultancy terms, customer agreements and any licences. Clear, signed agreements make that process smoother. Missing or ambiguous ones can slow a deal down or raise questions about whether the business really owns what it says it owns. Our Business Compliance Guide explains why organised records matter more broadly.
In India, contracts are governed by the Indian Contract Act, 1872. You do not need to know the Act in detail to run a business, but it helps to understand the basic building blocks the law generally looks for when deciding whether an agreement is a binding contract. In broad terms, a valid contract requires:
| Element | What it means in plain language |
|---|---|
| Offer | One party proposes clear terms on which it is willing to be bound, for example "we will design your website for this fee." |
| Acceptance | The other party agrees to those terms. If it agrees only with changes, that is generally treated as a new proposal rather than acceptance. |
| Lawful consideration | Each side gives or promises something of value in return, such as money, services, goods or a promise to do or not do something, and that exchange must be lawful. |
| Intention to create legal relations | The parties intend the agreement to have legal consequences. In business dealings this is usually presumed, whereas casual social arrangements generally are not intended to be legally binding. |
Beyond these core elements, the law generally also expects the parties to be competent to contract, to have given their free consent (not obtained through pressure, misrepresentation or similar unfair means), and the purpose of the agreement to be lawful. An agreement that falls short on any of these can be unenforceable, or can be set aside by one of the parties.
Two practical points follow for founders. First, the law cares about substance, not just paperwork: a beautifully formatted document can still have problems if, for example, the terms are too vague to show what was actually agreed. Second, being "legally binding" is only the starting point. A contract can be perfectly valid and still be a bad deal for you, because it is silent on the issues that later turn out to matter. Enforceability is the floor, not the goal.
Business agreements vary widely, but most share a common set of building blocks. Knowing them makes any draft easier to read and helps you notice when something important is missing.
Not every agreement needs every element in the same depth, but if a draft is silent on one of these, it is worth asking whether that silence is deliberate.
The exact set of agreements a business needs depends on its industry, structure and stage. That said, some come up again and again for Indian startups and small businesses.
Used when you need to share sensitive information, such as product plans, source code, pricing or client lists, with someone outside the business. Because NDAs are usually the first agreement a founder encounters, they get their own section below.
When two or more people start a business together, they should agree in writing on ownership percentages, roles and responsibilities, how decisions are made, how equity vests over time, and what happens if a founder leaves, stops contributing or wants to sell. Once outside investors come in, a shareholders' agreement typically sets out the rights of each class of shareholder. These are among the most important documents a company has, and the hardest to negotiate after a relationship has soured.
Whether you are buying services or selling them, these agreements set out the scope of work, deliverables, quality standards, the timelines the parties agree on, payment terms, liability and termination rights. For a services business, a well-structured master agreement with a separate statement of work for each project can save renegotiating the basics every time.
Employment terms cover compensation, duties, notice periods, confidentiality and, importantly, ownership of work created during employment. Consultants and freelancers need the same clarity, and arguably more, because the assumption that "we paid for it, so we own it" does not always hold for work created by people who are not employees. Our Copyright Registration Guide explains why ownership of commissioned work deserves careful attention.
Any business with a website or app interacts with users under some set of rules. Terms of use explain how the platform may be used, set out what you are and are not responsible for, and describe how disputes will be handled. A privacy policy explains what personal data you collect, why, and how it is handled. Both should describe how your platform actually works. A privacy policy copied from another business may make promises about data handling that your business does not keep, which is a problem in itself.
A licence lets someone use intellectual property without owning it: for example, allowing a partner to use your brand, licensing software, or using someone else's photographs or content. Licences should be clear about what exactly is licensed, for what purpose, in which territory, for how long, whether the licence is exclusive, and what payments apply. If you license out your brand or technology, it helps to have the underlying rights properly protected first; see our Trademark Registration Guide and Patent Registration Guide.
Depending on the business, other common documents include office or shop leases, distribution and reseller agreements, partnership deeds, loan and investment documents, and customer contracts or standard terms of sale. The Startup Legal Checklist shows where these typically fit into a founder's first year.
A non-disclosure agreement, also called a confidentiality agreement, is a contract in which one or both parties agree to keep certain information confidential and to use it only for an agreed purpose. NDAs are usually the first legal document a founder signs or asks someone else to sign, which makes them worth understanding properly.
An NDA protects information that is genuinely confidential and that you are sharing for a specific purpose. Typical examples include:
A one-way (unilateral) NDA protects information flowing in one direction, for example when you share your product plans with a development agency. A mutual NDA protects information flowing both ways, which is common when two businesses are exploring a partnership and each will reveal something sensitive. Choosing the right form matters: a mutual NDA used where only one side really discloses anything can place obligations on you that you did not need to accept.
An NDA is a promise, not a property right. It does not give you ownership of an idea, it does not bind anyone who has not signed it, and if someone breaches it, enforcing it can be slow and costly. Proving that a specific piece of information was misused can also be difficult. For that reason, NDAs work best as one layer of protection among several. Inventions may need a patent application before they are disclosed widely; our Patent Registration Guide explains why timing of disclosure matters. Brands are protected through trademarks, product appearance through design registration, and creative work through copyright.
An NDA makes sense when you are about to share information that is both genuinely confidential and genuinely valuable, with someone who is not yet bound by any other agreement. Common situations include:
There are also situations where an NDA adds little. Information that is already public cannot meaningfully be protected. A general pitch that reveals no sensitive detail may not need one. And in some settings, such as early conversations with many investors, insisting on an NDA before a first meeting can be unusual and may create friction; the better approach is often to decide carefully what you share at each stage.
Imagine a hypothetical freelance designer who signs an NDA before seeing a startup's product roadmap. The NDA defines the roadmap as confidential, limits its use to preparing a design proposal, and requires the material to be deleted if the engagement does not go ahead. If the engagement proceeds, the main service agreement then takes over, with its own confidentiality and intellectual property terms. Used this way, the NDA does a narrow job well: it covers the gap between "let's talk" and "let's sign."
Most contract problems in small businesses do not come from exotic legal issues. They come from a handful of everyday mistakes that are easy to avoid once you know to look for them.
Imagine a hypothetical two-founder software startup. One founder writes most of the early code before the company is incorporated; a freelancer builds the mobile app; a friend designs the logo as a favour. Nobody signs anything, because everyone is on the same team. A year later, the company is preparing for its first investment, and the investor's lawyers ask a simple question: does the company actually own its code, app and logo? Each answer now depends on goodwill and memory. Fixing it at this stage is possible, but it requires tracking everyone down, negotiating assignments under deadline pressure, and hoping no relationship has soured in the meantime. A few short, well-drafted agreements at the start would have answered the question in advance.
Free contract templates are easy to find online, and they can be a reasonable way to understand what a type of agreement usually contains. The problems arise when a template is signed as-is:
A professionally drafted or reviewed contract starts from your facts. It asks the questions a template never will: What exactly are you delivering? What happens if the other party pays late? Who owns what is created? How will disputes be resolved? The answers shape clauses that fit the deal, rather than generic language that may or may not apply.
Professional help does not always mean starting from a blank page. Often the most efficient approach is to have a suitable template customised to your situation, or to have a draft you received from the other side reviewed before you sign. What matters is that someone has read the document with your interests and your facts in mind.
Whether you drafted the agreement or the other side did, it is worth pausing on these questions before you sign:
If you cannot answer one of these confidently, that is usually the clause to ask about.
Many verbal agreements can be legally valid in India, because a contract does not always need to be in writing. The practical problem is proof. If a dispute arises, it can be very difficult to show exactly what was agreed. Some kinds of agreements also have specific formality requirements. A written, signed contract is almost always the safer choice for any business relationship that matters.
Contracts in India are governed by the Indian Contract Act, 1872. In general terms, a valid contract requires an offer, an acceptance of that offer, lawful consideration, and an intention to create legal relations, between parties who are competent to contract and who give their free consent, for a lawful purpose. Whether a particular agreement meets these requirements depends on its facts, so get advice on any agreement that matters to your business.
An NDA is useful whenever you need to share genuinely confidential information, such as source code, product plans, unreleased designs, client lists or pricing, with someone outside the business before a formal relationship is in place. Common examples include potential vendors, development agencies, freelancers, manufacturing partners and prospective business partners. It is less useful for information that is already public or for a general pitch that reveals nothing sensitive.
No. An NDA is a contractual promise not to use or disclose information in certain ways. It does not give you ownership of an idea, it does not bind anyone who has not signed it, and enforcing it after a breach can be slow and difficult. NDAs work best alongside other protections, such as sharing only what is necessary and, where relevant, protecting inventions, brands and creative work through patents, trademarks, copyright or design registration.
A template can help you understand what a type of agreement usually contains, but it is written for nobody in particular. It may not reflect your deal, your risks or Indian law, and templates combined from several sources often contain inconsistent definitions or contradictory clauses. For any agreement that matters to your business, having a template customised or reviewed by a professional is a sensible step.
Not without reading it carefully, and ideally having it reviewed. A contract prepared by the other side is naturally written to protect their interests. Many terms are negotiable, especially around scope, payment, liability, intellectual property ownership and termination. Understanding what you are agreeing to before you sign is far easier than trying to change it afterwards.
