總覽 / 示範對話

示範對話|Set 3:合約條款討論

對話 1|付款條件談判(Payment Terms)

N = Nexchip 業務經理(賣方)|O = Orion Telecom 採購總監(買方)

  1. N: Thank you for joining the call. Before we finalize the agreement, I'd like to walk through the payment terms in Clause 4 — we have some concerns about the proposed 60-day window. → 簽約前我想逐項討論第 4 條付款條件——我們對 60 天的付款期有些疑慮。
  2. O: Of course. To be upfront, net 60 is now our standard across all suppliers — our finance team tightened working-capital policies this year. → net 60 = 60 天付款;working capital = 營運資金。
  3. N: I understand the pressure on your side. That said, we'd be more comfortable with net 30, but we're open to discussing a middle ground. → 我們比較希望是 30 天付款,但願意討論折衷方案。(必用句 1)
  4. O: What did you have in mind?
  5. N: Before we get to numbers, could you clarify what triggers the payment cycle — invoice date or delivery date? → 能否釐清付款週期的起算點——發票日還是交貨日?(必用句 2)
  6. O: Good question. In the current draft it runs from the invoice date, and invoices are issued upon delivery acceptance.
  7. N: That helps. But acceptance can take up to two weeks on your end, so effectively we're looking at 70-plus days of exposure. That's a real strain on our cash flow. → exposure = 資金曝險;strain on cash flow = 現金流壓力。
  8. O: I hear you. Acceptance is usually done within five business days — we could commit to that in writing.
  9. N: That would help. Here's a thought: if we agree to net 45, would you consider a 2% early-payment discount in return? → 如果我們同意 45 天,你們是否願意以 2% 提前付款折扣作為交換?(必用句 3)
  10. O: Interesting. So payments made within 15 days earn the 2% discount, and otherwise net 45 applies?
  11. N: Exactly. It gives your finance team flexibility, and it rewards us when cash comes in early.
  12. O: I'd need to run the numbers, but net 45 plus a five-day acceptance window sounds workable. One more thing — what happens if an invoice is disputed? Does the payment clock stop? → 發票有爭議時,付款期限是否暫停計算?
  13. N: We'd propose that only the disputed portion is withheld — the undisputed balance stays on the normal schedule. And payment beyond net 45 would accrue late-payment interest at 1% per month. → 僅暫扣有爭議的部分,無爭議金額照常付款;逾期按月息 1% 計息。
  14. O: That's reasonable. Let's also build in a review of payment terms after the first twelve months, once we have a track record.
  15. N: Agreed. I'll send over revised wording for Clause 4 by Friday, and we can confirm on next week's call.

Useful takeaways

  1. 「付款條件」固定說 payment terms(複數),不是 payment condition。
  2. 表達立場用軟化句 "We'd be more comfortable with…",避免 "You must pay in 30 days" 這種命令語氣。
  3. 談期限前先問起算點:"What triggers the payment cycle — invoice date or delivery date?",否則 net 45 可能實質變 60 天。
  4. 讓步要綁交換條件:"If we agree to X, would you consider Y in return?" 是最經典的 trade-off 句型。
  5. 收尾要有下一步:"I'll send over revised wording by Friday." 明確 owner + deadline 才算談完。

對話 2|違約責任與賠償上限(Liability Cap)

O = Orion Telecom 法務暨商務代表(買方)|N = Nexchip 合約經理(賣方)

  1. O: Let's move to Clause 9 on limitation of liability. Frankly, a cap at 50% of the contract value doesn't reflect the risk we're taking on. I'd like to hear your reasoning. → 老實說,以合約總額 50% 為上限,不足以反映我們承擔的風險。
  2. N: Sure. Our pricing assumes a limited risk profile — if we underwrote unlimited liability, the unit price would have to rise significantly. That's standard in the semiconductor industry.
  3. O: We're not asking for unlimited liability. We propose raising the liability cap to 100% of the total contract value. → 我們提議將賠償上限提高到合約總額的 100%。(必用句 1)
  4. N: That doubles our exposure. Can you walk me through why 50% is insufficient?
  5. O: Your chips go into network equipment we deploy for carriers. A single defective batch could trigger recall and redeployment costs well beyond half the contract value. → 單一瑕疵批次可能引發的召回與重佈建成本,就遠超過合約額的一半。
  6. N: Understood — but much of that would be consequential damages, which we exclude.
  7. O: On that point — consequential damages should be excluded for both parties, not just one side. The current draft only protects Nexchip. → 間接損失應該雙方互相排除,而不是只保護單方。(必用句 2)
  8. N: That's a fair symmetry argument. We can make the exclusion mutual.
  9. O: Good. Then with consequential losses off the table, a 100% cap on direct damages is hardly unreasonable.
  10. N: Let me suggest a compromise: 80% of the contract value, applied in aggregate over the term. → in aggregate = 合約期間累計計算(相對於 per incident 逐次計算)。
  11. O: Aggregate is a problem — one serious incident could exhaust the cap. Separately, would you accept a carve-out for gross negligence and willful misconduct? → 你們是否接受將重大過失與故意行為排除在上限之外?(必用句 3)
  12. N: Those carve-outs are market standard; we can accept them. On the cap itself — how about 100% per incident, capped at 150% in aggregate?
  13. O: That structure works better for us. One more question: how does this clause interact with your insurance coverage?
  14. N: We carry product liability insurance of ten million US dollars per occurrence. We can attach a certificate of insurance as an annex.
  15. O: Please do. And if a third party sues us because of your product, we'd expect Nexchip to indemnify us and bear the legal costs. → indemnify = 補償/使免受損害;合約語境不用 "pay money back"。
  16. N: We'll accept a third-party indemnity for product liability, subject to the agreed cap. I'll circulate updated language tomorrow.

Useful takeaways

  1. 法律責任用 liability,一般職責才是 responsibility;「賠償」用 indemnify / damages / compensation。
  2. 挑戰對方條款先要理由:"I'd like to hear your reasoning." 比直接開價更有談判空間。
  3. 上限談判必問適用方式:per incident(逐次) 還是 in aggregate(累計),兩者風險差很大。
  4. 對等原則是強論點:"…for both parties, not just one side" 很難被正面拒絕。
  5. carve-out(除外條款)與 market standard(市場慣例)是責任條款攻防的高頻詞,主張時直接引用慣例最有力。

對話 3|交期延遲與違約金(Delivery & Penalty Clause)

N = Nexchip 供應鏈暨業務代表(賣方)|O = Orion Telecom 專案採購經理(買方)

  1. N: I understand your concern about delivery timelines, and we take it seriously. That said, I'd like to discuss the penalty structure in Clause 6 — as drafted, it leaves no room for circumstances beyond our control. → 現行草案的罰則完全沒有為不可控因素留空間。
  2. O: To be candid, we added this clause because of the delays last year. We need real accountability, not best-effort promises. → 我們要的是可究責的承諾,不是「盡力而為」。
  3. N: That's fair, and we're not asking to remove it. We can accept liquidated damages, provided there's a five-business-day grace period. → 我們可以接受違約金,但前提是有五個工作天的寬限期。(必用句 1)
  4. O: Why should the first five days be free? A delay is a delay.
  5. N: A short grace period covers logistics variability — customs clearance, port congestion — that neither party controls. It keeps the penalty focused on genuine production failures. → 寬限期是為了吸收雙方都無法控制的物流波動,讓罰則聚焦在真正的生產失誤。
  6. O: Hmm. Suppose we grant three business days instead of five. What about the rate?
  7. N: The draft says 1% of the total contract value per week, uncapped — that's disproportionate. The penalty should be capped at 5% of the value of the delayed shipment. → 違約金應以延遲該批貨款的 5% 為上限。(必用句 2)
  8. O: The delayed shipment only? If a late batch stalls an entire rollout, our loss isn't limited to that batch.
  9. N: True — but that's what the liability clause is for. Liquidated damages are meant to be a pre-agreed, predictable remedy, not open-ended compensation. → 違約金的本質是「事先約定、可預期的救濟」,不是無上限的求償。
  10. O: Alright — 0.5% of the delayed shipment value per week, capped at 5% of that shipment. But delays must be flagged early.
  11. N: Agreed. We'll notify you in writing within two business days of a delay becoming foreseeable, together with a recovery plan. Also, delays caused by force majeure events should not count toward the penalty. → 不可抗力造成的延遲不應計入違約金。(必用句 3)
  12. O: Accepted, with the standard definition — and force majeure must be declared promptly, not claimed after the fact. → 不可抗力必須即時宣告,不能事後才主張。
  13. N: Of course. One more idea: would you consider a bonus mechanism for early delivery to balance the penalty?
  14. O: I can't promise a cash bonus, but early-delivery performance will weigh into next year's volume allocation. Let's document today's points and have legal turn the revised clause by Wednesday.

Useful takeaways

  1. 「違約金」說 penalty / liquidated damages,絕不說 punishment money。
  2. 接受罰則時綁條件:"We can accept X, provided (that)…" 是有條件讓步的標準句型。
  3. 爭取 grace period(寬限期)要給正當理由(物流波動),而不是單純要求優惠。
  4. 罰則談三個變數:rate(費率)、base(計算基礎:整約 vs 該批貨)、cap(上限),缺一不可。
  5. 避免 "We will try our best to deliver on time" 這種模糊話;改說 "We commit to the agreed delivery schedule, subject to the grace period."

對話 4|保密與智慧財產權(Confidentiality & IP)

N = Nexchip 技術授權經理(賣方)|O = Orion Telecom 智財法務(買方)

  1. N: Before we get into the joint development schedule, we need alignment on Clause 11 — IP ownership. Our position is simple: background IP stays with each party, and we negotiate foreground IP case by case. → 既有技術(background IP)各歸各的,合作產出(foreground IP)逐案協商。
  2. O: Our draft assigns all deliverables to Orion. We're funding the customization, so we expect to own the results.
  3. N: Funding the customization doesn't mean acquiring our core technology. Any pre-existing technology remains the exclusive property of the originating party. → 任何既有技術仍為原持有方的專屬財產。(必用句 1)
  4. O: We don't dispute that in principle. The difficulty is drawing the line — where does your background IP end and the joint work begin? → 難的是劃界:你的既有技術到哪裡為止、共同成果從哪裡開始?
  5. N: We'll attach a schedule listing our background IP before the project starts — the SerDes architecture, the power-management libraries, our process design kits. Anything on that list stays ours. → 開案前以附件清單列明 background IP,清單內的都歸我們。
  6. O: A written inventory helps. But what about improvements you make to that background IP during the project?
  7. N: Improvements to background IP follow the background — they stay with the owner. But we'd grant you a license to use them within the products we develop together. → 對既有技術的改良隨主技術歸屬原持有方,但授權你們在共同開發產品內使用。
  8. O: And the genuinely new results — the custom module itself?
  9. N: For jointly developed IP, we suggest co-ownership with a royalty-free cross-license. → 針對共同開發的智財,我們建議共有並互相授予免權利金授權。(必用句 3)
  10. O: Co-ownership gets messy. Could either party use the joint results in projects with other customers?
  11. N: We'd accept a restriction: neither party uses the foreground IP with a direct competitor of the other for three years. That protects your differentiation without freezing our roadmap. → 三年內雙方都不得將共同成果用於對方的直接競爭者——保護你們的差異化,也不凍結我們的產品路線。
  12. O: Three years is workable. Now, confidentiality — the draft says obligations end when the contract ends. That's far too short for chip designs.
  13. N: Agreed. We're proposing a five-year confidentiality obligation surviving termination of the contract. Trade secrets, though, should stay protected for as long as they remain secret. → 我們提議保密義務在合約終止後仍延續五年;營業秘密則以持續保密為限、不設年限。(必用句 2)
  14. O: Sensible. Last question: what are the remedies if confidential information is leaked by a subcontractor?
  15. N: Each party is fully liable for its subcontractors, and any disclosure to them requires prior written consent plus a back-to-back NDA. → 各方對其分包商負完全責任;揭露前須書面同意並簽訂條件對等的保密協議。
  16. O: Good. Let's have both legal teams consolidate this into a revised Clause 11 by the end of next week.

Useful takeaways

  1. 「智慧財產權」是 intellectual property (IP) rights,不是 knowledge rights。
  2. 談合作開發必分清 background IP(合作前既有)與 foreground IP(合作中產生),混用等於把核心技術一併讓出。
  3. 用「開案前附 IP 清單(schedule / written inventory)」把抽象的歸屬爭議變成可操作的劃界方法。
  4. royalty-free cross-license(免權利金交互授權)與 survive termination(於合約終止後續存)是 IP 條款兩個必會片語。
  5. 「誰出錢誰擁有」的主張,用 "Funding the customization doesn't mean acquiring our core technology." 一句劃清界線。

對話 5|合約終止與續約條件(Termination & Renewal)

N = Nexchip 事業處副理(賣方)|O = Orion Telecom 商務總監(買方)

  1. N: We're almost there, but Clause 14 on termination for convenience is a sticking point for us. We'll be investing heavily in dedicated capacity for this contract, so a 90-day exit clause exposes us to significant risk. → 無因終止條款是我們的癥結點(sticking point);90 天就能解約讓我們的專屬產能投資曝險過高。
  2. O: We understand, but our board requires an exit mechanism in any three-year commitment. Market conditions can change quickly.
  3. N: We're not asking you to give it up entirely — we're asking to make it fair. We suggest a minimum commitment period of eighteen months before the exit clause takes effect. → 我們建議設定十八個月的最低承諾期,之後終止條款才生效。(必用句 2)
  4. O: Eighteen months is more than half the term. Would twelve months work?
  5. N: Twelve months only covers our equipment qualification phase — the dedicated line doesn't break even until month sixteen. Could we meet at fifteen months? → 十二個月只夠設備驗證期;專線要到第十六個月才損益兩平。能否折衷十五個月?
  6. O: Fifteen months, with the 90-day notice on top — so the earliest effective exit is month eighteen. I can take that to my management.
  7. N: Thank you. Beyond timing, there's the cost question. If you terminate for convenience, we'd expect reimbursement for non-recoverable costs. → 若貴方無因終止合約,我們會要求補償無法回收的成本。(必用句 1)
  8. O: Define "non-recoverable." We're not signing a blank check. → 請定義「不可回收」——我們不會簽空白支票。
  9. N: Three categories, all documented: unamortized equipment investment, raw materials and work-in-progress ordered against your forecast, and finished goods built to your specification. We'd open our books for audit. → 三類且皆須有憑證:未攤提設備投資、依你方預測下單的原料與在製品、按你方規格生產的成品;帳目開放稽核。
  10. O: With an audit right and a cap, that's acceptable. What about materials you could resell elsewhere?
  11. N: Anything we can reasonably resell or redeploy comes off the claim — we only recover what's genuinely stranded. That's the point of "non-recoverable." → 可轉售或轉用的部分從求償額中扣除,只補償真正無處可去的損失。
  12. O: Fair. Now, renewal — what are you proposing?
  13. N: Unless either party gives notice ninety days before expiry, the contract renews automatically for one year. Pricing for the renewal term would be reviewed sixty days before expiry. → 除非任一方在到期前九十天通知,否則合約自動續約一年;續約價格於到期前六十天檢視。(必用句 3)
  14. O: Auto-renewal with a price review works. And on wind-down — if the contract does end, both parties still fulfill purchase orders placed before the termination notice, correct? → wind-down = 收尾過渡期;終止通知前已下的訂單仍須履行。
  15. N: Correct — and confidentiality and warranty obligations survive termination. I'll have the revised Clause 14 to you by Monday.
  16. O: Great. If the numbers check out on our side, we should be ready to sign next month.

Useful takeaways

  1. 「終止合約」用 terminate the contract;break the contract 意近「違約」,會造成誤解。
  2. termination for convenience(無因終止)談三件事:最低承諾期、通知期、補償機制,缺一就是單方面風險。
  3. 對方拋出模糊概念時反問定義:"Define 'non-recoverable.'" —— 談判中最省力的防守句。
  4. 求償主張要附「可稽核 + 有上限 + 扣除可轉售部分」三個讓步,可信度立刻提高。
  5. 「自動續約」用 auto-renewal / renews automatically,並記住配套句 "Unless either party gives notice … before expiry…"。

五篇皆已依卡片嵌入全部必用句型、避開各卡的錯誤陷阱,並把延伸追問(發票爭議、保險、分包商洩密、wind-down 等)織入對話後段。若要我把這五篇存成 materials/dialogues/set3-*.md 供跟讀練習,說一聲即可。 e'll attach the valuation method as an annex so there's no argument later. 14. B: Sensible. Last piece — renewal. What are you proposing? 15. A: An evergreen structure: unless either party gives notice ninety days before expiry, the contract renews automatically for one year. 〔旁註〕evergreen structure / auto-renewal = 自動續約機制;正式場合說 terminate the contract,勿說 break the contract。 16. B: Agreed. Final package: termination for convenience only after month fifteen, ninety days' notice, reimbursement of audited non-recoverable costs capped at twelve months' forecast, a 90-day wind-down, buy-back of finished goods and WIP, surviving confidentiality and warranties, and one-year auto-renewal with 90-day notice. I'll have legal turn the draft this week.

Useful takeaways

  1. 面對刪不掉的條款,改為 為它定價:"We're not asking you to remove it — we're asking to price it."
  2. Non-recoverable costs 要拆成可稽核類別(unamortized capex / WIP / raw materials),對方才敢答應。
  3. 用 minimum commitment period + 投資回收期依據 對抗過短的無因終止通知期。
  4. 終止不是結束,先談 survival clauses(保密、保固、未結訂單)+ wind-down period。
  5. 續約用 evergreen / auto-renewal 句型:"Unless either party gives notice ninety days before expiry, the contract renews automatically."

5 篇對話均嵌入了各卡的 3 個必用句型與延伸追問,並避開卡上列的錯誤陷阱(如 payment terms 複數、liquidated damages、terminate 而非 break)。如需存成檔案(例如 set3-示範對話.md)或改寫難度(B1 簡化版/C1 進階版),告訴我即可。