Almost every client email fails in its first sentence. Not because it is rude — because it is a greeting. "Hope you're doing well", "Quick question", "Following up on our conversation": three sentences that tell the reader nothing, and the reader knows it. Every email they get that day opens the same way, and by the third or fourth one they have stopped reading and started scanning for the verb.
The opening line is not a courtesy. It is the only part of the email guaranteed to be read. Spend it on information.
The rule: the first sentence names the action
Before you write anything, decide what you actually need from the reader: a decision, a date, a fact, a yes, or nothing but attention. Then say it — in the first sentence, with the context attached.
Not "Hope the project is going well — I wanted to check in on the timeline." That buries the request under a greeting the reader has to excuse.
Instead: "We're on track for March 14, and I need one thing from you to stay there: the license email for the new environment."
One sentence: the status, the ask, the reason. The reader now knows exactly what this email is for, and answering it is a smaller job than parsing it.
Why "just checking in" fails
"Just checking in" is the most expensive phrase in freelance email, because it asks the reader to do the work of remembering why you exist. It contains no information, so the reply it produces — if any — is a polite version of "what about?".
Every email you send competes with the fifteen the reader will answer today. The ones that win are the ones that arrive with the question already sharpened: the date already attached, the choice already narrowed, the fact already stated. A reader does not answer a vague email; they answer a specific one that happens to be about their day.
Four openings that actually work
The decision opener. Name the decision, give the two options, ask for one.
"We can hold March 14 with the smaller scope, or move to the 28th with everything in. Which do you prefer?"
The reader answers in ten seconds. The alternatives are already priced and dated — that is the courtesy, not the greeting.
The fact opener. Lead with a number that changes the conversation.
"The audit is at 18 of 24 estimated hours, and the last four are the data-access ones we flagged."
Fact first, implications second. If the reader wants the implication, they will ask; the fact is what they needed.
The handover opener. "Here is everything you need to continue" — a list, not an essay.
"Three things to carry this forward: the vendor license request (action), the revised timeline (context), and the open decision (question, by Thursday)."
The no-opener. For the reader who gets a hundred emails: skip the opener entirely and start with a date or a verb.
"Thursday 10:00 still work for the review call?"
Brevity here is not rudeness; it is respect for their queue. The email that starts with the useful part is the email they read.
Putting this into practice this week? The full field note — with the four openings and the closing that schedules the follow-up for you — lives at consultant-stack.netlify.app/articles/the-email-that-gets-answered-openings-that-dont-waste-the-first-sentence.html. More notes on writing for clients: consultant-stack.netlify.app.
The one sentence you can keep
Not every email needs to be a scalpel. The relationship email — the check-in between projects, the "saw your post, made me think of your pricing thread" — has a job that is not information transfer. It exists to keep the name warm, and its opening can be human.
The distinction: relationship emails are rare on purpose, and they do not pretend to be about work. The emails that pretend to be check-ins but are actually requests are the ones that burn goodwill — the reader could not answer them, wants to help, but has nothing to grab.
If the email is a request, make it a request. If it is a relationship, make it a relationship. The failure mode is the hybrid.
What the opening predicts
Practice on the email you were about to send. Read the first sentence aloud. If a stranger could guess what this email is asking for, the opening works. If they would say "okay…?" — rewrite.
Two edits fix most openings:
- Move the ask to the top. Whatever the request is, say it before the context, not after.
- Attach one number or date to the request. "Need you to review" becomes "Need your yes/no on the scope change by Friday" — a deadline makes a request a decision.
These are not writing tricks; they are the difference between email as a transaction and email as a favour. You are paid for the first, and the second one quietly taxes every conversation.
The closing that matches
The same rule runs backwards: the last sentence should name what happens next, with an owner and a date.
"We'll proceed with the smaller scope unless I hear otherwise by Friday." That is a closing that schedules the follow-up for you. "Let me know what you think" schedules nothing — it parks the decision in the reader's inbox.
This note describes a communication method. No reply-rate statistics and no client cases are claimed.
More field notes on running a one-person consultancy: consultant-stack.netlify.app
Top comments (0)