SaaS Contracts · Memo

Most-Favored-Nation Clauses in Enterprise SaaS: When They Bind and When They Self-Destruct

Enterprise buyers ask for MFN clauses in nearly every large SaaS negotiation. Few of them work as the buyer expects. I am going to walk through the drafting realities, the antitrust overlay, and the conditions under which MFN clauses quietly become unenforceable.

Most-favored-nation clauses in SaaS agreements take a recognizable shape. The vendor commits that the buyer will receive pricing, terms, and service levels at least as favorable as those given to any comparable customer. The buyer's procurement team treats the commitment as a guarantee. The vendor's counsel treats it as a contingent obligation laced with carve-outs. The gap between those two readings is where the actual operation of the clause lives.

I draft and negotiate MFN clauses on both sides of the table. The buyers I represent are mostly mid-market companies who lack the procurement leverage to win them outright. The vendors I represent want MFN language that satisfies the buyer's procurement checklist without binding the vendor to operationally impractical pricing review obligations. The drafting choices that distinguish a workable MFN clause from a self-destructing one are technical, but the consequences are commercial.

The three categories of MFN clauses

The first category is the pricing MFN. The vendor commits that the buyer's pricing will not be higher than the pricing offered to comparable customers for comparable services. This is the most common form and the most heavily negotiated.

The second category is the terms MFN. The vendor commits that the buyer's contractual terms (liability caps, indemnity provisions, data rights, service levels) will be no less favorable than those offered to comparable customers. This is rarer and harder to enforce because the comparison across complete contract sets is operationally difficult.

The third category is the feature or service-level MFN. The vendor commits that the buyer will have access to any new features, integrations, or service levels on terms no less favorable than those offered to comparable customers. This is sometimes drafted as a 'most-favored-product' commitment.

Each category has a different enforceability profile. The pricing MFN is the most contested but also the most operationally workable. The terms MFN is rarely used in its pure form because of administrability problems. The feature MFN is sometimes useful but is often diluted by the vendor's right to control product roadmap.

The 'comparable customer' problem

The defining drafting question in any MFN clause is the comparable-customer definition. A vendor sells to enterprise customers across a spectrum of size, use case, deployment complexity, and commercial terms. Any two customers with similar list-price-equivalent contracts may have radically different effective rates because of volume, term length, payment terms, services bundle, and renewal credits.

The buyer wants a broad comparable-customer definition. The vendor wants a narrow one. The negotiated definition usually narrows to something like 'a customer of equivalent annual contract value, with a deployment of comparable complexity, on a contract term of equivalent length, purchasing a substantially similar bundle of services.' Each of those qualifiers can be the basis for the vendor to say no comparable customer exists.

The drafting move that tightens the definition: enumerate specific objective criteria with thresholds. Annual contract value within twenty-five percent. Term length within twelve months. Service bundle including the same modules within a defined catalog. User counts within a defined range. With objective criteria, the comparable-customer determination is auditable. Without them, the determination is whatever the vendor says it is.

The audit mechanism and the self-destruction problem

This is where the clause most often self-destructs. The MFN commitment is enforceable only if the buyer can verify compliance. The buyer asks for an audit right: the buyer's counsel may inspect comparable-customer contracts to verify that the vendor's pricing complies with the MFN.

The vendor cannot agree to that. Comparable-customer contracts contain confidential information about third parties. The vendor's confidentiality obligations to other customers prohibit disclosure. The negotiated compromise is usually some version of: the vendor will provide a redacted summary, or a certification from a vendor officer, or an audit by an independent third party with no further disclosure to the buyer.

None of those compromises work well. A redacted summary tells the buyer nothing useful because the redactions remove the pricing data. An officer's certification is unfalsifiable from the buyer's perspective. A third-party audit imposes administrative cost on the vendor with little operational benefit. The MFN clause that emerges from this compromise has no real enforcement mechanism. It is a procurement-checkbox clause that the vendor will not actually be held to.

This is the self-destruction pattern. The MFN clause looks robust in the contract, but the audit mechanism is too weak to enforce it, so the clause has the practical effect of a moral commitment. The buyer's procurement team is satisfied. The buyer's general counsel, when she looks at the clause two years later wondering whether the vendor is actually complying, has no way to find out.

The drafting moves that preserve enforceability

For buyer-side counsel who wants an actually enforceable MFN, the moves that have worked in deals I have negotiated:

1. The benchmark-pricing trigger. The MFN is tied to a defined external benchmark (Gartner pricing surveys, industry-standard list rates, the vendor's own published price list). When the benchmark moves below the buyer's contracted rate, the buyer gets the benchmark rate. The benchmark is auditable without disclosing third-party contracts.
2. The list-price MFN. The vendor commits that the buyer's effective rate will be no higher than the lowest list-price-equivalent rate publicly published for the same product configuration. The vendor's public price list is auditable. The clause does not catch private discounts to other customers but does catch list-price reductions.
3. The good-faith certification with consequences. The vendor certifies compliance on each anniversary, with a defined remedy if the certification is later shown to be false (typically a refund of the differential plus a penalty). The certification creates a record. False certification creates an enforceable cause of action.
4. The benchmark plus right of comparison. The buyer has the right to provide the vendor with the redacted text of a competing offer or a publicly disclosed competing rate; the vendor must match within a defined window or release the buyer from the contract early without penalty. This treats the MFN as a competitive-response commitment rather than a comparability audit.

Each of these has trade-offs. The list-price MFN catches less than the buyer would prefer. The benchmark MFN depends on the benchmark's quality. The good-faith certification depends on the vendor's willingness to face liability for a false certification. But each of them is enforceable in a way that the audit-mechanism MFN is not.

The antitrust overlay

MFN clauses can carry antitrust risk in some configurations. The Sherman Act section 1 framework, as applied in cases including United States v. Apple Inc., 791 F.3d 290 (2d Cir. 2015), treats certain MFN structures as facilitating horizontal coordination on price. The risk is highest when the MFN is between a dominant platform and many competing suppliers, and when the structure operates to raise prices across the supplier base.

For enterprise SaaS contracts, the antitrust risk is usually low. The MFN runs between a vendor and an individual buyer, not across a supplier base. The clause does not facilitate coordination among competitors. The exception is the vertical-coordination case: an enterprise buyer who is also a platform operator, requiring suppliers to give it MFN treatment relative to competing platforms, may face antitrust scrutiny if the platform has market power. The Apple case is the leading example. Counsel should evaluate the antitrust posture when the buyer occupies a market-power position relative to its suppliers.

The renewal-period interaction

The MFN's operation across the renewal interacts with the contract's auto-renewal terms. If the MFN guarantees the buyer the best comparable-customer rate during the term, but the contract auto-renews on the vendor's then-current standard pricing, the MFN's protection lapses at renewal. The drafting needs to address this. Either the MFN extends through renewals (which the vendor will resist), or the renewal pricing has a separate cap, or the buyer has a right to renegotiate before renewal with the MFN protection intact.

I have seen too many MFN clauses where the buyer assumed the protection extended through renewals, only to discover at the first renewal that it did not. The renewal-pricing question should be addressed explicitly in the same negotiation as the MFN, not left to a later renewal discussion.

Use in vendor-side drafting

From the vendor side, the MFN clause is a concession that the vendor wants to bound. The drafting moves that bound the concession without making the clause obviously unenforceable: a narrow comparable-customer definition, an exclusion for promotional or short-term pricing offered to acquire new business, an exclusion for negotiated remedies provided in connection with specific service-level failures, a sunset on the MFN obligation after a defined period (often eighteen months or two years), and the use of certification rather than audit as the verification mechanism. None of these are bad-faith moves; they reflect that the MFN is a commercial concession, not a regulatory obligation.

What I would not assume

The MFN clause is one of the most negotiated provisions in enterprise SaaS deals and one of the least frequently enforced. The litigation record on MFN clauses in SaaS is thin; most disputes settle privately because both sides have incentive to avoid the precedential exposure. Counsel relying on an MFN clause for buyer-side leverage should evaluate the enforcement mechanism before relying on it. Counsel drafting an MFN clause for vendor-side compliance should be aware that the clause will be tested in due diligence, in renewals, and in any subsequent dispute. The clauses that hold up are the ones drafted with realistic enforcement mechanisms; the ones that self-destruct are the ones drafted to satisfy a procurement checklist without operational follow-through. Outcomes in specific matters depend on the comparable-customer landscape and the actual pricing record.

Sergei Tokmakov, Esq., CA Bar #279869. This memo is attorney commentary on legal questions and is not legal advice. Reading it does not create an attorney-client relationship. Past matter outcomes depend on facts and the responding party; nothing here is a prediction of result.