SaaS MSA Review: 10 Clauses to Check Before Signing
By Siddhant Madan · 9 min · K2 Consulting
Your sales team has the deal marked as closed. Then the customer's MSA arrives. Forty pages, an order form and a security exhibit. The number on the front is attractive. The obligations buried in the back may not be.
The mistake is to read it as forty pages of equally important legal language. It isn't. A few provisions decide whether you get paid, whether you can keep using your product, and how far a dispute can reach into the rest of your business.
- Read the MSA, order form, SOW and security exhibit together. The document you skimmed may override the one you negotiated.
- Work out what the liability cap actually covers before bargaining over the multiplier.
- Don't trade away reusable technology, operational promises you cannot meet, or termination economics just to finish a redline.
Here are the ten places to look first. This is a vendor-side review, aimed at SaaS teams selling into enterprise buyers. The right fallback depends on the product, customer, law, insurer and size of the deal.
MSA Order of Precedence: Which Document Controls?
It usually lives under order of precedence. The MSA says your liability is capped. The order form says its terms prevail. The security exhibit says you will indemnify the customer for any security failure, without referencing the cap. You now have three documents and at least two plausible readings of your exposure.
In the event of any conflict, the terms of an Order Form or applicable exhibit shall control over this Agreement.
Illustrative buyer-side wording, not an actual client clause
This sentence is not clerical. It decides which commitments win. Read every exception to the hierarchy, including data-processing documents and statements of work. A carefully negotiated MSA is not much protection if a later SOW can quietly reopen it.
A customer asks for one small integration SOW. The SOW adds broad service warranties and says it takes priority. The fees are modest, but the new promises apply immediately. The project is now carrying obligations nobody priced when the commercial team approved it.
SaaS MSA Review Checklist: Ten Risk Areas
1. Scope and change control
Does the customer get the product described in your documentation, or whatever functionality its team later decides was implied? Make deliverables and dependencies identifiable. For implementation services, state how additions are requested, approved and paid for. Otherwise the work expands while the fee stays put.
2. Acceptance and payment
If payment depends on the customer's sole satisfaction, your invoice has become a negotiation tool. Put an objective acceptance process around bespoke work: a test against agreed criteria, a defined review period, specific defect notices and a route to correction. Don't force ordinary subscription fees through a custom-project acceptance process unless that is genuinely the deal.
3. The liability cap
Ask four questions before you change the number. Is the cap aggregate or per claim? Does it look back twelve months or at all fees payable? Does it run across the MSA or only the relevant SOW? Does it apply to both parties? The answer can matter more than whether the multiplier is one, two or three.
4. The exceptions to that cap
A cap with broad exceptions may not cap your most likely losses. Read every carve-out: confidentiality, privacy, regulatory compliance, indemnity, gross negligence and security incidents. Some higher-risk categories may justify different treatment, but an exception should be tied to a defined risk rather than swallow normal service failures. We unpack that problem in what uncapped actually reaches in an indemnity.
5. Third-party indemnities
Separate claims brought by outsiders from a dispute directly between buyer and vendor. If you are defending an IP claim, you need sensible rights to select counsel, control the defence, approve settlements and replace or modify the affected service. Exclusions should address unauthorized modifications, customer material and combinations you never approved. Check whether the indemnity sits inside or outside the liability cap.
6. Product IP and work product
This is the provision that can turn one customer into an accidental co-owner of the product. Distinguish customer data and specifically commissioned deliverables from your pre-existing software, reusable tooling, methods, libraries and general know-how. If the customer needs rights to embedded tools, a licence may solve the problem without transferring ownership of the platform you sell to everyone else.
7. Security and incident notices
Procurement may paste in a security schedule drafted for a much larger supplier. Your team, not procurement, will have to meet it. Check audit access, certifications, encryption promises, disaster recovery targets and the clock for reporting incidents. A notice obligation that starts before your team knows an incident occurred may be impossible to perform. The relevant privacy and sector rules still control where mandatory.
8. The DPA and subprocessors
If personal data is involved, the data processing agreement is part of the commercial deal. Identify the parties' roles, the processing scope, international transfers where relevant, subprocessor change processes, deletion and assistance duties. A customer veto over every routine subprocessor change can freeze your stack. See DPA and security exhibit review for the operational questions this creates.
9. Service levels and warranties
Separate what you promise about the service from what the customer wants to achieve with it. Define uptime measurement, excluded downtime and the credit-claim process. Check whether credits are the exclusive remedy for a particular SLA failure or whether the language accidentally attempts to eliminate remedies for unrelated breaches. Avoid an unqualified promise that the software will be error-free.
10. Termination, renewal and restrictions
Read the exit rights against the billing model. Can the buyer terminate for convenience midway through an annual term and demand prepaid fees back? Are cure periods realistic? Does auto-renewal lock the buyer in while your costs rise? Then look for non-solicits, exclusivity or MFN language that restricts future business with the customer's affiliates or other buyers.
How to Prioritize SaaS MSA Redlines
A thirty-comment redline tells procurement that everything is a fight. An effective redline shows which points are material and which are drafting preferences. Keep one list for must change, one for trade, and one for acceptable as written. The sales team needs to know the price of a concession before someone makes it on a call.
For example, if the customer wants a higher cap for a defined security incident, you might explore a separate, higher ceiling instead of excluding every confidentiality breach from the cap. But that ceiling has to make sense against your insurance, revenue and actual security exposure. There is no universal number that works for every vendor.
Preserve the MSA's cap when an order form or SOW adds detail. The precise hierarchy must be drafted to fit the agreement suite.
Except where the parties expressly agree otherwise by identifying the affected section of this Agreement, no Order Form or Statement of Work modifies the limitation of liability, indemnification or intellectual property provisions of this Agreement.
Illustrative fallback language only. Check for required DPA priority, negotiated exceptions and the governing law before using it.
Before you call it signed
Run a cross-document check. Confirm the defined terms match, the right exhibits are attached, the SOW does not reverse the MSA, and the final version captures what the business approved. Then record the concessions that operations will actually have to perform. A contract that is legally tidy but impossible to deliver is still a bad contract.
For a deeper look at one trap, read how the MSA/SOW liability split creates unpriced exposure. If the customer has already sent its paper, contract review and redlining is the starting point. For an enterprise MSA specifically, see MSA review and negotiation.
Need a contract reviewed or negotiated?
The general discussion above is not a substitute for assessing the actual agreement, commercial context and governing law. Explore commercial contract review.
Related reading
MSA Drafting for SaaS Startups: What Your First Enterprise Agreement Must Cover
Your first customer MSA becomes the paper your next ten buyers inherit. Draft the rights, caps and deal mechanics before their procurement team does.
SaaS Agreement vs MSA: Which Contract Should Your Startup Send?
A SaaS agreement and an MSA can cover the same relationship, but they organize it differently. Choose the structure before procurement chooses for you.
Source Code Escrow: What SaaS Vendors Can Offer Instead
Escrow may not solve the buyer's continuity problem. Data access and transition commitments may help.
Stop reading. Send the contract.
Marked up and explained, back within 24 hours.
Get my redline →First one free. Mutual NDA on the form. Calls whenever they help.