Master Services Agreement (MSA) Negotiation Playbook (2026)

What an MSA is and why it is worth negotiating well A master services agreement (MSA) is the framework contract that governs an ongoing services relationship. It holds the legal terms that apply to every engagement, so individual statements of work (SOWs) can cover only the specific work. Getting the MSA right matters because you negotiate it once and then live under it for years across many SOWs. This playbook covers the terms that carry the most risk, with the usual positions for customer and supplier and a fallback for each. It is general guidance, not legal advice. The right position depends on the deal, your leverage and the governing law, so have a qualified professional review a material MSA. ## Structure: MSA over SOWs Set the structure first. The MSA holds liability, IP, confidentiality, warranties, insurance and dispute resolution. Each SOW holds scope, deliverables, price and timeline. Include an order of precedence clause: usually the MSA governs legal terms and a SOW governs the work, so a SOW cannot quietly rewrite the liability cap or IP position. Decide whether a SOW can vary MSA terms at all, and if so, only by express reference. ## Limitation of liability This is the single most negotiated clause. - The cap: a common position is to cap liability at the fees paid over a prior period, often the preceding 12 months. Suppliers want a low cap; customers want one large enough to be a real remedy.

• Carve outs from the cap: confidentiality breach, IP indemnity, data protection breach, and death or personal injury are commonly excluded from the cap. Watch that carve outs are not so wide they swallow the cap.
• Excluded losses: indirect and consequential losses are usually excluded. Define the categories, because labels like loss of profit are read differently across jurisdictions.
• Mutuality: push for a mutual cap where you can. ## IP ownership Agree who owns what: pre existing IP stays with its owner; newly created deliverables either transfer to the customer or are licensed. Customers often want to own what they paid for; suppliers want to keep reusable tools, methods and know how. Fallback: the customer owns the bespoke deliverables, the supplier keeps its background IP and general know how, and the customer gets a wide licence to use the deliverable for its intended purpose. ## Confidentiality and data protection - Confidentiality: mutual, with a sensible definition, standard carve outs, and a duration that fits the information. Perpetual confidentiality for ordinary information is often unnecessary.
• Data protection: where personal data is processed, attach a data processing agreement and align roles, security, breach notice and transfer mechanisms. Keep the DPA consistent with the MSA liability position.
• Security: agreed security standards, with a no material reduction commitment. ## Warranties and service levels - Warranties: services performed with reasonable skill and care, deliverables conforming to the SOW, and compliance with law. Suppliers resist absolute warranties; customers want more than best efforts.
• Service levels: where relevant, define service levels, measurement, service credits, and a right to terminate for sustained failure. Make credits a meaningful remedy, not a token. ## Term, termination and exit - Term: the MSA term and how it interacts with open SOWs; usually the MSA survives while any SOW is live.
• Termination: for cause (breach with a cure period, insolvency) and for convenience on notice, at MSA or SOW level. Agree the effect on open SOWs.
• Exit: transition assistance, return or deletion of data and materials, payment for work done to the exit date, and survival of confidentiality, IP and liability terms. ## Preparation and common traps Decide your must haves before you start (often the liability cap and carve outs, IP ownership, and a usable exit). Build your standard and fallback positions on each clause so you negotiate from a known baseline. Common traps: a liability cap with carve outs so wide it is meaningless, IP terms that leave ownership unclear, no order of precedence so SOWs contradict the MSA, confidentiality with no end date, and no transition assistance on exit. ## One workspace for draft, review, track and govern A master services agreement is negotiated once and then lived under for years, so the hour you spend on the liability cap and the precedence clause pays back across every SOW that follows. The deeper problem is that this work is usually split across a drafting tool, a review tool, a spreadsheet of dates, and email threads, so nothing stays connected and knowledge lives in people's heads. A single AI workspace tuned to your company takes a different approach. You draft, understand, edit, track and govern every contract in one place, where each document is modelled as a structured clause tree rather than flat text, so the system can show per clause risk, flag where a draft departs from your standard positions, let you edit a clause in plain language, and keep a live timeline of what changed and when. Because it learns from your own documents and preferred terms, the output sounds like your company rather than a generic template. Adira is built around that idea. A single-pane view of upcoming obligations and overall legal health is on its roadmap. The point is not another tool to check, it is to make the judgement on this page a repeatable company standard instead of something each person re-derives on every deal.