Chris Voss spent his career negotiating with kidnappers and hostage‑takers for the FBI, which sounds like the least relevant possible background for a pre‑sales manual — until you notice that almost none of what he teaches is about price. It's about getting someone to genuinely agree to something, under pressure, without either side pretending the other doesn't have real concerns. That is exactly the shape of a scope negotiation, a POC boundary conversation, or an internal ask to delivery for one more day of estimate — none of which are commercial negotiations, and all of which are negotiations.

Tactical empathy first

Two specific moves do most of the work, and both are simpler than they sound:

• Mirroring — repeat back the last one to three words someone just said, as a question. "...three more configurations?" invites them to keep explaining rather than making you guess what they actually mean. It costs nothing and surfaces more than a direct question usually does.
• Labelling — name the emotion you're observing, without claiming to feel it yourself: "It sounds like this scope change feels non‑negotiable on your end" lands very differently from "I understand you need this." Labelling defuses a stuck position because being accurately seen is disarming in a way agreement isn't.

Both are discovery moves as much as negotiation moves — they extend the same muscle Module 08 already asks for, aimed specifically at the moment someone is pushing back rather than opening up.

The calibrated question, not the flat no

A direct "no" to a scope‑creep request invites an argument. A calibrated question — open, starting with "how" or "what," never "why" (which reads as an accusation) — hands the problem back without a fight: "How am I supposed to add that without moving the delivery date you also need?" The other person now has to solve your constraint, which is a completely different conversation from you defending a position. This is the negotiation‑table version of the exclusions discipline in MSP 04 and the scope‑creep warning in Module 11 — same problem, a better opening line for it.

The accusation audit — get ahead of the objection

Before a hard scope conversation, say the worst thing they might be thinking about you, out loud, before they do: "You're probably thinking we're using this change request to pad the invoice." Naming it removes its power — there's nothing left for them to accuse you of that you haven't already said yourself, more plainly than they would have. This is the proactive twin of the SE Loop in Mod 13+: the Loop rebuilds certainty after an objection lands, the accusation audit tries to make sure the harshest version of it never needs to.

"That's right," not "you're right"

When you summarise a customer's position back to them well enough, they say "that's right" — a sign they feel genuinely understood. "You're right" is usually just a polite way to end the conversation, and it predicts nothing. This matters most exactly where this manual keeps returning to it: getting a stakeholder to actually agree to a written success criterion (Module 11) or a scope exclusion (Template 10), rather than nodding to make the meeting end. If what you get back is "you're right," the agreement probably isn't real yet — go around again.

Shrinking concessions, not linear ones

Voss's Ackerman model for price negotiation — anchor low, concede in shrinking increments, land on a deliberately odd number, throw in something non‑monetary at the very end to signal finality — is an AE's tool, not yours, on commercial terms. The pattern still applies to scope: when a customer keeps asking for "just one more thing," conceding by steadily smaller increments each time (and stating that you're doing it) signals you're approaching a real boundary, in a way that conceding the same amount every time never does. The non‑monetary final concession has a direct pre‑sales equivalent too — throwing in a training session or a documentation extra costs you far less than another engineering week, and often closes the request outright.