US SaaS contracts
MSA vs SaaS agreement: which one you actually need
The names get used interchangeably, and the distinction is partly one of habit. But the structure you choose determines how every future deal gets papered.
1.4In the event of conflict, the terms of the applicable Order Form shall prevail over this Agreementthis Agreement shall prevail over any Order Form, except where the Order Form expressly identifies the section of this Agreement it overrides.
- An MSA is a framework; it needs order forms or SOWs to do anything. A SaaS agreement is usually self-contained.
- Framework structures pay off when the same customer buys repeatedly or the product line is broad.
- Whatever you call it, the risk clauses are identical — the choice is about operations, not protection.
Two structures
A master services agreement sets the legal terms of a relationship without committing anyone to buy anything. It is a container: the liability, indemnity, confidentiality, data and termination terms live there, and each actual purchase is documented separately in an order form or statement of work that incorporates the master terms by reference. Sign the MSA once, sign order forms many times.
A SaaS agreement (or subscription agreement, or terms of service) usually does both jobs in one document: it contains the legal terms and the commercial specifics — product, users, fees, term. For a single purchase of a single product, that is simpler.
In practice, many documents called “SaaS agreements” are structured as frameworks with order forms, and many “MSAs” are used for a single subscription. The label tells you less than the structure.
When the framework structure is worth it
- Repeat purchases. The customer adds seats, modules or services over time. Each addition is a one-page order form instead of a renegotiated contract.
- Multiple products. Product-specific terms go in a schedule; the legal core stays stable.
- Enterprise procurement. Large customers expect an MSA and have a process built around it. Sending a self-contained agreement can slow things down because it does not fit the template their legal team is used to.
- Services alongside software. Implementation, training and support engagements fit naturally as SOWs under a master.
When a single document is better
- One product, low touch. Self-serve or lightly-assisted sales where the customer signs once and rarely returns to the paperwork.
- Speed over flexibility. One signature, one document, done.
- Small counterparties. A framework structure can look heavy and slow to a twenty-person customer.
The order of precedence trap
Framework structures create a specific risk: conflict between the master and the order form. Sales teams are inventive, and an order form that says “liability cap: uncapped” or “payment: net 180” in a free-text field can override the carefully negotiated master — or not, depending on a precedence clause nobody read. Every MSA needs a clear rule about which document wins in a conflict, and order forms need to be templated tightly enough that sales cannot accidentally reopen the master.
What does not change
The risk allocation — liability, indemnity, data, IP, termination — is the same set of decisions under either structure. Choosing a SaaS agreement over an MSA does not make the liability cap easier to negotiate. It only changes where the clause sits and how often you have to negotiate it.
For a B2B software company past its first dozen customers, a short master agreement plus a tightly templated order form is almost always the right structure. It front-loads the negotiation once and makes every subsequent deal a commercial conversation rather than a legal one.
Next step
Have a contract like this on your desk?
Send it over. We will mark it up and walk you through it in twenty minutes — no cost, and you will know whether the desk is worth it.