Email sequence templates
Freelance client outreach: a three-message template
A focused offer for one observable problem, with a small list and a clear stopping point.
Adapt the example to your audience and check every claim before sending. Use the copy button on each message, or download its body as text. Copy the initial subject separately. Merge fields are preserved for your campaign editor.
Use this sequence when you have a relevant service, a verified observation and an appropriate contact route. It offers a small deliverable before asking for a larger commitment.
The designer, issue and messages below are fictional. Replace the finding and sender identity with facts you can support. A public contact address alone does not establish permission; check recipient expectations and applicable requirements.
Prepare the contact and the offer
This example assumes the organization explicitly accepts supplier enquiries and you have checked its current instructions. The service is a mobile form review. The specific finding is a submit button hidden by a fixed banner on a narrow screen.
Required merge field: firstName, with there as its readable fallback. The observed issue is written into the campaign copy after research; it is not a guessed field.
Use a separate campaign or carefully reviewed contact-specific content if observations differ. Do not send the same claim to everyone.
Message 1: offer something specific
Initial subject: Mobile enquiry form question
Hi {{firstName | there}},
Your site lists this address for supplier enquiries. On a narrow phone screen, the enquiry form's submit button sits behind the fixed contact banner.
I design mobile forms. I can send a short recording showing the overlap and one possible layout change.
Would you like me to send it?
MayaFreelance website designer
If you prefer not to hear from me again, reply and I will stop.The offer should be deliverable without inventing a conversion gain or requesting private account access.
Message 2: add a useful clarification
Use only if there has been no reply, bounce or opt-out and continuing remains appropriate. An illustrative three-day delay is not an optimal-timing claim.
Hi {{firstName | there}},
One detail I should have included: the overlap appears at the narrow layout. The desktop form remains visible.
I can send the recording by email, so you would not need to book a call to see the issue.
Would that be useful?
Maya
If this is not relevant, reply and I will stop.Recheck the observation before using this. Do not fill a follow-up with a new claim you have not verified.
Message 3: close the loop
If a final message is appropriate, send it after another considered gap, then end the sequence.
Hi {{firstName | there}},
I will close this out after this message.
If you would like the short recording later, reply here and I can send it. Otherwise I will leave it with you.
Thanks,MayaHonor the stopping promise. Do not restart the same pitch from another inbox.
Replace the facts, then deliver the promised recording
| Copy element | Replace with |
|---|---|
| Supplier-enquiry statement | The actual contact route and current instructions |
| Mobile form finding | A reproduced issue, including the relevant layout |
| Service and signature | Your real work and sender identity |
| Recording offer | An artifact you can prepare and share |
| Follow-up limit | A stopping promise your workflow will enforce |
After someone asks for the recording, end the automated introduction and reply personally:
Hi Alex,
Here is the recording I offered: [insert the actual permitted recording link].
It shows [the verified interaction and layout]. One possible change is [a suggestion you can explain]. I have not measured its effect on enquiries.
Would you like a scoped proposal for reviewing the form, or is the recording enough for now?
MayaThe square brackets are writing prompts, not merge tokens or working links. Replace them before sending. Use the campaign-writing guide to prepare the subject, message and sending settings.
Check the sequence in ColdMerge
Follow-ups are replies in the existing thread, without separately entered subjects. Keep the initial subject accurate; do not add a fake Re: to manufacture familiarity.
Preview a named contact and a contact without a first name. Hi there, is intentional, not an empty token. Field names are case-sensitive. Use the merge-token reference.
A detected human reply stops this campaign’s follow-ups; automatic replies continue. Mark a reply asking to stop as opted out. Read How unsubscribes work before launch.
For the audience selection and review process, use the campaign launch guide.
Check opt-out controls before launch
ColdMerge’s unsubscribe footer and one-click header start off. Review and enable the appropriate controls before sending. A reply asking to stop does not automatically suppress the address across campaigns: choose Mark as opted out manually. That suppression applies across the Organization. See How unsubscribes work for the configuration and recipient behavior.
No card required to start. Invited testers get the same 14-day free trial, and the plan is $0.99 a month if you subscribe.