Statement of work vs master service agreement is a question about layers. The master service agreement (MSA) sets the legal terms for the whole relationship, once. Each statement of work (SOW) describes one specific piece of work under those terms: scope, people, timeline, price. You sign the MSA one time and then add SOWs as the work changes.
General information, not legal advice. Have a lawyer review any contract you sign.
I sit on the vendor side of these. The pattern that works: fight hard on the MSA, then keep SOWs short enough that adding a new engineer or project takes a day, not a month of redlines.
Key Takeaways
- The MSA is the rulebook: IP, liability, confidentiality, payment terms, termination, non-solicitation. Negotiate it once.
- The SOW is the work order: who, what, when, how much. You will sign many of them.
- Most MSAs say the MSA wins any conflict unless the SOW explicitly overrides a named section.
- In staff augmentation, the SOW usually names roles, rates, and start dates. In project work, it names deliverables and acceptance criteria.
Statement of Work vs Master Service Agreement: What Goes Where
The University of Utah's purchasing glossary defines an MSA as "a contract between two or more parties that establishes what terms and conditions will govern all current and future activities and responsibilities" (source). Ironclad describes the MSA as "the foundational document that you negotiate once, upfront," and the SOW as the document that "outlines exactly what work will be done, what the deliverables are, the timeline, who's responsible for what, and how much it's going to cost" (source).
In practice:
| Topic | MSA | SOW |
|---|---|---|
| IP ownership and assignment | Yes | Rarely (only project-specific carve-outs) |
| Confidentiality | Yes | No |
| Liability cap and indemnities | Yes | No |
| Payment terms (net days, late fees) | Yes | Sometimes overrides for one project |
| Termination and notice | Yes | Project-specific exit, if any |
| Non-solicitation and conversion terms | Yes | No |
| Roles, headcount, named engineers | No | Yes |
| Rates or fixed price | Framework only | Yes |
| Deliverables and acceptance criteria | No | Yes (project work) |
| Start date, duration | No | Yes |
My rule: if a term would be the same for the next five projects, it belongs in the MSA. If it changes with the work, it goes in the SOW.
Which One Wins When They Conflict?
Order of precedence is the clause most people skip and later regret. Ironclad's summary of standard practice: "Almost always, it will state that the terms of the MSA take precedence over any conflicting terms in an SOW, unless the SOW explicitly states that it is intentionally overriding a specific section of the MSA."
Some agreements flip this for commercial terms, so the SOW controls price and scope while the MSA controls everything legal. Law Insider has sample clauses for both styles. Either works. What does not work is silence, because then two documents disagree and nobody knows which governs.
Read the precedence clause before you sign the MSA, and again every time a vendor sends a SOW with a sneaky "notwithstanding the MSA" sentence in it.
How the SOW Changes for Staff Augmentation vs Project Work
This is where most templates mislead startups. A project SOW describes outcomes: "build the checkout flow, acceptance criteria X, Y, Z, delivered by June 30, fixed price." The vendor owns the result.
A staff augmentation SOW describes capacity: "one senior backend engineer, Node and Postgres, starting March 2, monthly rate, reporting to your engineering manager." You direct the work and own the outcome. The American Staffing Association draws the same line between firms that "support or supplement a client's work force" and managed services, where the firm "assumes full responsibility for operating a specific client function" (ASA definitions).
If your augmentation SOW includes deliverables and acceptance criteria, you have mixed two models and created an argument for later. We wrote a full guide on how to write a staff augmentation SOW, and the agreement template covers the MSA side.
A Concrete Version
A Series A fintech signs one MSA with a LATAM staff augmentation provider in January. The MSA covers IP assignment, a mutual liability cap, confidentiality, net-15 payment, 30-day notice after an initial commitment, and the terms for converting an engineer to a full-time hire.
Then the SOWs:
- SOW 1 (January): two senior backend engineers, start February 3, monthly rate each.
- SOW 2 (April): one senior React engineer for the new dashboard, start May 5.
- SOW 3 (September): one of the backend engineers rolls off; SOW 1 is amended to one engineer with 30 days' notice.
Negotiating the MSA took three weeks of back-and-forth with counsel. Each SOW took one to two days, mostly waiting for signatures. Without the MSA, each of those three changes would have been a full contract negotiation. At even two weeks each, that is six weeks of legal friction across the year, versus three weeks once plus about five days of SOW paperwork. The gap grows with every SOW after that.
The Honest Counterpoint
An MSA is overkill for a one-off. If you are hiring one freelancer for a six-week fixed project and never plan to work with them again, a single services agreement with the scope attached is simpler and cheaper to review.
The other failure is the MSA that never gets reread. Startups sign a vendor's paper in a hurry, then two years later discover a 12-month non-solicit or an IP clause that only assigns code "upon full payment." Those terms live in the MSA, which is exactly why it is the document to fight over. See staff augmentation contracts: what to check and who owns the code a contractor writes.
Frequently Asked Questions
What is the difference between a statement of work vs master service agreement?
The MSA sets the legal terms for the whole relationship and is signed once. The SOW describes one specific engagement under those terms: scope, people, timeline, and price. You can have many SOWs under one MSA.
Can a SOW override the MSA?
Usually only if the MSA allows it. Most MSAs say the MSA wins unless the SOW explicitly states it is overriding a specific section. Check the order of precedence clause, and have counsel read any SOW that claims to change MSA terms.
Do I need an MSA for staff augmentation?
If you expect to add or change engineers over time, yes. The MSA holds IP, liability, conversion, and notice terms, and each SOW adds or removes people quickly. For a single short engagement, one combined agreement can be enough.
The Bottom Line
Negotiate the MSA like you will live with it for years, because you will. Keep SOWs short, specific, and fast to sign. If you are comparing providers, ask for their MSA before the sales call ends, and read it against how to evaluate a staff augmentation provider.
Ready to see who you would be signing for? Request a shortlist of vetted senior LATAM engineers.
Roberto Espinoza is CEO of Ruzora, which helps US startups hire pre-vetted senior LATAM engineers, with a vetted shortlist in 72 hours. See available engineers.
