A master services agreement (MSA) sets the overarching terms of a business relationship between two parties, while a statement of work (SOW) defines the work to be performed under that relationship, typically for a specific project or engagement.
The MSA vs. SOW distinction comes up constantly in business-to-business contracting, particularly when companies work with external vendors, consultants, agencies, and service providers.
Both of these agreements carry significant commercial weight, which is reflected in how often they're negotiated.
According to Ironclad's 2025 Contracting Benchmark Report, which draws on data from more than 1,700 customers, business services companies negotiate MSAs about 70% of the time and SOWs about 60% of the time.
To help you understand how these agreements work—individually and together—this guide explains what each one covers and how they work as part of the same contractual relationship.
What is an MSA?
An MSA, short for master services agreement, is a contract that establishes the legal and commercial framework for an ongoing business relationship, typically between a service provider and a client. It sets the ground rules for how the parties will work together, defining their baseline rights, obligations, and responsibilities before individual projects get underway.
An MSA typically addresses the terms that apply across the relationship, rather than the details of any one engagement. These terms can include:
- Confidentiality obligations
- Intellectual property ownership
- Payment arrangements
- Warranties and disclaimers
- Limitations of liability
- Indemnification
- Termination rights
- Dispute resolution procedures
Without an MSA, the parties may have to negotiate these foundational terms from scratch every time they enter a new engagement. By agreeing on them upfront, the client and service provider avoid reopening the same commercial issues each time.
That's why MSAs are common in continuous service relationships, including software development, IT support, consulting, marketing, and other professional or managed services.
What is an SOW?
An SOW, which stands for a statement of work, is a project-specific document that outlines the work a service provider agrees to perform for a client. It turns the goals of an engagement into a concrete plan, spelling out what needs to be delivered, who's responsible for each part, and what the parties expect the finished work to achieve.
A well-drafted SOW typically covers:
- Project objectives
- Scope of work
- Tasks
- Deliverables
- Milestones
- Deadlines
It should make clear what's included in the engagement—and what falls outside it.
Additionally, an SOW identifies each party's roles and responsibilities, including any resources, information, access, or approvals the client must provide. Project pricing and the payment schedule should be documented as well.
Just as important, an SOW explains how the parties will determine whether the work is complete.
Acceptance criteria set out the standards each deliverable must meet and the process for reviewing and approving it. Without well-defined criteria, the parties may have very different ideas about what counts as finished.
Like an MSA, an SOW gives both sides a shared reference point for managing the engagement. However, the two documents still differ in how they define and govern the parties' contractual relationship.
Master services agreement vs. statement of work: 8 key differences at a glance
Area
MSA
SOW
1. Scope
Governs the overall business relationship
Governs a specific project or engagement
2. Level of detail
Defines broad legal and commercial terms
Defines specific project requirements and deliverables
3. Number of documents signed
Typically involves one agreement per business relationship
Typically involves one agreement per project
4. Duration
Remains in effect for the term stated in the agreement, unless terminated earlier
Remains in effect for the duration of the project
5. Pricing and payment terms
Establishes general payment rules and procedures
Specifies project fees, rates, expenses, and payment schedules
6. Amendments
Requires formal amendments under the agreement's amendment clause
Allows project changes through change orders or addenda
7. Legal obligations
Establishes obligations across the business relationship
Establishes obligations for a specific project; can also operate as a standalone contract
8. Preparation and negotiation
Typically involves legal teams and business stakeholders
Typically involves project and commercial teams, often with legal review
MSA vs. SOW: 8 key differences explained
These eight differences break down what sets MSAs and SOWs apart and what those distinctions mean in practice.
1. What each agreement governs
An MSA sets the terms for the parties' overall business relationship. An SOW, on the other hand, describes the specific work the provider is being engaged to perform under that relationship.
For example, if you hire a software development firm, the MSA governs the ongoing relationship, while an SOW might cover a specific project, such as building a new product feature or integrating a third-party API. If you later hire the same firm to develop a mobile app, you can document that work in a separate SOW without establishing an entirely new contractual framework.
2. How much detail each agreement contains
MSAs generally cover broader legal and commercial terms, establishing the protections and procedures that apply to the entire relationship.
An SOW gets much more granular.
For a product feature build, for example, an SOW might specify:
- The functionality to be developed
- Technical requirements
- Third-party integrations
- Data migration needs
- Delivery milestones
- Testing requirements
- Acceptance criteria
This distinction matters when preparing or reviewing the documents.
Pro tip: Don't copy general legal provisions from the MSA into each SOW. It duplicates terms and makes every SOW harder to review.
3. How many agreements you sign
In a typical ongoing relationship, the parties sign one MSA and can issue multiple SOWs under it. As for the exact number of SOWs, there's no fixed limit. The number depends on how many separate projects or engagements the parties undertake.
4. How long each agreement lasts
An MSA usually remains in effect for the term set out in its duration and termination provisions. That could mean several years, or the period during which the parties maintain their business relationship.
An SOW, by contrast, typically runs for the period needed to complete the particular engagement. It may end when the agreed deliverables have been completed and accepted, or earlier if the parties terminate it under the applicable terms.
This distinction has an essential operational consequence: Completing or terminating one SOW doesn't automatically bring the MSA or every other active SOW to an end.
If you're managing several projects with the same provider, check how the documents address termination and whether ending one engagement affects the others.
5. How pricing and payment are addressed
The MSA normally establishes the general payment rules for the relationship. These may include:
- Invoicing procedures
- Payment deadlines
- Permitted payment methods
The SOW then sets out the financial details of the particular project. Depending on the arrangement, this could be a fixed project fee, hourly or time-and-materials rates, milestone-based payments, approved expenses, or a combination of these.
The SOW should make clear what triggers each invoice (such as milestones or dates) and how costs are calculated. For example, an MSA might require invoices to be paid within 30 days, while the SOW sets a fee for a specific software development project, payable in three installments tied to project milestones.
Keeping these details separate lets you maintain consistent payment procedures without locking every project into the same price.
6. How changes to each agreement are handled
Because an MSA governs the broader relationship, changing its terms can affect every engagement covered by the agreement.
For this reason, revisions generally require a formal amendment following the process set out in the MSA, which typically involves a written agreement signed by both parties. A casual email or verbal understanding may not satisfy those requirements.
Changes to an individual project, however, don't usually require amending the MSA. Instead, the parties can update the relevant SOW through a change order or addendum.
For instance, if a software development project needs an additional feature, an extended deadline, or more resources, the parties can document the change in that SOW without reopening the terms governing their entire relationship.
7. How each agreement creates binding obligations
An MSA creates binding obligations that apply across the business relationship, while an SOW creates obligations tied to a specific project.
Both documents can, therefore, carry contractual weight, even though they address different aspects of the parties' arrangement.
Importantly, an SOW doesn't need an MSA to be legally binding. It can also serve as a standalone contract, provided it contains the necessary terms and the parties intend to enter into a binding agreement. Whether it is enforceable, however, depends on the applicable law and the specific circumstances.
8. Who typically prepares and negotiates each agreement
Getting an MSA in place usually involves substantial legal input.
Because its terms can affect the entire relationship, the parties often negotiate it through their legal teams, with input from leadership, procurement, or other business stakeholders.
As for SOWs, they're usually shaped by the people closest to the project: project managers, delivery teams, department leads, and commercial teams.
These people are best positioned to determine what needs to be delivered, how long it will take, and what resources the work requires.
Of course, legal can still review the document, particularly when the engagement introduces unusual risks or departs from the terms already agreed in the MSA. In fact, Ironclad's report found legal involvement in 70% of SOWs in business services, compared with 90% of MSAs. This is a reminder that SOWs should never be automatically treated as low-risk paperwork.
Even though different teams may take the lead in preparing each document, MSAs and SOWs are ultimately two parts of the same contractual relationship.
How to combine MSAs and SOWs effectively
Combining an MSA with SOWs gives you a more complete way to manage an ongoing business relationship.
Used together, these documents provide clarity about the parties' rights and responsibilities, help keep protections consistent across projects, and make it easier to determine which terms apply when questions or disputes arise.
Here's how to make this combination work in practice:
- Put the MSA in place before or alongside the first SOW: Establish the overarching contractual terms before work begins. The MSA doesn't have to be signed long in advance; the parties can execute it alongside the first SOW.
- Have each SOW reference the governing MSA: Make the contractual connection explicit so it's clear that the SOW operates within the framework established by the MSA.
- Use the same MSA for subsequent engagements: As new projects arise, issue additional SOWs under the existing agreement rather than creating a new overarching contract each time.
- Keep the documents focused on their respective roles: Let the MSA govern the broader relationship, and each SOW capture the commitments for its particular engagement. This keeps the arrangement coherent without unnecessarily duplicating terms.
- Establish an order of precedence: If an SOW is intended to override a particular MSA provision, identify that provision and the exception.
- Review the agreements together before signing: Check that the SOW is consistent with the MSA and that any intended departures are clearly documented. For example, make sure different payment terms in an SOW aren't accidentally changing the payment rules agreed in the MSA.
Getting this structure right matters because the MSA can shape the legal and commercial risk of the entire relationship, while each SOW creates specific commitments around work, deadlines, and costs.
If you don't have an in-house legal team, or if yours lacks the expertise and time to handle this work, you can outsource it to a modern law firm like General Legal.
How General Legal can help with MSAs and SOWs
MSAs need careful legal judgment once; SOWs need fast, consistent review every time a new project starts. Hourly billing can make that second part expensive when SOWs arrive every few weeks.
General Legal is an AI-native law firm that combines experienced, US-barred attorneys with AI-powered workflows, helping startups and growth-stage companies manage commercial contracts and technology transactions.
Its attorneys draft, review, and negotiate:
- MSAs and SOWs
- SaaS and subscription agreements
- IP licenses
- Partnership agreements
- Other contracts that support technology businesses
Whether you need an MSA drafted from scratch, an existing agreement reviewed, or a new SOW checked against your established terms, General Legal provides attorney-led legal support.
AI handles the first pass (triage, issue spotting, and initial drafts), and attorneys handle the legal judgment, negotiation strategy, and final review. The result is faster turnaround on routine SOWs, with attorney oversight of the MSA terms behind them. Clients receive an upfront flat-fee quote and an expected turnaround before work begins.
General Legal also offers a free, technology-oriented MSA template.
It's a useful starting point if you're a technology or services business whose model fits the template's assumptions. For a significant or ongoing relationship, you should still have our lawyers tailor the template before signing.
To get started, create an account and open a matter, which requires no commitment or payment. If you'd rather learn more about our services first, you can book a quick introductory call with our team.
FAQ
What is an example of an MSA?
A startup might sign an MSA with a cloud infrastructure provider to establish the terms for an ongoing relationship, covering payment, data protection, confidentiality, liability, and termination.
What is an MSA used for?
An MSA establishes the legal and commercial framework for an ongoing business relationship. It lets the parties agree on core terms once and use separate SOWs or order forms to document new projects, services, or purchases.
What comes first, MSA or SOW?
Usually, the MSA comes first, establishing the terms that will govern future engagements. The parties can also sign the MSA and the first SOW together. The important thing is to have the necessary contractual terms agreed before work begins.
Is an SOW considered a contract?
It can be. An SOW is a project document, but it creates legally binding obligations when the parties agree to it, whether under an MSA or on its own, provided it contains the necessary terms and the parties intend to be bound.
Which document controls if an MSA and SOW conflict?
It depends on the order-of-precedence clause in the MSA. Often, the MSA takes priority unless the SOW expressly overrides a specific provision.
Are MSA and SLA the same?
No. The MSA establishes the broader legal relationship, while a service level agreement (SLA) defines measurable service standards, such as system uptime, support response times, and service availability. An SLA may be included in an MSA or attached to an SOW.
How does an order form differ from an MSA?
When comparing an order form vs. an MSA, the main difference is what each document covers. An MSA establishes the legal terms for the broader relationship, while an order form records the details of a specific purchase, such as the products or services, subscription terms, and fees.
- A master services agreement (MSA) sets the legal and commercial framework for an ongoing relationship, while a statement of work (SOW) defines the work, deliverables, and pricing for one specific project.
- Under a typical setup, the parties sign one MSA and then issue as many SOWs as they have projects, so new work doesn’t mean renegotiating core terms.
- Changing an MSA generally requires a formal written amendment, whereas an SOW can be updated through a change order or addendum.
- Ending or completing one SOW doesn’t automatically end the MSA or other active SOWs, so termination provisions should be checked across all documents.
- SOWs shouldn’t be treated as low-risk paperwork: Ironclad’s report found legal involvement in 70% of business services SOWs, compared with 90% of MSAs.
- To make the two documents work together, reference the MSA in every SOW, set an order of precedence, avoid copying MSA terms into SOWs, and review them together before signing.
| MSA | A contract setting the baseline terms for an ongoing relationship, such as confidentiality, IP, payment rules, warranties, liability, indemnification, termination, and dispute resolution. |
|---|---|
| SOW | A project-specific document covering objectives, scope, tasks, deliverables, milestones, deadlines, pricing, and acceptance criteria. |
| Scope and detail | The MSA is broad and legal; the SOW is granular and project-focused. |
| Number and duration | One MSA typically sits above many SOWs, and each SOW runs only as long as its project. |
| Pricing | The MSA sets general payment rules like invoicing and deadlines; the SOW sets fees, rates, expenses, and payment schedules. |
| Changes | MSA changes need a formal amendment; SOW changes can be made by change order or addendum. |
| Binding effect | Both create binding obligations, and an SOW can serve as a standalone contract if it has the necessary terms and the parties intend to be bound. |
| Working together | Sign the MSA before or with the first SOW, reference it in each SOW, set an order of precedence, and review both together. |
What is an example of an MSA?
A startup might sign an MSA with a cloud infrastructure provider to establish the terms for an ongoing relationship, covering payment, data protection, confidentiality, liability, and termination.
What is an MSA used for?
An MSA establishes the legal and commercial framework for an ongoing business relationship. It lets the parties agree on core terms once and use separate SOWs or order forms to document new projects, services, or purchases.
What comes first, MSA or SOW?
Usually, the MSA comes first, establishing the terms that will govern future engagements. The parties can also sign the MSA and the first SOW together. The important thing is to have the necessary contractual terms agreed before work begins.
Is an SOW considered a contract?
It can be. An SOW is a project document, but it creates legally binding obligations when the parties agree to it, whether under an MSA or on its own, provided it contains the necessary terms and the parties intend to be bound.
Which document controls if an MSA and SOW conflict?
It depends on the order-of-precedence clause in the MSA. Often, the MSA takes priority unless the SOW expressly overrides a specific provision.
Are MSA and SLA the same?
No. The MSA establishes the broader legal relationship, while a service level agreement (SLA) defines measurable service standards, such as system uptime, support response times, and service availability. An SLA may be included in an MSA or attached to an SOW.
How does an order form differ from an MSA?
When comparing an order form vs. an MSA, the main difference is what each document covers. An MSA establishes the legal terms for the broader relationship, while an order form records the details of a specific purchase, such as the products or services, subscription terms, and fees.
- Contract vs. Agreement: What’s the Legal Difference?Compare contracts vs agreements, understand what makes them legally binding, and learn how to protect your business when making deals.
- Contract Law vs. Commercial Law: 5 Key DifferencesCompare contract vs commercial law so you can understand their differences, identify the right legal framework & protect your business in every deal.
- Legal Contract Requirements: 8 Clauses for BusinessesExplore legal contract requirements so you can understand what makes agreements enforceable, identify key clauses, & protect your business from risks.
