Writing Concise Executive Emails

Executive email is the highest-leverage written form in B2B sales — and the most consistently misused. Reps trained on long, polite, throat-clearing emails to peers send the same emails to executives and wonder why response rates collapse. The executive is not rude. The executive is rationing the only resource that matters: attention.

The operating principle: an executive should be able to read your email, understand the answer, and act on it from a phone in 30 seconds. Anything that interferes with that — a buried ask, an unclear subject, a multi-paragraph wind-up — costs you the response.

• Clarity — the answer or the ask appears in the first sentence, not the third paragraph. The executive should never have to scan to find what you want.
• Brevity — under 120 words for almost any executive email. If you cannot get under 120, the message is not yet sharp enough; do not send the long version.
• Relevance — every sentence answers 'why does this matter to the executive's quarter?' If it does not, cut it. Background, history, your team's process, and your enthusiasm are almost always cuttable.

A good test: read the email aloud and time it. If it takes more than 25 seconds to read, it is too long for the executive's actual attention budget.

Use the same structure every time. The executive learns it; you become predictable to read; response rates improve.

1. Subject line — the action you want. 'Approval needed: extended pilot terms' beats 'Quick question.'
2. First sentence — the answer or the ask. 'I'd like 15 minutes Thursday to walk you through the revised pricing — does 2pm work?'
3. Second short paragraph — the why. Two or three sentences of context, anchored to something the executive already cares about.
4. Third element — the evidence. A bullet list (3–5 items max) or a single attached one-pager. Never a wall of text.
5. Closing — the explicit next step. Who does what, by when. No 'let me know your thoughts' — that is offloading the next step onto the executive.

Subject lines — write them last, in the executive's language, naming the action. Compare:

• Weak: 'Following up on our conversation'
• Stronger: 'Decision needed by Friday: pilot scope'
• Strongest: 'Pilot scope: $40K saved if approved by Friday'

Opening lines — never 'I hope this email finds you well.' Executives read this as 'this email contains nothing.' Open with the answer, the ask, or a single sentence of customer-relevant context.

Calls to action — explicit, single, and easy to answer. 'Yes/no by Thursday EOD' beats 'let me know what you think.' If you need three things, lead with the most important and put the others in a one-line list — never blend them into prose.

Read every email twice before sending. The second read is for cuts. Almost always remove:

• Throat-clearing openings — 'I hope you're doing well,' 'It was great connecting last week,' 'As you know, our team has been working on...'
• Unnecessary credentials — 'As I mentioned, our company was founded in...' The executive does not care; if they do, they will ask.
• Hedging language — 'I just wanted to,' 'sorry to bother you,' 'when you have a moment.' These signal junior status and devalue the ask.
• Process narration — 'After speaking with my team, we discussed several options, and concluded that...' Skip to the conclusion.
• Multi-ask emails — if you need two unrelated things, send two emails. Mixing asks halves the response rate on both.

Ineffective (220 words, buried ask, no clear action):

*'Hi James, I hope you're doing well! It was great to meet you and the team last Wednesday. As discussed, we've been working through the various options for the pilot and our team has put together what we think is a really compelling proposal. There are a few different paths we could take, each with their own merits, and I wanted to walk you through them when you have a moment. I've attached a detailed deck with all the options and our recommendations. Let me know what works best for your schedule and we can find a time to discuss. Looking forward to hearing your thoughts!'*

Effective (62 words, lead-with-answer, clear action):

*'James — recommending Option B (90-day pilot, two business units, $48K). It hits your Q3 board commitment without expanding scope.*

*Quick rationale:* *• 60% of the value with 40% of the cost vs Option A* *• Same exit criteria you wanted* *• No new procurement cycle required*

*Can we lock this on a 15-min call Thursday at 2pm? Reply yes/no — I'll send the invite.'*

Same information. Different respect for the executive's time.

1. Draft the email at full length first; do not self-edit while drafting.
2. Cut to under 120 words on the second pass. Almost every email tolerates this.
3. Move the ask to the first sentence. If you cannot, the email has the wrong frame.
4. Rewrite the subject line in the executive's language, naming the action.
5. Read it aloud — 25 seconds or less.
6. Send before 8am or after 6pm in the executive's time zone — top of the inbox at the moment they triage.