A practical email writing process with an annotated product announcement, a review checklist, and guidance for briefing an AI draft.
Before writing a marketing email, finish this sentence: "After reading this, the recipient should be able to..."
If the answer contains several unrelated actions, narrow the brief. An email can contain detail without asking the reader to make five decisions at once.
Who is receiving this, what do they already know, and why is the message useful now? A long-time customer needs less introduction than someone who signed up yesterday. A user blocked by a setup issue needs an answer, not a tour of the company.
Gather the facts before drafting: the feature or offer, who can use it, any limitations, the destination link, and the date if timing matters. Mark unknowns as unknowns. Do not ask an AI writer to fill gaps with plausible claims.
Here is a fictional example for a product that has added CSV export:
Subject: Export your report as a CSV
You can now download the rows behind your monthly report.
Open a report and choose Export CSV. The file includes the filters you selected, so you can work with the same view in a spreadsheet.
Export is available to workspace admins. If you need access, ask your workspace owner.
Open your report
The opening names the change. The middle explains the action and an access limitation. The button should link to the report, not a homepage that makes the reader find it again.
This is an example, not a claim about Brew's reporting features. The structure works because the facts are concrete.
Remove the company introduction unless the recipient needs it. Replace "improve your workflow" with the task that becomes easier. Delete claims such as "save hours" unless you have evidence and the context to explain it.
Read the email aloud. If a sentence sounds like something nobody on your team would say, rewrite it. A calm, direct message can carry more confidence than a row of superlatives.
Use headings when the email is long enough to need them. Keep essential details as live text. Label the button with the destination or action, and make the link work when images are blocked.
Give it the audience, purpose, approved facts, voice examples, required link, and exclusions. "Write an exciting launch email" leaves the important decisions unspecified. A useful brief constrains the draft without scripting every sentence.
In Brew, review the copy and visual preview together. Check merge fields against sample contacts and send a test to a real inbox. Do not turn an approved layout into approval of an invented discount or testimonial.
Choose an outcome that matches the email: opening a report, booking a useful call, or completing a setup step. A higher open rate does not prove that the copy helped.
If you have enough traffic to compare versions, use a focused A/B test. Otherwise, collect replies and inspect where readers stop. One clear improvement is more useful than a new template every week.
