us-business-english

jezweb ｜ 寫作與文件 ｜ 原文 ｜ MIT

寫給美國讀者的商務英文：EN-US 拼字、語氣階梯與避開企業流行語

---
name: us-business-english
description: "專業溝通用的美式商務英文寫作風格：直接、以行動為導向，採用 EN-US 拼字（color、organize、center）。只要使用者是寫給美國讀者看的，就用這個 skill，包括 email、聊天訊息、提案、客戶溝通、部落格文章、網頁文案，或任何商務寫作。適用於起草、編輯和檢查專業文字的語氣。"
---

# US Business English

專業而直接。有自信但不強迫推銷。友善但不隨便。寫起來要像一位把事情做完的稱職美國專業人士，不像矽谷兄弟，不像華爾街備忘錄，也不像企業流行語製造機。

## 拼字（EN-US）

| 模式 | 美式 | 不是 |
|---------|----------|-----|
| -or | color, favor, honor, behavior | colour, favour |
| -ize | organize, realize, specialize, recognize | organise, realise |
| -er | center, fiber, meter, theater | centre, fibre |
| -ense | license（名詞和動詞）, defense, offense | licence (noun), defence |
| 單 L | traveling, canceling, modeling | travelling, cancelling |
| -og | catalog, dialog, analog | catalogue, dialogue |
| -ment | judgment, acknowledgment | judgement, acknowledgement |

**名詞/動詞備註：** 跟英式/澳式英文不同，美式英文的 "license" 和 "practice" 名詞、動詞都用同一個拼法，不需要區分。

**常見陷阱：** inquiry（標準寫法，不是 enquiry）、curb（路緣）、tire（輪胎）、program（所有情境）、check（不是 cheque）、gray（不是 grey）。

**日期格式：** 月 日, 年：January 15, 2026。所有書面溝通都用這個，除非要配合特定系統的格式。

## 語氣階梯

依情境調整正式程度。預設用「專業又友善」：清楚且有人味。

| 情境 | 正式程度 | 問候 | 結尾 |
|---------|-----------|----------|----------|
| Slack/Teams（內部） | 輕鬆 | "Hey" / 名字 | 不需要 |
| 寫給既有客戶的 email | 專業友善 | "Hi [Name]" | "Best" / "Thanks" |
| 寫給新客戶的 email | 專業 | "Hi [Name]" | "Best" / "Thanks" |
| 提案或報價 | 專業 | "Hi [Name]" | "Best regards" / "Best" |
| 會後跟進 | 專業友善 | "Hi [Name]" | "Thanks" / "Talk soon" |
| 陌生開發信 | 溫暖的專業 | "Hi [Name]" | "Best" / "Thanks" |
| 正式信函或法律文件 | 正式 | "Dear [Name]" | "Sincerely" |

**絕對不要用：** "Dear Sir/Madam"（除非真的是法律情境中完全不知道收件人）、"Warmest regards"、"Respectfully yours"（留給軍方/政府）、"Cheers"（讀起來像裝出來的英式）。

## 結尾用語排名

在美國中小企業的情境中，從最常用到最少用：

1. **Best**：預設，幾乎哪裡都適用
2. **Thanks**：有事請對方幫忙，或感謝對方付出時
3. **Best regards**：再正式一級，適合提案
4. **Regards**：中性，稍微冷一點
5. **Talk soon**：輕鬆，表示彼此有持續的關係

**避免：** "Cheers"（美國人聽起來像英式/澳式）、"Kind regards"（有點僵硬）、"Warm regards"（用過頭了）、"Respectfully"（政府/軍方的語氣）。

## 避免清單

### 企業流行語

看到這些就直覺地換掉：

| 不要寫 | 改寫成 |
|-----------|-------|
| "synergy" / "synergize" | "working together" / "combined effort" |
| "leverage"（動詞） | "use" / "take advantage of" |
| "circle back" | "follow up" / "come back to this" |
| "touch base" | "check in" / "connect" |
| "loop in" | "include" / "bring in" |
| "bandwidth"（指時間） | "time" / "capacity" |
| "actionable insights" | "useful information" / "what we found" |
| "move the needle" | "make a difference" / "improve" |
| "deep dive" | "closer look" / "detailed review" |
| "pivot" | "change direction" / "adjust" |
| "align on" | "agree on" / "get on the same page" |
| "unpack"（一個想法） | "look at" / "go through" |
| "cadence" | "schedule" / "frequency" |
| "deliverables" | "what we'll provide" / "the work" |

### 外來用語與矯枉過正

書面的專業溝通要避免：

- **"Whilst"、"amongst"**：改用 "while"、"among"
- **"Shall"**：改用 "will" 或 "should"
- **"Keen"**：改用 "interested" 或 "excited about"
- **"Brilliant" / "lovely"**：聽起來像英式，改用 "great" / "sounds good"
- **正式 email 裡的 "Dude"、"awesome"、"totally"**：Slack 上沒問題，提案裡不行
- **硬裝隨性**：對新客戶說 "Hey buddy!" 太過頭了

## 寫作原則

1. **先講重點。** 第一句話就回答問題或說明目的。背景放在後面，不要放前面。

2. **段落要短。** 最多兩到三句。一段一個想法。留白是你的朋友。

3. **自然使用縮寫。** "We've"、"I'll"、"that's"、"won't" 讀起來有人味。提案中稍微收斂一點，但 email 要像真人寫的。

4. **用主動語態。** 要寫 "We'll send the report Monday"，不要寫 "The report will be sent on Monday."

5. **具體勝過模糊。** 要寫 "I'll have this to you by Thursday"，不要寫 "I'll get back to you soon."

6. **一封 email 一個請求。** 有多個請求？編號列出來。不要把第二個請求埋在第四段裡。

7. **配合對方的節奏。** 客戶寄來短 email？就短短回。寄來詳細的 brief？就詳細回應。兩行能講完就不要寫五段。

## 範例

### 給既有客戶的進度更新

**太公司腔：**
> Dear Mr. Thompson, I am writing to provide you with a comprehensive update regarding the current status of your website redesign project. Please find below a summary of the deliverables completed to date and the anticipated timeline for remaining action items moving forward.

**對的語氣：**
> Hi David,
>
> Quick update on the website -- we've finished the homepage and the three main service pages. Everything's looking solid.
>
> Next up is the contact form and booking system, which we'll have ready by end of next week. I'll send over a preview link once it's live on the staging site.
>
> Best,
> [Your name]

### 送出報價

**太僵硬：**
> Dear Client, Please find attached our formal quotation for the proposed scope of work as discussed. We trust this meets your requirements and look forward to your favorable response at your earliest convenience.

**對的語氣：**
> Hi Sarah,
>
> Thanks for the call yesterday -- good to get a clear picture of what you need.
>
> I've put together a quote based on what we discussed. The short version: $4,500 for the full site, including the booking system. That covers design, development, and getting it live on your domain.
>
> Happy to hop on a call if you have any questions.
>
> Best,
> [Your name]

### 拒絕請求

**太直接：**
> We can't do that.

**太委婉：**
> While we certainly appreciate your suggestion and would love to explore this further, unfortunately at this current juncture it may not be feasible for us to accommodate this particular request given our current bandwidth constraints.

**對的語氣：**
> Hi Mark,
>
> Thanks for thinking of us for this. Unfortunately it's not something we can take on right now -- we're at capacity through March.
>
> If timing works, we'd be happy to look at it in April. Otherwise, I can recommend a couple of people who might be able to help sooner.
>
> Best,
> [Your name]

## 情境規則

**企業客戶：** 正式程度比他們高一點點，但保持清晰、有人味。用 "Best regards" 取代 "Best"，但仍然用 "Hi [Name]"，不要用 "Dear Mr. Smith"。絕對不要把他們的行話原樣丟回去，他們說 "synergize"，你就說 "work together"。

**傳達壞消息：** 要直接但友善。說明問題、簡短解釋原因、提出前進的路。不要廢話，不要過度道歉。一個 "sorry" 就夠，兩個是在道歉，三個就是卑躬屈膝了。

**報價：** 直接且有自信。要寫 "The cost for this is $X"，不要寫 "We would like to propose a fee of $X for your consideration."。寫明包含哪些項目。不要含糊。金額直接寫美元符號，除非國際情境需要，否則不加 "USD"。

**拒絕：** 尊重且簡短。給出理由（一句話），可能的話提供替代方案。不要過度解釋，也不要過度道歉。

**跟進：** 輕鬆但有目的。"Just checking in on this" 沒問題。"I trust this email finds you well" 不行。"Wanted to bump this to the top of your inbox" 也可以。

---
name: us-business-english
description: "American business English writing style for professional communications — direct, action-oriented, EN-US spelling (color, organize, center). Use whenever the user is writing for an American audience: emails, chat messages, proposals, client communications, blog posts, web copy, or any business writing. Apply to drafting, editing, and tone-checking professional text."
---

# US Business English

Professional and direct. Confident without being pushy. Friendly without being sloppy. Write like a competent American professional who gets things done -- not like a Silicon Valley bro, not like a Wall Street memo, and not like a corporate buzzword machine.

## Spelling (EN-US)

| Pattern | American | Not |
|---------|----------|-----|
| -or | color, favor, honor, behavior | colour, favour |
| -ize | organize, realize, specialize, recognize | organise, realise |
| -er | center, fiber, meter, theater | centre, fibre |
| -ense | license (noun and verb), defense, offense | licence (noun), defence |
| Single L | traveling, canceling, modeling | travelling, cancelling |
| -og | catalog, dialog, analog | catalogue, dialogue |
| -ment | judgment, acknowledgment | judgement, acknowledgement |

**Noun/verb note:** Unlike British/Australian English, American English uses "license" and "practice" for both noun and verb forms. No split needed.

**Common traps:** inquiry (standard, not enquiry), curb (road edge), tire (wheel), program (all contexts), check (not cheque), gray (not grey).

**Date format:** Month Day, Year -- January 15, 2026. Use this in all written communications unless matching a specific system format.

## Tone Ladder

Match formality to context. Default to "professional friendly" -- clear and personable.

| Context | Formality | Greeting | Sign-off |
|---------|-----------|----------|----------|
| Slack/Teams (internal) | Casual | "Hey" / first name | None needed |
| Email to existing client | Professional friendly | "Hi [Name]" | "Best" / "Thanks" |
| Email to new client | Professional | "Hi [Name]" | "Best" / "Thanks" |
| Proposal or quote | Professional | "Hi [Name]" | "Best regards" / "Best" |
| Follow-up after meeting | Professional friendly | "Hi [Name]" | "Thanks" / "Talk soon" |
| Cold outreach | Warm professional | "Hi [Name]" | "Best" / "Thanks" |
| Formal letter or legal | Formal | "Dear [Name]" | "Sincerely" |

**Never use:** "Dear Sir/Madam" (unless truly unknown recipient in legal context), "Warmest regards", "Respectfully yours" (reserve for military/government), "Cheers" (reads as affected British).

## Sign-off Ranking

From most to least common in US SME context:

1. **Best** -- default, works almost everywhere
2. **Thanks** -- when you're asking for something or appreciating effort
3. **Best regards** -- one step more formal, good for proposals
4. **Regards** -- neutral, slightly cooler
5. **Talk soon** -- casual, signals ongoing relationship

**Avoid:** "Cheers" (sounds British/Australian to American ears), "Kind regards" (slightly stiff), "Warm regards" (overdone), "Respectfully" (government/military tone).

## Avoid List

### Corporate Buzzwords

Replace these reflexively:

| Instead of | Write |
|-----------|-------|
| "synergy" / "synergize" | "working together" / "combined effort" |
| "leverage" (verb) | "use" / "take advantage of" |
| "circle back" | "follow up" / "come back to this" |
| "touch base" | "check in" / "connect" |
| "loop in" | "include" / "bring in" |
| "bandwidth" (for time) | "time" / "capacity" |
| "actionable insights" | "useful information" / "what we found" |
| "move the needle" | "make a difference" / "improve" |
| "deep dive" | "closer look" / "detailed review" |
| "pivot" | "change direction" / "adjust" |
| "align on" | "agree on" / "get on the same page" |
| "unpack" (an idea) | "look at" / "go through" |
| "cadence" | "schedule" / "frequency" |
| "deliverables" | "what we'll provide" / "the work" |

### Foreign-isms and Overcorrections

Avoid in written professional comms:

- **"Whilst", "amongst"** -- use "while", "among"
- **"Shall"** -- use "will" or "should"
- **"Keen"** -- use "interested" or "excited about"
- **"Brilliant" / "lovely"** -- sounds British, use "great" / "sounds good"
- **"Dude", "awesome", "totally"** in formal emails -- fine on Slack, not in proposals
- **Forced casualness** -- "Hey buddy!" to a new client is too much

## Writing Principles

1. **Lead with the point.** First sentence answers the question or states the purpose. Context comes after, not before.

2. **Short paragraphs.** Two to three sentences max. One idea per paragraph. White space is your friend.

3. **Natural contractions.** "We've", "I'll", "that's", "won't" -- reads human. Ease off slightly in proposals, but emails should sound like a person wrote them.

4. **Active voice.** "We'll send the report Monday" not "The report will be sent on Monday."

5. **Specific over vague.** "I'll have this to you by Thursday" not "I'll get back to you soon."

6. **One ask per email.** Multiple requests? Number them. Don't bury the second ask in paragraph four.

7. **Match their energy.** Short email from client? Short reply. Detailed brief? Detailed response. Don't write five paragraphs when two lines will do.

## Examples

### Status update to existing client

**Too corporate:**
> Dear Mr. Thompson, I am writing to provide you with a comprehensive update regarding the current status of your website redesign project. Please find below a summary of the deliverables completed to date and the anticipated timeline for remaining action items moving forward.

**Right tone:**
> Hi David,
>
> Quick update on the website -- we've finished the homepage and the three main service pages. Everything's looking solid.
>
> Next up is the contact form and booking system, which we'll have ready by end of next week. I'll send over a preview link once it's live on the staging site.
>
> Best,
> [Your name]

### Delivering a quote

**Too stiff:**
> Dear Client, Please find attached our formal quotation for the proposed scope of work as discussed. We trust this meets your requirements and look forward to your favorable response at your earliest convenience.

**Right tone:**
> Hi Sarah,
>
> Thanks for the call yesterday -- good to get a clear picture of what you need.
>
> I've put together a quote based on what we discussed. The short version: $4,500 for the full site, including the booking system. That covers design, development, and getting it live on your domain.
>
> Happy to hop on a call if you have any questions.
>
> Best,
> [Your name]

### Saying no to a request

**Too blunt:**
> We can't do that.

**Too soft:**
> While we certainly appreciate your suggestion and would love to explore this further, unfortunately at this current juncture it may not be feasible for us to accommodate this particular request given our current bandwidth constraints.

**Right tone:**
> Hi Mark,
>
> Thanks for thinking of us for this. Unfortunately it's not something we can take on right now -- we're at capacity through March.
>
> If timing works, we'd be happy to look at it in April. Otherwise, I can recommend a couple of people who might be able to help sooner.
>
> Best,
> [Your name]

## Context Rules

**Corporate clients:** Match their formality up one notch but stay clear and human. "Best regards" instead of "Best", but still "Hi [Name]" not "Dear Mr. Smith". Never mirror their jargon back -- if they say "synergize", you say "work together".

**Delivering bad news:** Be direct but kind. State the issue, explain why briefly, offer the path forward. No filler, no excessive apologies. One "sorry" is enough -- two is apologetic, three is groveling.

**Quoting prices:** Direct and confident. "The cost for this is $X" not "We would like to propose a fee of $X for your consideration." Include what's covered. No hedging. Use dollar amounts without "USD" unless international context requires it.

**Saying no:** Respectful and brief. Give the reason (one sentence), offer an alternative if possible. Don't over-explain or apologize excessively.

**Following up:** Casual but purposeful. "Just checking in on this" is fine. "I trust this email finds you well" is not. "Wanted to bump this to the top of your inbox" works too.