Master Services Agreement (MSA) & Statement of Work (SOW)

What is a Master Services Agreement (MSA) & Statement of Work (SOW)?

A Master Services Agreement (MSA) is a framework contract between a service provider and a client that sets the general terms governing all the services the provider will deliver over time. The specific details of each project — scope, timeline, fees and deliverables — are captured in a Statement of Work (SOW) or work order issued under the MSA. Together, the MSA and SOW avoid the need to renegotiate standard terms for every project while keeping each engagement specific and clear.

MSAs are the backbone of the Indian IT, consulting, staffing, design and business-process outsourcing industries. They are governed by the general law of contract under the Indian Contract Act, 1872, and are routinely negotiated on cross-border deals where jurisdiction, data protection, intellectual property and limitation of liability are the highest-risk provisions.

Key Clauses & What's Included

• Services and Change Control — how services are defined, how new services are added through SOWs, and how scope changes are proposed, priced and approved to prevent creep.
• Statement of Work Mechanics — the standard format of a SOW (deliverables, milestones, timelines, fees, acceptance criteria) and the process to execute each new work order.
• Intellectual Property — ownership of work product, source code and materials, assignment to the client, and licences for any pre-existing IP the provider brings to the table.
• Confidentiality and Data Protection — protection of confidential information and personal data, aligned with the Information Technology Act and its rules on sensitive personal data, and relevant data-transfer norms.
• Limitation of Liability and Exclusions — a liability cap, typically linked to the fees paid, with carve-outs for wilful misconduct, fraud and breach of confidentiality, and caps on consequential loss.
• Indemnities — mutual or one-way indemnities for IP infringement, data breaches and third-party claims, with the scope of indemnity carefully bounded.
• Payment and Invoicing — fee models (fixed or time and material), invoicing cycles, late-payment interest, taxes and any set-off rights.
• Term, Termination and Transition — initial term, renewals, termination for convenience and for cause, and assistance to transition services out on exit.
• Warranties and Acceptance — performance standards, acceptance testing of deliverables, and the correction of defects.
• Dispute Resolution, Jurisdiction and Anti-Corruption — governing law, arbitration or court forum, and compliance with anti-bribery and anti-money-laundering norms.

Who Needs This & When to Use

An MSA is appropriate when one party will provide services to another on an ongoing or repeat basis, rather than through a single one-off contract. This includes IT services and software development firms, consulting and advisory firms, staffing and BPO companies, design and marketing agencies, and any vendor serving enterprises under multiple engagements.

It is also the right structure when the same service provider and client expect a series of projects, because negotiating one comprehensive MSA once is far more efficient than drafting a full contract each time. For a one-off development job, a standalone consultancy or software development agreement may be simpler; if you expect repeat work, an MSA plus SOWs is the professional approach.

How We Draft It & Process

We begin by mapping your business model: which side you are on (provider or client), the nature of the services, whether engagements are repeat, and the value and risk profile of typical projects. We also ask about data flows, IP ownership expectations and whether work crosses jurisdictions.

Our lawyers then draft a balanced MSA with a standard SOW template, negotiating from your position — a provider-friendly or client-friendly starting draft as you require. We issue a fixed-fee quote before drafting and explain each material clause, particularly limitation of liability and IP. If you conclude a deal with a redlined contract from the other side, we handle the negotiation clause by clause and deliver the agreed suite in editable format.

FAQ

Q1. What is the difference between an MSA and an SOW?
The MSA is the master or umbrella agreement that sets lasting terms such as IP ownership, confidentiality, liability and dispute resolution. The SOW records the specifics of one project — scope, milestones, fees and timelines — and incorporates the MSA by reference. Both together form the complete contract for each engagement.

Q2. Why should I put a cap on liability?
Without a limitation-of-liability clause, a service provider can face unlimited exposure for a client's consequential losses. A negotiated cap (for example a multiple of the fees for the relevant SOW) makes the commercial risk predictable, but must be balanced with carve-outs — almost no client will accept a cap covering deliberate breach or data-loss liability. Getting this balance right is what the negotiation is about.

Q3. Does an MSA need to be in a special form to be valid in India?
No special form is required beyond the normal essentials of a valid contract under the Indian Contract Act. Nevertheless, we recommend a written agreement executed properly, and stamping where required by the relevant state's Stamp Act, because an unstamped agreement may face admissibility issues in court as evidence.