How to Negotiate a Master Service Agreement With No Leverage

The MSA arrives as an attachment to an onboarding email, somewhere between the W-9 request and the vendor portal invitation. That placement is the first useful piece of information in the whole negotiation. Nobody sent it to you to be negotiated. It was sent as a step, in the same spirit as the tax form.

So the honest version of the question is not how to get better terms. It is narrower than that: given that the person who emailed the document cannot change a word of it, and the person who can has never heard of your name, what is worth asking for, in what order, and where do you put the ask so that it still means something six weeks later when an invoice is sitting in someone's approval queue.

What follows is procedure, not legal advice, and it cannot tell you what a court in your state would do with any of these sentences. Where a statute is quoted, the section number and the date it was read are printed with it so you can check whether it still says that.

The MSA is not where your project lives

A master services agreement is a container. It is written once, approved internally, and issued to every vendor in a category, which is the whole reason it is not open for editing. The commercial detail gets pushed down one level, into a statement of work that is drafted per engagement.

Here is that split in a real document. Exhibit 10.29 to a public company's SEC filing is a master services agreement dated 29 June 2010 between United BioSource Corporation and Corcept Therapeutics Incorporated. Two things about it before it gets used for anything. It is here because it is a real, complete, publicly readable MSA, so the architecture can be pointed at instead of described. And it is sixteen years old, from a pharmaceutical services engagement between two companies, with most of its numbers redacted at the filer's request — a specimen of how these agreements are assembled, not evidence of what terms are standard in your market now.

Section 1.1 says the services to be performed "and accompanying timelines, budget and payment terms shall be specified in separate Statements of Work," which on signature "shall be deemed incorporated herein," and that "Each SOW shall constitute a separate agreement and shall stand alone with respect to any other SOW entered into under this Agreement." Section 1.2 adds that changes to the services are "memorialized via an amendment to the applicable SOW."

Read that list again: timelines, budget, payment terms. Those are the three things you wanted to negotiate, and none of them is in the MSA. They are in a document that has not been written yet, which the manager who hired you is usually the one drafting.

That is the leverage you have, and it is not nothing. Two documents means two reviewers. The MSA goes to legal and gets compared against a template. The SOW goes to the person with the project deadline, and the thing they want most is to start.

Read the order-of-precedence sentence before you draft anything

There is one sentence that decides whether any of this works, and it is usually in the same section that introduces the SOW. In the filed agreement above it reads: "In the event of a conflict between this Agreement and any SOW, the provisions of this Agreement will control, unless the SOW specifically acknowledges the conflict and expressly states that the conflicting SOW controls."

The exception is the entire game. Under that wording, a better payment term typed into your SOW is worth exactly zero, because it conflicts with the MSA and does not announce itself as conflicting. The clause is not hostile. It exists so that a project manager cannot accidentally rewrite the liability cap while describing a deliverable. But it means the sentence you need in the SOW is the awkward, explicit kind: this paragraph expressly modifies Section 2.1 of the Agreement for this Statement of Work only.

Precedence clauses come in roughly three shapes, and it is worth deciding which one you are looking at before you mark up anything.

Federal procurement writes this kind of hierarchy down explicitly, which makes it a useful thing to read once. FAR 52.215-8, Order of Precedence, Uniform Contract Format (Oct 1997), resolves any inconsistency by giving precedence in this order: "(a) The Schedule (excluding the specifications). (b) Representations and other instructions. (c) Contract clauses. (d) Other documents, exhibits, and attachments. (e) The specifications." The commercial-items version, FAR 52.212-4(s), ranks the schedule of supplies and services first and "other documents, exhibits, and attachments" eighth out of nine (both read on acquisition.gov, 26 September 2026).

One caveat, and it is not a small one: that is a procurement regulation, prescribed into contracts that federal agencies sign. It does not reach a commercial MSA, it is not a background rule that fills in when a private contract is silent, and no client is obliged to rank documents the way it does. Its use here is as a specimen — evidence that order of precedence is something sophisticated buyers set down deliberately, and a map of where attachments tend to land when they do. In the government's own stack, an attachment sits below the clauses and below the representations.

That is the part worth carrying back to the private deal. Emailing a PDF of your own standard terms and assuming it is now part of the agreement settles nothing by itself. Your terms rank wherever that contract's own precedence clause puts them, and in client-drafted paper an exhibit is rarely near the top.

Four asks a reviewer can approve without escalating

Rank your redline by cash effect divided by approval friction. The items below score well on both, because none of them moves liability, indemnity or insurance, which are the three areas where a contract reviewer usually has to go ask someone.

1. What starts the payment clock. The filed agreement's section 2.1 says all payments are "due within thirty (30) days after receipt of invoice." That is a good clock, and it is worth recognising a good clock when you see one, because the version you should push back on looks similar and behaves completely differently: payment due thirty days after client approval of the deliverables, with approval left undefined and owed by nobody. Ask for the invoice to become submittable on delivery.

2. A deadline on silence. The companion ask, and the one that makes the first one real: if the client does not accept or reject in writing within a stated number of business days, the deliverable is treated as accepted. On the client's side this reads like housekeeping. On yours it converts a duration into a due date. There is more on how that sentence interacts with the rest of the document in the nine clauses that decide whether you get paid.

3. Rights transfer on payment, not on creation. Section 5.1 of the same filed MSA is the clause to watch: all work product "shall be considered 'work for hire' and shall be owned solely and exclusively by Client without any further payment owed," with an assignment of everything else on top. Note the direction of that last phrase. The transfer is not conditioned on the money arriving. The ask is one clause: effective upon receipt of payment in full for the applicable SOW.

4. Bound the withholding. Section 2.1 also creates "Disputed Amounts," invoice amounts subject to a bona fide dispute raised by the client within a set number of days, which "may be withheld from the specific invoice to which it relates." In the public copy the number of days is redacted, along with several other figures, because the filer requested confidential treatment. You cannot delete a dispute mechanism, and you should not want to. What you can ask for is shape: the dispute has to be in writing, itemised, raised inside a stated window, and the undisputed remainder of the invoice is still due on the original date.

Each of those four fits in a single sentence. That matters more than it sounds like it should. A markup with eighteen comments in it gets routed to a queue and comes back in three weeks with the project already started; a markup with four gets answered by the person who opened the email.

Some of it is already law, so do not spend a concession on it

Three states now put a payment deadline and a written-contract duty on the hiring party rather than on you, which changes what a negotiation is even about. If the term you are asking for is one the statute supplies, you are not requesting a favour and you should not trade anything for it.

Illinois goes furthest, and the detail gets missed. The Freelance Worker Protection Act requires the written contract to include "the date on which the contracting entity must pay the contracted compensation or the mechanism by which such date will be determined, which shall be no later than 30 days after the products or services are provided" (820 ILCS 193/15(b)(3)). Read the end of that sentence twice. It is a ceiling on what the contract itself may say, not merely a gap-filler. Section 10(a) supplies the fallback separately: compensation is due on or before the contract date, or, if the contract does not specify, no later than 30 days after completion of the services.

The way to see that this really is an Illinois difference is to line up the equivalent provision in the other two acts, because all three have one and all three are worded almost identically. New York requires the written contract to state "the date on which the hiring party must pay the contracted compensation or the mechanism by which such date will be determined" (Gen. Bus. Law section 1412(2)(c)). California requires "the date on which the hiring party shall pay the contracted compensation or the mechanism by which the date shall be determined" (Bus. and Prof. Code section 18103(b)(3)). Neither one carries the trailing clause. The 30 days appears elsewhere in both statutes, as a default that operates only where the contract is silent, so a stated later date is not displaced by it (Gen. Bus. Law section 1411(1)(b); Bus. and Prof. Code section 18102(a)(2)). Same number, different job: in Illinois it constrains the drafter, in New York and California it fills a gap the drafter left.

The practical consequence is narrow. A 60-day term sitting in a contract governed by Illinois law is in tension with 193/15(b)(3) in a way that the identical term under New York or California law is not. What follows from that tension — whether it is a defect in the contract, a claim, or nothing you can use — is a question for a lawyer admitted there, not something to read off the section number.

All three make a waiver unenforceable, which is the provision that matters most when you have no leverage. Illinois: "any provision of a contract purporting to waive rights under this Act is void as against public policy" (820 ILCS 193/35(b)). California: "A waiver of any provision in this part shall be deemed contrary to public policy and is void and unenforceable" (Bus. and Prof. Code section 18104). New York's Article 44-A carries the equivalent provision at General Business Law section 1415(1).

The thresholds and start dates are not interchangeable, and this is where summaries of these laws go wrong. Illinois reaches contracts worth $500 or more, singly or aggregated with all contracts between the same two parties in the preceding 120 days (820 ILCS 193/5), and applies only to contracts taking effect after 1 July 2024 (193/35(a)). California uses $250 on the same 120-day aggregation (section 18101(a)) and applies only to contracts entered into or renewed on or after 1 January 2025 (section 18107). New York's figure is $800 on the same 120-day aggregation (Gen. Bus. Law section 1410(3)), and its statewide act took effect on 28 August 2024, separately from the older New York City ordinance. The remedies differ too: Illinois gives double the underpayment plus costs and reasonable attorney's fees on a two-year clock (193/30(a)), with $500 in statutory damages where a written contract was requested and refused (193/30(b)), while California awards an extra $1,000 for the refused contract and up to twice the amount unpaid (section 18106(b)).

Whether any of this reaches your engagement is a question about your facts, not about the statute, and it belongs to a lawyer admitted where the client is. The Illinois sections above were read through the General Assembly's own full-text service and the California sections on leginfo.legislature.ca.gov, both on 26 September 2026. The two state pieces on this site go through each act on its own terms: Illinois FWPA and New York's two overlapping laws. Recheck cadence for those pages is 90 days.

The clauses you will not win, and what to take instead

Some asks fail for structural reasons. Indemnity language, liability caps, insurance requirements and choice of venue are usually set by someone who never sees your file, because they are risk positions rather than commercial terms. Arguing them by email is how a four-item redline becomes a month of nothing. The move is to name a substitute that costs the other side less.

Uncapped or one-way indemnity. The full-strength ask, a mutual indemnity with a cap tied to fees, is a policy change. The narrow one often is not: a carve-out for claims arising from material the client supplied or instructions the client gave. That is a sentence about facts rather than about risk appetite, which is why it sometimes clears. What each of those clauses actually does is set out in reading the indemnity clause and the liability cap.

Termination for convenience. Do not fight the right; size the consequence. Client paper often sizes it already, and the filed MSA is a good illustration of what that looks like from the vendor's side. Section 7.2 lets either party terminate without cause on notice. Section 2.5 then provides that on termination — unless the termination is for the contractor's own breach or otherwise for cause, which is a carve-out worth noticing — the contractor is compensated for all fees and actual documented permitted costs due as of the termination date but not yet paid, and reimbursed for reasonable uncancellable third-party obligations. Section 2.4 handles the slower version, where a client suspends the work rather than ending it: past a stated number of days of suspension, the client pays for services rendered plus reasonable costs arising from the delay. Those are three numbers you can ask for even when the right to terminate is untouchable. Sizing them is its own exercise, covered in kill fees and termination for convenience.

Venue and governing law. Realistically, this one stays. It is worth reading anyway, because it tells you where a dispute would have to be brought, and that changes the arithmetic of any amount under a few thousand dollars. An anti-waiver provision of the kind quoted above is not erased by a choice-of-law clause, but what that interaction produces in practice is a lawyer's question and not a drafting tip.

Send it as a numbered list with a fallback attached to each item

The form of the request does real work. One email, numbered, each item carrying four things: the section number, the change you want, one sentence of commercial reason in the client's own language, and a fallback you will accept.

The fallback is the part people leave out, and it is the part that converts. A reviewer working through a template comparison has two cheap outcomes available: accept, or reject and move on. An item with no alternative attached gives them only the second one. An item that says or, if the cap cannot move, a carve-out for client-supplied materials would resolve this hands them a way to close the comment without asking anyone's permission.

Two more things that cost nothing to try. Ask who owns the document, because "our legal team" is often one named person with a queue, and a question addressed to a queue gets queue treatment. And ask whether there is pre-approved alternate language for the clause in question, since organisations that issue the same paper hundreds of times per year tend to have a set of fallbacks already cleared. You are not asking for an exception if the exception is already written.

When the MSA is already signed

Leverage comes back, on a schedule. It returns at the next SOW, at the first change order, and at the invoice dispute window, and those are all documents you get to help draft.

There is also a specific protection worth knowing about for the moment the squeeze arrives late, after the work is delivered and somebody suggests a discount to speed up payment. California's act says that once a freelance worker has commenced performance, the hiring party shall not require, as a condition of timely payment, that the worker accept less compensation than the contract specifies or "provide more goods or services or grant more intellectual property rights than agreed to in the contract" (Bus. and Prof. Code section 18102(b)(1) and (b)(2), read 26 September 2026). Illinois and New York have the first half of that sentence and not the second: 820 ILCS 193/10(b) and General Business Law section 1411(2) both cover being asked to accept less money, and neither mentions rights. The extra-rights clause is California's, which is exactly the sort of difference that disappears when these laws get summarised as one rule.

For the ordinary version of the same problem, where the work grew rather than the fee shrank, the route the filed MSA itself specifies is an amendment to the applicable SOW. What goes on that page, and when to send it, is in the one-page change order. And where a purchase order and the agreement disagree, that MSA settles it in advance at section 11.3: any purchase order is "for administrative convenience only," and the agreement prevails over it, including over any new terms the PO tries to introduce. Which document wins is a recurring question with a recurring answer, worked through in contract terms versus invoice terms.

What to hand a lawyer, and what to date

If the engagement is large enough to justify an hour of advice, three files make that hour useful: the MSA with your four comments in it, the precedence sentence copied out on its own, and the draft SOW. The two questions worth paying for are whether the statute in the client's state reaches this contract, and whether the modification sentence in your SOW is drafted tightly enough to do what you think it does.

Put a date on everything else. The statutory sections quoted here were read on 26 September 2026: 820 ILCS 193/5, 193/10, 193/15, 193/30 and 193/35 through the Illinois General Assembly's full-text service; California Business and Professions Code sections 18101 through 18107 on leginfo.legislature.ca.gov; New York General Business Law sections 1410 through 1415 in the codified text of Article 44-A current to 1 January 2026, with nysenate.gov as the official source; and FAR 52.215-8 and 52.212-4 on acquisition.gov. Three states passed freelance payment statutes inside eighteen months of each other, and the list is still moving, so a page like this one is worth rechecking every 90 days before you rely on a number in it.