An MSA (master services agreement) holds the legal terms that stay the same across every engagement with a client: payment terms, IP, confidentiality, liability. An SOW (statement of work) defines one specific engagement: deliverables, timeline, price and assumptions. Agencies use them together so each new project needs a short SOW instead of a fresh contract.
When agencies grow past a handful of clients, the single-contract model starts to break. Renegotiating boilerplate for every project wastes time, every engagement becomes a small legal review, and sales cycles slow down.
In this guide:
- The exact difference between an MSA and an SOW, and what belongs in each
- When to use a single contract versus an MSA plus SOW structure
- How to structure SOWs so they're fast to draft and easy to approve
- The clauses that frequently get misplaced between the two documents
- How to handle change orders, addendums, and renewals cleanly
Done well, this structure cuts follow-on contract turnaround from weeks to days. Done poorly, it creates ambiguity about which document controls and which terms apply.
What is an MSA
A Master Services Agreement is a long-form contract that establishes the standing relationship between an agency and a client. It contains the legal terms that won't change from project to project: payment terms, IP ownership, confidentiality, liability, warranties, dispute resolution, and so on.
The MSA does not define specific work. It defines the rules of engagement under which any future work will be performed. Once signed, both parties can execute SOWs quickly without renegotiating the underlying terms.
Think of the MSA as the constitution. The SOWs are the laws passed under it.
What is an SOW
A Statement of Work is a short-form document that defines a specific engagement: what will be delivered, by when, for how much, and under what assumptions.
A typical SOW includes:
- Description of services and deliverables
- Timeline and milestones
- Pricing and payment schedule
- Specific assumptions and exclusions
- Acceptance criteria
- Names of key personnel
- A reference back to the governing MSA
Because the legal heavy lifting is in the MSA, SOWs can be 2 to 5 pages instead of 15 to 30. They get written, reviewed, and signed in days, not weeks.
When to use a single contract
Not every agency needs the MSA-plus-SOW structure. A single combined contract works well when:
- You're a solo or very small agency with infrequent new engagements
- You only do one type of work (e.g., website builds with no follow-on services)
- Your average engagement is under $25,000 and you rarely have repeat work
- Your sales cycle is so short that a 5-page contract is faster than maintaining two documents
For most agencies in the $25,000-and-up engagement range, the MSA-plus-SOW model pays for itself within a few clients.
When to use MSA plus SOW
The MSA-plus-SOW structure becomes valuable when:
- You have ongoing clients who buy multiple engagements
- Your retainers and projects coexist (the MSA covers both)
- You want to spin up new work quickly without legal review every time
- You work with enterprise clients whose procurement teams expect this structure
- You want to standardize terms across your client base for easier risk management
Enterprise clients often require this structure because their own purchasing processes are built around it. If you sell to mid-market and up, having an MSA ready signals professionalism.
What belongs in the MSA
The MSA holds the standing legal terms. A clean MSA structure includes:
Definitions: A short section defining key terms used throughout (Services, Deliverables, Confidential Information, etc.).
Engagement Process: A clause stating that specific services will be defined in SOWs, and that each SOW is governed by the MSA.
Payment Terms: Default invoice timing (Net 15, Net 30), late fees, suspension rights, and currency.
Intellectual Property: Default ownership rules, the trigger for IP transfer (typically full payment), and the agency's portfolio rights.
Confidentiality: Mutual confidentiality obligations, carve-outs, and term length.
Warranties and Disclaimers: Standard performance warranty, disclaimers of outcome guarantees, and disclaimers of implied warranties.
Limitation of Liability: Cap on total liability (typically tied to fees paid in the prior 12 months) and exclusion of consequential damages.
Indemnification: Mutual indemnification provisions for IP infringement and gross negligence.
Term and Termination: How the MSA itself starts and ends, what happens to active SOWs upon MSA termination, and survival clauses.
Force Majeure: Standard force majeure clause covering pandemics, natural disasters, and government actions.
Governing Law and Dispute Resolution: Which state's laws govern, where disputes are resolved, and any required mediation or arbitration.
General Provisions: Notice requirements, assignment and subcontracting rights, severability, and integration clauses. If you use partners to deliver part of the work, make sure the MSA allows it (see white-label vs subcontracting).
For more detail on writing each of these clauses well, see our agency contract essentials guide.
What belongs in the SOW
The SOW holds the engagement-specific details. A clean SOW structure includes:
Reference to MSA: A short opening paragraph: "This Statement of Work is issued under and governed by the Master Services Agreement dated [date] between [Agency] and [Client]."
Project Description: A few sentences describing what the engagement is about.
Deliverables: A bulleted list of specific outputs with quantities and specs.
Timeline: Start date, milestone dates, and target completion date.
Pricing: Total fee, payment schedule (deposit plus milestones, or monthly retainer), and any pass-through expenses.
Assumptions: What you're assuming about client inputs, decision timelines, and access. Example: "Client will provide brand assets within 5 business days of kickoff."
Exclusions: What is explicitly not included. Example: "Excludes paid media management, video production, and translation."
Acceptance Criteria: How the client signals approval of deliverables and what counts as acceptance.
Key Personnel: Account lead, project manager, and main client contact.
Signatures: Both parties sign the SOW separately from the MSA.
A good SOW reads like a project brief with legal teeth, not a contract.
Common misplacements
The most common mistake is putting the wrong content in the wrong document.
Engagement-specific terms in the MSA: Things like specific deliverables, milestones, or pricing belong in the SOW. If they're in the MSA, every new engagement requires an MSA amendment.
Standing legal terms in the SOW: Things like IP ownership, liability caps, and confidentiality belong in the MSA. Re-stating them in every SOW creates risk that they'll drift apart over time.
Payment terms split awkwardly: Default payment terms (Net 30, late fees) belong in the MSA. The specific schedule for a given engagement (deposit plus three milestones) belongs in the SOW.
Termination of one bleeding into the other: Be explicit about what happens if the MSA terminates (do active SOWs continue?) and what happens if a single SOW terminates (does the MSA survive?). The default should be: MSA termination ends future SOWs but allows active SOWs to complete; single SOW termination has no effect on the MSA.
Handling change orders
When scope changes mid-engagement, you need a clean way to amend the SOW without reopening the whole document.
A common approach: each SOW includes a "Change Order Process" section that defines how amendments work. Change orders themselves are short, one-page documents that reference the SOW and add or modify deliverables, timeline, or pricing.
A typical change order:
- References the original SOW by date and title
- Describes the change in plain language
- States the impact on timeline (if any)
- States the impact on pricing (additional fee or credit)
- Both parties sign
Set a default that no out-of-scope work begins until a change order is signed. This single rule prevents the most common form of agency profit leakage.
For a structured way to manage change orders, your project management workflow should track them as approval items, not just notes in a chat thread.
Renewals and amendments
For retainer engagements, the SOW should define how renewal works. Common patterns:
- Auto-renewal with notice: The SOW renews monthly or quarterly unless either party gives 30 days notice.
- Fixed term with explicit renewal: The SOW runs for 6 or 12 months and requires a new signed SOW to continue.
- Evergreen with annual review: The SOW continues indefinitely, with a scheduled annual review of pricing and scope.
The MSA itself should run on a longer term (often 2 to 3 years, renewing automatically) and survive any individual SOW termination.
When the MSA needs updating (new privacy laws, business changes, etc.), use an Amendment to the MSA rather than a new MSA. This preserves the contract history and avoids confusion about which version controls.
Sales process integration
The MSA-plus-SOW structure changes how sales conversations flow.
First engagement: Both the MSA and the first SOW get signed together. This takes longer than a single contract for new clients, but it sets up everything for the future.
Follow-on engagements: Only a new SOW is needed. Sales can move from "we should do this" to signed paperwork in days. The MSA never reopens.
Larger engagements: For projects above a certain threshold (often $100,000 or more), the SOW may still get a legal review even if the MSA is in place. Build that into your sales cycle expectations.
This structure pairs well with a clean new business process where SOWs are part of the proposal-to-close workflow.
Storing and versioning
Both MSAs and SOWs should be:
- Stored in a central, searchable location
- Version-controlled (template v3.2, signed copy v3.2-ClientName-2026)
- Indexed by client and engagement
- Linked together in your project management system so anyone can pull up the relevant docs
A common mistake is signing an MSA, executing a few SOWs, and then losing track of which version of the MSA actually applies. Version control prevents this.
Clients should be able to find their active MSA and every signed SOW without emailing you for a copy. In AgencyPro, contracts and proposals with e-signatures are part of Documents on the Pro plan and above, so signed copies sit next to the client's projects.
When to get legal review
Even with a strong MSA-plus-SOW structure, some situations warrant legal review:
- Initial drafting of your standard MSA template
- Annual review of the MSA template
- Any client whose procurement team requires significant changes to your MSA
- SOWs above your normal engagement size (often $100,000+)
- SOWs with unusual IP terms, exclusivity, or non-compete provisions
- International engagements where governing law gets complicated
For routine SOWs under your normal threshold, the structure is designed to let your team execute without legal involvement. That's the whole point.
Final thoughts
The MSA-plus-SOW model cuts sales cycle time on repeat work, reduces legal cost per engagement, matches how enterprise procurement teams buy, and makes follow-on work faster to sign.
The setup work is real: you need solid templates, clear internal processes, and a place to store and version everything. But once it's in place, the model pays for itself within a handful of engagements and keeps paying as the agency grows.
If you sell repeat work and still write a single combined contract for every engagement, this is the legal upgrade to make first.
Frequently asked questions
When should an agency use an MSA versus a single combined contract?
Use an MSA when you expect more than one engagement with the same client over 12 to 24 months, or when the client is large enough that legal review takes weeks. For one-off projects with new clients, a single combined contract is often faster and simpler.
What goes in the MSA vs the SOW?
The MSA holds the legal terms (liability, IP, payment, termination, confidentiality). The SOW holds the business terms specific to each engagement (scope, deliverables, timeline, price, milestones). Keep them separated; mixing them defeats the purpose.
Can a client require its own MSA?
Yes, especially with enterprise clients. Their legal teams often refuse to use vendor MSAs. Maintain a list of non-negotiable redlines (liability cap, IP on payment, no unlimited indemnification) and accept their MSA only if those redlines are honored.
How long should an MSA last?
Most MSAs run 2 to 3 years with auto-renewal. Beyond 3 years, terms tend to drift from market standards. Build a clause that allows either party to renegotiate annually with 60 days notice. This balances continuity with flexibility.
Do agencies need a lawyer to draft each SOW?
No. The SOW should be standardized so account leads can produce them without legal review. Lawyers should review the MSA template once and any non-standard SOW clauses (custom IP terms, unusual liability terms). Routing every SOW through a lawyer kills sales velocity.
Want contracts and SOWs next to the projects they govern? AgencyPro Documents (Pro plan and above) lets you create contracts and proposals from templates, collect e-signatures and keep signed copies with the client's work. Start from the master services agreement template or the scope of work template, or book a demo.