MSA vs SOW: how the two-document model actually works

Agencies, consultancies and software vendors typically structure client relationships using two contracts: a Master Service Agreement (MSA) and a Statement of Work (SOW). Here's what each does and how they fit together.

The Master Service Agreement (MSA)

The MSA is signed once at the start of the relationship. It contains the legal scaffolding that doesn't change project-to-project: payment terms, IP assignment, confidentiality, liability caps, governing law and termination.

The Statement of Work (SOW)

Each new project is captured in a SOW that sits underneath the MSA. The SOW contains the project-specific commercials: scope, deliverables, milestones, fees and acceptance criteria.

Why the two-document model wins

• Sales velocity: subsequent projects only need a 1-page SOW, not a full contract.
• Cleaner legal hygiene: legal terms are negotiated once, not every project.
• Better dispute outcomes: clear separation between commercial scope and legal terms.

When you can skip the MSA

For one-off engagements with a client you'll never work with again, a single combined service agreement is fine. The MSA + SOW model only pays off when the relationship is ongoing.