petrogurcak/written-negotiation

Written Negotiation — Email + De-Escalation Async

Overview

This skill covers the written/async layer of negotiation. Where tactical-empathy delivers Voss's verbal moves in real time and reading-people reads the body, this skill handles the medium that hosts most modern business negotiations — email, Slack/Teams DM, contract markup threads, formal letters, async deal closing. The frame is Voss's tactical empathy adapted to writing, supplemented by Mark Goulston's Just Listen for async de-escalation, plus CZ-specific written norms (vykání, paper trust, indirect refusal idioms). For full Voss email playbook including the "Email Magic" line, paraphrased mirroring rules, and the 5 scenario templates, see ../references/voss-email-adaptations.md. This skill assumes you have read that file before drafting any high-stakes written negotiation.

The non-negotiable principle: voice and text are different mediums and the methodology must adapt. Voss is explicit on this — what works at the table doesn't work the same way in an inbox:

"It's very difficult to find Black Swans with email for the simple reason that, even if you knock your counterpart off their moorings with great labels and calibrated questions, email gives them too much time to think and re-center themselves to avoid revealing too much. In addition, email doesn't allow for tone-of-voice effects, and it doesn't let you read the nonverbal parts of your counterpart's response."

— Voss, Never Split the Difference

The trade-offs going from voice to text:

You lose:

• Tone — late-night-FM-DJ voice doesn't translate. The same words read flatter, more aggressive, more ambiguous.
• Real-time silence — Voss's 4-second pause after a mirror is impossible in writing. The counterpart reads at their own pace.
• Body co-signal — you can't read pacifiers, lip compress, neck touches in response to your number.
• Mirror-neuron empathy — Fisher/Ury & Patton: "the lack of audio and visual cues in texts and email make it much harder to hear or interpret the emotional undertones of communication, which can feed our tendency to hear the worst." Both sides hear worst-case interpretations of ambiguity.

You gain:

• Composition time — you can label, mirror, re-read, edit, sleep on it. Voss's first instinct is rarely his best take. Your tenth-draft reply can be.
• Permanent record — paper trail for legal, project management, future re-negotiation. CZ business culture trusts paper above verbal.
• Counterpart re-reads — each pass through your labeling deepens the empathy effect. A well-crafted email lands twice — once when read, once when re-read by the recipient before responding.
• Pre-staging — you can deploy your structure (BATNA, ZOPA anchor, multi-issue trade) in a single complete message rather than improvising sequentially.

CZ context. The Czech business norm is that paper trumps verbal. A handshake or "máme dohodu" at lunch is the start of negotiation, not the close. The closing move is the written confirmation. This means:

• Every verbal agreement requires written follow-up within 24-48 hours, or it didn't happen.
• The party that controls the written record controls the precedent. If you don't summarize the meeting first, the counterpart will, and their version becomes canonical.
• Aggression in writing is read more harshly than aggression in voice. A heated tone over coffee is forgotten by Friday; a heated email is forwarded, screenshotted, retained.

This skill operationalizes all of that. Everything below is designed to be copy-pasted into your next reply, then adapted to the specific situation.

---

When to use

Use this skill when the user is drafting, responding to, or planning written/async negotiation. Concretely:

• Klient sent an angry email — refund demand, complaint about deliverable, scope dispute. You need to respond within 24 hours and cannot afford to escalate.
• Partner / vendor / klient asked for a discount or scope reduction by email mid-deal.
• Vendor missed a deadline and emailed an explanation; you need to respond firmly without blowing up the relationship.
• Contract markup came back with red-line changes you need to push back on.
• Follow-up after a silent meeting — counterpart went quiet, you need a single message that re-opens dialogue.
• Slack/Teams DM with a tense colleague or cross-team partner — territorial dispute, delivery escalation, blame email forwarded into the channel.
• Cold outreach to a high-status counterpart where the first message decides whether you get a second.
• Final closing email after a verbal agreement — the written confirmation that locks the deal.
• Termination / exit communication — letting a vendor go, ending a klient relationship, declining a partnership.
• Any high-stakes async message where you'd benefit from drafting, sleeping on it, then sending tomorrow morning.

When NOT to use

• Live verbal phrasing ("co řekl při hovoru?", "co teď odpovědět při schůzce?") — use tactical-empathy (Voss). This skill provides written templates; that one provides spoken language.
• Body language reading — use reading-people (Navarro). Cannot read body in writing.
• Strategic structural prep (BATNA, ZOPA math, multi-issue trade analysis, walk-away point) — use batna-strategy. You cannot write your way out of a structurally weak position; the math must be done before the keyboard.
• High-emotion live conflict (cofounder split, firing in person, family business dispute happening now) — use emotional-conflict. Written de-escalation works for cooled situations; live emotional conflict needs the full Goulston Persuasion Cycle delivered in person.
• Crisis / abuse / clinical situations — refer to professionals (CZ helplines: 112, 116 006, 116 111, 116 123). This skill is not therapy or crisis support.
• Manipulating someone weaker than you (dependent klient, unsophisticated counterpart, vulnerable family member). Voss methodology assumes adversarial-cooperative business contexts where both sides are competent. Using it for dominance is unethical and backfires when detected — and written records make detection easier.
• When face-to-face is genuinely available and the matter is emotional. Fisher/Ury are explicit: "difficult conversations involving emotions or relationship issues are best pursued face-to-face, if at all possible, and definitely not by email or text." If the relationship matters and the meeting is feasible, escalate the medium up before drafting the email.

---

Diagnosis (read incoming first)

Before you write a single word of reply, diagnose the incoming message. Most bad reply emails fail not at the writing stage but at the reading stage — the responder rushed past what the counterpart actually said and answered the wrong message. The 3-step diagnosis:

Step 1 — Actual ask vs surface ask

The surface ask is what the email literally says. The actual ask is what the counterpart needs to feel resolved. They are often different. A klient who writes "Chci 50% refund" usually doesn't actually need 50% — they need to feel that their frustration was heard, that the failure was acknowledged, and that something concrete will change. The 50% is a position; the actual interest is dignity + assurance.

Ask of every incoming message:

• What is the literal text request? (= surface ask)
• What outcome would make them write a follow-up email saying "thank you, that resolved it"? (= actual ask)
• What's the gap between the two? That gap is your trade space.

Step 2 — Emotion signaling

What emotion does the message carry? Look for:

• Frustration — short sentences, exclamation marks, "konečně", "už po několikáté", "očekával jsem", "nesplnili jste". They feel ignored or wronged.
• Fear / anxiety — vague language, hedging, escape clauses, "kdybyste náhodou", "obáváme se", CC'ing more people. They feel exposed or out of control.
• Status threat — formality shift (Vy with cold tone), titles, "z mé pozice", "naše společnost vyžaduje". They feel disrespected and are armouring.
• Resignation — long delays, single-line replies, "uvidíme", "nějak to dořešíme". They've checked out and the deal is dying.
• Anger — ALL-CAPS, accusatory language, "vy jste", "neschopnost", absolute words ("vždy", "nikdy"). They are flooded.

The emotion tells you which BCSM stage to enter. If frustration / anger → Active Listening + Empathy (mirror, label) before anything else. If resignation → re-warm via labeling + No-oriented question. If fear → reassurance through transparency + concrete plan, not "everything will be fine" platitudes.

Step 3 — Cialdini principle being deployed against you

Is one of Cialdini's 7 principles being used to pressure you?

• Reciprocity — "Po tom všem, co jsme spolu udělali..." (manufactured debt)
• Commitment — "Vy jste mi v hovoru slíbili..." (foot-in-the-door extraction, often misremembered)
• Social proof — "Jiní dodavatelé v podobné situaci..." (peer pressure, often vague)
• Authority — Forwarded email from CEO / lawyer (borrowed authority)
• Liking — "Vždycky jsme si rozuměli, tak..." (weaponized friendship)
• Scarcity — "Buď to vyřešíme do pátku, nebo..." (manufactured deadline)
• Unity — "Jako kolegové z oboru bychom měli..." (fake tribal appeal)

Detection doesn't mean you accuse them of using a tactic. It means you don't fall for it. You acknowledge the surface (label the pressure), then bring the conversation back to objective criteria.

Concrete example — diagnosing an angry klient email

Incoming (real-world condensed):

"Dobrý den, jsem dost zklamaný z toho, jak projekt dopadl. Máme tam bug, který náš tým objevil hned po nasazení a který jsem vám hlásil minulý týden. Reakce z vaší strany je pomalá. Tohle není to, co jsme si dohodli — investovali jsme do toho 200k a teď řešíme problémy. Žádám 50% refund. Pokud do pátku nebude jasné řešení, budeme se obracet na právníka."

Diagnosis:

• Surface ask: 50% refund (100k Kč).
• Actual ask: (a) Acknowledgement that the failure happened. (b) Concrete plan for the bug. (c) Some financial gesture proportional to actual impact, not the anchor he threw. (d) Restored sense that he can trust the relationship going forward.
• Emotion: Frustration (primary) + status threat ("budeme se obracet na právníka" = he's signaling power). NOT anger-flooded — sentences are coherent, structured. He's deliberate, not emotional. This is a position-anchored opening move, not an outburst.
• Cialdini: Scarcity (Friday deadline — likely real but bears verification) + Authority (lawyer threat — borrowed). Note that lawyer mention almost always means he hasn't talked to a lawyer yet; if he had, the lawyer would write.

Implication for reply: Mirror + label first (defuse frustration, show you read it), then calibrated question (surface what would actually make him whole), then anchor (palm-down on the 50%, palm-up on alternatives), then No-oriented soft close (give him control). Do NOT lead with refusal of the 50%; that triggers escalation. Do NOT lead with offer of a different number; that anchors the negotiation at his frame.

---

Subject line tactics

The subject line is read before the body. It pre-frames how the body will be received. Most negotiation emails fail at the subject line — they trigger defense before the recipient reaches paragraph one.

DO — labeling-style subjects

Open without forcing a position. The subject acknowledges the topic but doesn't pre-commit to an answer. Counterpart can engage without losing face on either side.

Examples:

"Question about the Q3 timeline"
"Concern with proposal section 4"
"Following up on yesterday's meeting"
"Vaše zpětná vazba k projektu [name]"
"K vaší žádosti o úpravu ceny"
"Dotaz k smlouvě, klauzule 4.2"
"Vrátím se k naší středeční diskusi"

Each one says "I want to talk about X" without saying "and the answer is Y." That gives the counterpart room to reply collaboratively rather than defensively.

DON'T — solution-promising subjects

These trigger defensive posture before line one of the body is read.

Examples:

"Solution for Q3 issue"        ← presumes problem exists, presumes you can solve unilaterally
"Re: Final answer on pricing"   ← shuts dialogue
"Approval needed by Friday"     ← creates pressure (Cialdini scarcity), reads as ultimatum
"Důležité — okamžitá pozornost" ← panic-framing, escalates emotion
"Nesouhlasím s vašimi podmínkami" ← position-locked, no exit
"Refund policy clarification"   ← framing as policy = bureaucratic defense

The pattern: any subject line that contains a position, a deadline, or a verdict will activate the limbic threat response before the body has a chance.

Special cases

• Re-engaging after silence — "Vzdal jste to s [project]?" — Voss's Email Magic line as subject. Aggressive opening, but the entire point is to provoke a No-response. Use only when traditional follow-ups have failed.
• Difficult news (cancellation, decline, exit) — "Update k naší spolupráci" — neutral, opens the door without pre-loading the news. Body delivers the substance.
• Time-sensitive but legitimate — "Rozhodnutí potřebné do [datum] — k vašemu zvážení" — real scarcity, but framed as "for your consideration" not "you must answer."

---

Voss adapted templates

For full inline reference of all Voss techniques translated to written form, see ../references/voss-email-adaptations.md. Inline summary follows.

Mirror as paraphrase (NOT literal quote)

Live mirror = repeat last 1-3 words of what they just said in inquisitive tone. In writing, literal quoting reads legalistic and hostile. Adapted form: paraphrase their key point at the opening of your reply, signaling you read the message in full and absorbed the central concern.

DO — paraphrase as opener:

> Their incoming: "We can't accept those terms because of budget constraints."
> Your reply opener: "Z vaší zprávy chápu, že hlavní překážka je rozpočet — 
> a že současná struktura nesedí. Chci se ujistit, že tomu rozumím správně 
> než navrhnu úpravu."

DON'T — literal quote:

> Your reply opener: "Re vaše vyjádření 'we can't accept those terms'..."

Literal quoting reads as legalistic preparation for dispute. It signals "I'm building a record against you" rather than "I heard you."

Labeling templates

The "It seems / It sounds / It looks" formula translates intact to writing. Same "no I" rule as in voice — labels open with the situation, not with your perception.

Czech templates:

| Template | When to use | |----------|-------------| | "Vypadá to že…" | Generic emotion label, neutral hypothesis frame | | "Zní to jako že…" | When the emotion came through their text (frustration, fatigue) | | "Mám pocit že…" | Tentative — invites correction, lower amplitude | | "Asi vás to…" | Empathetic, even lower amplitude — for fragile situations | | "Z vaší zprávy chápu, že…" | Cool paraphrase variant — best for legal / formal contexts |

English templates:

| Template | When to use | |----------|-------------| | "It seems like…" | Generic emotion label | | "It sounds like…" | When emotion came through their text | | "It looks like…" | When you're inferring from action (delays, CC patterns, vague timeline) | | "I'm guessing this feels…" | Tentative — invites correction |

Critical rule. Labels invite correction. If they correct ("ne, není to tak že nesedí timing — sedí, ale chybí vám jeden výstup") — good. You've started the conversation, and they revealed the actual issue, which the surface ask had hidden.

Calibrated questions in writing

Calibrated questions work better in writing than live, because the counterpart has time to construct a thoughtful answer. In voice, "Co by muselo být pravda, aby X fungovalo?" can sound rhetorical or evasive. In email, the counterpart reads it twice, considers, and replies with substance.

Templates (CZ):

"Co konkrétně by mělo být součástí, aby vám to fungovalo?"
"Co by muselo být pravda, aby [návrh] dával smysl?"
"Co je v tomhle pro vás nejdůležitější?"
"Jaký by byl pro vás ideální výsledek?"
"Pomozte mi pochopit, jak jste přišli k [číslu / požadavku]."
"Co tomu brání ze strany vašeho týmu?"
"Co by se ve scope změnilo, kdybychom se posunuli na [nové číslo]?"
"Jak to mám udělat, když [vaše constraint]?"  [killer Q]
"Která část je pro vás nejdůležitější — [A] nebo [B]?"
"Co se ve vaší situaci změnilo od posledního hovoru?"

Templates (EN):

"What would need to be true for [proposal] to work?"
"What matters most to you in this?"
"What would the ideal outcome look like?"
"Help me understand how you arrived at [number / requirement]."
"What's standing in the way on your side?"
"How am I supposed to do that, given [your constraint]?"  [killer Q]
"Which part is most important — A or B?"
"What's changed on your end since we last spoke?"
"What would need to be true for us to bridge the gap?"
"What does success look like from your seat?"

The killer Q — "Jak to mám udělat?" / "How am I supposed to do that?" — works especially well in writing. Voss's example of using it via email (the consultant's payment dispute, where it was step 6 of his 8-step script) ended with full payment. The mechanism in text is identical to voice: it's a non-aggressive way of saying No while inviting the counterpart to participate in solving your dilemma.

No-oriented soft close

Yes-questions feel pressuring in text — they read as forcing a commit. No-questions feel safe and give the counterpart agency. Voss's framing: "the 'No' answer the email demands offers the other party the feeling of safety and the illusion of control."

CZ table:

| Yes-version (avoid) | No-version (use) | |---------------------|-------------------| | "Souhlasíte?" | "Je něco, co vám tu chybí?" | | "Můžeme se posunout?" | "Je nějaký důvod, proč bychom se neměli posunout?" | | "Funguje vám pátek?" | "Je pátek špatný den?" | | "Pošlete mi to?" | "Bylo by problém mi to poslat?" | | "Vyhovuje vám to?" | "Je v tomhle něco, co nesedí?" |

EN table:

| Yes-version (avoid) | No-version (use) | |---------------------|-------------------| | "Are you available Friday?" | "Is Friday a bad time?" | | "Do you agree?" | "Have I missed anything important?" | | "Will this work?" | "Is there something here that doesn't work for you?" | | "Can we proceed?" | "Is there a reason not to move forward?" | | "Does this make sense?" | "Is there anything here that doesn't make sense?" |

The Email Magic line. Voss's most-cited one-line email — for re-engaging a counterpart who has gone silent after multiple polite follow-ups:

CZ: "Vzdal jste to s [tímto projektem]?"

EN: "Have you given up on [this project]?"

Use sparingly — once per relationship, when normal follow-ups have failed and the deal is dying. The mechanism: it forces a No answer, which feels safe to the counterpart, while activating loss aversion ("the implicit threat that you will walk away on your own terms"). Voss reports near-100% reply rate within 24 hours, almost always with the structure "No, we haven't given up — we've just been [reason]..." which gives you back a real timeline.

---

Anchor positioning in writing

How you position your anchor determines whether it lands or triggers defense. Three frames, each with its own use case:

Palm-up framing

Asking, openness, exploration. Use when you don't yet have leverage, when the relationship matters, when you want to surface the counterpart's interests before stating yours.

"Rád bych slyšel váš pohled na…"
"Zajímalo by mě, jak vidíte…"
"Co byste navrhovali jako spravedlivé řešení?"
"I'd value your perspective on…"
"Curious how you see X."
"What's your read on…"

Used too much, palm-up reads as supplicant — like you have no position of your own. Combine with at least one palm-down or constraint statement per email so you don't sound like a beggar.

Palm-down framing

Asserting, declaring, anchoring. Use for non-negotiables, after rapport is established, when you need to state a position with weight.

"Naše hranice je [X] z těchto důvodů: A, B, C."
"Pod [Y] nemůžeme jít, protože [konkrétní impact]."
"Z naší strany je [X] minimum, které dává smysl."
"Our threshold is X for these reasons: A, B, C."
"We can't move below Y because Z."

Palm-down is Fisher/Ury's "objective criteria" delivered with confidence. It works only when the criteria are real. If you say "naše hranice je X" without giving the reason, you sound stubborn. If you say "naše hranice je X protože hodina senior dev v Praze stojí 1 800-2 200 Kč podle Pařízek-Stahl 2025 reportu", you sound principled.

Constraint statement

Not "no", but "this is the box". Use when you want to signal hard limits while preserving flexibility on other dimensions. The most powerful written-negotiation move — it locks one variable while opening trade space on the others.

"Mám pevný termín do pátku — v rámci toho jsem flexibilní na scope."
"Cena je pro mě fixní, ale můžeme upravit timeline nebo deliverables."
"Z mé strany je rozpočet hard, ale jsem otevřený diskutovat scope."
"I have a hard constraint of X by Friday — within that, I'm flexible on…"
"Price is fixed on my side, but we can adjust timeline or deliverables."
"My budget is hard, but I'm open on scope and timeline."

Constraint statement signals: I'm not stubborn, I have one real limit, and within that I'll trade. It invites multi-issue negotiation rather than position-haggling on a single number.

---

Red flags in incoming written communication

Patterns that tell you something underneath the surface text. Recognizing them prevents wrong responses.

| Signal | What it means | What to do (don't escalate) | |--------|---------------|------------------------------| | ALL-CAPS in any sentence | Emotional flooding — limbic system has hijacked the cortex | Reply slowly, lower energy than them. Do NOT match. Wait 4-12 hours before sending. | | Long delay + cold tone | Flight — they're disengaging, deal is dying | Re-warm with empathy, not pressure. Voss Email Magic line if it's been 14+ days. | | CC'ing additional people (manager, colleagues, lawyer) | Territorial display, often a status play | Address it directly: "Vidím, že do toho přibyl(a) [name] — pomohlo by, kdybychom srovnali pohledy přímo s vámi než se rozhodne, koho zapojit dál?" | | Vague timeline ("brzy", "ASAP", "co nejdříve") | ZOPA hidden — they don't want to commit to a real deadline | Surface it: "Co konkrétně driveruje tu urgenci? Chci se ujistit, že trefíme váš skutečný termín." | | Sudden formality shift (Vy s chladným tónem po dřívější vřelosti) | Professional distance signal — they're armouring | Match the formality. Don't try to recover warmth via casualness — that reads as oblivious or manipulative. Re-establish substance first, warmth later. | | Single-line replies after long thread | Either annoyed or busy — ambiguous | Calibrated question to disambiguate: "Mám pocit, že jsem se rozepsal — co by od vás potřebovalo být kratší/jasnější, ať se posuneme dál?" | | Forwarded email as their reply (no original message) | Authority play — they're showing you they have backup | Acknowledge the additional party in your reply, address substance. Don't be pulled into the chain-of-command frame. | | Past deadline brought up unprompted | Setting up a future leverage play | Address it now, not later: "Vidím že jste zmínili [X termín z minulosti] — co konkrétně z toho je teď živé?" | | Switching between formality registers in one email | Drafted under stress, possibly multiple sittings | Don't read into individual word choices — read the whole. Reply to the substance, not the tone inconsistencies. | | "Just to clarify…", "as we discussed…", "for the record…" | They're building a paper record — anticipating dispute | Take it seriously. Reply with equal precision; don't be sloppy with dates, numbers, commitments. |

---

5 scenario templates

Five common scenarios with full CZ email templates. Copy, then adapt to the specific names, numbers, and history. For additional context per scenario including the underlying Voss move structure, see ../references/voss-email-adaptations.md.

Scenario 1 — Angry klient demanding refund

Klient sent an upset email after a deliverable failed expectations. They threw a high anchor (50% refund, big number) and a deadline (Friday or lawyer). You need to defuse without conceding the anchor.

Subject: Vaše zpětná vazba k projektu [name]

Dobrý den [name],

děkuji za vaši zprávu — i když je nepříjemné ji číst, oceňuji, že jste 
napsali přímo a rovnou. Beru to vážně.

[MIRROR / paraphrase]
Z vaší zprávy chápu, že [project] nesplnil očekávání ve [konkrétní 
oblasti, kterou v emailu zmínili] — a že jste zároveň investovali čas, 
peníze i důvěru, a výsledek tomu zatím neodpovídá.

[LABEL]
Zní to jako že to bylo dost frustrující — a že dnešní stav neodpovídá 
tomu, co jsme si na začátku domluvili. To není pocit, který chci, abyste 
z naší spolupráce měli.

[CALIBRATED QUESTION — surface actual interest]
Pomozte mi prosím pochopit, co konkrétně by se muselo stát, aby z 
vašeho pohledu byla situace férově dořešená? Jestli se mohu zeptat, 
jak jste přišli ke konkrétní výši, kterou navrhujete — pomohlo by mi 
to pochopit, jak to vidíte z vaší strany.

[ANCHOR — palm-down on the 50%, palm-up on alternative]
Rád bych s vámi našel řešení, které bude férové pro obě strany. Z naší 
strany je 50% refund výrazně mimo rámec toho, co odpovídá skutečnému 
dopadu — ne proto, že chyba není naše, ale proto, že proporční náprava 
vypadá jinak. Předtím než navrhnu konkrétní řešení, ale chci si být 
jistý, že rozumím úplnému obrazu.

[NO-ORIENTED SOFT CLOSE]
Bylo by špatné, kdybychom si dali 20 minut hovor zítra nebo v pátek 
ráno, ať to projdeme přímo? Pokud telefon není teď ideální, mohu 
poslat strukturovaný návrh emailem nejpozději do středy.

S pozdravem,
[name]

Why this works. The label defuses frustration before any substance is discussed. The calibrated question surfaces both his actual interest (what would resolve it) and his anchoring logic (how he got to 50%) — both of which are likely soft. The palm-down anchor on 50% is paired with a palm-up offer of dialogue, not refusal. The No-oriented close gives him control. The two options at the end (call or written proposal) prevent silent stalling.

Scenario 2 — Partner asking for discount mid-deal

Partner / klient is mid-project and writes asking for a price reduction. Often triggered by their own internal pressure (CFO, layoffs, budget cut). You want to preserve the relationship but not concede the number.

Subject: K vaší žádosti o úpravu ceny

Dobrý den [name],

děkuji za přímou zprávu — vážím si toho, že jste to napsali otevřeně 
spíš než to tahali do nepříjemného hovoru.

[MIRROR]
Z vaší zprávy chápu, že žádáte o snížení smluvní ceny o [X %] / na 
částku [Y] kvůli [důvod, který v emailu zmínili]. Beru to jako vážnou 
žádost a chci ji zvážit férově.

[LABEL]
Vypadá to že tlak na rozpočet je teď silnější než když jsme začínali — 
to se v projektech stává a chápu, že to není rozhodnutí, které byste 
psali ze srdce. Z mé strany žádný osobní problém s tématem není.

[CALIBRATED QUESTION — interest, not position]
Co se konkrétně na vaší straně změnilo od posledního hovoru, že jsme 
najednou na jiném čísle? A která část naší spolupráce je pro vás v 
této chvíli nejdůležitější — chci se ujistit, že případná úprava 
zachová to, co je pro vás kritické.

[CONSTRAINT STATEMENT]
Z naší strany máme hranici, pod kterou nemůžeme jít — fixní náklady na 
[konkrétní položka, např. senior tým + nástroje] tvoří [Z %] z původní 
ceny, takže snížení o víc než [malé X] by znamenalo, že by projekt 
přestal být udržitelný a kvalita by tím utrpěla. To by nebylo dobré 
pro nikoho z nás.

[OPTIONS — multi-issue trade]
Mám dvě varianty, které vám mohu navrhnout:
- (A) Upravený scope za novou cenu — vyřadíme [konkrétní deliverable], 
      cena padne na [částka], harmonogram zůstává stejný.
- (B) Původní scope s prodlouženým harmonogramem — rozložíme platby na 
      [N] měsíců místo [původní], cash-flow je pro vás příznivější.

[NO-ORIENTED CLOSE]
Sedlo by vám sdílet, který směr vám dává větší smysl? Pokud žádný z 
těch dvou, rád si poslechnu, co konkrétně by potřebovalo být jinak.

S pozdravem,
[name]

Why this works. The label normalizes ("to se v projektech stává") so they don't feel judged for asking. The calibrated question separates position (lower price) from interest (lower fixed cost, cash-flow timing, fewer line items on Q4 P&L). The constraint statement uses objective criteria (fixed cost percentage) rather than "to je moje cena". The two options open multi-issue trade space — almost always one of them fits the actual interest better than a flat price cut.

Scenario 3 — Vendor missing deadline

Vendor (subdodavatel, freelancer, contractor) writes admitting they will miss a deadline. You need to push back firmly without burning the relationship — vendors who are protected when they slip become loyal; vendors who are punished become defensive.

Subject: Status update k [project / deadline]

Dobrý den [name],

děkuji, že jste napsali rovnou — je vždycky lepší vědět včas než pozdě.

[MIRROR / paraphrase]
Z vaší zprávy chápu, že termín [konkrétní deadline] se posune kvůli 
[důvod, který v emailu zmínili] — a že odhadujete reálný termín někdy 
kolem [pokud uvedli, jinak vynech].

[LABEL]
Tlak na vás teď musí být dost — souběh [okolnosti, např. nemoc v týmu, 
dva projekty paralelně] není snadná situace a vidím, že se snažíte to 
řešit transparentně. To si vážím.

[CALIBRATED QUESTION]
Pomozte mi prosím pochopit dvě věci:
- Co konkrétně teď drží termín nejvíc? (Chci vědět, jestli to je 
  blocker, který se uvolní, nebo strukturální problém.)
- Co by potřebovalo být pravda, aby revidovaný termín byl realistický 
  a ne další optimismus?

[CONSTRAINT — palm-down]
Z mé strany mám fixní deadline [datum] kvůli [downstream důvod — např. 
launch klientovi, regulace, smluvní pokuta]. Pod tento termín se 
nemůžu pohnout, protože by to znamenalo [konkrétní impact — penále, 
ztráta klienta, atd.].

[OPTIONS — preserve relationship + protect downstream]
Mohu navrhnout dvě varianty:
- (A) Upravený scope za původní termín — určíme spolu, co lze vyřadit 
      z první fáze a co odsunout do follow-up dodávky.
- (B) Zachovaný scope, ale do [konkrétní datum, ne "co nejdřív"], a 
      mezitím vám pomůžu [konkrétní podpora — přidám zdroje, vyjasním 
      requirements, atd.].

[NO-ORIENTED CLOSE]
Bylo by problém vyhradit si zítra 30 min na hovor, ať to spolu 
projdeme rychle a rozhodneme se? Po hovoru bych rád poslal stručný 
zápis s tím, co jsme dohodli, abychom oba měli to samé.

S pozdravem,
[name]

Why this works. The label preserves dignity ("snažíte se to řešit transparentně"). The two calibrated questions distinguish blocker types (resolvable vs structural) — critical for assessing real risk. The constraint is grounded in downstream consequence (objective criteria), not personal preference. The options give them a face-saving path (scope reduction is rarely held against a vendor; missed deadlines are). The "stručný zápis" closing line is the CZ paper-trail discipline — verbal alone won't lock the new commitment.

Scenario 4 — Contract markup pushback

Counterpart sent back a smlouva with red-line changes that you can't accept (klauzule on liability, IP, exclusivity, payment terms). You need to push back legally and commercially without escalating to a lawyer-driven exchange.

Subject: Vaše komentáře ke smlouvě [project name]

Dobrý den [name],

děkuji za podrobné komentáře ke smlouvě — vidím, že jste tomu věnovali 
čas, což oceňuji. Prošel jsem všechny vaše návrhy a chci na ně 
odpovědět věcně.

[MIRROR — surface the actual concerns]
Z vašich komentářů vyplývá, že hlavní obavy jsou kolem [klauzule X — 
např. "limitace odpovědnosti"] a [klauzule Y — např. "exkluzivita"]. 
Ostatní úpravy beru jako technické a s těmi nemám problém.

[LABEL — per klauzule]
Vypadá to že [klauzule X] je pro vás citlivá — zní to jako že vás 
znepokojuje [konkrétní implikace, např. "scénář, kdy by limitace 
ošetřila i naše hrubé pochybení"]. Pokud rozumím dobře, jádro vaší 
obavy je [parafráze v jejich slovech, ne právním jazyce].

[CALIBRATED QUESTION]
Pomozte mi prosím pochopit dva body:
- Co konkrétně by ta klauzule v nejhorším scénáři pro vás znamenala? 
  (Chci se ujistit, že rozumím skutečné obavě, ne jen formulaci.)
- Která z těch dvou klauzulí je pro vás důležitější — pokud bych měl 
  na jedné víc ustoupit, na které?

[ANCHOR — palm-up on framing, palm-down on existence]
Z naší strany [klauzule X] existuje, protože [důvod — např. 
"odpovídá to běžné praxi v IT projektech a chrání nás před nároky 
z věcí mimo naši kontrolu, jako třetí strany v dodavatelském řetězci"]. 
To je důvod, který nemůžeme úplně opustit, ale jsme otevřeni hledat 
formulaci, která řeší vaši obavu, aniž by ten důvod zrušila.

[OPTIONS — alternative phrasings, not removal]
Mohu navrhnout 2 alternativní formulace, které jsou pro nás přijatelné:
- (A) Klauzule zůstane, ale omezíme její scope na [konkrétní situace], 
      mimo to platí standardní pravidla.
- (B) Klauzule zůstane, ale přidáme protective language pro vás — 
      [konkrétní výjimka pro hrubou nedbalost / úmysl].

Pro [klauzuli Y] mohu navrhnout [analogická úprava].

[NO-ORIENTED CLOSE]
Je některá z těch variant blíže tomu, co byste potřebovali? Pokud ne, 
rád si poslechnu, co by muselo být jinak — a navrhuji 30min hovor s 
[jejich právníkem / vašimi PM] před tím, než pošleme finální verzi.

S pozdravem,
[name]

Why this works. Mirror separates the substantive disputes from the technical (most contract markups have 80% acceptable + 20% real disputes — surfacing this prevents over-negotiation). The label translates legal language back into emotional language ("co vás znepokojuje"), which the counterpart can engage with without retreating to formal positions. The calibrated question on prioritization is a multi-issue trade lever — they're rarely equally important. The options show that you're not removing the klauzule but reformulating, which preserves the underlying interest.

Scenario 5 — Follow-up after silent meeting

You had a meeting; counterpart was engaged but ambiguous; week passed, no follow-up from them. Standard "just checking in" doesn't work — it's been done to them 100 times. You need a single email that re-opens dialogue without sounding desperate.

Subject: Vrátím se k naší středeční diskusi

Dobrý den [name],

[MIRROR / where we left off]
Naposledy jsme zůstali u otázky [konkrétní téma z hovoru — ne obecné 
"posunutí"]. Zatím jsem od vás neslyšel, jak v tom dál postupujete, a 
chtěl jsem se vrátit, než to upadne mezi věci, na které ani jeden z 
nás nemá čas.

[LABEL — soft, multiple hypothesis]
Vypadá to, že buď je teď z vaší strany jiná priorita, nebo jste 
narazili na něco, co jsme spolu na hovoru úplně nevyřešili. Obojí je 
v pohodě — chci jen vědět, jak to z vašeho pohledu vidíte.

[CALIBRATED QUESTION]
Co se na vaší straně od středy změnilo, co bych měl vědět? A co by 
od mě potřebovalo přijít, aby další krok byl pro vás jasný?

[ANCHOR — concrete forward path]
Z mé strany navrhuji [konkrétní postup — např. "poslat upřesněný 
proposal s timelinem do pondělí" / "naplánovat 20min hovor tento 
týden, ať dotáhneme [otázku X]"]. To je založeno na tom, že [důvod — 
např. "máme deadline na launch v Q3 a do té doby musíme kick-offnout 
do dvou týdnů"].

[NO-ORIENTED CLOSE]
Je něco v tomto návrhu, co nesedí? Pokud ano, rád upravím podle toho, 
co potřebujete.

S pozdravem,
[name]

---

[ALTERNATIVE — pokud je to už 14+ dní bez odpovědi a normální 
follow-up nezabral, pošli místo toho jediný řádek (Voss Email Magic):]

Subject: Krátká otázka

Dobrý den [name],
vzdal jste to s [project / spolupráce]?

[name]

Why this works. The mirror is specific (concrete topic from the meeting, not generic "the project") — that signals you actually were listening. The label offers two non-judgmental hypotheses, neither of which makes them feel cornered. The calibrated question isn't accusatory (no "why did you go silent"). The anchor includes a real reason (objective criteria), not "I just want to know." The Voss Email Magic alternative at the bottom is the nuclear option for situations where the polite version has failed.

---

CZ-specific written norms

CZ business culture has specific written conventions that don't appear in English-language Voss / Goulston source material. Violating them turns a technically perfect email into a culturally tone-deaf one.

• Vykání default in business email. Never start with "Ahoj [name]," in B2B context unless the relationship has been explicitly tykání-promoted. The transition Vy → Ty in Czech business is a relationship milestone (often initiated over pivo, not over email). Premature tykání reads as American-style fake intimacy.

• "Děkuji za Vaši zprávu" — safe formal opener. Universally acceptable, signals respect, buys you the next sentence. Variations: "Děkuji za přímou zprávu" (when they were blunt), "Děkuji, že jste napsali rovnou" (when they raised an issue early). Avoid "Děkuji za Váš čas" as opener — it's a meeting-end phrase, not an opener.

• "To bude těžké" / "Uvidíme" / "To si musíme rozmyslet" in YOUR reply = polite NO. If you actually mean YES, use "Souhlasím", "Jdu do toho", "Můžeme se domluvit". Czech indirect-NO idioms catch foreigners and bilingual users — using them ambiguously will be interpreted as decline by CZ counterpart.

• Written follow-up POVINNÝ after every verbal agreement. CZ business culture trusts paper above verbal — even after a hand-shake "máme dohodu", the deal is not closed until the email confirmation lands. Send within 24-48 hours: a 5-line email summarizing what was agreed, with bullet points and one closing line "Pokud něco nesedí, dejte mi vědět nejpozději do [datum]."

• Avoid "ASAP", "co nejdříve", "okamžitě" — Czechs prefer specific deadlines. "ASAP" in CZ inbox reads as American urgency-theater. Replace with "do pátku 14:00", "do konce týdne", "do 15.5.". Specificity is read as professional; vagueness as evasive.

• CC discipline — over-CCing (manager, kolegové, právník) reads as aggression in CZ. Excessive CC is interpreted as either (a) status play ("look how many people I have behind me"), or (b) blame-broadcasting ("I'm getting witnesses for the dispute I'm anticipating"). Default: CC only people directly involved in the action item. If you must add someone, add a single line in the body explaining why ("Přidávám do CC [name], která bude koordinovat [konkrétní část]").

• Pozdrav variations:

  • "S pozdravem," — formal default. Always safe.
  • "S přátelským pozdravem," — warmer, for established relationships. Premature use reads as overfamiliar.
  • "Hezký den," — casual but professional. Use only after relationship is established.
  • "Mějte se," / "Měj se," — informal, only with tykání-relationships.
  • "S úctou," — extremely formal, almost only used toward authority figures (lawyer, government). In normal business, reads as obsequious or sarcastic.

• Timestamp discipline — Czech business norm is morning (8-10) or end-of-day (16-18). Late-night emails (after 22:00) are read as either workaholic-display or poor boundaries. If you're drafting at 23:00, schedule send for 8:00 next morning. Same content, much better received.

• Length norm — CZ business emails skew shorter than US equivalents. A 6-paragraph American "thoughtful long email" reads as windy in Czech inbox. Aim for 3-5 short paragraphs in routine messages, 6-8 paragraphs only when delivering a structured proposal (see scenario templates above).

---

Cialdini in text

Cialdini's 7 principles work in writing too — sometimes more, because the recipient has time to fully absorb them. For full principle definitions, ethical use cases, and manipulation flags, see ../references/cialdini-7-principles.md. The three principles most relevant to written negotiation:

Authority — credentials embedded subtly

Authority in writing is established not by self-declaration ("I have 15 years experience") but by embedded references to track record that the reader pattern-matches as authority signal. Examples:

"Z poslední podobné situace s [klient ze stejného sektoru] vím, že…"
"Když jsme dělali [analogický projekt] pro [klient], narazili jsme na…"
"Standardní postup, který funguje v [vašem sektoru], je…"

Each line implies "I've done this before" without saying it explicitly. The reader picks up the credential without you sounding self-promotional.

Ethical boundary. Embed only references that are real and verifiable. If pressed, you must be able to name the project. Borrowed authority — citing experts irrelevantly, name-dropping clients you barely worked with — collapses when checked, and CZ business is small enough that it gets checked.

Social proof — peer citation

Social proof in writing requires specificity. Vague "jiní klienti v podobné situaci…" triggers skepticism. Concrete "[konkrétní firma] ve stejné velikosti se rozhodla pro [konkrétní opci] a [konkrétní výsledek]" activates the principle.

Example application:

"Naši klienti v [sektor / velikost] obvykle volí variantu (B) — z 
posledních pěti projektů se pro ni rozhodli čtyři. Důvod, který nejčastěji 
slyším, je [konkrétní reason]. Neříkám, že to je vaše situace — jen abyste 
měli kontext, jak se obvykle rozhoduje."

The closing disclaimer ("neříkám, že to je vaše situace") is critical — it preempts defensive resistance. Counterpart hears the social proof and reframes it as information, not pressure.

Ethical boundary. Cite real cohort members. If you don't have peer data, skip the move. Manufactured social proof ("all our clients agree") is detected within 1-2 emails and destroys credibility.

Commitment — small public yes patterns in email threads

Email threads are public commitment archives. Every "yes" in a previous message is referenceable. Use this ethically by structuring your asks to align with their previously-stated values:

"V minulém emailu jste zmínili, že [konkrétní hodnota / cíl]. Tahle 
varianta odpovídá tomu — protože [explicit logical link]."

This works because (a) it shows you read carefully, (b) it makes the new ask feel consistent with their existing identity, (c) declining the new ask now requires them to either contradict themselves or explain the contradiction.

Ethical boundary. Don't twist their words. If they said "chceme rychlost" and you frame "v minulém emailu jste zmínili, že prioritizujete rychlost" — that's accurate. If they said "rychlost je důležitá, ale ne za každou cenu" and you frame "prioritizujete rychlost" — that's manipulation, and they'll catch it. CZ counterparts are particularly sensitive to selective quoting; they read carefully and remember.

---

Anti-patterns

Patterns that look like polite professional email but actively harm written negotiation. ❌ flagged.

• ❌ Solving in the subject line. "Solution for X", "Final answer on pricing", "Approval needed by Friday" — triggers defensive reading before line one. Use labeling-style subjects instead (see Subject line tactics above).

• ❌ Literal quoting from their email. "Re vaše vyjádření 'we cannot accept those terms'..." — reads legalistic, signals dispute prep. Paraphrase instead.

• ❌ Default palm-up everything. "Rád bych slyšel váš pohled... pokud byste mohli... jak by se vám líbilo, kdyby..." — too much palm-up reads as supplicant. Mix in palm-down anchor and constraint statements per email.

• ❌ Over-CCing as pressure tactic. Adding CFO, právník, manager to escalate visibility = aggression in CZ context. Default CC = only operationally involved parties.

• ❌ Matching ALL-CAPS energy. Their flooding ≠ your flooding. Their ALL-CAPS sentence in a complaint email is a limbic outburst; if you reply in ALL-CAPS or aggressive bold, you've joined them in the limbic system instead of pulling them out. Reply with deliberate calm typography — normal case, short paragraphs, factual structure.

• ❌ "ASAP" or "co nejdříve" without specific reason. Vague urgency reads as either bluffing scarcity (Cialdini manipulation flag) or amateurism. Replace with specific deadline + real reason ("do pátku 14:00, protože v pondělí předáváme klientovi").

• ❌ Defensive language. "Jen pro upřesnění..." / "Jak jsem již zmínil v minulém emailu..." / "Aby nedošlo k nedorozumění..." — these are defensive markers that signal you anticipate dispute. They also imply the counterpart wasn't paying attention or is being deliberately obtuse, which they will read accurately. Replace with neutral framing: "Pro úplnost přidávám..." / "Doplňuji..."

• ❌ "Děkuji za pochopení" before they've understood. Standard CZ closing line — but used at the end of an email delivering bad news that they haven't yet agreed to, it presumes consent and reads as pre-emptive dismissal. Replace with: "Dejte mi prosím vědět, jak to z vaší strany vidíte." — invites response rather than closing the door.

• ❌ Skipping written follow-up after verbal agreement. "Domluvili jsme se na hovoru, není potřeba to rozepisovat." — in CZ context, no written confirmation = no agreement. Always send the 5-line summary within 24-48 hours.

• ❌ Walls of text without structure. Long unbroken paragraphs of negotiation language in email = unreadable. Even when the substance is right, the form prevents it from landing. Break into short paragraphs with whitespace; use bullet points for options; use clear section markers ("Mirror", "Constraint", "Options") if it helps you draft, then strip them before sending.

• ❌ Using "I" framing in labels. "Mám pocit, že vás to zaskočilo" — reads as your interpretation imposed on them, defensive trigger. Replace with "Vypadá to, že..." / "Z vaší zprávy chápu, že..." — neutral hypothesis they can accept or reject without losing face.

• ❌ Sending immediately after writing a high-stakes email. First draft is rarely best draft. Save as draft, sleep, re-read morning. The version you send tomorrow is almost always tighter than the one you'd have sent at 23:00.

• ❌ Replying to ALL-CAPS / aggressive emails within 1 hour. They're flooded; if you reply within their flood window, you'll likely flood back. Wait minimum 4 hours, preferably overnight. Fast replies to angry emails are a classic relationship-destroyer.

---

Output template

Full workflow for processing a high-stakes incoming email.

Scenario (concrete). Klient mi včera napsal angry email — projekt, který jsme dodali před týdnem, obsahuje bug který našel jeho team a teď žádá refund 50% z 200k Kč částky. Já vím že bug existuje ale myslím že refund je přemrštěný.

The skill returns the following 6-step workflow:

Step 1 — Diagnose incoming

• Surface ask: 50% refund (= 100k Kč).
• Actual ask: (a) Acknowledgement that the bug is real and the failure is on us. (b) Concrete plan for fix. (c) Some financial gesture proportional to actual impact (likely 10-25%, not 50%). (d) Restored sense that future delivery will be better.
• Emotion: Frustration (primary, surface) + status threat (lawyer mention = leverage signal). NOT flooded — coherent sentences, structured argument. This is a deliberate opening anchor, not an outburst.
• Cialdini being deployed:
  • Scarcity (Friday deadline — likely real, but verifiable)
  • Authority (lawyer mention — borrowed; if he had a lawyer, the lawyer would write)
  • Possibly Commitment (referencing what was originally agreed — re-read original contract / proposal to verify his framing matches)

Step 2 — Self-check (your emotional state)

Before drafting, check yourself:

• Are you defensive? (= would write "we did everything right, the bug is minor")
• Are you scared? (= would write "we'll do anything to make this right")
• Are you angry? (= would write nothing for 12 hours, then write something terse)

If any of these, wait 24 hours before sending the reply. Draft now if needed (drafts release pressure), but do not send. Re-read tomorrow at 9:00. The version you send tomorrow is the version that wins the negotiation.

If you're calm and analytical, proceed to Step 3.

Step 3 — Draft subject line

Apply labeling-style framing:

"Vaše zpětná vazba k projektu [name]"

Avoid:

• "Re: Refund request" (positions you reactively)
• "Náš návrh řešení" (presumes you're solving unilaterally)
• "Důležité — k vašemu emailu" (panic-frame)

Step 4 — Draft response (full CZ template)

Subject: Vaše zpětná vazba k projektu [name]

Dobrý den [name],

děkuji za vaši zprávu — i když je nepříjemné ji číst, oceňuji, že 
jste mi napsali přímo. Beru to vážně a chci na to odpovědět věcně.

Z vaší zprávy chápu, že po nasazení projekt obsahuje bug, který váš 
tým objevil a hlásil minulý týden, a že naše reakce byla pomalejší, 
než jste očekávali. Investovali jste 200k a místo hladkého launche 
teď řešíte problém — a to není stav, ve kterém by spolupráce měla po 
týdnu od dodání být.

Zní to jako že to bylo dost frustrující — chápu, že tohle není to, 
co bylo dohodnuté. Bug existuje a odpovědnost za jeho odstranění je 
na nás.

Předtím, než navrhnu konkrétní řešení, potřebuji prosím porozumět 
dvěma věcem:
- Co konkrétně by se muselo stát, aby z vašeho pohledu byla situace 
  férově dořešená — kromě finanční náhrady, jaký výsledek by pro vás 
  byl přijatelný?
- Jak jste přišli ke konkrétní výši refundu, kterou navrhujete? 
  Pomohlo by mi to pochopit váš pohled na proporci.

Z naší strany 50% refund neodpovídá skutečnému dopadu — ne proto, že 
chyba není naše (ta je), ale proto, že proporční náprava vypadá 
jinak: oprava bugu (na náš účet), kompenzace za delay vašeho launche 
(diskutabilní suma podle skutečného impactu), a posílení QA pro 
další fázi (preventivní krok). Konkrétní číslo bych rád navrhl po 
hovoru, kdy budu mít úplnější obraz.

Bylo by špatně, kdybychom si dali 30 minut hovor zítra nebo v pátek 
ráno? Pokud telefon není teď ideální, mohu poslat strukturovaný 
návrh emailem nejpozději v pátek do 12:00 — chci, abychom se 
posunuli věcně, ne pod tlakem deadline.

Bug fix už pracuji s týmem na rozhraní — předběžný odhad opravy je 
[konkrétní timeframe], finální odhad pošlu samostatným emailem do 
zítra do 14:00.

S pozdravem,
[name]

Step 5 — Pre-send checklist

Re-read your draft against anti-patterns:

• [ ] Subject line is labeling-style, not solution-promising?
• [ ] No literal quotes from his email?
• [ ] Mirror present at opening (paraphrase of his core point)?
• [ ] At least one label of his emotion?
• [ ] No "I" framing in labels (use "Vypadá to..." / "Zní to...")?
• [ ] Calibrated question that surfaces actual interest, not surface ask?
• [ ] Constraint or palm-down anchor on the 50% (with reason, not bare assertion)?
• [ ] No-oriented soft close at the end?
• [ ] No "ASAP" / "co nejdříve" — only specific deadlines?
• [ ] No defensive language ("just to clarify", "as I mentioned")?
• [ ] No "Děkuji za pochopení" before he's understood?
• [ ] No CC of additional people without explicit reason?
• [ ] No ALL-CAPS, no aggressive bold?
• [ ] Length is 3-7 short paragraphs, not a wall of text?
• [ ] You waited 4+ hours since drafting, and re-read once?

If any unchecked, fix. Then send.

Step 6 — Decision tree based on their reply

Reply scenario A — Concession ("Ok, pojďme se domluvit, ozvu se v pátek na hovor.")

• Confirm hovor date/time in writing within the same thread.
• After hovor, send written summary within 24h: agreed scope of remediation, financial number, timeline, next milestone.
• The hovor is the deal; the email summary is the closure.

Reply scenario B — Counter ("30% refund a koupíme váš timeline na bug fix.")

• He moved off 50%. That's progress. Don't accept the first counter — it's almost never his best.
• Reply: another mirror + label + calibrated question on what drove him to 30% specifically. "Z vaší zprávy chápu, že 30% by pro vás bylo akceptovatelné. Pomozte mi pochopit — jak jste se na 30% dostali, co je tam zahrnuto?"
• Likely true zone: 10-20%. Anchor your counter at low end with objective criteria (delay impact in days × his daily revenue, etc.). Multi-issue trade: extended QA, bonus deliverable, future-credit on next project.

Reply scenario C — Escalation ("Píšu vám naposledy. Buď 50%, nebo právník.")

• Diagnostic: is the lawyer real? Re-read his original — if it said "obracíme se na právníka", he's escalating; if it said "musel bych zvažovat právní krok", he was bluffing.
• If real: switch register to formal. Confirm receipt of his position. State your position with objective criteria. Offer one final mediated path (hovor with both legal counsels, or written settlement proposal). Do NOT match his ALL-CAPS or ultimatum tone.
• If bluff: he's testing whether you fold. Reply calmly: "Beru vážně, že rozhodnutí o právním kroku je z vaší strany na stole. Před tímto krokem bych ale rád zkusil jednou vyřešit věc přímo. Posílám návrh konkrétních kroků [v separátním emailu / telefonicky zítra]." Then send the substantive proposal — don't get pulled into the ultimatum frame.

Reply scenario D — Silence (3+ days no response).

• Usually means he's either talking to internal stakeholders or to (claimed) lawyer, OR he's cooled down and isn't sure how to step back from his anchor without losing face.
• Day 4: short follow-up — "Chci se ujistit, že email z [datum] dorazil. Je nějaký důvod, proč bychom se k tomu neměli vrátit?" (No-oriented soft close.)
• Day 7: Voss Email Magic — "Vzdal jste se s tímhle?" Single line. Subject: "Krátká otázka."

Reply scenario E — He's right and you should concede more than you initially thought.

• This is the scenario nobody plans for and most negotiators handle worst. Sometimes the counterpart is right and your initial frame was wrong.
• If after his calibrated-question answer you realize the actual damage is closer to 35-40% than the 10-25% you'd estimated, say so. Voss: "That's right" moments come from genuine empathy, not just labeling. Replying: "Po vašem upřesnění chápu, že dopad na váš launch byl výrazně větší, než jsem zpočátku odhadoval. Reviduji svůj odhad — navrhuji 35% kompenzaci + opravu bugu na náš náklad + [bonus]. Pokud to dává smysl, mohu zítra poslat formální revidovaný návrh."
• Honest concession when warranted preserves the relationship. Stubborn lowball when he's right destroys it.

---

References called

• ../references/voss-email-adaptations.md — primary reference. Voss tactical empathy adapted for written/async contexts. Subject line tactics, mirroring as paraphrase, labeling templates (CZ + EN), calibrated questions in writing, No-oriented soft close, anchor positioning (palm-up / palm-down / constraint), red flags table, 5 scenario templates, CZ-specific written norms.

• ../references/cialdini-7-principles.md — for authority embedded subtly, social proof citation discipline, commitment in email threads. Each with text-specific example. Manipulation flags + defense playbook for when used against you in incoming email.

• ../references/cz-business-culture-deltas.md — CZ business culture differences vs US/Anglo-Saxon baseline. Vykání default, paper-trust, indirect-NO idiom translation table, anti-patterns (over-CC, fake-American positivity, skipping written follow-up).