A first email has one job: give a relevant person enough context to decide whether to reply. A company’s hiring activity can help explain why you chose to contact it, but a vacancy does not prove that the team needs outside help, has a budget or is ready to buy. Keep the message close to what you can verify.
Before drafting, confirm that the company fits your service, the role or hiring detail is current, and the recipient’s responsibilities are plausibly connected to your offer. If any part is uncertain, remove it or do more research rather than turning a guess into personalisation.
Begin with a real reason
Choose one observation that makes the message relevant. It might be a current listing for a role related to your service, a team expansion described by the company, or a location where you can provide support. State only the part that is both public and useful to the recipient.
Then connect that observation to your own work in one plain sentence. For example, a provider of maintenance staffing could explain that it supplies qualified maintenance workers in a specific region. That is more useful than a broad claim about helping companies scale, and it does not imply that the recipient has a staffing problem.
Avoid opening with a compliment that could apply to any company, a claim that you have been following the recipient for years, or a statement about their internal situation that they have not confirmed. Relevance comes from a clear connection, not from making the email sound unusually familiar.
Write a clear subject line
Use a short subject that accurately describes the topic. A verified role or function can be enough context. Do not suggest there is an existing relationship, urgent issue or promised result when there is not. Avoid adding the recipient’s name merely to make a generic subject appear personal.
Keep the subject consistent with the body. If the email is an introduction about a service, do not frame it as a reply, an account notice or a private opportunity. The recipient should be able to understand what kind of message it is before opening it.
Draft the subject after the body so it reflects the actual point of the email. Remove vague urgency, unexplained abbreviations and claims of familiarity that could mislead the recipient. If you are writing to a role-based address or a shared team inbox, avoid a subject that pretends to be a personal conversation with a named individual.
A useful test is whether the subject would still feel accurate if the recipient forwarded the message to a colleague. If it depends on an inside joke, an implied referral or a supposed prior discussion that never happened, choose a clearer description instead.
Build a short message
A practical first email can follow four steps: say why you chose the person, name the verified context, describe your service briefly, and ask one simple question. A flexible draft might look like this:
Hi {Name}, I saw that {Company} is hiring for a {verified role}. We provide {specific service} for {relevant team or setting}. Is this something you oversee, or would another colleague be a better person to ask?
Replace each placeholder with information you have checked. If the name, role or team is not available, remove it. Describe what you do rather than promising a result, and make the question easy to answer with a short reply or a redirection.
Keep the message focused on one service and one reason for contact. A list of capabilities, several links and multiple requests make the recipient work harder to understand the point. Share additional detail after they indicate that it is relevant.
Adapt the message to the verified context
The same structure can work across services, but the reason for writing should match what you actually know. A workforce provider might mention an employer-posted warehouse role and state which worker types it recruits nearby. A technical consultancy might refer to a public opening for a specialist role, while recognising that the company may be building that capability internally. An outsourced operations provider might describe the specific process it supports and ask whether that responsibility sits with the recipient.
These examples should not be turned into claims about a shortage, project or purchase plan. The point is to connect a verified observation to a service in a way the recipient can confirm or correct. If the connection needs several sentences of explanation, the company or contact may not be a strong fit for that message.
Keep a small set of approved message components if more than one person sends outreach. Shared wording can help maintain accurate service descriptions and required sender details, but each message still needs a real company reason and a relevant contact. Do not copy a personalisation line across accounts when its underlying fact applies to only one of them.
A useful service description answers three questions without turning the email into a brochure: what work you do, which type of team it supports, and where or under what conditions you can deliver it. Leave out features that do not connect to the reason for writing. If the recipient needs more detail to assess fit, invite a short reply rather than attaching a long catalogue of services.
Put the reason for writing near the beginning. A long introduction about your company makes the recipient wait to understand why the email is relevant. Use a short sign-off with your real name, role and business identity. If the channel or market requires an address, privacy notice or unsubscribe method, include it in the format that applies to your campaign.
Keep the first request proportional to the amount of context you have provided. Asking whether the topic belongs with the recipient is usually a smaller commitment than asking them to schedule a long call, share internal plans or review a proposal. You can offer a next step, but do not imply that a reply is owed.
Before sending to a group, read the message aloud and remove phrases that sound like a pitch deck. “We are the leading provider” is not useful unless you can support the claim and it matters to the recipient. A plain description of the service, the types of teams it supports and the relevant geography is easier to assess.
Check before sending
Read the draft once from the recipient’s point of view. Check that:
- The company, person, role and location are correct and current.
- The observation supports the reason for contact, without implying a need you cannot know.
- The service description is specific and accurate.
- The question is clear, low-pressure and relevant to the person’s role.
- The message includes the identification and opt-out details required for your market and channel.
If you cannot verify a detail, leave it out. A concise message with one accurate reason is preferable to a longer note assembled from weak signals. Keep a record of the source and date you checked so the context can be reviewed before a follow-up.
Follow up with care
Check that the message renders as intended on a small screen. Use short paragraphs, ordinary punctuation and links only when they help explain the offer. Avoid attachments in an initial cold introduction unless the recipient has asked for them or the context clearly calls for one. Make sure a link points to the page you describe and that the destination represents your business accurately.
Also verify the sending details: the sender name should identify a real person or a clearly named team, the reply address should work, and the signature should not promise availability that you cannot provide. Correcting these basics is part of relevance because they help the recipient understand who is contacting them and how to respond.
No reply does not tell you why someone did not respond. If a follow-up is appropriate, keep it brief, refer to the same factual context and add only useful information. Do not manufacture a new reason to write or switch channels just to get around silence. Stop when the person replies, asks not to be contacted, or the information is no longer current.
Measure whether the messages are reaching the right people and starting relevant conversations, not whether one phrasing guarantees a sale. Review replies and opt-outs by segment, and adjust the research or service fit when the pattern suggests the audience is wrong.
Do not send a follow-up simply because an email platform reports an open or click. Automated security checks and privacy features can make those events hard to interpret, and they do not prove that the recipient wants to hear from you. Base another contact on the context, your follow-up policy and applicable rules, not on a claim that you watched the person’s activity.
Keep a consistent record of replies, redirects and requests to stop. If someone says that another colleague handles the topic, update the contact path rather than continuing to message the first person. If the recipient declines or opts out, honour that response and suppress the address as required by your process.
For the steps before writing, see our guides to finding companies hiring and choosing a relevant decision-maker. This article is practical guidance, not legal advice; check the rules that apply to your audience and channel.
For a respectful next step after sending, read our guide to following up on a B2B email and knowing when to stop.
If identifying suitable companies and contacts is taking longer than writing the message, you can review our company research options before deciding how to build your prospect list.