A Good MSA Can Still Produce a Bad Deal

A company signs a $1.2 million agreement to roll out a new operations platform across its 5 locations. The master services agreement took 2 months to negotiate, and it shows. Liability, confidentiality, termination, security, ownership, and indemnification all landed where the company’s lawyers wanted them.

A few weeks later the statement of work is signed, with a pricing exhibit attached. In month 5 the company adds a location through a change order. Every document gets reviewed, and none of them looks wrong on its own.

By month 6 the project is over budget, the vendor is behind schedule, and the buyer has paid an invoice it disputes. The MSA hasn’t been breached once.

The company is fictional. Its problems are common, and you won’t find any of them by reading one clause at a time.

The SOW Rewrote the MSA

In month 3 the buyer disputes a $180,000 invoice. The MSA handles that well. The buyer can withhold amounts it disputes in good faith, the vendor keeps working while the dispute gets resolved, and any breach gets 30 days to cure before anyone acts on it.

Then the vendor points to the SOW. “Notwithstanding anything in the Agreement, Vendor may suspend the Services if any invoice remains unpaid 10 days after its due date.”

The MSA’s order of precedence clause says the MSA controls unless an SOW expressly says otherwise, and the vendor’s position is that “notwithstanding anything in the Agreement” says exactly that. The vendor doesn’t need to win that argument. The buyer can pay $180,000 to keep a $1.2 million project moving, or argue precedence while its implementation team sits idle. A dispute right you can’t use without stopping the project isn’t much of a right.

Nobody was careless. The MSA went through legal. The SOW went through the project team a few weeks later, on the vendor’s template, and nobody read the two side by side.

What to Check

• The exception in your order of precedence clause. “Unless the SOW expressly states otherwise” is the door an SOW walks through.
• Every “notwithstanding” in an SOW, order form, or exhibit. Each one is an attempt to override something.
• The payment, suspension, and dispute terms in each SOW, read against the MSA’s versions.
• Your entire agreement clause. It decides which documents count, and it usually wipes out the proposal and every promise made during the sale.

The lasting fix lives in the MSA. Name the terms an SOW can never change, like liability, indemnity, payment, suspension, and termination, and require a signed amendment to the MSA to change them.

The Integration Everyone Assumed

The SOW says the vendor will integrate the new platform with the buyer’s core systems. The requirements document lists 4 integrations, and the architecture diagrams show all 4. The deliverables table, the part of the SOW that defines what the vendor delivers and gets paid for, lists 3.

In month 4 the vendor prices the fourth, a connection to the buyer’s inventory system, as a $145,000 change order. The buyer believes it was included all along. The vendor believes it was discussed and never sold. Both are reading the same SOW in good faith, and the SOW says the deliverables table “sets out the complete list of Deliverables.” The requirements document is attached “for reference only.”

It’s the precedence problem again, inside a single document. Requirements and diagrams describe what the buyer hopes to get. The deliverables table describes what the vendor agreed to deliver. When they disagree, the language that calls itself complete wins, and the gap becomes a change order.

What to Check

Write down the 5 things you’d be most upset not to get from this vendor. For each one, find the sentence in the contract that obligates the vendor to deliver it. A diagram, a proposal slide, or a line in meeting notes doesn’t count. If you can’t point to the sentence, you have a scope problem, and it’s cheaper to find it now than in a change order.

• Whether each attachment is incorporated as binding or attached “for reference.”
• Whether the deliverables table calls itself complete or exclusive.
• The assumptions section. A line like “Client will provide API access to all source systems” can move work, and cost, onto your side of the table.

The Change Order That Moved Every Date

In month 5 the buyer adds another location. The change order adds $210,000 and 90 days, and its key sentence reads “The Project Schedule is extended by 90 days.”

The buyer meant the dates for the new location. The vendor reads it as every date in the Project Schedule, including the milestones for the original 5 locations. That matters because the vendor is already 6 weeks behind on 2 of those locations, and the remaining milestones, $500,000 of the contract, carry delay credits and a termination right if the vendor runs more than 60 days late.

Move every date by 90 days and the vendor isn’t late anymore. The buyer bought one more location and gave up its leverage on the other 5.

Change orders get drafted fast, because their whole point is to keep the project moving. A change order that describes a change (“the schedule is extended”) instead of restating it (the new dates, written out) leaves the other side to decide what it meant.

What to Check

For every amendment and change order, answer these from the text of the document itself.

• Which deliverables changed?
• Which dates changed, written as dates?
• Which fees changed?
• Did acceptance criteria change?
• Did warranties or service levels change?
• Does it say everything else stays the same?

If any answer depends on what someone meant, rewrite the change order before you sign it.

The $1.2 Million Project That Costs $1.461 Million

The implementation fee is $1.2 million, and that’s the number on the approval memo. The pricing exhibit also allows separate charges for travel, third-party licenses, after-hours work, and data conversion support.

Each charge arrives on its own invoice, small enough to approve without a meeting, and each has a good reason behind it. The cutover has to happen overnight. The legacy data is messier than anyone expected. 6 months in, the approvals add up to $42,000 in travel, $68,000 in third-party licenses, $96,000 in after-hours support, and $55,000 in data work.

The $1.2 million project now costs $1.461 million, almost 22% over, and that’s before either change order. Every charge was allowed by the contract and approved by someone. Nobody owned the total.

What to Check

Search your active agreements for expenses, pass-through costs, third-party fees, licenses, overtime, after-hours rates, additional services, reimbursables, usage charges, and true-ups. For each one you find, answer 4 questions.

• Is it capped with a not-to-exceed amount?
• Does it need written approval before the work happens?
• Is it billed at cost, or with a markup?
• Does someone own the running total against the headline price?

A not-to-exceed on reimbursables and a written pre-approval rule are easy to ask for before signature and hard to get after.

The Indemnity Worth $300,000

The last problem is one the buyer hasn’t hit yet. The MSA has a strong IP indemnity. If a third party claims the platform infringes its patent, the vendor defends the buyer and pays. The MSA also caps the vendor’s total liability at the fees paid in the 12 months before a claim.

Suppose the claim had arrived in month 2, when the buyer had paid $300,000. Unless the indemnity is carved out of the cap, $300,000 is the most the buyer can recover, and a patent defense can cost more than that before anyone sees a courtroom.

The same cap shrinks at the other end. Run the formula 2 years after go-live, when the only fees paid in the prior 12 months are for support, and the cap is the support bill.

The indemnity reads well. What it’s worth depends on another clause in the same MSA, and on the calendar. We wrote about the same arithmetic in Findings We Didn’t Teach the System to Look For, where a $5,000,000 insurance policy sat behind a cap of about $140,000.

What to Check

For each protection that matters to you, ask what it’s worth in dollars today, and again a year after the project ends.

• IP infringement indemnity
• Data breach and confidentiality liability
• Insurance requirements
• Service credits
• Transition assistance and termination rights

Then check whether each one is carved out of the cap or has its own higher cap, and which fees the cap counts. This SOW, every SOW, and the trailing 12 months produce 3 different numbers.

Review the Deal, Not the Document

Every document in this deal would have passed review on its own. The MSA was strong, the SOW was reasonable, the pricing exhibit was standard, and the change order was routine. The buyer still paid an invoice it disputed, got billed for an integration it thought it owned, absorbed $261,000 in charges nobody totaled, and watched a late vendor become an on-time one overnight. Its best protection is worth a fraction of what it reads like.

Each of those problems sits where 2 documents, or 2 clauses, meet. Scope sets price, acceptance gates payment, payment terms decide suspension rights, change orders move delivery commitments, and the liability cap decides what an indemnity is worth.

You can run every check in this piece by hand, with the documents, a highlighter, and an afternoon per deal. Start with the agreements that carry the most money. If something here already happened to you, the next amendment or renewal is where you fix it.

Revver Contract Intelligence reads deals this way. An SOW, exhibit, or change order linked to its MSA is reviewed with the related agreements in its Document Family beside it, so the suspension clause and the dispute right sit on the same desk. Underneath the review is our Cross-Clause Binding Matrix, the map of how provisions change each other’s meaning. Each finding quotes the contract language it’s about, or names the clause that’s missing, and the ones that need a change come with drafted language to ask for it. A separate read looks past the standards entirely, for interactions no one wrote down, and reports them as Emergent Findings. Every review ends with a Review Receipt listing each standard checked, including the ones that came back clean.

If your book is full of deals signed before anyone read them this way, start with a Portfolio Audit. Revver and our Advisors run it with your team across the agreements you’ve already signed, so you go into the next renewal knowing what to ask for. Or reach me at sp@revver.ai.

Revver Contract Intelligence is an AI-native platform that evaluates a company’s contracts from its own position, turning the judgment behind every decision into institutional knowledge that compounds over time.