The Master Services Agreement is the backbone of a negotiated SaaS deal — the durable legal terms the commercial relationship rests on. It is also where the clauses that can genuinely hurt you live, which is why understanding its key sections matters even though the drafting belongs to a lawyer. This is a map of what to look for, not legal advice: never sign or draft a binding MSA without qualified legal review.
The clauses that carry risk
- Limitation of liability — caps how much each side can owe if things go wrong; often the single most negotiated and most consequential clause.
- Indemnification — who covers whom for third-party claims (IP infringement, data breaches); asymmetric or uncapped indemnities are a serious exposure.
- Intellectual property — who owns what: your product stays yours, the customer's data stays theirs; watch for clauses that blur this.
- Data and confidentiality — how data is handled and protected, dovetailing with the DPA.
- Termination — how and when either party can exit, notice periods, and what happens to data on exit.
- Warranties and SLA — what you promise about the service and the remedies if you fall short.
Liability is where deals turn
The limitation-of-liability clause deserves special attention because it defines your worst-case exposure. A well-structured cap — often tied to fees paid — bounds your risk; an uncapped liability, or carve-outs that swallow the cap, can expose the whole business to a single claim. Enterprise customers routinely push to raise or remove caps, and this is precisely the negotiation where a lawyer earns their fee. Never treat the liability cap as boilerplate.
Templates start; lawyers finish
A template MSA is useful for understanding the structure and producing a first draft of your standard terms, and it gives you a baseline to negotiate from. But the exact wording of liability, indemnification, and IP clauses is where generic language can quietly expose you, and where the customer's redlines need expert interpretation. Use a template to learn and to draft; use a lawyer to review anything before it binds you.
These two clauses interact: a broad indemnification obligation can undercut an otherwise reasonable liability cap, because indemnities are often carved out of the cap. Read them as a pair to understand your true exposure, and have a lawyer confirm the cap actually limits what you think it does. This interaction is exactly the kind of subtlety a template will not flag for you.
The SaaS MSA carries the deal's real legal risk in its liability, indemnification, IP, data, and termination clauses — with the liability cap and its interaction with indemnities being the parts most worth scrutinising. Understand these well enough to read an MSA intelligently and negotiate confidently, and rely on a qualified lawyer for the wording, because the clauses in an MSA are the ones you least want to get wrong.
Independent software engineer in Nairobi specialising in Acumatica customisations, Laravel backends, and tax fiscalisation integrations across East and Southern Africa.