Recurring service relationships, such as agency work, consulting, or vendor-customer engagements, often necessitate either a master services agreement (MSA) or a statement of work (SOW).
If you’re a founder or team lead, it’s essential to understand the difference between these two agreements. At some point, your business will start doing repeat work with the same counterparty, and you’ll have to enter into either an MSA or an SOW. When that moment comes, you’ll want to have a firm handle on how the agreements function and which is right for the situation.
Here, we’ll cover the basics of MSAs and SOWs and when to use each, as well as how to handle common conflicts over terms.
What is an MSA, and what is an SOW?
A master services agreement (MSA) is a broad, overarching legal contract that outlines an ongoing business relationship between two parties. The master services agreement covers terms that apply to long-term work.
Think of a master services agreement as a foundational document. This agreement becomes a reference point for future work with the counterparty, reducing the need for lengthy negotiations and new contracts for every project.
As foundational documents that govern longer-term relationships, MSAs typically cover periods of one to three years. MSAs are common in agency, consulting, and vendor-customer arrangements, as well as in IT service engagements and enterprise SaaS implementations. MSAs are also typical in high-risk industries, such as construction and energy, as the parties must agree on liability and insurance terms before beginning work.
A statement of work (SOW) defines the actions each party will perform in a specific project. Even with a repeat counterparty that has provided similar services before, each new project typically requires a fresh SOW.
SOWs detail the scope of work for the engagement, covering deliverables, timelines, milestones, and budget. SOWs also determine when projects are “done.” For example, an SOW for a graphic design team creating a brand kit might consider the project complete when the final files for all graphic elements have been delivered.
Sometimes, parties consider an SOW more informal than an MSA because MSAs tend to undergo more extensive legal review as their terms apply to every project rendered with the counterparty. But SOWs are every bit as formal as MSAs. SOWs are legally binding documents in their own right, and when there’s a dispute, parties can reference the terms set out in the SOW to clarify expectations and any violations.
MSAs and SOWs are different, but they work in tandem. The legal terms outlined in an MSA (such as liability or indemnification) guide projects over the course of years. SOWs cover project specifics in that timeframe.
When neither an MSA nor an SOW is the right move
Not all engagements are governed by MSAs or SOWs. When the counterparty isn’t providing a recurring service, for example, if they’re selling a one-time service or a product, an MSA or SOW won’t apply. These one-off engagements might be governed by a purchase order, short-form contract, or licensing agreement instead.
Key differences between an MSA and an SOW
MSAs and SOWs serve different purposes. The master services agreement defines how parties engage, and the statement of work details what actions they’ll perform. Here’s what a typical MSA and SOW contain.
What an MSA typically covers
- Payment terms: For example, net-30 or net-60 terms and late-payment penalties.
- Intellectual property rights: Who owns intellectual property created during the engagement.
- Confidentiality: What information should be protected and for how long.
- Warranties and disclaimers: What commitments does each side uphold regarding the quality and nature of the work or product.
- Indemnification: Who is responsible for a third-party lawsuit.
- Limitation of liability: The cap on each party’s financial exposure.
- Dispute resolution: Which jurisdiction’s law governs the agreement, and whether the parties will use arbitration or litigation to resolve disputes.
What an SOW typically covers
- Scope of work: The nature of the project, which generally includes the following:
- Deliverables: The outputs to be created or provided.
- Timelines and milestones: When the deliverables should be achieved, piecewise and overall.
- Costs: The billing structure and amounts for each item.
- Acceptance criteria: The quality standards that deliverables must meet.
When to use an MSA vs. an SOW
Determining whether your business relationship requires an MSA vs. SOW depends on factors such as relationship duration, project complexity, payment terms, and the likelihood of repeat work.
Use an MSA + SOW for ongoing or multi-project work
If you plan to perform repeat work with the same party, start with an MSA. While it might take time to negotiate, the agreement will save you time in the long run. When you begin making individual SOWs for additional projects with the party, you can quickly negotiate line items such as deliverables and timelines without having to hash out terms in the MSA, such as liability caps or IP ownership.
Use an SOW alone for simple, one-off work
Using an SOW alone is typically only viable for one-off, low-risk projects where you’re unlikely to require the vendor’s services in the future. The SOW will cover the bases by describing project costs, scope, timeline, and deliverables.
But there’s a tradeoff. When you skip the more intensive negotiation needed for an MSA, you may have to define terms (such as IP ownership) as needs arise. If you work with the counterparty again, you’ll need to negotiate an MSA mid-relationship, when you may be reluctant to walk away. That reticence can give the other party leverage.
How MSAs and SOWs work together
While some one-off projects can be governed by an SOW alone, it’s more likely that you’ll use SOWs and MSAs together. When combining these two legal documents, consider the following:
- Chronology: As the legal scaffold for an entire engagement between parties, the MSA is the chronological starting point, meaning it should be negotiated and signed before you start drafting the first SOW.
- The MSA drafting party: Either party can draft an MSA, and the one that does is at an advantage. The drafting party sets the initial terms on liability caps, IP ownership, indemnification, and more—of course, in a way that works in its favor. The other party will then redline the contract, defending its position in rounds of negotiation. Smaller parties can find themselves at a disadvantage when negotiating legal terms with a larger entity that uses a pre-established MSA framework across deals and is reluctant to change it.
When MSA and SOW terms conflict
Despite careful drafting in both an MSA and an SOW, these two documents can still contradict each other. Oftentimes, an MSA has an order-of-precedence clause that says what document controls. Typically, that’s the MSA. Disputes commonly involve:
- Payment terms: An MSA might set net-30 terms, while an SOW sets milestone payments.
- Scope: The SOW expands beyond the services established in the MSA.
- Liability caps: The SOW raises or lowers the MSA’s cap for the specific project.
- Project-specific carve-outs: The SOW contains exceptions that apply to the terms of a certain project and not to the engagement at large.
Managing MSAs and SOW contracts at scale
If you are tracking and updating dozens, if not hundreds, of MSAs and SOWs, watch out for these mistakes.
- Drafting MSAs without thinking about future SOWs: MSA terms are so rigid that SOWs cannot make exceptions for special cases, or provide little protection. Try drafting an SOW template while drafting an MSA so that you have a broad idea of what future SOWs might look like.
- SOWs that don’t reference the MSA: SOWs should mention the relevant MSA by name and effective date so that parties are clear on which terms govern which aspects of the engagements. This language often looks like: “This Statement of Work is entered into pursuant to the Master Services Agreement dated [date] between [parties].”
- Scattered SOW and MSA contract versions: When documents are scattered across coworking tools (i.e., Slack and shared drives) or e-signature accounts, there is no single source of truth. Prevent slowdowns by housing contracts in a single place and having all stakeholders use it.
- Not planning for renewals: Using a contract lifecycle management (CLM) tool, such as DocuSign, can help you stay on top of renewals and terminations with automated features that notify you when these events are coming up.
Speed up MSA and SOW redlining with Crosby
Drafting MSAs and SOWs can be a time sink for growing businesses with already overtasked teams. Plus, those teams might not have the contracting experience to confidently create agreements in the first place. Hiring in-house counsel is often too much for a small organization managing relatively few contracts.
Crosby is an AI-first law firm that gives your team the benefit of expert legal counsel at fixed, per-document pricing. AI does the first pass, flagging potential risks, and barred attorneys oversee the work. Contracts are turned around in hours.
Talk to Crosby to learn more.

