The offer arrives on a Tuesday afternoon. Salary, start date, a line about "let us know if you have any questions". You open a reply, type two sentences, delete them, and close the laptop. Or it is the vendor thread: eleven messages, four people in copy, and a price that has not moved since message three.
Most negotiations now happen at least partly in writing, and most people treat the written part as a slower version of talking. It is not. Text is a different medium with different physics, and if you know what it removes you can decide, each time, whether to type or to call.
What text strips out
A conversation carries three channels: the words, the tone, and the timing. Text keeps the first and deletes the other two.
Tone goes first. "That's not going to work for us" said warmly, with a shrug, is an invitation to keep talking. The same seven words in an email are a wall. The reader supplies the tone from their own mood, and on a bad day the mood is not generous.
Timing goes next. In a room you see the half-second before they answer, the glance at a colleague, the pause after your number. Each is information. In email there is no pause to read, only a gap of hours that could mean anything from "thinking hard" to "on holiday". You lose the flinch, and the flinch is often the most honest thing the other side tells you.
And one thing text adds: permanence. Every sentence you write can be forwarded, quoted back and read by someone you never addressed. That is a feature or a trap, depending on what you wrote.
What email is good for
- Documenting. After a call, the email that says "to confirm what we agreed" is the most valuable message in the thread. Memory drifts; a written summary does not.
- Giving room to think. A written proposal lets the other side read it twice, check with their boss and answer without having to save face in real time. It gives you the same. If a question would put either side on the spot, text is kinder and usually gets a better answer.
- Several parties. One message reaches five people with identical wording. No one can later claim they heard a different version.
- Precision. Scope, dates, exclusions, payment terms. Anything with more than three numbers in it belongs in writing, because nobody retains it from a call.
What email is bad for
Everything that depends on the two channels text removes. Reading a reaction: you cannot. Trading quickly: "If I move on the start date, can you move on the base?" takes ten seconds out loud and three days by email, and the three days give both sides time to harden. Repairing a misunderstanding: a clarification in writing often reads as a correction, and the thread gets colder with each round. Anything with heat in it: a disagreement typed late at night is a disagreement you will reread in the morning.
The pattern is simple. Text is for things that should hold still. Voice is for things that need to move.
The one rule for numbers
Never put in writing a number you have not decided to live with.
Out loud, a number is a move. You can say it, watch the reaction and adjust in the next sentence. In writing, a number is a position. It gets forwarded to the person with the budget, pasted into a spreadsheet and quoted back to you three weeks later: "In your email of the 4th you said 95." The flexibility you meant to signal with it is gone; the figure stays.
This cuts both ways. A low number you typed to seem reasonable becomes your ceiling. A high number you typed to anchor becomes the reason they stopped replying. So before any figure goes into a message, ask one question: if this were the final result, would I sign? If yes, send it. If no, you have two honest options. Send a range whose bottom you would sign, or move the number to a call.
Spoken, a number is a move. Written, it is a position. Only write down positions.
The salary case is the sharpest version. A recruiter writes: "Could you share your expectations?" Typing a single figure hands them your anchor with no reaction to read. Two better answers: "I'd rather talk this through once I understand the scope; do you have fifteen minutes this week?" Or, if they insist on writing: "Based on the role as described, I'm looking at a range of X to Y, depending on the total package." Make sure X is a number you would actually accept.
Moving a stalled thread to a call
You can tell a thread has stalled when the replies get shorter, the gaps get longer, and the same point has been restated twice without a counter. At that stage, another paragraph will not help. The thread needs a voice.
Ask for the call in a way that is easy to accept: short, with a reason, with two concrete slots. Do not explain your position again in the same message; that gives them something to reply to in writing instead.
Three sets of lines you can use as they are.
Asking for a call.
- "I think we're closer than the thread makes it look. Could we take fifteen minutes on Thursday at 10 or Friday at 2 to settle the last points?"
- "This will go faster out loud. Which of these two slots works for you?"
Restating a position without hardening it.
- "To keep us on the same page: our position is 95 for the scope in the attachment. The scope is where I see room, not the price."
- "Where I stand hasn't changed: the start date is fixed on my side, the base is where I'd like to find a way."
Confirming what was agreed.
- "Thanks for the call. To confirm: 95, net 30, delivery by 15 March, scope as attached. If I've missed anything, tell me today and I'll correct it."
- "Summary of where we landed: base X, start 1 April, review after six months. Reply with a yes and I'll send the paperwork."
That last pattern, a summary with a request for a yes, is the quiet workhorse of written negotiation. It turns a vague agreement into a documented one, and a silence into a problem for the other side rather than for you.
At your own table
Before you reply to the next negotiation email, run three checks. Does this message need to hold still or move? Does every number in it pass the "would I sign" test? And has the thread stalled, in which case the right reply is a request for fifteen minutes, not another argument?
The email is the easy half. The call you move it to is where tone and timing come back, and where you have to say "95 is my position" out loud and hold the pause. On Pacct you can rehearse that call against an AI counterpart that pushes back, and the debrief afterwards shows you what you said when the silence got long.
