Your biggest prospect's legal team sent back the order form with one new clause: you guarantee they always get your best price, forever, compared to any other customer. It reads like standard boilerplate. It is one of the most consequential lines you'll sign this year, and almost nobody reads it that carefully before agreeing.
That's a most-favored-nation clause, and before you sign one, there's a three-question test that tells you exactly how much risk you're taking on.
What an MFN clause actually asks for
A most-favored-nation clause guarantees a customer that they'll receive pricing and terms at least as good as anything you give any other customer for a comparable deal. It shows up in an estimated 15-20% of enterprise SaaS agreements above roughly $500,000 in annual contract value, most often pushed by procurement teams and strategic investors who want a pricing floor they can point to later.
The problem is scope. A well-scoped MFN clause is a reasonable ask. An unscoped one, as Arc's 2026 guide to the clause lays out, effectively hands one customer veto power over your entire future pricing strategy, because every discount, every bundle, and every promotional deal you cut anywhere else can trigger a retroactive obligation to match it.
The three-question test before you sign
Run every proposed MFN clause through these three questions. Two or more "no" answers means you're carrying real pricing risk, not just a favor to a good customer.
- Is it scoped to similarly situated customers? A fair clause only compares you to other customers of the same tier, deal size, and region. An unscoped one compares you to literally anyone you've ever sold to, including a struggling startup you discounted 40% just to keep them alive.
- Does it cover list price only, or actual net price? This is the one founders miss most often. A clause that reaches your negotiated net price, after every discount and bundled credit, ties your hands on every future deal. A clause limited to published list price leaves your actual negotiating room intact.
- Is it time-boxed? A clause that runs for 12 to 18 months and comes up for renegotiation at renewal is very different from one that silently runs for the life of the contract, quietly aging into obligations neither side remembers agreeing to.
The math on why this matters more than it looks
Say your MFN customer pays $180,000 a year. Eight months later, you launch a new tier bundled with a partner integration and price it at an effective 25% discount for a different segment entirely. If your MFN clause reaches net price with no similarity scoping, your MFN customer can now demand that same 25% off, retroactively, on a deal that has nothing to do with them: a $45,000 hit you never priced in, on a clause you signed to close one deal eight months earlier.
That's the actual cost of an unscoped clause: it's not the discount you're giving today, it's every pricing decision you haven't made yet, priced at whatever your most aggressive future deal turns out to be.
The fallback language to propose
Don't refuse an MFN clause outright if a strategic account is asking in good faith. Counter with a version scoped on all three dimensions, and send it the same day the request lands:
We're comfortable committing that your pricing will be at least as favorable as any other customer of comparable size and deal structure, measured against our published list price and standard discount bands, for the next 12 months. That keeps this fair to you without freezing our ability to run new pricing models for entirely different segments of the business.
That single paragraph resolves all three risk points at once: it names "comparable size and deal structure" as the scoping boundary, it anchors to list price and standard bands instead of every one-off deal you'll ever cut, and it puts a 12-month clock on the obligation instead of leaving it open-ended.
When to just say no
If your pricing model is still evolving, which is true of most companies under $10 million in ARR, an MFN clause of any scope is a bet against your own future flexibility. You don't yet know what your packaging will look like in 18 months, so you can't accurately price the risk of promising to match it.
It's also worth testing how hard the ask actually is. MFN requests are frequently a procurement reflex rather than a deal-breaker: if the account represents under 20% of your ARR and isn't a strategic investor, pushing back with the scoped version above resolves the request in most cases without losing the deal.
Frequently asked questions
What is a most-favored-nation clause in a SaaS contract?
It's a contract term guaranteeing a customer that their pricing and terms will be at least as good as those given to any other customer in a comparable deal. It's most common in large enterprise deals and investor-linked agreements.
Can you negotiate an MFN clause instead of removing it entirely?
Yes, and that's usually the better outcome. Scoping it to similarly situated customers, limiting it to list price rather than net price, and time-boxing it to 12-18 months resolves most of the risk while still giving the customer a genuine commitment.
What happens if you breach an MFN clause?
Remedies are whatever the contract specifies, typically a retroactive price adjustment or credit, occasionally paired with a termination right for material breach. This is exactly why the scoping language matters more than whether you agree to a clause at all.
Should an early-stage startup ever agree to an MFN clause?
Only with tight scoping and a short time box. Below roughly $10 million in ARR, your pricing model is still changing too much to safely promise parity against deals you haven't structured yet.
An MFN clause isn't a red flag by itself. An unscoped one is. Run the three-question test before your next redline forces the conversation, and you'll close the deal without quietly signing away control of every pricing decision you haven't made yet.
If you're still building out the rest of your enterprise contract playbook, this clause is worth adding to it before your next big deal lands. If you want a second pair of eyes on a specific clause, that's the kind of contract question we help early-stage SaaS founders work through.