How to Respond When a Customer Demands MFN Pricing
A most favored nation clause sounds like a fair ask: promise this customer they'll never pay more than anyone else for the same thing. In practice it's one of the most expensive concessions you can grant, because it doesn't just set today's price, it constrains every pricing decision you make for every other customer for as long as the clause runs.
What the clause is actually asking for
An MFN clause commits you to give the signing customer pricing, discounts, or terms at least as good as whatever you give any other customer, often within a defined segment or product line. Some versions are prospective only, applying to future deals you sign with others. The more aggressive versions are retroactive, meaning if you discount a comparable customer later, you owe this customer a true-up, sometimes with an audit right to verify it.
The retroactive, audit-backed version is the one that actually hurts. It turns every future discount decision into a compliance question, and it means someone on your team now has to track and report against a promise made in a contract most reps have forgotten exists.
Why the scope matters more than whether you say yes
Almost no CRO can flatly refuse an MFN request from a large enough account and still close the deal, so the real negotiation is about scope, not existence. A clause limited to customers of comparable size and product mix, within the same fiscal year, is a very different commitment than one that says any customer, ever. The first is something your finance team can actually monitor. The second is a promise you will eventually break without realizing it, because pricing exceptions accumulate faster than anyone tracks them.
Push for prospective-only application, a defined comparison cohort, and a request-based process instead of a standing audit right. Most procurement teams will accept a narrower clause if you frame it as making the promise enforceable instead of just aggressive on paper.
The narrower version most CROs should offer instead
- Prospective only: the clause applies to deals you sign after this one, not ones you've already signed.
- A defined comparison cohort: same product edition, similar contract value band, similar industry, not your entire customer base.
- Notice-based, not audit-based: the customer can ask whether they're still getting comparable terms, rather than holding a standing right to inspect your other contracts.
- A sunset: the obligation expires after a fixed term, typically two to three years, instead of running for the life of the relationship.
Red flags that mean you should escalate before agreeing
Watch for three signals that the ask has gone past what's reasonable: no defined comparison cohort at all, which means literally any discount anywhere in your customer base could trigger an obligation; a retroactive true-up with an audit right, which turns your pricing history into shared information; and no carve-out for one-time promotional pricing or acquisition-driven legacy deals, which means an unrelated discount decision suddenly costs you revenue on this account too. Any one of these belongs in front of your deal desk and legal before you agree to it, not after.
A fourth, quieter red flag: language that ties the clause to any affiliate or subsidiary of the customer, not just the signing entity itself. That can pull an entire corporate family into a single account's pricing protection, which is a much larger commitment than the deal in front of you would suggest on its own.
Pricing the concession instead of giving it away
An MFN clause is a real cost to you, so treat it like one in the negotiation instead of granting it as a goodwill gesture. Trade it for something that offsets the risk: a longer initial term, a committed expansion path, or the right to use the account as a reference. If the customer won't give up anything in return for a protection this valuable, that's a sign they're asking for it reflexively rather than because they actually need it, and it's worth pushing back harder on scope.
Have your deal desk quantify the expected cost of the clause before the negotiation, not after, by estimating how often a comparable customer typically gets a better deal over the sunset period. That number turns an abstract legal ask into a concrete trade you can negotiate around with the same discipline you'd apply to any other concession.
It's also worth deciding in advance who inside your company has the authority to approve an MFN request at all, rather than letting it default to whoever's negotiating the deal that week. A clause with this much downstream reach deserves the same approval rigor as a large discount, not a quieter path through legal redline where its actual cost is easy to underestimate.
What Good Looks Like
Every MFN request gets scoped in writing to a defined comparison cohort, applies prospectively only, and carries a fixed sunset, tracked in a single internal registry so future discount decisions get checked against it.
Building The Capability (5-Stage Skill Ladder)
How to Get Started
Frequently Asked Questions
Is it ever fine to just say no to an MFN request?
Yes, especially with mid-market accounts where the ask is more of a template clause their legal team includes by default than a real requirement. Ask directly why they need it. Often the answer reveals they'd accept a narrower version, or drop it entirely once you push back once instead of immediately agreeing.
How do we actually track compliance once we've agreed to one?
Keep a simple internal registry of every account with an active MFN clause, its cohort definition, and its expiration date, and check new discount approvals against that registry at the deal desk stage. Without a registry, nobody remembers the clause exists until the customer's legal team raises it during a renewal dispute.
Does an MFN clause apply to one-time promotions, like a holiday discount?
Only if you didn't carve it out. Always exclude time-limited promotional pricing, bundled deals tied to a specific campaign, and pricing inherited from an acquisition, since none of those reflect your normal price for a comparable customer. Without the carve-out, a single promotional discount to a different customer can trigger a true-up.
What's a reasonable duration for an MFN clause?
Two to three years is a common middle ground: long enough that it feels meaningful to the customer, short enough that it doesn't outlive your pricing model. An indefinite clause with no sunset is the version most likely to become a real problem years later, once nobody at your company remembers agreeing to it.
About the numbers
This guide doesn't quote a sourced benchmark. Figures in it are estimates or general guidance, so check them against your own numbers.
Related Guides
Pricing Objection Scripts for B2B Sales Calls
Word-for-word responses to the five B2B price objections reps hear most, with the questions to ask first and what to trade instead of discounting.
Building a Deal Desk: Who Approves Discounts and How Fast
How to set up discount approval tiers for a small sales team, so reps know exactly who can approve what, without every deal waiting on one busy executive.
Repricing Legacy Accounts Without Blowing Up the Renewal
A checklist for raising a legacy account's price at renewal without triggering a churn risk or breaching an old contract term.
Answering Data Residency Objections Without Overpromising
How to handle a buyer's data residency or regulatory objection with accurate answers, and when to say you genuinely can't meet the requirement.
Navigating Enterprise Vendor Portals: Coupa, Ariba, and Payment Terms
What happens when a large buyer routes your deal through Coupa or Ariba, and how to avoid losing weeks to vendor onboarding after the contract is signed.
How Enterprise Deal Cycles Are Actually Changing
What's genuinely changing enterprise deal velocity right now, from AI-assisted buying committees to procurement automation, and what hasn't changed at all.