A first name does not make an email relevant. Start with one company detail you can verify. Then ask whether it connects to the person's stated role, what your team can genuinely offer, and one small next step.
The worksheet turns those notes into a first-touch message. It cannot tell you whether the recipient has a need or will reply.
Start with evidence, not a personalization token
A job title can help explain why a message may be relevant. It does not prove that the person owns a particular problem, is working on a project, or has budget authority.
Look for a company or professional fact that is both current enough to matter and easy to verify. Examples include a public product announcement, a role description on the company's careers page, or a statement on the company's website. Salesforce's prospecting guidance recommends researching the business and looking for a real reason for the timing, rather than contacting someone with no understanding of their company.¹
For each fact, record:
- What you observed: a short, factual note.
- Where it came from: the public page or source.
- When you checked it: useful when the information can change.
- What it does not prove: the limit of your inference.
If no relevant fact turns up, do not make one up. Use an honest role-based opening, research a different contact, or skip the message.
Use the four-part evidence-to-sentence worksheet
Fill in these four rows before drafting. Keep facts separate from hypotheses.
- Verified context: What did the company or person actually say or do, and where can I confirm it? Write one factual sentence and note the source and date.
- Role connection: Why might that fact intersect with this person's stated responsibilities? Explain relevance as a question or possibility, not as a claim about private priorities.
- Supportable offer: What can your team genuinely provide that relates to this situation? Name one specific resource, capability, or next step without an unsupported result promise.
- One clear ask: What is the smallest useful action you are requesting? Ask one direct, low-friction question.
This is a drafting check, not a response-rate formula. Salesforce recommends concise, conversational emails with a low-stakes question and clear next action. HubSpot's examples also pair relevance with a reason for reaching out.²³
Turn the worksheet into a short first touch
Use this as a structure, not a mail-merge template:
Subject: [specific, accurate topic]
Hi [Name],
I saw [verified company fact] on [source]. Since your role includes [responsibility supported by a public source], I wondered whether [related task] is relevant to your team. We can [specific, supportable offer]. Would [small next step] be useful?
[Name]
Keep only what the evidence supports. If you cannot confirm the role, ask whether the issue sits with that team or leave the role line out. Do not promise a result your team cannot substantiate.
Worked hypothetical: turn evidence into one sentence
The names, company, event, date, role, source and offer below are fictional placeholders. None describes a real person or customer story.
Worksheet notes
- Verified context: [Company] announced [initiative] on its public news page on [date].
- Role connection: [Name]'s public profile says they lead [relevant function]. This supports a possible connection, not proof of a current need.
- Supportable offer: [Your team] can share [specific resource it actually provides].
- One ask: Ask whether the person wants the resource sent.
How the notes become an email
The company announcement gives you the opening fact. The role note offers a cautious reason the fact could matter to this person. The resource and question complete the message.
Hi [Name], I saw [Company]'s announcement about [initiative] on its news page on [date]. Your public profile says you lead [function], so I thought [specific resource] might be useful. Would you like me to send it?
Replace each bracket with a fact or offer you have checked. Drop any role or offer clause you cannot support. This example shows a drafting method, not proof of need or a promise of a reply.
Run a claim check before sending
Read the message once for evidence and once for the ask:
- Can I open the source and confirm the company detail?
- Did I describe the person's role accurately, without assuming authority or intent?
- Is the problem framed as a possibility unless the prospect stated it?
- Can my team substantiate every outcome or capability in the message?
- Is there one clear question, with no hidden second request?
- Would the email still be understandable if the recipient has never heard of us?
If a line fails, remove it or rewrite it as a question. One supported reason is more useful than several decorative personal details.
Where contact discovery fits
If you already know the company context but still need to identify relevant people, RadarLeads can help search business contacts by job title and company and export selected contacts as a CSV. The public site says verification status is shown where available; treat that as contact-data context, not proof of a current company trigger or of the claims in your email.⁴
Find the contact, then verify the context independently before using it in outreach. A database match can help you locate someone to research; it cannot establish that person’s current priorities or make an unsupported message relevant. Create a free RadarLeads account to explore a segment.