How to Write a Business Email: Format, Subject Lines, Templates

How to Write a Business Email: Format, Subject Lines, Templates

TL;DR: A business email needs six parts: a clear subject line, a named greeting, a one-sentence purpose up front, the request or context, a specific next step, and a professional sign-off with a signature block. Keep it under 200 words. Lead with what you want the reader to do, then explain why.

In my 24 years of training in Singapore, I have seen the same three things sink most business emails. The subject line is vague. The first sentence does not say what the email is for. And the call to action is hidden in the last paragraph, where most readers never reach. Fix those three, and you will get a reply within a day. This guide walks through how to write business emails that hit those marks, with two worked templates and an honest opinion on why cold B2B email is harder than every template library admits.

If you would prefer to learn this in a classroom with feedback on your own emails, our Writing Professional Emails WSQ course covers everything below over one focused day.

Business email vs. formal vs. professional — which one are you writing?

These three labels get used interchangeably. They are not the same thing.

Think of it like the difference between a shirt, a uniform, and a suit. All three are clothes you wear to work. But you would not wear a uniform to a wedding, and you would not wear a suit on the factory floor. The category matters.

• A professional email is any work email you send in your professional capacity. The recipient could be a colleague, a contractor, a client, or a hiring manager. The defining feature is that it represents you at work.
• A formal email is a register, not a category. It uses titles, full names, hedged language, and complete sentences. You write formally to a regulator, a senior stakeholder you have never met, or a legal counterparty.
• A business email is a professional email written between businesses, or between a business and the people it sells to, hires, partners with, or owes money to. It carries commercial weight. Someone is going to spend money or make a decision based on what you sent.

The practical implication: a business email is almost always written in a moderately formal register, but the register shifts depending on the existing relationship. A first contact with a procurement officer is formal. A follow-up with a vendor you have worked with for three years is not.

If you are writing to a manager about a project update, you are writing a professional email, and our sibling guide on how to write a professional email is the better fit. If you are writing a difficult message to a senior, see writing formal emails to your boss. If you are writing to win, keep, or end a commercial relationship, you are in the right place.

The 6-part structure of a business email

Every effective business email contains six parts in this order:

1. Subject line — 6 to 10 words. What the email is about and what action is wanted.
2. Greeting — named where possible. “Dear [Full Name]” for first contact, “Hi [First Name]” once a thread is established.
3. Opening line — one sentence stating the purpose. Not pleasantries.
4. Body — context, request, supporting detail. Three short paragraphs maximum.
5. Closing line — the specific next step you want, with a date if possible.
6. Sign-off and signature block — closing phrase, your name, role, company, contact details.

The order matters more than the wording. A business email is like a newspaper article. The headline tells you what happened. The first paragraph tells you the five Ws. Only readers who care drop down for the detail. Your subject line is the headline. Your first sentence is the lede. If those two parts work, the rest gets read.

Here is a small habit that fixes most weak emails. Write the email. Then delete the first paragraph. About 80% of the time, what is left is a stronger email. The first paragraph is usually warm-up text the writer needed to get going, not information the reader needed.

Do try it out the next three emails you write. You will notice how much faster you finish.

Subject lines that get opened in B2B contexts

Subject lines are the only part of a business email the recipient sees before deciding whether to read. Five patterns work in B2B contexts:

• Topic + action: “Q3 proposal — review needed by Friday”
• Reference + topic: “Re your call: revised pricing for the ASEAN rollout”
• Specific number: “3 changes to the SOW for your sign-off”
• Question: “Are you the right person to approve invoice #4821?”
• Named context: “Tan & Co. — follow-up from yesterday’s meeting”

Three patterns to avoid:

• One-word subjects: “Update”, “Quick question”, “Hello”. They tell the reader nothing.
• Clickbait: “You won’t believe what happened” reads as marketing spam in a business context.
• All caps or excessive punctuation: “URGENT!!! PLEASE READ” trips spam filters and signals panic. Senior people do not write subjects like this.

The strongest subject lines pair a specific noun with a specific action. “Meeting” is weak. “Vendor review meeting — agenda attached” is strong. A manager scanning twenty subject lines on a Monday morning is rewarding specificity, not creativity. Give them specificity.

Greetings and closings that actually fit 2026

The old rules said “Dear Mr. Smith” for everything and “Yours sincerely” to close. Most of those rules no longer apply.

For greetings, use this hierarchy:

Situation	Greeting
First contact, formal context (legal, government, senior executive)	Dear [Full Name]
First contact, business peer	Dear [First Name]
Established thread	Hi [First Name]
You don’t know the name	Dear [Role], e.g., “Dear Hiring Manager”
Group email, internal	Hi team / Hi all

“Hey” is too casual for first contact in almost every business context. “To whom it may concern” reads as a form letter. Use a role title instead.

For closings, fewer options than the textbooks suggest actually fit modern business email:

• Best regards — safe default for most business emails.
• Kind regards — slightly softer, good for client-facing notes.
• Sincerely — still appropriate for formal or first-contact business emails.
• Yours faithfully — only when you addressed the email “Dear Sir/Madam” or used a role title. Pedantic but correct.
• Thanks — fine when you have asked for something specific and the favour is mutual.

Avoid “Cheers” (too casual outside informal contexts), “Warmly” (reads as marketing), and any closing with a smiley face in a first-contact business email.

Worked example 1: business email for a proposal

A proposal email is one of the highest-stakes business emails most people send. You are asking someone to spend money. The email must be confident without being pushy, and specific without being long.

Here is a template for sending a proposal to a prospect you have already met:

Subject: Proposal — Customer experience review for ABC Pte Ltd

Dear Sarah,

Following our discussion on 12 May, please find the attached proposal for the customer experience review we scoped together. It covers the two pain points you raised (the drop-off at checkout and the post-purchase email sequence) and proposes a six-week engagement at SGD 18,500.

Three things you may want to look at first:

1. The scope on page 2 — confirm I have captured the right two journeys.
2. The timeline on page 5 — the start date assumes a 2 June kick-off; let me know if that needs to shift.
3. The investment summary on page 8 — broken down by deliverable so you can compare with anything else on the table.

Could we schedule a 30-minute call next week to walk through any questions? I am available Tuesday afternoon or Thursday morning, Singapore time.

Best regards,
[Your Name]
[Role], [Company]
[Phone] | [Email]

What this template does well: it references the previous conversation, names the deliverable, gives a price up front, and points the reader to the three pages they will care about. The next step is specific (a 30-minute call) with proposed times. The reader can reply with one line: “Tuesday 3pm works.”

Worked example 2: business email to a client (escalation, not promotion)

The harder business email is the one where you have to tell a client something they do not want to hear. The instinct is to soften, hedge, and bury the bad news in the third paragraph. That instinct is wrong. Burying bad news makes the client feel ambushed when they finally find it.

Subject: Project Helios — timeline slip, options inside

Hi James,

I am writing to let you know that the Phase 2 delivery date will slip by two weeks, from 14 June to 28 June. I want to walk you through what happened and the two options we have.

What happened: the data migration from the legacy CRM threw up a schema mismatch we had not anticipated in the discovery phase. Resolving it has taken our integration team longer than planned.

Two options:

1. Accept the two-week slip. The full scope ships on 28 June with no change to cost. This is what I recommend.
2. Descope the legacy CRM integration. Phase 2 ships on the original 14 June date without that integration; we add it back in a Phase 3 at a small additional cost.

I would like to meet this week to talk through both. I am available Wednesday 2pm or Friday 10am.

Apologies for the slip. We caught it as early as we could, and I would rather give you accurate dates than optimistic ones.

Best regards,
[Your Name]

The structure does three things at once. It states the bad news in the first sentence. It explains the cause without making excuses. And it gives the client agency by offering two options. The apology is one line, near the end, after the client has the information they need to act.

Managers and clients can be quite demanding when timelines slip. Of course they will be unhappy. But they will be far more unhappy if they find out late, or if you offer no options, or if the apology comes before the facts. Tell them early. Tell them clearly. Offer choices. (When the message is closer to a structured workplace apology, see how to write an apology email at work for the wording template.)

Cold B2B email: why most templates fail (and the one that works)

I will say this plainly. Most cold B2B email templates fail because they were written for a SaaS sales team in San Francisco selling to another SaaS sales team in San Francisco. Drop those templates into a Singapore, Malaysian, or Indonesian B2B context, and they read as exactly what they are. Scripts.

The patterns that no longer work:

• “Hi {first_name}, I came across your LinkedIn profile and was impressed by your work at {company}.” Everyone has received fifty of these this month. The recipient knows you scraped LinkedIn.
• “We help companies like {industry_peer} achieve {vanity_metric}.” Name-dropping a competitor in a first email reads as pressure, not credibility.
• “Do you have 15 minutes for a quick call this week?” You have not earned 15 minutes yet.

A cold B2B email that actually gets replies tends to do three things. It names something specific about the recipient’s business that is publicly visible, like a recent product launch, a new hire, or a press mention. It states one concrete observation, not a sales pitch. And it asks for a single, low-cost reply. Not a meeting. Not a demo. Harvard Business Review’s research on cold outreach reaches the same conclusion: specificity and small asks out-perform polished pitches.

A simple version:

Subject: Question about your ASEAN rollout

Hi Priya,

I saw the announcement about your KL office opening last month. Congrats on the milestone.

One question: when you expand into Malaysia from Singapore, are you handling the GST/SST tax registration in-house or working with a local partner? We have helped three other Singapore SaaS companies through that step in the last year and I keep seeing the same friction point.

Happy to share what we learned in a one-paragraph reply — no meeting needed unless it is useful.

Best regards,
[Your Name]

Notice what is absent. No company tagline. No “We help X achieve Y” line. No calendar link. The ask is small enough that a reply costs the recipient nothing. If they engage, the conversation has earned its way forward.

If you write cold B2B email regularly, our Communicate with Confidence programme covers tone calibration for first-contact business writing.

Writing business emails when English isn’t your first language

In Singapore and across ASEAN, most business emails are written by professionals whose first language is not English. The good news: recipients across the region know this, and read accordingly. The work is to make sure the email reads as competent, not as translated.

After 24 years of training Singapore professionals, I see the same three patterns trip people up. These are the sentence shapes that tip off a reader to a translation-shaped email:

1. Over-formality at the open. “I hope this email finds you well and your family is in good health” is warm in many languages and slightly heavy in English business email. “I hope you are well” is enough.
2. Direct verb translations that don’t fit the register. “Kindly do the needful” is correct grammar in Indian English but reads as old-fashioned in Singapore or Australian business contexts. “Please action this by Friday” is more current.
3. Stacked politeness markers. “Would it be possible to perhaps consider whether we could potentially schedule” — each word is polite, but the stack reads as evasive. Pick one. “Could we schedule a call on Tuesday?” is direct without being rude.

A three-pass edit fixes most of this:

• Pass 1: Read the email aloud. Anything that sounds like a script gets cut.
• Pass 2: Find every sentence longer than 25 words. Split or shorten.
• Pass 3: Find every adjective. Delete two-thirds of them.

The goal is not to sound like a native speaker. The goal is to sound like a busy professional. Native English business writers are also editing out their own over-formality and stacked politeness. The underlying writing problem is the same. SkillsFuture Singapore funds English-medium business communication courses for exactly this reason.

Give it a try on your next email to a client. You will be surprised how much shorter it gets, and how much sharper it reads.

Etiquette mistakes that cost business

Six mistakes that erode professional credibility, in order of how much damage they do:

1. Reply-all on a thread that should have been a direct reply. You have just made forty people read your one-line response.
2. CC weaponisation — copying someone’s manager to apply pressure without telling the recipient why. Once spotted, it is rarely forgiven.
3. “As per my last email” in a follow-up. The phrase reads as passive-aggressive even when no aggression was intended. “Following up on my note from Tuesday” does the same job without the edge.
4. Late acknowledgement — letting a client email sit for three days without even a “Got it, will respond by Thursday.” A two-line acknowledgement preserves the relationship. Silence damages it.
5. All-caps subject lines or excessive exclamation marks. Reads as panic.
6. No signature on a first-contact email. The recipient has no idea who you are or how to reach you outside this thread.

If business email is a meaningful part of your role and you have not had any structured training on it, our Writing Professional Emails course covers the full toolkit (structure, tone, escalation, cross-cultural calibration) over a focused day. Intellisoft has trained 48,000+ working professionals and 12,600+ companies on courses like this one. We run it as both a public class and an in-house programme. Most participants tell us afterwards that the time-savings on email alone pays back the course within a month.

For the follow-up thread that comes after this first email, see how to write a follow-up email.

I hope you’ll like this guide. Try the “delete the first paragraph” habit on your very next email. It is the smallest change with the biggest payoff in everything above.

[[AUTHORBIO]]

FAQ

What’s the difference between a business email and a professional email?

A professional email is any work email you send in your professional capacity. A business email is the subset of professional emails written between businesses, or between a business and its customers, vendors, hires, or partners. Business emails carry commercial weight. Someone is going to spend money or make a decision based on what you sent. The structural rules are the same. The stakes and register are slightly higher for business email.

How do you start a business email?

Use a named greeting where possible. “Dear [Full Name]” for first contact, “Hi [First Name]” once a thread is established. Then state the purpose of the email in the first sentence. Avoid pleasantries longer than one short line. A reader who sees the purpose in the first sentence will keep reading. A reader who has to wade through two paragraphs of warm-up may not.

What’s a good subject line for a business email?

A specific noun paired with a specific action. “Q3 proposal — review needed by Friday” is strong. “Update” or “Quick question” is weak. Aim for 6 to 10 words. Avoid all caps, excessive punctuation, and one-word subjects. If the email has a deadline or a reference number, put it in the subject line. The reader should be able to find the email by searching their inbox a month later.

How long should a business email be?

Most business emails should be under 200 words. The exception is a substantive update or a proposal email, where 300 to 400 words is fine if the structure is scannable (bullet points, short paragraphs, clear sections). The test is not word count but scannability. Can the reader extract the key information in 15 seconds? If yes, the length is right.

Is a business email the same as a B2B email?

Not quite. A B2B email is a business email sent specifically from one business to another (sales, partnership, vendor management). A business email is the broader category and also covers customer service, recruitment, supplier negotiation, and any other commercial communication. All B2B emails are business emails. Not all business emails are B2B. If you do a lot of B2B writing, our Business Presentation Skills programme is the natural next step from email into proposal and meeting communication.

[[RELATEDPOSTS]]

[[JSONLD]]