Cold Email 3-Touch Sequencer

What it does

You describe your offer, the recipient's role and their likely problem. You get three plain-text emails spread over nine days, written in full and ready to send, each with a body of about 40-60 words.

• Email 1 opens with the recipient's problem as it looks from their role, then one sentence on what you do and your result, and ends with one specific question they can answer in a line. It does not ask for a call.
• Email 2 gives a new reason to reply instead of "just following up": what the problem costs someone in their role, or a detail of how you got your result if you gave one. Its question comes from a different angle, or is even easier to answer.
• Email 3 closes the loop, asks nothing new, makes "no" or "not now" easy, and names a moment when getting in touch would make sense.

Your result is used exactly as you state it, and no other numbers, client names or claims are added. Brackets are kept for the one thing only you can supply: a fact about a single recipient you have to look up. Each email reads complete without it. A few lines at the end give two other subject lines, the pre-send checks that apply and the word counts.

A plain request for a cold sequence tends to produce long emails, a meeting request in the first message and made-up case studies. This prompt rules those out.

Use it when

• You are starting outbound for a service business and need a clean first sequence.
• Your current cold emails are long, full of links or ask for a call straight away.
• You want a sequence you can send as it is, or personalise in a minute per prospect.

Skip it when

• You have no real result or reason to contact this person yet. The sequence depends on both.
• You are writing to existing customers or warm leads. A personal message with context works better than a cold sequence.

The prompt

Write a 3-email cold outreach sequence for me, ready to send.

My offer: [WHAT YOU DO for WHOM, with RESULT]
Recipient: [ROLE] at [COMPANY TYPE]
Their likely problem: [PAIN]
Sign-off: [NAME]

Write every email in full from what I gave above. A slot in [BRACKETS] is only for a fact about one recipient that I have to look up myself, such as one observation about their company. Use at most one per email (the greeting's [first name] does not count), never for the main point of an email, and write each email so it still reads complete if I delete the slot. Do not ask me questions first: if something is missing, write from what is here and name the gap under "Before you send".

Email 1 (Day 1): open with their likely problem as it shows up day to day in their role and kind of company: concrete, in their terms, and true for most people in that position. Then one sentence on what I do and my result. End with one specific question about their situation that they can answer in one line; not a request for a call or a meeting. No links and no attachments.
Email 2 (Day 4): a new reason to reply, not a reminder. Build it from what I gave: what the problem costs someone in their role (time, money, risk or missed results, in plain words), or a detail of how I got the result if I described one. Ask a different question from email 1: another angle, or something even easier to answer.
Email 3 (Day 9): close the loop politely. Ask nothing new and do not repeat an earlier question; make it easy to say no or "not now", and name one specific moment when getting in touch would make sense for them.

For every email: a subject line of five words or fewer, in lowercase, with no hype; a body of about 40-60 words (never over 70), in plain text, that sounds like a busy peer and not a vendor; at most one question. Start with "Hi [first name]," and end with my sign-off. Never write "just following up", "guarantee" or any urgency I cannot back, and use no adjectives about my own service. Use my result exactly as I gave it: do not round it up, and add no other numbers, client names or claims. If I gave no result, do not invent one: build the sequence on the problem and say so under "Before you send".

After the emails, add at most about 60 words in total:
- Other subject lines: two alternatives for email 1, on one line.
- Before you send: only the checks that apply (what to verify or personalise, and an opt-out line if the recipient's country requires one).
- Word counts: one line with the three body counts.

How to use

1. Replace the placeholders:
   • [WHAT YOU DO for WHOM, with RESULT]: one sentence with a result you can prove, for example "I rebuild slow Shopify themes for skincare brands; for my last three clients, mobile product pages went from over 5 seconds to under 2.5 seconds to load". If you know how you got the result, add it in a few words: email 2 can use it.
   • [ROLE]: the recipient's job title.
   • [COMPANY TYPE]: the kind of company (industry and size).
   • [PAIN]: the problem they most likely have, as concretely as you can. Emails 1 and 2 are built on it, so this line matters most.
   • [NAME]: your name as you sign emails.
2. Paste it as the first message of a new chat (see "How to run").
3. Fill or delete the one bracketed slot an email may have, and replace [first name] in each greeting. The emails read complete without the slot; filling it per recipient makes email 1 sharper.
4. Work through the "Before you send" checks.
5. If you write sequences often, keep the prompt with your offer filled in, and change only the recipient lines each time.

How to run (Oct 2026)

• ChatGPT: paste it as the first message, or save it in a Project's instructions with your offer filled in. GPT-6 at Instant or Medium on the Thinking slider is enough for short emails.
• Claude: paste it as the first message, or use a Project with your offer saved in the instructions. Claude Sonnet 5.5 keeps a plain, low-hype tone well.
• Gemini: paste it as the first message, or save it as a skill in the Gemini app (type / and its name). Gemini answers briefly by default, which suits this format.
• GLM: use it through the Z.ai API. GLM-4.7-Flash is free there and enough for short emails; with GLM-5.3, reasoning_effort low is enough for this job.

Example

Input (illustrative)

• [WHAT YOU DO for WHOM, with RESULT]: I rebuild slow Shopify themes for skincare brands; for my last three clients, mobile product pages went from over 5 seconds to under 2.5 seconds to load
• [ROLE]: Head of E-commerce · [COMPANY TYPE]: skincare brand with 10-50 employees
• [PAIN]: paid social traffic leaving slow mobile product pages
• [NAME]: Lena

Output

EMAIL 1 (Day 1)
Subject: slow mobile product pages

Hi [first name],

When paid social traffic hits a slow mobile product page, people leave before seeing the product. [what you saw on their product page]

I rebuild Shopify themes for skincare brands. For my last three clients, mobile product pages went from over 5 seconds to under 2.5 seconds to load.

How long does your product page take to load on mobile?

Lena

EMAIL 2 (Day 4)
Subject: paying for clicks that leave

Hi [first name],

A slow mobile page makes paid social look worse than it is: you pay for every click, but people who leave before it loads never see the product, so each sale costs more. The fix sits in the theme, not the ad account.

Is page speed something your team tracks, or does it sit with an agency?

Lena

EMAIL 3 (Day 9)
Subject: closing the loop

Hi [first name],

I'll stop here so I'm not cluttering your inbox, and if speed isn't a priority, no reply needed. If it comes up later, for example before a big sale or a theme change, I'm happy to look at one product page on a phone and tell you what is slowing it down.

Lena

Other subject lines: product page speed · mobile pages and paid social
Before you send: check that your three clients are fine with being counted; load their product page on your phone and fill the email 1 slot, or delete it; add an opt-out line if the recipient's country requires one.
Word counts (body): 60 / 57 / 52

Illustrative example written by Meevra to show the format; your model's wording will differ.

Troubleshooting

• The emails read like ads. Add "Describe what I do, not how good it is."
• Whole sentences came back in brackets. Reply "Write the emails in full from my offer and their problem. Keep at most one bracketed slot per email, only for a fact about the recipient I have to look up."
• Email 1 asks for a call. Reply "Replace the ask with a question about their situation they can answer in one line."
• The same question appears in every email. Reply "Give email 2 a different question from email 1, and remove the question from email 3."
• A number appears that you did not give. Reply "Use only my result; remove every other number and claim."
• An email runs over 70 words. The word-count line will show it; reply "Cut that email to about 60 words and keep its question."

© 2026 Meevra · meevra.com · Licensed to the purchaser for personal and internal business use.