One Contract Does Not Fit All — What Changes When You Draft by Industry

The One-Size-Fits-All Trap

Ask most small and mid-sized businesses in India how their commercial contracts are drafted, and the answer is usually some version of the same story: a template was downloaded, adapted from a contract used with a different counterparty, or inherited from a lawyer who drafted one master agreement years ago and has been reusing it — with minor edits — ever since. The logo changes. The parties change. The core structure almost never does.

This works, right up until it does not. A commercial contract is not a formality to satisfy before business begins — it is the document that determines who bears the cost when a delivery is late, who owns the intellectual property created during an engagement, what happens when a regulator intervenes mid-contract, and how much one party can be made to pay the other when something goes wrong. Every one of those questions is answered differently depending on what kind of business is signing the contract.

A software company licensing a SaaS product faces an entirely different risk profile from a manufacturer supplying components on a purchase order, which is different again from a real estate developer collecting instalments from homebuyers, a hospital engaging a diagnostic vendor, or an NBFC outsourcing its collections function. Yet all five are routinely handed the same generic "service agreement" or "vendor contract" template — often the same one, recycled from a completely unrelated deal — with only the names changed.

This problem is especially acute for foreign companies establishing an Indian subsidiary or entering into their first India-based commercial relationships. It is natural to reach for a group contract template that has worked in the parent company's home jurisdiction — the United States, the United Kingdom, Singapore — and adapt it for Indian use with light local review. But the sector-specific risk allocation embedded in that template was built for a different legal system, a different regulatory framework, and often a different commercial norm around liability and indemnity altogether. A US-style unlimited indemnity clause, or a UK-style liquidated damages formula, does not automatically translate into an Indian contract without careful recalibration against both Indian contract law and the specific sector the Indian entity operates in.

The Five Drafting Variables That Change by Sector

Before looking at individual industries, it helps to understand what actually moves when a contract is calibrated for a sector. In our drafting practice, five variables account for almost all of the meaningful difference between a generic agreement and one built for a specific industry. Understanding these variables is more useful than memorising sector-specific clause libraries, because new business models — a manufacturing company adding a subscription-based maintenance service, a healthcare provider launching a consumer app — routinely straddle more than one sector, and the same five questions still apply.

1. Risk Allocation & Liability Caps

How much can one party be made to pay the other if things go wrong, and for what kind of loss? A liability cap that makes sense for a small consulting engagement can be catastrophically inadequate for a SaaS platform processing financial data, and unnecessarily punitive for a low-margin manufacturing supply contract. The right cap — and the right carve-outs from it, such as for data breaches, IP infringement, or gross negligence — depends entirely on what could realistically go wrong in that sector.

2. Intellectual Property Ownership & Licensing

Who owns what is created during the engagement, and under what licence does each party use it afterward? This question looks entirely different for a software development agreement (source code, derivative works, pre-existing IP), a media and content deal (copyright, moral rights, distribution rights), and a manufacturing contract (product designs, tooling, process know-how).

3. Regulatory Riders & Statutory Overlays

Many sectors in India operate under a regulator that imposes its own contractual requirements — irrespective of what the parties would otherwise agree. RBI's outsourcing directions for banks and NBFCs, RERA's requirements for real estate agreements, CDSCO and drug-licensing conditions for pharma supply, and the DPDP Act's obligations for any contract involving personal data are not optional additions — they are mandatory riders that a sector-blind contract will simply omit.

4. Performance, Delivery & Acceptance Standards

What does "delivered" or "completed" actually mean? For a manufacturer, it may mean passing a quality inspection against agreed specifications. For a SaaS provider, it may mean uptime measured against a service level agreement. For a construction contractor, it may mean achieving a certified stage of completion. A contract that uses vague, one-size-fits-all acceptance language leaves both parties guessing — and disputing — at the exact moment certainty matters most.

5. Termination & Exit Mechanics

How a contract ends, and what happens immediately afterward, varies enormously by sector. A SaaS contract needs data retrieval and deletion terms. A manufacturing supply contract needs provisions for work-in-progress and tooling. A real estate contract needs refund and possession mechanics tied to RERA timelines. A staffing or outsourcing contract needs transition and handover obligations. Generic "either party may terminate on 30 days' notice" language ignores all of this.

Industry by Industry — What to Build In

The following is not an exhaustive list, but it covers the sectors where LexWin most frequently sees businesses relying on contracts that were never built for their actual risk profile.

These nine sectors are not an arbitrary selection. They represent the largest share of LexWin's commercial contract engagements, and — not coincidentally — the sectors where we most often find an existing contract that was drafted for a different purpose entirely and simply relabelled. A services agreement built for a marketing consultancy, handed to a SaaS company; a generic vendor contract, handed to an NBFC bound by RBI's outsourcing framework; a builder-buyer agreement drafted before a project's RERA registration was finalised, never updated to match it. Each of these is a live example we have encountered, not a hypothetical.

What unites them is not the industry itself but the pattern: the contract reads as complete, uses confident legal language, and would pass a casual read-through — yet it is missing the one provision that determines the outcome of the dispute, audit, or regulatory inspection that eventually tests it.

A Closer Look — The Highest-Stakes Sectors

A few sectors carry disproportionate contractual risk because the gap between a generic clause and a sector-calibrated one is especially wide. These deserve closer attention.

IT, Software & SaaS

The single most consequential clause in a SaaS or software services contract is the liability cap — and it is also the clause most commonly copied verbatim from an unrelated template. A cap set at "the fees paid in the preceding 12 months" may sound protective, but if the same contract is silent on carve-outs for data breach, confidentiality breach, and IP infringement, the customer may find that a catastrophic data exposure is capped at a trivial subscription fee — while the vendor discovers, too late, that a court reads the cap as inapplicable to statutory data protection liability altogether. Data processing terms — required in substance if not always in explicit statutory form under the DPDP Act — must specify purpose limitation, sub-processor consent, breach notification timelines, and data return or deletion on termination.

Manufacturing & Industrial Supply

Manufacturing contracts live or die on specification precision and inspection rights. A purchase order that references "as per sample" or "as per specifications" without incorporating a detailed, version-controlled specification document invites dispute the moment a batch is rejected. Force majeure clauses drafted for a services business — built around vague "acts of God" language — routinely fail to address the risks that actually disrupt manufacturing supply chains: raw material shortages, port congestion, or supplier-tier failures. Ownership of tooling, dies, and any IP embedded in a custom design also needs explicit allocation; without it, both parties may reasonably believe they own the same asset.

Real Estate & Construction

Every real estate contract involving a registered project must be built around RERA — not as an afterthought, but as the frame within which payment schedules, possession dates, and disclosures are drafted. A builder-buyer agreement that specifies possession dates inconsistent with the RERA-registered timeline, or payment milestones untethered to actual construction stage, creates an immediate compliance gap and a strong ground for buyer disputes. Defect liability periods, carpet area guarantees, and title and encumbrance warranties are not optional additions — they are the clauses most frequently tested when a project is delayed or a dispute reaches RERA or the courts.

Healthcare & Pharmaceuticals

Contracts in this sector must operate on two tracks simultaneously — commercial terms and regulatory compliance. A supply agreement for pharmaceutical products that does not reference drug-licensing conditions, batch traceability, and recall procedures leaves both manufacturer and distributor exposed the moment a quality issue surfaces. Where patient data is involved — diagnostics, hospital IT vendors, telemedicine platforms — the DPDP Act's treatment of health information demands specific consent, purpose-limitation, and breach-notification language that a generic vendor contract will not contain.

BFSI — Banks, NBFCs & Fintechs

Any bank or NBFC outsourcing a function — collections, customer service, technology, KYC verification — is bound by RBI's outsourcing directions, which mandate specific contractual content irrespective of what the vendor is willing to agree to commercially. This includes the regulated entity's right to audit the vendor, data localisation and access controls, restrictions on further sub-contracting, business continuity obligations, and — critically — exit assistance provisions that allow the bank or NBFC to transition away from the vendor without service disruption. A vendor contract that omits these is not merely commercially weak; it can render the regulated entity non-compliant with its own regulator.

E-Commerce & D2C Retail

E-commerce contracts must distinguish clearly between the marketplace model and the inventory model, because liability for defective products, delayed delivery, and consumer grievances falls very differently depending on which structure applies. The Consumer Protection (E-Commerce) Rules impose specific obligations — a designated grievance officer, clear return and refund timelines, accurate country-of-origin and seller information — that a generic vendor or supplier contract will not address at all. Seller onboarding agreements for marketplaces also need explicit indemnity and de-listing provisions, since the platform's own regulatory exposure depends on how clearly it has allocated responsibility to individual sellers.

Media, Entertainment & Content

Content and media contracts turn almost entirely on precise IP licensing — the difference between an assignment and a licence, the scope of territory and duration, and whether rights are exclusive or non-exclusive. A generic services agreement will typically grant a broad, perpetual licence by default (or fail to specify one at all), which can permanently disadvantage a content creator or production house that intended to retain ownership and license only specific uses. Influencer and talent agreements additionally need clear disclosure obligations under advertising standards, revenue-share or royalty mechanics tied to measurable triggers, and moral rights language that a standard commercial template omits entirely.

Generic Clause vs. Sector-Calibrated Clause

The pattern repeats across sectors: the generic version reads professionally and appears complete, but omits the exact provision that matters when the contract is tested.

Cross-Cutting Clauses That Need Sector Calibration

Beyond the sector-specific provisions above, certain standard clauses appear in nearly every commercial contract — but the correct drafting of each still depends heavily on the industry involved.

These clauses appear in almost every commercial contract we draft, regardless of sector — but treating them as boilerplate is precisely the mistake this guide is arguing against. The table below sets out where generic drafting typically falls short, and which sectors are most exposed as a result.

How LexWin Approaches Sector-Specific Contract Drafting

We do not maintain a single master template that gets recycled across clients. Every commercial contract is built around the specific risk profile of the sector and the deal.

Who Needs This — and When

Sector-specific contract drafting is relevant at every stage of a business's growth — but the risk of relying on generic templates compounds as transaction volume and value increase. A single mismatched clause in a low-value pilot engagement is an inconvenience; the same clause, unreviewed and reused across a hundred subsequent contracts as the business scales, is a systemic exposure that surfaces all at once during due diligence for a funding round, an acquisition, or a regulatory audit.

Contract Health Check — 10 Questions to Ask About Your Current Contracts

Run this quick diagnostic against the commercial contracts your business currently uses. If you answer "no" or "unsure" to more than three, your contracts likely carry meaningful, sector-specific risk.

• Does your liability cap include carve-outs appropriate to your sector — data breach, IP infringement, product liability — or is it a flat, undifferentiated number?
• If you are a regulated entity (bank, NBFC, fintech, healthcare provider), do your vendor contracts contain the specific clauses your regulator requires?
• Does your force majeure clause reflect the disruptions that actually affect your sector, rather than generic boilerplate?
• If your business handles personal or sensitive data, do your contracts contain DPDP-aligned data processing terms — not just a standard confidentiality clause?
• Do your payment and delivery terms reference measurable, sector-relevant acceptance criteria rather than vague language like "satisfactory completion"?
• If you are in real estate, are your buyer agreements consistent with your RERA-registered project timelines and disclosures?
• Does your IP ownership clause correctly allocate rights in designs, source code, or content created during the engagement — including pre-existing IP?
• Do your termination clauses address sector-specific exit mechanics — data return, tooling ownership, transition assistance — not just a notice period?
• Was your current contract template drafted for your specific sector, or adapted from an agreement used in a different industry?
• Has your contract template been reviewed in the last 12–18 months against regulatory or statutory changes affecting your sector?

The cost of getting this right is almost always smaller than the cost of getting it wrong. A properly calibrated contract, drafted once with the correct sector-specific provisions built in, can be reused with confidence across dozens of subsequent deals. A generic contract that appears to work only postpones the cost of the missing clause — it does not eliminate it, and the eventual bill, in the form of an uncovered loss, a failed regulatory audit, or a dispute that could have been avoided, is almost always larger than the cost of drafting the contract correctly the first time.