MSA vs SaaS Agreement: Which Terms Control and Why It Matters

What is an MSA?

A master services agreement is a framework contract. It sets the terms that will apply to every piece of work between two businesses (payment terms, confidentiality, intellectual property, warranties, liability, insurance, dispute resolution) without describing any specific project. The actual work is then ordered through separate statements of work (SOWs), each of which describes the deliverables, timeline and price for one project and incorporates the MSA by reference.

The point of the structure is efficiency. The legal terms are negotiated once, and each new project only needs a short SOW. MSAs are common for consulting, implementation, marketing, staffing and development work, where what is being bought is people's time and the results they produce. Because the output is created for you, ownership of deliverables is one of the central issues in a services MSA.

What is a master SaaS agreement?

A master SaaS agreement, often titled a master subscription agreement, borrows the MSA structure for software. It sets the general terms for using the vendor's hosted platform: the access right, acceptable use, data ownership and security, uptime, fees and renewal, liability and termination. Individual purchases are then made through order forms that list the products, number of users, subscription term and price.

The difference from a services MSA is what you are buying. Under a SaaS agreement you do not receive deliverables that you own. You receive a time-limited right to access software the vendor runs and keeps. The central issues are therefore different: what the vendor may do with your data, whether the service will be available, how the price changes at renewal, and how you get your data out when you leave.

Master subscription agreements are usually supported by several attached or linked documents: a service level agreement for uptime and support, a data processing addendum for personal information, an acceptable use policy, and sometimes a security exhibit. Together these form the SaaS contract, and you should read them as one document.

MSA vs SaaS agreement: what is the difference?

The two structures look alike on paper, which is why they get confused, but they allocate risk around different questions. The table summarises the practical differences.

Which document controls when the terms conflict?

Most master agreements include an order-of-precedence clause that ranks the documents. A common version says the order form wins over the master agreement, and the master agreement wins over any policy or exhibit, except where the master agreement says otherwise. Read this clause early, because it tells you where the vendor can quietly change your deal. If the order form controls, a single line in an order form ("Customer's liability cap shall be one month of fees") can undo a protection you negotiated in the master agreement.

Some vendors reverse the ranking so that the master agreement always wins unless the order form expressly says it overrides a named section. That protects the master terms, but it also means a price cap or data commitment written loosely into an order form may not take effect. Whichever ranking you have, make sure the concessions you care about are in the document that wins.

Where the contract is silent, courts fall back on ordinary rules of interpretation. Under the approach summarised in the Restatement (Second) of Contracts, section 203, specific terms are generally given more weight than general language, and separately negotiated terms are given more weight than standardized ones. In practice that tends to favour the order form, since it is specific to your purchase and is the document most likely to have been negotiated. It is a tie-breaker, though, not a guarantee, and relying on it means the conflict has already become a dispute.

Do you need both an MSA and a SaaS agreement?

If you only buy software access, a SaaS agreement or master subscription agreement is enough. You need services terms as well when the vendor will also do work for you: implementation, data migration, configuration, custom integrations, training or ongoing managed services. Vendors handle this in one of three ways. Some include a professional services section inside the master subscription agreement. Some attach a separate professional services addendum. Some ask you to sign their full MSA alongside the subscription terms, with services ordered through SOWs.

The services side also brings different pricing risk. Implementation is often sold as a fixed fee based on assumptions about your data and systems, and the SOW may say that any change in those assumptions is billed at hourly rates through a change order. Read the assumptions list as carefully as the price, because it is where a fixed fee quietly becomes time and materials.

Any of these can work, as long as the services terms answer the services questions. Check who owns custom configurations, scripts or integrations built for you, whether you can keep using them if you leave the platform, how acceptance of the services works, and whether the liability cap for services is separate from the cap for the subscription. A common trap is a single liability cap measured by subscription fees, which leaves a costly failed implementation effectively uncovered.

What are the traps in a master agreement structure?

The master structure is efficient, but it spreads the deal across documents in ways that make risk easy to miss.

• Terms incorporated by a web link. Acceptable use policies, support policies and sometimes the whole master agreement may sit on a vendor web page that can change. Look for a continued use clause and ask that changes apply only at renewal, or not reduce your rights during a paid term.
• Order forms that renew independently. Each order form may have its own term and auto-renewal date, so a company with five order forms can face five different cancellation deadlines.
• Order forms signed by the wrong person. A team lead clicking "accept" on an upgrade can create a new order form that binds the company to fresh terms and a new minimum commitment.
• Master terms that outlive the products. Confidentiality, payment and audit rights in the master agreement may survive after every order form has ended, which is usually fine but worth knowing.
• Liability caps measured per order form. A cap equal to "fees paid under the applicable Order Form" can be tiny for a small add-on product, even if that product holds your most sensitive data.

How should you review a master agreement and its order forms?

Review the master agreement thoroughly once, then review each order form against it. The master agreement deserves the full read: data rights, uptime, liability, indemnity, termination and exit. If you are on the vendor side or drafting your own framework, the free master services agreement template shows how the master terms and statements of work are meant to fit together.

Pay particular attention to the definitions section, because the master agreement's definitions apply to every order form. A broad definition of "Usage Data" or "Aggregated Data" that the vendor may use freely, or a narrow definition of "Customer Data" that excludes files, logs or outputs you create, can matter more than any single clause. The same goes for how "Fees" is defined if the liability cap is measured by fees paid.

For each order form, a shorter check is enough. Confirm the products, quantities and prices match what was agreed; check the term start and end dates and the renewal and notice terms; look for any language that says it overrides the master agreement; and make sure anything you were promised in negotiation, such as a renewal price cap, is written there. Keep every signed order form in one place with its renewal date, because the master agreement alone will not tell you what you have committed to.

Which terms belong in the master agreement and which in the order form?

As a rule of thumb, anything that should apply to every purchase belongs in the master agreement, and anything specific to one purchase belongs in the order form. Data ownership, data use limits, security commitments, the liability structure, indemnity and exit rights should sit in the master agreement, so they cannot be traded away one order at a time. Price, seat counts, the subscription term, renewal caps and any product-specific service levels fit naturally in the order form.

If a vendor offers a concession on a master term, such as a higher liability cap, ask for it as an amendment to the master agreement rather than a line in one order form, so it covers every product you buy. And if you negotiate a master agreement once and then buy more products later, check that new order forms still point to the version you negotiated rather than the vendor's current online terms.