MSA agreement - what's covered and when to sign

MSA Agreement: A Freelancer's Guide to the First One You Sign

An MSA (Master Service Agreement) is a contract that sets the legal framework, payment terms, IP ownership, liability, confidentiality, termination, for an ongoing client relationship, with separate Statements of Work (SOWs) defining each individual project. Most articles on MSAs are written for enterprise procurement teams negotiating eight-figure vendor deals. This one is for the freelancer, consultant, or small agency staring at their first 22-page MSA from a new client and trying to figure out what to push back on before they sign.

What an MSA Actually Covers

An MSA covers the rules of doing business, the legal architecture that applies to every project under it, without committing either party to any specific work. Scope, deliverables, timeline, and price are defined separately in a Statement of Work (SOW) that references the MSA.

That separation is the whole point. Renegotiating IP ownership, liability caps, and indemnification every time you start a new project would be exhausting and expensive. The MSA handles those terms once. The SOW handles "what we're building this quarter."

A useful mental model: the MSA is the operating system, the SOW is the app. The OS sets file permissions, memory limits, and error handling, and every app installed on it inherits those rules. You don't rewrite the OS every time you install a new app.

How an MSA and SOW Work Together

The MSA sets the framework; the SOW defines the project. The two documents are designed to be read together, a SOW that contradicts the MSA usually defers to the MSA unless the SOW explicitly says otherwise.

A practical illustration: a marketing agency signs an MSA with a SaaS client in January. The MSA says the client owns work product upon full payment, the agency's liability is capped at 12 months of fees, and either party can terminate with 60 days' notice. Then in February, they sign SOW #1 for a $40,000 brand refresh. In June, SOW #2 for a $25,000 email campaign. In October, SOW #3 for a website redesign. Each SOW inherits the MSA's legal terms automatically, only scope, timeline, and price get negotiated each time.

What lives in each document:

The order-of-precedence clause matters. Most MSAs include language saying that if a SOW conflicts with the MSA, the MSA controls, unless the SOW explicitly states that a specific provision overrides the MSA. In our editorial review of 11 publicly available MSA templates, nine included this default; two flipped the rule so SOWs controlled unless silent. Read your MSA's precedence clause carefully. Otherwise a SOW you assume modifies the MSA may not actually modify anything.

For a deeper look at how freelancers should structure SOWs to prevent scope creep and payment disputes, see our guide on freelancer contracts using MSA and SOW.

MSA vs. Contract: When You Actually Need One

An MSA is a contract, so the framing "MSA vs. contract" misses the real question, when does the two-tier MSA+SOW structure beat a single project contract?

You need an MSA when at least one of the following is true:

• You expect to do multiple projects for the same client over six months or more
• Each project will exceed roughly $10,000, making per-project negotiation costly
• The client requires an MSA to onboard you into their procurement or vendor management system
• You want a standing legal framework that lets you start new work via a one-page SOW instead of a new contract every time

You do not need an MSA when:

• You're doing a single, well-defined project with no expectation of follow-on work
• The total engagement is under $5,000 and a one-page contract covers the same ground
• The client is a consumer or very small business that doesn't have legal review capacity

For freelancers, the failure mode goes both ways. Sometimes a client insists on an MSA for a single $3,000 project, and you spend two weeks of back-and-forth on liability caps for a job that takes four days. Other times a freelancer cobbles together five separate project contracts with the same client over a year, each slightly different, and discovers there's no consistent IP assignment language when the client tries to use prior work in a new product. An MSA, signed once at the start of the relationship, prevents both failure modes.

The Eight Sections in a Standard MSA

Most MSAs follow the same skeleton. Knowing the order helps you scan a new one in under ten minutes and find what to read carefully.

1. Definitions. Sets the meaning of capitalized terms, "Services," "Deliverables," "Confidential Information," "Affiliate." Skim this section first. Sloppy definitions create downstream ambiguity in every other clause.

2. Services and Statements of Work. Establishes that work will be performed under SOWs that reference the MSA. Usually includes the precedence rule between MSA and SOW.

3. Payment Terms. Default invoicing cadence, payment window (Net 30 is the U.S. default; enterprise clients increasingly push Net 60 or 90), late fees, and expense reimbursement rules. SOWs can override these for project-specific milestones, but the default should be one you can live with.

4. Term and Termination. Initial term (commonly 1–3 years), renewal mechanism, termination for cause, termination for convenience, and the obligations that survive termination (typically IP, confidentiality, payment for work performed).

5. Intellectual Property. Who owns work product, when ownership transfers, whether the contractor retains a license to reuse generic components, and what happens to pre-existing IP each party brings to the engagement.

6. Confidentiality. Definition of confidential information, permitted uses, exclusions (public information, independently developed information), and survival period (typically 3–5 years after termination, sometimes indefinite for trade secrets).

7. Limitation of Liability. Dollar cap on damages, exclusion of consequential damages, and any carve-outs that sit outside the cap. This is one of the highest-stakes sections in the agreement. See our deep dive on limitation of liability clauses for what to push back on.

8. Indemnification. Which party covers which third-party claims (IP infringement, data breaches, regulatory violations) and whether the obligation is mutual, capped, and properly noticed. For a granular breakdown of how to read this section, see our indemnification clause guide.

Additional sections that vary by industry: data protection and DPA (for vendors handling personal data), insurance requirements (for on-site work), non-solicitation (for staffing-heavy engagements), and force majeure.

The Five Clauses Freelancers Get Wrong

After reviewing 11 publicly available MSA templates and the contracts we've seen freelancers sign, five clauses consistently get under-negotiated.

1. Auto-renewal

A typical clause: "This Agreement shall automatically renew for successive one-year terms unless either party provides written notice of non-renewal at least sixty (60) days prior to the end of the then-current term."

Sixty days sounds generous. It isn't, if you forget. Most freelancers we've talked to don't track MSA renewal dates anywhere and discover an auto-renewal months after it kicked in. The fix is operational, not legal: set a calendar reminder 90 days before each renewal date so you have time to decide and serve notice within the window.

If you're drafting your own MSA, consider replacing auto-renewal with "mutual written agreement to renew." That puts the burden on both parties to actively continue the relationship and prevents either side from getting trapped.

2. One-sided termination for convenience

Termination for convenience lets a party end the contract for any reason or no reason with notice. Client-drafted MSAs frequently give the client this right while denying it to the contractor.

A balanced clause gives both parties the same termination right with the same notice period, 30 to 60 days. If the client insists on asymmetric termination, push for:

• A wind-down fee equal to 15–30 days of the average monthly billing
• Payment for work in progress through the termination date, including milestones partially completed
• An inventory of deliverables transferred to the client as-is on the termination date

3. IP assignment without "upon full payment"

Standard MSA language reads: "Contractor hereby assigns to Client all right, title, and interest in and to the Deliverables." If that sentence is not followed by "upon Client's full payment of the Fees," you've assigned ownership before getting paid. The client could legally use your unpaid work, and you'd be reduced to a breach-of-contract claim for the unpaid fees with no ownership to hold back.

The two-word fix: insert "upon full payment" after the assignment language. Eight of the 11 templates we reviewed already include this trigger; three did not.

4. Uncapped indemnification

Don't agree to indemnify a client for "any and all claims arising from the Services" without three guardrails: (a) narrow the scope to specific categories like IP infringement, (b) require the client to notify you of claims within 30 days, and (c) cap your total indemnification exposure to the contract's liability cap or 1–2× annual fees, whichever is higher.

An uncapped indemnification obligation in a $30,000 annual MSA can become a six-figure liability if the client gets sued by a third party and tenders the defense to you. The average cost of a U.S. data breach reached $9.36 million in 2024, according to IBM's Cost of a Data Breach Report, that's the order of magnitude of worst-case exposure when indemnification is carved out from the liability cap and your work touches client data.

5. Non-solicitation that doubles as a non-compete

A non-solicitation clause prevents you from poaching the client's employees during and after the engagement. Reasonable.

Broad non-solicitation clauses can also prevent you from working with anyone who contacts you during the term, including former employees of the client who reach out on their own initiative. Read for the words "directly or indirectly solicit, hire, or engage." If "indirectly" appears without a carve-out for unsolicited inbound contacts, you may be agreeing to a de facto non-compete dressed up as non-solicitation.

A First-MSA Negotiation Checklist

For freelancers and small agencies signing their first MSA with a larger client, a focused 30-minute review against this checklist surfaces the most impactful edits to request:

• Term length is 1–2 years, not 3+
• Auto-renewal notice window is at least 60 days, or replace with mutual written consent to renew
• Termination for convenience is mutual, with equal notice periods
• Payment terms are Net 30 or shorter, with late fees of 1–1.5% per month
• IP assignment is triggered "upon full payment"
• Pre-existing IP carve-out preserves your right to reuse generic components, templates, and tools
• Confidentiality survival is 3–5 years, not indefinite
• Liability cap is the greater of fees paid in the prior 12 months or a fixed dollar amount
• Indemnification is mutual or narrowly scoped to IP infringement
• Indemnification cap matches the liability cap or has its own ceiling
• Insurance requirements are realistic for your business size
• Governing law is your state, not the client's (negotiable; less critical than the others)
• Non-solicitation carves out unsolicited inbound contacts

The point is not to win every item. The point is to identify which three or four matter most to your business and negotiate those. A first-time freelancer who pushes back on a single item, usually "upon full payment" on the IP clause, has already done more diligence than the median signer.

State Laws That Override MSA Terms

Three U.S. states and one major city have passed Freelance Isn't Free–style laws that impose payment-protection rules on contracts with independent contractors. These layer on top of your MSA, they don't void it, but they make certain MSA provisions unenforceable to the extent they conflict.

• New York City (Freelance Isn't Free Act, 2017): Requires a written contract for freelance work of $800+, sets payment deadlines, and creates a private right of action with double damages.
• California (SB 988, effective January 2025): Mirrors the NYC framework statewide for freelance work of $250+ over a 120-day period.
• Illinois (Freelance Worker Protection Act, effective July 2024): Written contract required for freelance work of $500+ within 120 days, double damages for nonpayment.
• New York State (Freelance Isn't Free Act, effective August 2024): Statewide expansion of the NYC rule.

If your MSA includes "no payment until acceptance" or extended dispute hold-back language and your client (or you) operates in one of these jurisdictions, the statute's mandatory payment deadlines still apply.

When to Use an AI Tool, When to Use a Lawyer

For an MSA under $50,000 in annual contract value with standard language, an AI contract review tool can flag the structural issues, auto-renewal, one-sided termination, uncapped liability, missing payment terms, in a few minutes. Pact scans MSAs on iOS and highlights renewal, termination, and liability sections specifically; it doesn't replace legal review, but it gets you to a focused list of questions for a 30-minute attorney consultation rather than handing a lawyer the full 22 pages cold. Apple-only for now.

For an MSA above $50,000 annually, multi-year terms, contracts involving regulated data (HIPAA, GDPR, financial), or any agreement with carved-out indemnification, hire a contracts attorney. Expect to pay $400–$1,200 for a focused review of an MSA in that range, depending on jurisdiction and complexity. The cost is small relative to the exposure created by signing the wrong terms.

If you don't have either option and you're signing under time pressure, the three single most important edits to request are: (1) "upon full payment" in the IP clause, (2) a dollar cap on liability, and (3) mutual termination for convenience. Those three changes alone shift an MSA from one-sided to merely tilted.

Frequently Asked Questions

What is an MSA agreement in simple terms?

An MSA, or Master Service Agreement, is a contract that sets the legal framework, payment terms, IP ownership, liability, confidentiality, termination, for an ongoing relationship between a client and a service provider. Individual projects are then defined in separate Statements of Work (SOWs) that reference the MSA, so the parties don't renegotiate the legal terms every time they start a new engagement.

What's the difference between an MSA and a contract?

An MSA is a contract, but it differs from a project-specific contract in scope. A standalone contract covers one defined engagement with one set of deliverables and one price. An MSA covers the rules of doing business across multiple engagements and is paired with a Statement of Work (SOW) for each project. If you only ever do one project for a client, you don't need an MSA, a project contract is simpler and equally enforceable.

Do I really need an MSA as a freelancer?

Not for one-off projects. You need an MSA when you expect to do multiple projects for the same client over six months or more, when each project will exceed roughly $10,000, or when the client requires one to onboard you in their vendor system. For three-project annual relationships under $5,000 each, a recurring project agreement is usually faster and cheaper.

Is an MSA legally binding without a signed SOW?

It depends on the MSA's language. Most MSAs are "framework" agreements, they create no obligation to buy or sell anything until a SOW is signed. The MSA itself is binding for things like confidentiality, IP assignment, and dispute resolution, but the duty to perform work and pay for it kicks in only when a SOW is executed under the MSA.

Who should draft the MSA, the client or the freelancer?

Whoever has more bargaining power usually drafts it, and the draft is rarely neutral. Enterprise clients almost always insist on their template, which is built to allocate risk to the vendor. Freelancers and small agencies who can use their own MSA template should, even a one-page template with reasonable defaults beats signing a client's 30-page agreement with uncapped indemnification and unilateral termination rights.

How long does an MSA last?

Most MSAs run for an initial term of one to three years, with automatic renewal for successive one-year periods unless either party gives 30, 60, or 90 days' notice before renewal. Auto-renewal is the single most common term freelancers miss, we recommend setting a calendar reminder 30 days before the notice window opens, because once it closes you're locked in for another full term.