Software Negotiations: Do You Know How to Say NO?

Short answer: saying “no” well is a core software-negotiation skill. The move is William Ury’s “Yes, No, Yes”: name the interest behind your no, deliver the no clearly, then hand the other side a path to yes.

This is fundamental in any software negotiation, and something you have to master. William Ury of the Harvard Program on Negotiation wrote a whole book on how to say “no.” It is one of the most-used words in the language, so learning to use it well in a software or SaaS negotiation is worth the effort.

The Yes, No, Yes Framework.

1. Saying “no” to something means you are saying “yes” to something else. There is always a reason for the no, and that reason is what you are protecting.
2. Express your “yes,” then deliver your “no.”
3. Propose a “yes,” a path forward.

An Example in a Software/SaaS Negotiation.

1. “Your company is not making a real long-term commitment to our technology” is your internal “yes,” the reason you must say no.
2. “So we cannot give you the discount you asked for” is your “no.”
3. “However, if we can agree on a long-term commitment, we can get there on the discount. What matters more to your company?” is the proposed “yes.”

Why It Works.

The “Yes, No, Yes” structure lets you hold your position without blowing up the relationship. You acknowledge a legitimate interest, decline clearly, and immediately hand the other side a path forward, so your “no” reads as principled rather than personal. Contrast that with the three poor ways people handle hard issues: accommodating (saying yes when you should say no), attacking (saying no badly), and avoiding (saying nothing at all). The framework also pairs with the rest of the negotiation toolkit, listening for the other side’s real interest first, which is the same idea behind what a software company can learn from an FBI negotiator and why education drives software negotiations.

Where Vendors Need This Most.

In my experience the “Yes, No, Yes” move earns its keep on a handful of recurring vendor asks. Uncapped liability is the big one. The customer wants the cap removed; your yes behind the no is that the business cannot take on bet-the-company risk for a single deal, your no is that the cap stays, and your path forward is a negotiated carve-out or a higher cap tied to higher fees. Broad indemnities are next. You are protecting your ability to defend only what you actually control, so the no is to open-ended indemnification, and the yes is a tight, defined indemnity for IP infringement or your own breach. Source-code escrow, unlimited audit rights, and most-favored-pricing follow the same pattern: name what you are protecting, decline the broad version, and offer the narrow version that still meets the customer’s real need. The discipline is to never deliver the middle no by itself. A bare no on liability sounds like stubbornness; the same no wrapped in a reason and a trade sounds like a deal you are trying to close. Decide your three yeses before the call, so when the pressure comes you are reaching for a prepared answer instead of improvising one.

Frequently Asked Questions.

What is the “Yes, No, Yes” method? Name the interest you are protecting (the yes behind the no), state your no clearly, then offer a constructive path forward (a second yes), so the refusal is principled rather than personal.

Why not just say no directly? A bare no invites a fight or damages the relationship. Anchoring it to a legitimate interest and offering a path forward holds your position while keeping the deal alive.

Where does this apply in software deals? Anywhere you must decline, discounts, scope, custom terms, indemnities. Tie the no to your model (for example, price follows commitment) and propose the trade that would get you to yes.

Use this in your next software or SaaS negotiation. I hope this helps.

For the broader playbook on the customer side of every deal, see Contract or Policy? When Software Companies Should Use Each, and on the human dimension see SaaS Contract Negotiations Are Not All About the Software.

Knowing when to hold your no also means knowing when a software or SaaS deal is actually done, and if you want to sharpen the skill itself, here is where to go for software negotiation training.

“The Power of a Positive No” on Amazon

Disclaimer:

This post is for informational and educational purposes only, and is not legal advice. You should hire an attorney if you need legal advice, which should be provided only after review of all relevant facts and applicable law.