Master Services Agreement

A Master Services Agreement (MSA) is a framework contract between two parties establishing the general terms that govern an ongoing business relationship. Specific projects, services, or transactions are executed under separate Statements of Work (SOWs) that reference and incorporate the MSA's terms, letting parties negotiate general terms once (payment, IP, confidentiality, liability, indemnification, term and termination) and then quickly add new work without renegotiating fundamentals. MSAs are the standard structure for professional services relationships (consulting, agencies, development shops) and are increasingly used in SaaS for enterprise customers. It's the way sophisticated buyers and sellers manage ongoing relationships without re-papering every transaction.

The structure:

MSA (master document) covers:

• Payment terms and invoicing.
• Intellectual property ownership.
• Confidentiality and data protection.
• Warranties and representations.
• Indemnification.
• Liability limitations.
• Term and termination.
• Dispute resolution.
• General terms (force majeure, assignment, governing law).

SOWs (specific work documents) cover:

• Description of work or services.
• Deliverables and acceptance criteria.
• Timeline and milestones.
• Pricing and payment schedule.
• Specific terms unique to this project.
• Reference to and incorporation of MSA.

Why use MSA + SOW structure:

Speed: once MSA is negotiated, new SOWs can be executed quickly without legal review of every term.

Consistency: same terms apply across multiple projects with the same vendor.

Flexibility: project-specific terms can be added in SOWs without renegotiating MSA.

Risk management: liability and indemnification negotiated once at appropriate level.

Common MSA scenarios:

Consulting and professional services: McKinsey, BCG, big law firms, accounting firms all use MSAs with clients.

Development agencies: web/app development shops use MSAs with clients for ongoing project work.

SaaS enterprise contracts: increasingly use MSA + Order Form structure (MSA covers general terms, Order Form covers subscription specifics).

Software development outsourcing: offshore development teams use MSAs with clients.

What founders negotiate:

IP ownership: who owns work product (typically customer for paid work; vendor retains pre-existing IP).

Liability caps: limits on vendor exposure (typically tied to fees paid in trailing 12 months).

Indemnification: scope of indemnification, especially IP infringement.

Term and termination: notice periods, termination for convenience vs. for cause.

Payment terms: net terms (30, 45, 60 days), late payment provisions.

Key negotiation patterns:

Mutual liability caps: both parties capped at same level.

Carve-outs from liability cap: IP indemnification, confidentiality breaches, gross negligence often carved out.

Termination for convenience: typically allowed with notice (30-90 days).

Order of precedence: which document controls if MSA and SOW conflict (usually SOW for project-specific terms).

What founders get wrong: Signing vendor's MSA without negotiation, then facing terms that disadvantage the company. The right discipline: negotiate MSA terms thoughtfully; use SOWs for project-specific terms; review legal review of MSA structure.

Related: Customer Contract · Vendor Contract · Statement of Work · Indemnification Clause · Arbitration Clause

FAQ

What is a Master Services Agreement?
A framework contract between two parties establishing general terms that govern an ongoing business relationship, with specific projects executed under separate Statements of Work (SOWs) that reference and incorporate the MSA's terms.

Why use MSA + SOW structure?
Speed (new SOWs execute quickly without renegotiating fundamentals), consistency (same terms across projects), flexibility (project-specific terms in SOWs), and risk management (liability negotiated once at appropriate level).

What do MSAs typically cover?
Payment terms, IP ownership, confidentiality, warranties, indemnification, liability limitations, term and termination, dispute resolution, and general terms. SOWs cover project-specific scope, deliverables, timeline, and pricing.