B2B lead generation
Cold Email Templates We Recommend Adapting to Your Offer
· Updated
We suggest using a template to organize accurate information, rather than to supply facts about you or the prospect. The two examples below focus on introducing a lead-generation service and introducing freelance design work.
Treat both examples as illustrative drafts. Replace each bracket only with information you can support, and review sending requirements separately. Neither example represents a successful campaign or an expected response rate.
Choose the parts you can honestly fill in
Before choosing the wording, write down the intended recipient, the relevant public detail and the deliverable you can perform. Check that the connection between them makes sense. A template does not establish that the person wants the service or that their business has the problem you suspect.
Review existing proof separately from a proposed outcome. If you have a relevant example, describe it accurately. If you do not, remove the proof sentence rather than claiming clients, awards or revenue results you cannot substantiate.
Consider an introduction for a lead-generation service
Consider this illustrative subject: “A question about [specific service or market]”.
Consider this illustrative message: “Hi [name], your [public page or announcement] mentions [accurate relevant detail]. We offer [defined lead-generation deliverable] for [specific audience]. Would discussing [concrete scope] be useful for your team? [Sender name, company and contact information].”
Check the first sentence against the actual public source. The next sentence should describe the work, rather than promise an increase in sales. Review whether the final question gives the recipient a specific conversation to consider.
Consider keeping the service introduction and request to connect specific. Add a substantiated proof example only if it fits this offer and recipient, and avoid predicting what the conversation will produce before understanding the situation.
Consider an introduction for design work
Consider this illustrative subject: “Design support for [specific project or material]”.
Consider this illustrative message: “Hi [name], your [accurate public project or material] on [source] caught our attention. We offer [specific design service] and thought that scope might be relevant to your team. Here is [a relevant portfolio example you can share]. Would a conversation about [defined project scope] be useful? [Sender name, portfolio and contact information].”
Choose a portfolio example that shows the kind of work being offered. Do not imply the prospect has commissioned a project, needs a redesign or has a problem they have not confirmed. If there is no relevant public project, change the opening instead of inventing one.
Review any mention of similar clients or industry recognition as an optional fact to substantiate, not a credential that comes with the template. Keep the introduction useful without borrowing achievements you do not have.
Review what a reply would mean
Decide who will check replies and what counts as interest, a referral, a request for clarification or a request to stop. A positive reply is not the same as a booked meeting or a signed client. Keep those steps separate when reviewing the campaign.
Client Ascension related reading: review the planning and review guide for buyer fit, sending checks and response ownership. Keep those operating decisions separate from editing the wording of a template.
Check the details outside the template
For messages to personal Gmail accounts, Google’s sender guidance says subjects and other message elements should accurately represent sender identity and message content, without being misleading. Check the completed example against those requirements before sending.
Before using either example, review the sending provider’s requirements and the rules applicable to your situation. These short examples are not complete ready-to-send compliance documents. Add accurate sender and contact details, review opt-out handling and make sure any request to stop is acted on across the tools you use.
Finally, read the completed message aloud. Check for unsupported assumptions, unexplained promises and empty placeholders before evaluating whether the message is appropriate to send at all.
Prepared by Client Ascension with AI assistance. Documentation checked 2026-10-29.





