What it means
Service providers and clients often work together on many projects. A master services agreement, or MSA, sets the standing rules for a continuing client and supplier relationship, commonly addressing payment mechanics, confidentiality, use of data, intellectual property, liability, termination and disputes.
A statement of work, or SOW, then specifies a particular assignment. The documents work together: neither a signed framework nor a project outline should leave a reader guessing who must deliver what.
For a design agency, the MSA might establish who owns completed deliverables, how confidential client information is handled and how invoices are disputed, while an SOW could describe a website design, milestones, accepted files, price and launch date. A second SOW could then cover analytics without renegotiating every standing legal term, although the client and agency can still agree project-specific terms when appropriate, since the MSA is not a rule that all jobs must be identical.
Order of precedence matters when the documents conflict. If the MSA limits liability one way and a later SOW says something different, the parties need to know which wording controls and whether the exception was deliberately approved, and the choice is a negotiated legal decision, not automatically that the MSA always wins.
Identify the named documents and amendments clearly, with authorised signatures and dates. Scope belongs in a document people can actually use, so define outputs, responsibilities, client inputs, acceptance process, schedule and change control.
A request for extra pages or a new integration may require another agreed price and deadline, and the change mechanism should work with the MSA payment and liability rules, so an account manager should not treat every email from a project contact as a contract amendment if only authorised signatories can approve changes. Confidentiality and data handling can be more than boilerplate, because a service provider might see customer records, credentials or unpublished product plans, so define permitted uses, security duties, subcontractor access, retention and return where relevant.
The client should verify that the framework matches the actual project risk, since an old MSA for a brochure project may not fit a later assignment involving sensitive personal data. Intellectual property needs precision too: does the client own final deliverables after payment, or receive a licence, and can the vendor reuse pre-existing code, templates or know-how?
A broad sentence giving the client everything can unintentionally include supplier tools, while a vague licence may leave the client unable to use the final work, so tie the SOW's named outputs to the framework's ownership and licence terms. There is no universal legal-cost saving formula.
If ten future projects would otherwise each need a full contract review costing an estimated $8,000, and setting up an MSA costs $20,000, a rough net avoided-review estimate is $60,000, which assumes the projects really reuse the standing terms and the SOWs need no comparable review. Actual costs and delays may differ, so the arithmetic is a planning illustration.
In practice
Real-world examples.
Example
A consultancy signs an MSA with a retail client and adds each agreed project through a separate statement of work. The first SOW covers a pricing review and the second a store-staffing study. Neither needs the liability and confidentiality terms to be negotiated again.
Example
An IT provider and client review whether the agreed liability provisions fit a new sensitive-data project. The earlier projects involved only internal reports, so the parties agree extra security duties in the new SOW. They record the change in a signed amendment rather than an email thread.
Example
The parties amend the MSA or state a specific exception when a new SOW conflicts with an earlier rule. A construction-software firm, for instance, needs a longer payment period for one large project. The exception is signed by authorised people on both sides and applies only to that SOW.
Formula
Calculation
Illustrative review-cost estimate = (estimated full-contract reviews avoided x cost per review) minus initial MSA cost. Worked example: 10 x $8,000 = $80,000 of avoided reviews, and $80,000 - $20,000 = $60,000, but only if assumptions about future SOW reviews hold. If only four of the ten projects reuse the standing terms, the avoided reviews fall to 4 x $8,000 = $32,000 and the net estimate becomes $32,000 - $20,000 = $12,000.Case study
Seen in the real world.
This illustrative and entirely fictional example follows Apex Digital, an invented agency that negotiated a full contract for each assignment with one large client. The parties agree an MSA for standing terms and use separate SOWs for campaign scope, price and dates. A later data-heavy project prompts a review of the original confidentiality and security terms before the SOW is signed.
In the fictional story the team has clearer obligations; no time or legal-cost saving is guaranteed. When the new SOW proposed access to sensitive customer data, the parties reviewed the framework's data terms rather than blindly reusing them. In this invented case the documents helped the team start work with clearer obligations, and no specific number of days or cost saving was promised.
Watch out
Common mistakes.
- Failing to state which signed document controls if terms conflict.
- Leaving liability, IP or data duties vague for the work actually performed.
- Assuming an old framework automatically suits every new project or remains in force.
Questions
People also ask.
What is an MSA?
A contract setting standing terms for a continuing services relationship.
How are projects added?
Often through statements of work that specify a project scope, deliverables, price and dates.
Why use one?
It can reduce repeated negotiation and improve consistency, provided documents and new risks are reviewed.
From the founder's library
Take it further with the book.
Build your financial confidence beyond this definition. Shihan's full-length guide, Accounting Fundamentals, takes the same plain-English approach and turns it into a complete, practical playbook for non-finance managers, business owners and students - with chapter-end quiz answers and presentation slides included.
25% off with code MMHQ25, applied at checkout. Priced in USD - checkout may show the equivalent in your local currency.
View the book and save 25%