Most commercial disputes are not caused by bad faith. They are caused by agreements that did not anticipate the problem before it arose — contracts that were vague where they should have been precise, silent where they should have spoken, and overly optimistic where they should have been cautious. The five mistakes set out below account for a disproportionate share of the contract disputes that reach litigation or negotiated settlement.

1. An Undefined or Ambiguous Scope of Work

The scope of work clause is the foundation of every commercial agreement. It defines what is being promised, by whom, and on what terms. When it is vague — when it uses language like "as required," "reasonable efforts," or "industry standard" without further definition — the parties are effectively deferring the agreement to a later date. That deferred agreement rarely arrives amicably.

In service contracts, scope disputes are among the most common grounds for non-payment and termination claims. Scope must be defined in specific, measurable terms, with clear boundaries on what falls inside and outside the engagement. Assumptions must be surfaced and documented.

2. No Liability Cap, or a Cap That Has No Practical Effect

An uncapped liability position is a significant commercial risk that is rarely appreciated at the time of contracting. A service provider who delivers work worth ₹5 lakhs but whose agreement contains no liability cap may find themselves exposed to consequential losses many times that amount if the service fails. Courts in India have shown willingness to award damages well beyond the contract value in appropriate cases.

Liability caps must be carefully calibrated: set at a level that is meaningful, typically linked to fees paid over a defined period, and the carve-outs — for fraud, wilful misconduct, confidentiality breach, and indemnity obligations — must be negotiated deliberately rather than adopted by default.

3. Missing or Unworkable Termination Provisions

Termination clauses are often drafted as an afterthought. The result is agreements where the parties cannot end the relationship without a dispute about whether the conditions for termination have been met. Common failures include: termination for cause provisions that set an impossibly high bar; no termination for convenience right; no clarity on the consequences of termination (obligations that survive, fees payable, return of materials); and no cure period before termination takes effect.

A well-drafted termination clause should address the grounds for termination (cause and convenience separately), the notice period required, the obligations that attach upon and after termination, and what happens to work in progress and advance payments.

4. An Inadequate Dispute Resolution Clause

Most standard agreements contain a dispute resolution clause that says little more than "disputes shall be referred to arbitration" or "the courts of [city] shall have jurisdiction." This is not sufficient. An arbitration clause without specifying the institution, the seat, the number of arbitrators, and the governing procedural rules is an invitation to a preliminary dispute about how the main dispute will be resolved.

Dispute resolution should be designed to match the commercial relationship — the value at stake, the nature of the parties, and the time sensitivity of resolution.

5. Boilerplate Adopted Without Review

The most quietly dangerous section of any commercial agreement is the boilerplate — the standard clauses at the end dealing with governing law, entire agreement, waiver, severability, notices, and amendment. These clauses are routinely copied from previous agreements or downloaded templates without review. They are also the clauses most frequently litigated.

An entire agreement clause that is incorrectly drafted can exclude representations that induced the contract. A waiver clause that is too broadly written can prevent a party from enforcing a breach. Each of these clauses must be read as operative legal text, not as filler.

---

The common thread in each of these mistakes is the same: they arise from treating a contract as a formality rather than a working document. Agreements drafted carefully and specifically — with the particular transaction and parties in mind — rarely generate these disputes.

A founder agreement is typically signed in the early weeks of a company's life — when trust is high, the future is open, and the formalities of legal documentation feel unnecessary. It is often a short, loosely worded document that reflects the enthusiasm of the relationship rather than the legal architecture of the business. It is also, in most cases, the document that will cause the most damage when the relationship fractures.

What a Founder Agreement Actually Needs to Do

The function of a founder agreement is not to express goodwill between co-founders. It is to answer, in advance, the questions that will arise when the goodwill is no longer sufficient: Who owns what percentage, and on what basis? What happens if a founder leaves in the first year? Who has decision-making authority over operational, financial, and strategic matters? What are the restrictions on a departing founder's ability to compete or use company IP? How are disputes between founders resolved without destroying the business?

A document that does not answer these questions is not a founder agreement in any meaningful sense. It is a statement of intention, which has limited legal value.

The Vesting Problem

Equity vesting is the most important mechanism in any founder agreement, and it is also the most frequently omitted or misconfigured. The purpose of vesting is to ensure that equity is earned over time — that a founder who leaves after six months does not walk away with the same ownership stake as one who remains and builds the company for five years.

Standard vesting schedules in early-stage companies typically run over four years with a one-year cliff. However, the schedule alone is not the agreement — the critical provisions surround what triggers accelerated vesting, what constitutes a "good leaver" versus a "bad leaver," and what happens to unvested equity on departure.

In the absence of a vesting schedule, a co-founder who exits on day one retains their full equity position. This is the scenario that makes an otherwise fundable company uninvestable — no institutional investor will commit capital where a departed founder holds a material, unearned stake.

Decision-Making and Deadlock

Where founders hold equal stakes — a 50/50 split between two co-founders is common — the agreement must address deadlock. A company where two equal shareholders cannot agree on a material decision, and where no mechanism exists to resolve the impasse, is a company that cannot function. Courts will not manage the business for the parties. Investors will not provide capital into a deadlocked structure.

Deadlock mechanisms range from the procedural (escalation to independent advisors, cooling-off periods) to the structural (a casting vote for the CEO) to the transactional (buy-sell mechanisms). The appropriate mechanism depends on the nature of the business and the relationship — but some mechanism must exist.

When to Fix a Deficient Agreement

The right time to fix a founder agreement is before it is needed — which means before external investment, before a co-founder departure, and before any significant commercial transaction. In practice, the events that trigger a review are precisely the events that make revision most difficult.

If the existing agreement is silent or inadequate on vesting, decision-making, or exit mechanics, it can in most cases be renegotiated and restated — but this must be done while the relationship remains functional. The moment to act is now, not when the problem has arrived.

Intellectual property is often the most valuable asset a startup possesses — more valuable, in the early stages, than revenue, equipment, or customer relationships. It is also the asset most commonly left unprotected. Founders tend to assume that a confidentiality agreement provides comprehensive protection, or that IP created by employees automatically belongs to the company. Neither assumption is reliable under Indian law without the right contractual architecture in place.

What Contracts Can Protect

Contracts are the primary tool for managing IP that is not registrable, or that has not yet been registered — trade secrets, confidential business information, proprietary processes, source code, client data, and know-how. These forms of IP derive their protection almost entirely from contractual obligation.

Effective contractual IP protection requires, at minimum: a clear definition of what constitutes confidential information; an IP assignment clause in all employment and contractor agreements vesting IP created in the course of work in the company; non-disclosure obligations that survive the termination of the relationship; restricted use provisions; and return and destruction obligations upon termination.

The Employee and Contractor Problem

Under Indian law, the position on employer ownership of employee-created IP is less settled than in some other jurisdictions. While the Copyright Act, 1957 provides that copyright in a work created by an employee in the course of employment belongs to the employer, the position on IP created by independent contractors requires explicit contractual assignment.

A startup that engages freelancers, consultants, or contract developers without a written IP assignment clause may find that the contractor retains ownership of the IP they have created — even if the startup has paid for it in full. Every engagement with an external person who creates anything of value must include an explicit, unambiguous assignment of all IP so created to the company.

What Contracts Cannot Do

Contracts operate between parties — they bind the people who sign them. They do not bind third parties who independently develop or acquire the same IP, and they do not substitute for statutory registration where registration is available and appropriate. A trademark is not protected against third-party infringement by a confidentiality agreement — it is protected by registration under the Trade Marks Act, 1999.

Contracts and statutory registration are complementary, not interchangeable. Contracts protect what registration cannot reach; registration protects against the world. A startup's IP strategy requires both.

Non-Compete and Non-Solicitation Clauses

Restrictive covenants are frequently included in employment agreements, but their enforceability under Indian law is limited. Section 27 of the Indian Contract Act, 1872 renders agreements in restraint of trade void, and Indian courts have historically applied this provision strictly. Non-compete clauses operative during employment are generally enforceable; those operative post-termination are generally not.

Confidentiality obligations, by contrast, are enforceable post-termination and represent the more reliable contractual tool for protecting the business after a departure. IP protection strategy should not rely on non-compete clauses as a primary defensive mechanism.

Litigation is rarely won or lost in the courtroom. The foundation of any commercial dispute — the evidence, the legal basis, the narrative, and the strategic position — is built in the weeks and months before a notice is sent or a plaint is filed. Parties who treat pre-litigation preparation as a formality often find that by the time the dispute becomes formal, their position has been materially weakened by their own conduct.

The Role of Pre-Litigation Assessment

Before any formal legal step is taken, the dispute must be assessed honestly and in detail: the contractual framework governing the dispute and what it actually says; the factual record and what documentation exists to establish it; the legal cause of action; the quantum of loss; the forum with jurisdiction; and the limitation position under the Limitation Act, 1963.

Preserving and Organising the Evidence

The evidentiary record in most commercial disputes is digital — emails, WhatsApp messages, contract documents, invoices, delivery receipts, and meeting notes. This record must be preserved, organised, and reviewed before any formal communication is sent. Sending a legal notice that asserts a factual position that the documentary evidence contradicts is a significant strategic error.

Communications sent after a dispute arises — including internal communications between company personnel — may be discoverable in proceedings. The discipline of factual and documentary assessment must begin before those communications accumulate.

The Legal Notice: Purpose and Drafting

A legal notice under a commercial agreement serves several purposes simultaneously. It communicates the claimant's legal position formally and on the record. It creates a limitation period trigger in some cases. It opens the door to settlement by framing the dispute in legal terms. And it becomes part of the evidentiary record of any proceedings that follow.

A well-drafted notice states the facts clearly and specifically, identifies the legal basis of the claim precisely, sets out the relief sought, provides a defined response period, and reserves all rights without foreclosing future options. A notice that makes claims that cannot be substantiated damages the sending party's credibility and strengthens the recipient's position.

Settlement as Strategy, Not Weakness

The majority of commercial disputes that enter formal proceedings eventually settle — often on terms that could have been achieved before proceedings began, at a fraction of the cost. Pre-litigation negotiation, conducted from a prepared and documented legal position, is not a sign of weakness. It is, in many cases, the commercially rational course.

Without prejudice communications, made before formal proceedings commence, give both parties space to resolve the dispute without those positions being used against them in court. The decision about whether to proceed to formal litigation or pursue settlement is a strategic one best made when the pre-litigation preparation has been done properly.

Indemnity clauses are among the most commercially significant provisions in any commercial agreement, and among the least understood. They are routinely included in contracts as standard text, negotiated on instinct rather than analysis, and then — when a claim arises — subjected to a level of scrutiny that reveals how imprecisely they were drafted. The result is disputes about the very mechanism that was intended to resolve disputes.

What an Indemnity Clause Does

An indemnity clause obligates one party (the indemnifier) to compensate the other party (the indemnified) for specified losses — losses that may arise from the indemnifier's own acts or omissions, from third-party claims, or from other specified events. Unlike a damages claim for breach of contract, an indemnity operates as a primary obligation: the indemnified party does not need to prove a breach of contract, only that the triggering event has occurred and the loss has been suffered.

This distinction matters significantly. A breach of contract claim requires proof of breach, causation, and quantum — all of which may be contested. An indemnity claim, where the trigger is clearly established and the loss is documented, can be considerably simpler to establish.

Scope: What is Covered and What is Not

The scope of an indemnity is defined by the trigger event and the categories of loss covered. Common triggers include: third-party claims arising from a party's breach; infringement of third-party intellectual property rights; a party's breach of applicable law; specific identified risks such as product liability; and tax liabilities arising from the transaction.

The categories of loss covered — whether limited to direct losses, or extending to consequential, indirect, and third-party losses — must be expressly stated. An indemnity that does not specify the categories of loss covered will be interpreted according to the principles of contractual construction, which may not align with what either party intended.

The Mutual vs. Unilateral Question

Many commercial agreements contain mutual indemnities — each party agrees to indemnify the other. Mutual indemnities appear balanced on their face but are often asymmetric in practice: if one party bears significantly more operational risk than the other, the indemnities will not be equivalent in commercial effect even if they are symmetric in language.

Whether an indemnity should be mutual or unilateral is a negotiating and risk-allocation question that should be answered by reference to the specific transaction, not by convention.

Procedural Obligations: Notice and Control

Most well-drafted indemnity clauses include procedural obligations: an obligation to notify the indemnifier promptly upon becoming aware of a claim; an obligation to allow the indemnifier to assume control of the defence; and an obligation not to make admissions or settle the third-party claim without the indemnifier's consent.

Failure to give timely notice may reduce or extinguish the indemnity claim, particularly where the indemnifier can show that earlier notice would have allowed them to mitigate the loss. A party that settles a third-party claim without involving the indemnifier may find the indemnity unavailable for precisely that settlement amount.

Enforceability Under Indian Law

Indemnity agreements are governed by Sections 124 to 147 of the Indian Contract Act, 1872. Courts in India have generally given effect to indemnity clauses where they are clearly drafted and the trigger event is established. However, indemnity clauses that seek to indemnify a party against the consequences of its own fraud or wilful misconduct have been read narrowly, and clauses contrary to public policy may not be enforced as written. Precision in drafting is the most effective protection against these outcomes.

The Digital Personal Data Protection Act, 2023 (DPDP Act) represents the most significant development in Indian data protection law since the Information Technology Act, 2000. Its passage into law marks the end of the informal data governance practices that characterised Indian digital businesses for the previous two decades. Compliance is not optional, and the obligations it imposes have direct implications for how businesses draft their contracts, manage their vendor relationships, and communicate with their users.

The Core Framework

The DPDP Act applies to the processing of digital personal data within India, and to the processing of personal data of individuals in India by entities located outside India where such processing is in connection with offering goods or services in India. Its reach is therefore broad, covering most consumer-facing digital businesses and a significant proportion of B2B platforms.

The Act creates two primary categories of obligation-bearer: the Data Fiduciary (the entity that determines the purpose and means of processing personal data) and the Data Processor (the entity that processes data on behalf of the fiduciary). The obligations of each differ, and the contractual relationship between them must reflect those differences.

Consent as the Legal Basis

The DPDP Act makes consent the primary lawful basis for processing personal data. Consent must be free, specific, informed, unconditional, and unambiguous — a clear affirmative act. It must be sought separately for each purpose, and withdrawal of consent must be as easy as giving it.

A single, catch-all consent obtained at registration — covering all current and future uses of personal data — does not satisfy the Act's requirements. Consent must be granular and purpose-specific. Bundling consent for data processing with consent to terms of service is problematic under the Act's framework.

Rights of the Data Principal

The Act confers on Data Principals the right to access information about the personal data being processed; the right to correction and erasure; the right to grievance redressal; and the right to nominate another person to exercise rights in the event of the principal's death or incapacity.

Data Fiduciaries must establish accessible, functional mechanisms for Data Principals to exercise these rights. A privacy policy that lists these rights without providing a means of exercising them does not satisfy the Act's obligations.

Obligations on Data Fiduciaries

Beyond consent management and Data Principal rights, Data Fiduciaries must: process personal data only for the purpose for which consent was obtained; implement appropriate technical and organisational security measures; notify the Data Protection Board of India in the event of a personal data breach; erase personal data when the purpose for which it was collected has been fulfilled or on withdrawal of consent; and not transfer personal data to countries not notified as permissible by the Central Government.

Contract Implications: Vendors and Data Processors

Where a Data Fiduciary engages a third party to process personal data on its behalf — a cloud service provider, a marketing analytics platform, a payment gateway — the relationship must be governed by a written contract that contains specific obligations on the Data Processor. The Data Fiduciary remains responsible for the processing carried out by its processors; a contract that does not impose appropriate obligations on the processor does not shift that responsibility.

Standard vendor agreements must be reviewed for DPDP Act compliance. In many cases, they will need to be supplemented or replaced. A data breach caused by a processor's failure can expose the fiduciary to significant regulatory liability, and the contractual framework is the primary tool for managing that exposure.

Significant Data Fiduciaries

The Act creates an additional category — Significant Data Fiduciaries — for entities that handle large volumes of personal data. These entities are subject to enhanced obligations, including the appointment of a Data Protection Officer, an independent data auditor, and the conduct of periodic Data Protection Impact Assessments.

The DPDP Act is operationalised through rules that continue to be developed. The framework is live and the obligations are current. The appropriate time to begin compliance work is now — when the choices about how to structure data practices, draft user-facing documents, and govern vendor relationships can be made deliberately rather than reactively.