The MSA is the paper that makes everything after it fast. Negotiated once, usually painfully, it becomes the quiet legal backbone that every future order form, renewal, and expansion rides on top of.
A master services agreement (MSA) is the top-level contract between a customer and vendor that governs all future orders, statements of work, and service engagements under one set of legal terms. It covers intellectual property, liability, warranties, indemnification, data handling, confidentiality, and termination. The MSA is signed once and followed by multiple order forms or SOWs that reference it, which lets both sides transact faster on subsequent purchases without renegotiating the underlying legal framework.
The six things to understand about a master services agreement before you sign one, negotiate one, or send one to a buyer. The MSA is the longest-lived document in a vendor relationship and the one that gets referenced every time an order form, renewal, or dispute shows up.
A master services agreement is a top-level legal document that establishes the standing terms under which a vendor provides services to a customer. It is not tied to a specific purchase. Instead, each specific purchase gets documented in a separate order form or statement of work that references the MSA, inheriting its terms.
The MSA is negotiated and signed once at the start of the vendor relationship. After that, new purchases, additional seats, expansion into new modules, and renewals happen through short order forms that reference the signed MSA. The legal framework stays stable while the commercial detail flexes under it.
A standard B2B SaaS MSA covers intellectual property ownership and license grants, limitation of liability, warranties and disclaimers, mutual indemnification, data processing and privacy, confidentiality, service levels at a framework level, payment terms, and the rules for termination. Pricing and quantities live in the order form, not the MSA.
A one-off agreement covers one specific engagement with its commercial terms and legal terms bundled into a single document. An MSA separates the two: legal in the master, commercial in the order form. If a buyer only ever intends to make one purchase, a one-off agreement is simpler. If expansion is likely, the MSA pays back the extra setup cost on every subsequent order.
Every MSA includes an order of precedence clause that resolves conflicts between the master and the order forms. The usual pattern: the order form wins for commercial terms it addresses, the MSA wins for everything else, and any addendum or exhibit wins over both for the narrow topic it covers. Getting this clause right prevents disputes later.
An MSA typically has a long or indefinite term and stays in force as long as any order form under it is active. Each order form has its own commercial term, usually one or three years, with its own renewal mechanics. Terminating the MSA generally terminates all live order forms; terminating a single order form does not touch the MSA.
A master services agreement is usually fifteen to thirty pages. The exact clauses vary by industry and vendor, but the structure below is close to universal in modern B2B SaaS. Knowing the shape of the document makes it easier to spot the handful of clauses that are actually non-standard and worth meaningful negotiation.
The license grant defines what the customer gets access to, usually a non-exclusive, non-transferable right to use the software and services during the subscription term. The scope follows the quantities in the order form. Restrictions on reverse engineering, competitive benchmarking, and resale typically appear in the same section as the grant.
The vendor retains ownership of the software, platform, and any derivative works. The customer retains ownership of the data they put into the system and anything they produce using it. Feedback and suggestions the customer provides are typically assigned to the vendor on a non-exclusive basis so improvements can ship to everyone.
Most MSAs cap each party's total liability at the fees paid in the prior twelve months, with carveouts for breach of confidentiality, indemnification obligations, gross negligence, and willful misconduct. Enterprise buyers often push for a super-cap or an uncapped carveout for data breaches. This is one of the most negotiated clauses in the document.
The vendor warrants that the service will materially conform to its documentation and that it has the right to grant the license. Everything else is disclaimed: no implied warranties of merchantability, fitness for a particular purpose, or non-infringement beyond the express terms. The remedy for a warranty breach is usually re-performance or a refund, not open-ended damages.
The vendor indemnifies the customer against third-party intellectual property claims arising from the service. The customer indemnifies the vendor against claims arising from the customer's data or its use of the service in violation of the agreement. Both indemnities require prompt notice, cooperation, and the indemnifying party controlling the defense.
Standard MSAs allow termination for material breach after a cure period (usually thirty days), termination for insolvency, and termination for convenience of individual order forms at renewal. Mid-term termination for convenience is rare for the paying party and typically requires paying out the remaining committed fees. Post-termination data return obligations get spelled out here.
The MSA is one piece of a stack of documents. Understanding how the pieces interact, and which clause overrides which, is the difference between a clean contract architecture and a mess of conflicting terms that take a lawyer to untangle on every renewal.
The MSA holds the legal framework: IP, liability, warranty, indemnity, data, termination, confidentiality, and governing law. It does not contain prices, quantities, or specific deliverables. The master is designed to survive many order forms without needing to be amended for routine commercial changes.
An order form is a short document, usually one to three pages, that captures a specific purchase: the products or modules, the quantities (seats, environments, usage units), the term, the price, and any term-specific commercial variations such as ramp pricing or committed volumes. The order form references the MSA and inherits all its legal terms.
A statement of work describes a specific professional services engagement: implementation, custom integration, training, or a fixed-scope project. Where the order form sells subscription access, the SOW sells people's time and defined deliverables. The SOW references the MSA and inherits its terms, though it often includes its own acceptance criteria and payment milestones.
Exhibits attached to the MSA (sometimes labeled as schedules or appendices) cover specific framework topics that need their own detail: a data processing addendum, a security exhibit, service level definitions, a sub-processor list. These sit under the MSA and automatically apply to every order form unless an order form expressly overrides them.
If a legal term in the MSA needs to change (a liability cap, a notice address, a new carveout), the parties sign an amendment that is attached to the master. Amendments cover topics that affect all current and future order forms, not just one deal. Signing a new order form never amends the MSA; the MSA can only be changed by amending it directly.
When documents conflict, the order of precedence clause decides which wins. The common pattern: addenda beat exhibits, exhibits beat the MSA, order forms beat the MSA for commercial terms the order form addresses. The order form never overrides core legal terms like liability or indemnification unless the MSA expressly allows it. This clause lives inside the MSA itself.
The master services agreement has a specific place in the arc of an enterprise sale. It is not the first paper (that is usually the mutual NDA) and it is not the last (that is usually the signed order form). Treating the MSA as the single legal event, rather than one of several, is how deals get stuck in redlines for months.
An MSA is unnecessary at discovery. It becomes relevant when a specific purchase is in sight and both legal teams need the framework in place before the first order form can be signed. The usual trigger is a verbal commitment to buy, with price and scope roughly agreed. Starting MSA redlines earlier wastes legal cycles on both sides.
The best run cycles negotiate the MSA and the first order form in parallel, not in sequence. Commercial terms sometimes depend on legal terms (a lower liability cap might trade for a longer term, for example), so running them together surfaces those tradeoffs instead of discovering them at signature. Both tracks aim to converge on a single signature event.
The first order form is almost always signed at the same time as the MSA, often on the same signature page. From the buyer's perspective, there is no reason to sign a master framework without a committed purchase under it. From the vendor's perspective, the MSA by itself produces no revenue. The two documents land together.
Six months later, when the customer wants to add seats, a new module, or professional services, the sales team sends a one-page order form that references the signed MSA. No legal review on the master, no indemnification debate, no liability cap conversation. The MSA has already done that work. Expansion closes in days instead of months.
At renewal, the customer signs a new order form for the next term under the existing MSA. The MSA itself does not renew; it stays in force. Occasionally a renewal is paired with an MSA amendment to update a term that has shifted (a new data processing requirement, a changed notice address), but the master itself keeps running.
If a dispute arises or either side wants to terminate, the MSA is the document that governs the process. Notice requirements, cure periods, governing law, dispute resolution, data return obligations, and surviving sections (confidentiality, indemnification, limitation of liability) all live in the MSA. The order form is almost silent on these topics by design.
Strkr stores the signed MSA on the account record alongside every order form, SOW, amendment, and renewal that lives under it. Order of precedence, effective dates, and surviving clauses stay linked to the master, so legal and sales never guess which terms are in force on a given opportunity.
MSA stands for master services agreement, sometimes written as master service agreement. It is the top-level contract between a customer and a vendor that establishes the standing legal terms under which the vendor provides services. Specific purchases and quantities are documented separately in order forms or statements of work that reference the signed MSA.
An MSA is the top-level framework contract that covers the legal terms of the relationship: IP, liability, warranty, indemnification, data, confidentiality, and termination. A statement of work (SOW) is a document under the MSA that describes a specific professional services engagement with its scope, deliverables, timeline, and price. The MSA is signed once; multiple SOWs can be signed under it.
An MSA holds the legal framework and does not contain prices or quantities. An order form is a short commercial document that captures a specific purchase: the products, seats, term, and price. The order form references the signed MSA and inherits all its legal terms. One MSA, many order forms, is the standard pattern in B2B SaaS.
A typical B2B SaaS MSA covers the license grant, intellectual property ownership, limitation of liability, warranties and disclaimers, mutual indemnification, data processing and privacy, confidentiality, service levels, payment terms, termination rights, governing law, and the order of precedence between the master and its attachments. Pricing and quantities live in the order form, not the MSA.
Most MSAs have an indefinite or long term and stay in force as long as any order form under them is still active. The commercial terms live in the order forms, each of which has its own term (typically one or three years). Terminating the MSA generally terminates all live order forms; terminating a single order form does not touch the MSA.
Either party can send the first draft, but in B2B SaaS the vendor usually sends their standard MSA as the starting point. Enterprise buyers often insist on their own paper. In practice, the paper that wins is the paper of the party with more leverage, which is usually the buyer in a large deal. The MSA and the first order form are typically signed at the same time, on the same signature page.
Not exactly. An NDA (usually a mutual NDA) covers confidentiality during the pre-sale evaluation period. An MSA covers the full commercial and legal relationship after a purchase. Most MSAs include a confidentiality section that supersedes the earlier NDA for the covered relationship once the MSA is signed, but the NDA often remains useful for discussions that fall outside the MSA scope.
Yes. If a legal term in the MSA needs to change, the parties sign a formal amendment that is attached to the master. Amendments apply to all current and future order forms under the MSA. Signing a new order form never amends the master; the MSA can only be changed by amending it directly, which usually requires another round of legal review on both sides.
No sales call, no migration consultant, no four-month implementation. Enter your card, get 14 days of the full Pro tier, cancel any time before day 14 with zero charge. Spin up a workspace, import your CSV, and have something useful before lunch.
