Eighteen months ago I agreed to a two-sentence request from an enterprise buyer's legal team: any pricing we offered to a similarly situated customer would automatically apply to their contract too. It read like fair-play boilerplate, so I signed it without pushing back.
Then we raised prices twice. Both times, our own legal team flagged that same account before we could send the new number, because the clause we'd waved through was quietly capping every price increase we tried to make.
What a most-favored-nation clause actually promises
A most-favored-nation, or MFN, clause guarantees a customer gets terms at least as good as anything you offer a comparable customer, for the life of the contract. It shows up in roughly 15 to 20% of enterprise SaaS agreements with annual contract value above $500,000, almost always inserted by the buyer's procurement or legal team as a hedge against being the customer who overpaid.
On paper it sounds reciprocal. In practice it's one-directional: the customer benefits every time you get more competitive, and you owe them nothing when their own usage or requirements are what changed.
Why it felt harmless when we signed it
We were closing our first deal over $250,000 and didn't want a clause fight to be the reason it slipped a quarter. The request came in during final redlines, framed as standard language, and our lawyer's note called it negotiable but low-risk at our size. All of that was true in the moment. What none of us modeled was what happens once the company grows past the pricing tier that clause was written against.
What it actually cost us
The clause had no scope limit, so it applied to every commercial term, not just list price, including bundled discounts, multi-year prepay terms, and one-off pilot pricing we offered to land smaller logos. Eighteen months later, closing a $340,000 deal at a steeper enterprise discount meant our legal team had to first calculate whether that discount would trigger a price credit for the original MFN account, then decide whether to restructure the new deal's terms specifically to avoid tripping it.
That review added roughly two weeks to a deal that was already on a tight timeline, and it happened again on the next enterprise contract, and the one after that. A clause we'd treated as boilerplate had turned every future discount decision into a compliance question first and a sales question second.
The redline language that actually works
If a buyer's counsel asks for MFN language, this is the counter that keeps the relationship intact without leaving the clause open-ended:
We're comfortable with a price-parity commitment scoped to list price only, applied prospectively, with a 30-day adjustment window following written notice. We'd ask that it exclude time-limited promotional pricing, multi-year prepay discounts, and bundled or pilot arrangements, and that compliance be handled through an annual written certification rather than an audit right.
That language works because it doesn't refuse the ask, it just narrows what the clause can reach. Most procurement teams will accept a scoped version once they see it in writing, because their real goal is price protection, not visibility into your entire discount strategy.
The three changes I'd negotiate now
- Scope it to list price only, and explicitly exclude bundled discounts, multi-year prepay terms, and time-limited pilot pricing, so ordinary sales flexibility doesn't trigger it.
- Make it prospective and notice-based, with a defined adjustment window, market standard is around 30 days, instead of an open-ended, retroactive obligation.
- Replace any audit right with an annual self-certification. Audit rights sound reasonable until a customer's counsel requests visibility into every other contract you've signed that year.
What to do before your next enterprise contract
- Pull every active contract and flag which ones carry an MFN, price-parity, or most-favored-customer clause. Most teams have never actually inventoried this.
- For each one, note what percentage of ARR it touches, and whether it's scoped to list price only or to every commercial term.
- Draft the three fallback terms above now, so they're your first offer in the next redline instead of a concession you make under deadline pressure.
Frequently asked questions
What is a most-favored-nation clause in a SaaS contract?
It's a clause guaranteeing a customer receives pricing or terms at least as favorable as any comparable customer for the length of the agreement. It's most common in multi-year enterprise deals above roughly $500,000 in annual contract value.
How common are MFN clauses in enterprise SaaS deals?
They appear in an estimated 15 to 20% of enterprise SaaS agreements above $500,000 ACV, typically requested by the buyer's procurement or legal team rather than offered by the vendor.
Can you negotiate the scope of an MFN clause?
Yes, and you should. Scope it to list price only, add carve-outs for pilots and bundled discounts, and replace open-ended audit rights with an annual self-certification.
Does an MFN clause mean you can never discount again?
No, but an unscoped one means every future discount decision has to be checked against it first. A properly scoped clause lets you keep discounting freely outside the terms it actually covers.
It's the same lesson we learned the hard way with uncapped indemnification clauses: the clause that costs you isn't the one you fight over at signing, it's the one nobody thought to scope.
If you want a second read on a clause before you sign it, that's a contract review question we help early-stage SaaS founders work through.