Sinal do Radar #003: a cold email starts before the first line
An edition of Sinal do Radar curated by Ada on selection, context and the decision not to contact a company before writing a B2B cold email.
Ada’s editorial
For this edition, I chose a simple rule: a cold email starts long before the subject line, the opening line or the send button.
It starts with the decision to include a company in a list. With the signal that warrants attention. With the source of the data. With the choice of channel. And sometimes with the most sensible conclusion of all: do not make contact.
When that work is missing, the writing tries to compensate. The email acquires vague praise, artificial urgency and personalisation that merely repeats the company’s name. It looks specific, but it is still a mass message.
Context is not decoration. It is the verifiable reason why that company was selected, the problem that may be worth examining and the boundary that prevents the team from turning sales research into noise.
Recommended reading
-
B2B cold email with real data
A guide to moving from research to first contact without confusing available data with automatic permission to write.
-
Subject line, opening line and CTA: cold email with context
A short playbook for aligning all three parts of the message with the same business reason, without attention tricks or false familiarity.
-
Cold email pack by sector
Working templates to adapt to different sectors. They are starting points for review, not messages ready to send in bulk.
Signal of the week
This week’s signal is simple: the quality of a cold email is measured first by the quality of the selection.
Before writing, the team should be able to answer:
- why this company belongs in the chosen segment;
- which public, relevant signal prompted the analysis;
- where the data being used came from;
- why email is an appropriate channel in this case;
- what small, proportionate next step is being proposed;
- what reason would lead the team to exclude the company without making contact.
If the answers are unclear, changing the subject line will not solve the problem. It is better to return to the research, reduce the list or not send the message.
An operational boundary
This material is editorial and operational; it does not constitute legal advice. Before any campaign, validate the rules that apply to the specific case, the source and use of the data, the appropriate basis for contact, the sender’s identification and the mechanisms for opting out.
An objection must be recorded and respected without friction. Removing an address only from the current spreadsheet is not enough: the team needs a suppression list or equivalent control that prevents new imports, automations or campaigns from reintroducing that contact.
The same care begins before the message. Purchased lists, volume as a goal and data without a clear source do not become legitimate simply because they receive a personalised opening line.
Closing note
The pack in this edition helps structure messages by sector, but no template replaces judgement. My view is simple: if the context does not stand up to a careful review, the message should not go ahead either.
Choose a few companies. Confirm the context. Write directly. Provide a clear way to opt out. And always preserve the option of deciding that the email should never be sent.