Skip to content
Institute of Technical Leadership
All blog posts

Commercials

The Most Powerful Thing You Can Do in a Negotiation Is Go Quiet

Principal Architect · 30 July 2026 · 7 min read

The account manager slid the renewal across the table and read the number out loud, because he wanted to watch my face while he did it. Support and licensing for the next year, up 28 percent, no explanation attached. I had a whole speech prepared about budget pressure. I didn't give it. I stared at the sheet for about eight seconds, doing arithmetic, and he filled the gap himself: "There's some flexibility in the professional services line, if the licence number is the problem."

I hadn't asked for anything. The silence asked.

The silence only works because of what you did the week before

Going quiet is not a trick you can borrow. It works when you can afford to wait, and you can only afford to wait if you already know what happens when nobody speaks.

If you walk into that room without having done the preparation, silence isn't pressure. It's you panicking with your mouth shut, and experienced negotiators can tell the difference across a table in about two seconds.

So here's the homework, and it is genuinely an hour's work, not a framework.

What do you actually need, and what are you calling a need because it was in last year's plan? What does the person opposite need, in their world, from their manager, measured on their scorecard? What do you do if you get nothing at all: not "we escalate", but the specific next step with a date and a cost attached? And what evidence do you have that isn't your own opinion restated more confidently?

The walk-away point is the one people skip, and it's the one that makes the room go quiet in a useful way. If you know you can run the current version for another seven months without support, that seven months is sitting in your chest the whole conversation. You don't have to mention it. It changes how long you're willing to sit in an awkward pause, and the other side reads that instantly.

What they say they want is almost never what they need

Two positions collide, everyone digs in, and the meeting turns into a slow argument about a number.

A procurement lead says "we need 15 percent off". Underneath that is usually something much more specific and much easier to satisfy. They've been given a savings target for the quarter. They need something they can put in a report by the 30th. Fifteen percent off the licence line is one way to get that. So is a longer term at flat pricing, or moving two days of consultancy into the deal at no charge, or shifting the payment into the next financial year.

I've watched a three-week standoff over price end in eleven minutes when somebody finally asked "what does this need to look like for you to sign it off internally?" Anything above a certain figure needed a director's approval, and the director was on leave until the following month. The price was fine. The signature was the problem.

Ask the question. Not "can you do better on price", which invites a yes or no, but the one that makes them describe their own constraints out loud. People are surprisingly willing to tell you exactly what they're trapped by, if you sound like you're trying to get them out of it rather than trying to win.

With no authority, evidence is the authority

Most of the negotiating a technical leader does isn't with vendors at all. It's internal, and it's with people who don't report to you and never will. The team who own the deployment pipeline. The security architect who can hold your go-live. The programme director with three projects competing for the same four engineers.

You cannot instruct any of them. Which is why the currency is evidence.

Here's the difference in practice. "We really need those two engineers in October, it's going to be tight otherwise" is a feeling, and feelings get triaged against other people's feelings, usually by seniority. "With the current three engineers we complete 62 of the 90 sites by the freeze date. With five, we complete all 90 with a fortnight of contingency. Here are the last six weeks of completion figures the run rate is based on" is a decision waiting for a signature.

The second one also does something the first can't. It moves the argument off you. You're no longer a person asking for more, you're the person who has laid out what each option produces. If the director decides three engineers is the right answer, fine, that's a legitimate call and they've made it with their eyes open. You've done your job either way.

Bring the working, not the conclusion. People argue with conclusions and engage with arithmetic.

The vendor you'll never see again, and the colleague you see on Thursday

These two are not the same negotiation.

With an external supplier there's a deal, there's a contract, and there is a defensible amount of hard bargaining. You can sit in the silence. You can go to the alternative. It's transactional and both sides know it.

Internally, you are negotiating with someone you'll need again in six weeks, probably at short notice, probably when you're in trouble. Every point you win by grinding somebody down is borrowed against the next favour. I've seen leads win the resourcing argument in March and then discover in July that nobody will take their calls.

So internally, the aim isn't to win. It's to be the person whose asks are trusted. That means saying "I can live with three engineers if I can drop the reporting sites to the second phase" in the room, rather than agreeing in the meeting and escalating afterwards. It means being visibly willing to take the smaller version of what you wanted. And it means that when you do say "this one I can't move on", it lands, because you haven't said it five times already this quarter.

A worked example: the storage renewal at a container port

Infrastructure lead of a 24-person service team at a container port operator, first year in the role, handed a storage support renewal that came in 30 percent up on the previous year. No budget for it. Standard move is to go in and ask for a discount, which is asking permission to be told no.

What she did instead took about two hours. She pulled the actual support tickets for the previous eighteen months: eleven cases, two of them severity one, average response well inside the contracted window. She checked what a competitor's migration would cost in real terms, including the six weekends of engineer time, and got that to a rough number. And she worked out that the arrays had 22 months of useful life left, which meant a one-year extension was genuinely all she needed.

Then she made one request in writing before the meeting: flat renewal for twelve months, and in exchange a commitment to run the refresh evaluation with them early the following year.

In the meeting, the account manager explained why 30 percent was unavoidable. She said "I understand, and I can't sign that". Then she stopped talking.

He came back four days later at a 4 percent increase with the evaluation commitment written in. Not because she was aggressive. Because she'd spent two hours finding out that her alternative was survivable, and he could hear that in how comfortable she was with the pause.

Monday morning

Take whatever negotiation you've got open right now, the renewal, the resourcing ask, the scope conversation with the client, and write one sentence at the top of a page: "If we get nothing at all, what we do instead is ______, by ______, and it costs us ______."

If you can't complete that sentence with specifics, you're not ready to be in the room, and you should spend Monday filling it in rather than rehearsing arguments. If you can complete it, you've just bought yourself the right to sit in a silence and let the other side speak first.

Principal Architect

Founder of the Institute of Technical Leadership, writing from two decades of technical delivery.

This is the kind of thing we teach properly in Foundations of Technical Leadership.

Foundations of Technical Leadership is 25 self-paced lessons, with templates you can use the same week.