Module 1 of 6 — MSAs for Indian Businesses

What an MSA Does (and Why You Need One)

Reading module · approx 12 min

A Master Service Agreement is not a contract for a specific job. It is the permanent legal infrastructure inside which all future work orders run. Understanding this structure is the first step to drafting or reviewing an MSA that actually does what the parties intend.

The MSA and Statement of Work model separates two things that are often confused: the commercial framework governing how the parties work together (the MSA) and the specific terms of each engagement (the SOW or Work Order). The MSA sets out the liability, IP, payment, dispute, and termination rules once. The SOW plugs into it with the specifics — deliverables, timelines, fees, personnel — for each project.

This separation is efficient. Once an MSA is in place, parties can engage on new projects without renegotiating the entire legal framework every time. A single MSA can govern dozens of SOWs over years. It also reduces negotiation fatigue: the hard commercial terms are agreed at the start; later SOWs typically negotiate only scope, price, and timeline.

Why a purchase order is not enough

A purchase order or work order without an MSA creates several gaps. First, IP ownership is not addressed — in the absence of a written assignment, Indian copyright law may vest copyright in the creating party, not the commissioning party, in some circumstances. Second, liability is unallocated — each party defaults to full liability for all losses, which is commercially unsuitable for services relationships. Third, there is no governing mechanism for changes in scope, which are inevitable in any substantial engagement.

The risk is asymmetric: the party receiving the services bears the IP and quality risk; the party providing the services bears the payment risk. Both risks are better managed inside an MSA.

The MSA versus a standalone services agreement

A standalone services agreement is appropriate for one-off engagements with no expectation of repeat work. The MSA structure is appropriate when:

The parties expect multiple engagements over time
The services are complex enough that a single document combining framework and specifics would be unwieldy
The counterparty requires MSA-first as a standard commercial practice (common in IT services, consulting, and outsourcing)

For a single, clearly scoped, fixed-fee engagement, a well-drafted services agreement may be simpler and equally effective. For anything with volume, complexity, or repeat engagement characteristics, the MSA structure is more appropriate.

Governing law and the Indian legal framework

An MSA governed by Indian law is subject to the Indian Contract Act, 1872 for its basic validity, the Specific Relief Act, 1963 for injunctive relief and specific performance, and various sector-specific statutes depending on the nature of services. IT services agreements are frequently subject to MEITY guidelines. Data-related clauses must comply with the Digital Personal Data Protection Act, 2023. Payment terms interact with GST, TDS, and FEMA for cross-border arrangements.

Common mistake Parties frequently copy MSA templates without customising the governing law, jurisdiction, and currency clauses. An MSA template drafted for US or UK law that is deployed for an India-India transaction will contain references to UCC, GDPR, or other foreign frameworks that are either irrelevant or misleading. Always audit the applicable law section and remove or replace foreign law references before signing.

Module 2 covers the scope of services and SOW structure — the provisions that cause the most disputes in practice.