SaaS contracts
MSA vs SaaS agreement in EU deals: which structure fits
The two names are used interchangeably, and the difference is partly habit. But the structure you pick decides how every later deal is papered, and a German enterprise buyer will usually send a framework of its own.
1.4 In 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 and needs order forms or SOWs to do anything. A SaaS agreement is usually self-contained.
- A framework pays off when the same customer buys repeatedly or the product line is broad.
- Whatever it is called, the risk clauses are the same. The choice is about operations, not protection.
- A German enterprise buyer will usually send its own framework, a Rahmenvertrag, so expect that structure.
Two structures
A master services agreement sets the legal terms of a relationship without committing anyone to buy. It is a container: liability, indemnity, confidentiality, data and termination terms sit there, and each purchase is recorded separately in an order form or statement of work that incorporates the master terms. Sign the MSA once and the order forms many times.
A SaaS agreement (or subscription agreement, or terms of service) usually does both jobs in one document: the legal terms and the commercial details of product, users, fees and term. For a single purchase of a single product that is simpler.
In practice many documents called “SaaS agreements” are built as frameworks with order forms, and many “MSAs” cover a single subscription. The structure tells you more than the label.
When the framework structure is worth it
- Repeat purchases. The customer adds seats, modules or services over time, and each addition is a one-page order form instead of a renegotiated contract.
- Several products. Product-specific terms go in a schedule while the legal core stays stable.
- Enterprise procurement. Large customers expect an MSA and have a process built around it. A self-contained agreement can slow things down because it does not fit the template their lawyers know.
- Services next to software. Implementation, training and support 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 seldom returns to the paperwork.
- Speed over flexibility. One signature, one document.
- Small counterparties. A framework can look heavy to a customer with twenty people.
The order of precedence trap
A framework creates one specific risk: a conflict between the master and an order form. An order form that says “liability cap: uncapped” or “payment: net 180” in a free-text field can override the negotiated master, or not, depending on a precedence clause nobody read. With order forms winning by default, a free-text field on a sales document can silently rewrite the master. Every MSA needs a clear rule on which document wins, and order forms need a template tight enough that sales cannot reopen the master by accident.
In EU deals: the Rahmenvertrag and the call-off
A German enterprise buyer will usually send its own framework, a Rahmenvertrag, often with its general purchasing terms attached, and individual orders follow as call-offs. The master agreement should say that the order or call-off comes first, then the master, then the data processing agreement for personal data, then the security addendum, and the purchasing terms last. How to structure a framework so that purchase orders stay simple is in framework agreements and call-offs, and the German buyer’s package is in the German enterprise MSA guide.
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 changes only where the clause sits and how often you negotiate it.
For a B2B software company past its first dozen customers, a short master agreement and a tightly templated order form is almost always the right structure. It puts the negotiation up front, once, and turns every later deal into a commercial conversation instead of 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.