A first message needs a defensible reason for contact, not clever personalisation. A follow-up needs a new reason to re-enter the conversation. If neither exists, stop.
Pass a respectful targeting gate
A public email address or profile does not automatically make a sales message relevant. Before adding a person to a contact list, write down why this role, at this organisation, in this context, could reasonably care about the problem.
| Gate | Question | Stop when |
|---|---|---|
| Role fit | Does this person appear to own, perform or evaluate the workflow? | The role is merely nearby and you are hoping for a referral. |
| Business context | What professional fact makes the problem relevant now? | The only detail is personal, sensitive, stale or unrelated to the offer. |
| Source | Where did the contact detail and context come from? | You cannot document the source or its permitted use. |
| Expectation | Would the recipient understand why this specific business message reached them? | The connection requires a long explanation or invented familiarity. |
| Channel and rule | Do applicable requirements and platform policies support this kind of contact? | You have not checked, or the context prohibits solicitation. |
| Suppression | Has the person or organisation declined, opted out or asked not to be contacted? | Any suppression signal exists. Do not route around it through another channel. |
Respectful targeting reduces the list. That is the point. Research should disqualify poor contacts before a message reaches them.
Build the reason for contact
The opening can usually be assembled from four records:
Reason-for-contact record
Weak:
“I saw your impressive company and wanted to reach out. We help innovative teams streamline operations and save time. Are you free for a quick call?”
The compliment proves nothing, “operations” is undefined and the call asks for time before the recipient can judge relevance.
An explicit first-message example
Illustrative message, not a tested campaign or customer result. Assume the sender has a product that turns emailed site updates into a draft weekly report. A construction firm has publicly advertised for a project coordinator whose listed duties include collecting site updates. That job posting is the only known context; the sender does not know how the firm handles the work.
Subject: Question about collecting site updates
Hi Jordan,
Your project coordinator posting mentions collecting updates for weekly reports. I’m working on a small product that turns emailed updates into a draft report with unresolved items left for review.
I do not know whether your team handles reports that way. Is collecting the updates itself a problem, or is the harder part somewhere else?
If this is irrelevant, a brief no is enough and I will close the contact.
Sam
The message separates observation from hypothesis. It describes the product without claiming a result. It also gives the recipient a simple way to end the contact.
Personalisation that should stay out
- Do not mention family details, private activity or sensitive personal information to prove you researched someone.
- Do not call a generic company-page detail “something I noticed about your work” when it has no connection to the problem.
- Do not imply a referral, relationship or customer base that does not exist.
- Do not claim “similar companies save…” without a documented, applicable source and permission to use it.
- Do not use hidden tracking or channel switching as a substitute for a reply. Review the rules and expectations that apply to your setup.
Three follow-up options, not a fixed sequence
The title names three useful follow-up types. It does not mean every prospect should receive all three, or that they belong on a universal schedule. Choose one only when it adds information and the contact remains appropriate.
1. Clarify the reason
Use this when the first message may have left the workflow unclear. Do not simply restate the pitch.
Hi Jordan,
I may have made the question too broad. The product only handles one step: turning emailed site updates into a draft report and flagging missing items for review. It does not manage the full project.
Does that step sit with your coordinator, or should I close this as a non-fit?
2. Add an inspectable example
Use this when a sample can help the recipient assess relevance without booking a call. Make clear whether the data and outcome are fictional.
Hi Jordan,
I made a sample showing the input email, the draft report and one unresolved update. It uses fictional data and does not claim a customer result.
If reviewing that would help you answer the workflow question, I can send it. If not, no action needed.
3. Close the contact
Use this when there is no new evidence to add or when another attempt would create pressure rather than clarity.
Hi Jordan,
I’m closing this contact so I do not keep adding messages to your inbox. I will not follow up again about this offer.
Sam
Do not send even a closing note when the recipient has already opted out, objected or when applicable rules and channel expectations indicate that you should simply stop.
Keep a message and follow-up decision log
| Field | Entry |
|---|---|
| Recipient and role | Who was considered, and what makes the role relevant? |
| Source and observed context | Where did the business contact and trigger come from? Record the date. |
| Permission/rule check | Which applicable law, channel policy, community rule or relationship context was checked? Escalate uncertainty instead of asserting compliance. |
| Message version | Exact reason for contact, problem hypothesis, product statement and ask. |
| Response or silence | Record what happened without treating silence as interest, rejection or permission. |
| New reason to follow up | Clarification, requested information, inspectable example or none. |
| Decision | Send, wait, stop, suppress or ask for compliance review. |
| Suppression record | Opt-out, objection, wrong person, closed contact and any organisation-level restriction. |
| Learning | Targeting issue, message confusion, non-fit reason or product question. Do not infer more than the response supports. |
Decide without a universal cadence
Timing depends on the channel, the original context, the recipient’s behaviour and applicable requirements. A buying cycle does not create permission by itself. Before any follow-up, ask:
- Has the person replied, declined, opted out or requested information?
- Is the original reason for contact still current?
- Do I have new information that helps them assess relevance?
- Would waiting change the interpretation, or am I using delay as an excuse to resend?
- Does the channel permit this action, and is the suppression record clear?
- Would I be comfortable explaining this message and its data source to the recipient?
If the answer does not support another message, stop. No fixed number of follow-ups can make an irrelevant contact respectful.