The SaaS / Software Procurement Playbook: Twelve Moves Your Software Vendor Has Already Rehearsed
Every software salesperson you meet has been trained. Four to six weeks a year, paid, professional. A meaningful part of it is specifically about negotiating against people like you.
Which means the moves they make in your meeting are not spontaneous. They are rehearsed, they have names, and they have been used successfully a couple of hundred times this year alone.
They work almost entirely because you think they’re spontaneous.
The two that cost most
They go quiet.
You send your counter-proposal and nothing happens. A week. Two. Three. Your emails get short acknowledgements or no reply.
Most buyers get anxious. They start wondering whether they pushed too hard. And then, without the other side having said a single word, they send a follow-up that improves their own position. “We could probably be flexible on the term if that helps.”
You have just negotiated against yourself. They didn’t move. You did. And they now know precisely how much pressure it takes.
That’s the move. Its entire purpose is to test whether your deadline is real.
They nibble at the close.
Everything is agreed. Price, terms, all of it. The paperwork is coming and you’re relieved. Then: “Oh, one small thing. We’d need net thirty rather than net sixty. And could we use your logo on our site?”
Small. Reasonable. You are at the finish line and you do not want to reopen anything.
So you say yes. And that is exactly why it works.
Both counters require doing nothing
For going quiet: do not chase, and do not improve your offer.
Send one short note confirming your position stands and the date you need an answer by. Then wait.
The party who breaks silence with a new number has conceded. If that’s them, you’ve gained something. If it’s you, you’ve paid for the privilege.
And remember what you know about their calendar. If their quarter is closing, silence is far more expensive for them than for you. Your deal is on their pipeline report with a date attached and somebody asks them about it every Monday morning.
For the nibble: every request gets priced, without exception.
The words are: “Happy to look at that. What are you giving me for it?” Said pleasantly. You’re not refusing, you’re establishing that the exchange rate applies right up to signature. Do it once and the nibbling stops.
Ten more, briefly
The high anchor. An opening number well above expectation, framed as standard pricing. Don’t negotiate from it. Reframe onto a different basis: cost per active user, or five-year total cost, or the rate card rather than the discount.
“That’s our best price.” Delivered early, with finality. It’s information about their authority, not their pricing. “I understand that’s the best you can approve. Who approves the next level?”
The exploding deadline. Check their fiscal calendar. If it’s genuine, wait until the final week and ask again. If it isn’t, let it expire and say nothing.
The bundled sweetener. Free modules or extra users instead of a price reduction. It protects the rate card and inflates the baseline your next uplift compounds against. Take it, then repeat the original ask.
Going over your head. Their VP calls your CIO about “the relationship.” Brief your executive before the negotiation starts, not after the call. Their script is one sentence: “I’ve asked [name] to handle the commercial side and I’m supporting their position.”
Deal desk theatre. “I fought hard for you internally.” Thank them and continue. Never treat their internal process as your problem.
“We’ve never done that for anyone.” “I’m not asking for anyone else’s deal. What would it take to do it for us?”
The relationship appeal. “After five years together, I’m surprised we’re here.” Agree warmly and continue. “Five years is exactly why I’d expect you to want this to work for both of us.” Never apologise for negotiating.
The late redline. Contract changes arriving days before signature. Announce the rule at the start: nothing is agreed until everything is agreed, and the contract is part of everything.
Scope expansion at renewal. The renewal arrives bundled with new modules. Separate them explicitly and close the renewal first, or the expansion budget pays for the increase.
The discipline underneath all of it
Plan your concessions before the meeting rather than during it.
Decide what you’ll give, in what order, and what each one has to buy. Write it down, because a concession made in the room without a pre-agreed price is a gift.
Three rules make it work.
Every concession is conditional. Never “we can do three years.” Always “we can do three years if the cap survives into renewal.” The word “if” is the entire discipline.
Concessions get smaller. Eight, four, two, a half signals a floor. Eight, six, five, four signals there is more behind it, and they will keep pushing, correctly.
Never concede twice in a row. If they haven’t moved since your last movement, the next thing out of your mouth is a request, not an offer.
Recent Posts
The SaaS / Software Procurement Playbook: Twelve Moves Your Software Vendor Has Already Rehearsed
Every software salesperson you meet has been trained. Four to six weeks a year, paid, professional. A meaningful part of it is specifically...
The SaaS / Software Procurement Playbook: Your 30% Discount Is Not a Discount
There’s a term in a large share of software agreements that costs organisations six figures, appears on the first page of the order...
The SaaS / Software Procurement Playbook: The Cheapest Bid Was Not the Cheapest Supplier
An RFP is not a document for comparing suppliers. It’s the instrument that sets the terms on which you’ll later negotiate, and most...



