EN
Ihor Nikolenko- Why a "blast to everyone" stays silent while a sequence sells
- Where the list comes from: the entry point into the sequence
- The seven emails in a sequence: what each one does
- Subject lines by headline formula
- Deliverability: three settings without which your emails never arrive
- What to measure and how not to break trust
- Where the sequence leads
- In short
- Questions people ask most often
You have a list. A few hundred or a few thousand addresses collected from forms, webinars, and orders. And it's silent. Once a quarter you write "we have a promo" to everyone at once, get a couple of unsubscribes and zero sales, and conclude that email doesn't work. What's actually not working isn't email. What doesn't work is one email "to everyone about everything," sent to people standing on different rungs and expecting different things.
This matters right now for a simple reason. Social networks and messengers rent you attention: reach is there today, the algorithm changes tomorrow. Your address list is the one thing that actually belongs to you. It's a channel you can switch on any night, measure down to the individual email, and scale without negotiating with a platform. And it keeps working after you close your laptop, if it's built as a sequence instead of a blast.
In this article I'll cover how a sequence differs from a blast, where a list comes from, what seven emails make up a sequence, how to write subject lines using headline formulas, why deliverability depends on three domain settings, and what to measure so you don't break trust.
Why a "blast to everyone" stays silent while a sequence sells
A blast is a single email sent whenever you feel like it. A sequence is a chain of emails triggered by something a person did: subscribed, downloaded, registered, didn't pay. The difference is fundamental. A blast gets read by whoever happens to be in the right frame of mind that particular day. A sequence gets read by everyone at their own pace, from the first email to the last, because it follows their step, not your calendar.
Every email in the sequence does one thing and moves the person up one rung. The first confirms she made the right choice. The next ones show the problem, the method, the proof. Only after that comes the offer with a condition. Trying to sell in the first email is the same as quoting a price before the person understands what she's buying.
Where the list comes from: the entry point into the sequence
The sequence starts with an entry point, and the entry point has to be honest. A person leaves her address in exchange for a specific promise: a checklist, a recording, a template, a calculation. The promise has to address her problem — the product can wait — and it has to be delivered in the first email, or the whole sequence starts with disappointment.
Three things, without which a list poisons itself. Consent: the person knows she'll be getting emails, and that's stated next to the form where it's visible, not buried in fine print in a policy. Address confirmation: double opt-in filters out mistyped and unowned addresses, and your sender reputation only gains from it. And no purchased lists, ever: addresses of people who don't know you generate spam complaints, and complaints kill deliverability for everyone who's actually waiting for you.
The seven emails in a sequence: what each one does
- The promised thing. Right after signup: what the person came for, plus one sentence about what's coming next and how often.
- The story. Why you do this work. Not a biography — the specific moment you saw the problem you now solve.
- The problem, in her words. The same five to ten pain statements from your avatar. She reads it and thinks: "this is about me."
- The method. How it gets solved, step by step. You show her there's a path and hand her the map.
- Proof. Verifiable facts: projects, documents, process, your experience. No adjectives.
- The offer with a condition. Who it's for, what it is, the result, the timeline, the price or how to get it, what happens if it doesn't work out.
- The deadline. The final email with an honest limit: a date, a number of spots, or a condition that genuinely expires.
The pace of a sequence depends on the product, but the principle is the same: one email a day or two while the person's still warm, no "silence for a week" inside the chain. After the seventh email, people who didn't buy shift into a calmer mode: one useful email every week or two, and a return to the sequence whenever a new occasion comes up.
Subject lines by headline formula
A subject line gets scanned the same way as a landing page headline: one second to decide "open it or not." So it's written with the same formulas as headlines in the D.N.A. launch model: result plus condition, "without X," a contrast, a question the reader is already asking herself. I write five to ten variants for every email and keep the one that names the reader's situation most precisely — not my product.
The preheader — that line visible next to the subject — continues the thought instead of repeating it. It's best to avoid capital letters, exclamation points, and words like "free" in the subject line: they hurt both open rates and spam filter trust. A first name in the subject line only works if the list has it correctly stored, otherwise "Dear {name}" wrecks everything you've built.
Deliverability: three settings without which your emails never arrive
The best sequence in the world is worthless if it lands in spam. Deliverability depends on whether mail servers trust your domain, and that trust is built from three DNS records: SPF, DKIM, and DMARC. SPF states which servers are allowed to send email from your domain. DKIM signs every email so the recipient can verify it wasn't tampered with. DMARC spells out what to do with emails that fail these checks and sends you reports.
This isn't "a job for IT people" — it's half an hour in your domain panel, following your email service's instructions. Three more rules: send from your own domain, since free email addresses won't cut it; start with small volumes so your reputation warms up; and keep your unsubscribe link somewhere visible, because someone who can't find it will hit "spam" instead, and that's worse than an unsubscribe. Services like SendPulse or Mailchimp will show you which of these records aren't set up yet.
| Email type | Goal | When it's sent | What we measure |
|---|---|---|---|
| Welcome sequence | Deliver the promise, move up one rung | Automatically after signup | Opens, clicks per email, replies |
| Warm-up before the offer | Show the problem, method, proof | Before a launch or within a sequence | Clicks to the page, read-through |
| Sales email | Offer with a condition | After the warm-up | Clicks to the offer, payments |
| Deadline | An honest limit | Last day | Payments on the final day |
| Abandoned cart or form | Bring them back to an unfinished action | A few hours after the action | Completed actions |
| Regular value email | Stay top of mind | Once a week or two | Replies, unsubscribes, returns to the sequence |
What to measure and how not to break trust
Three metrics show up in any service: opens, clicks, and replies. And one you can only see yourself: how many people from the sequence reached payment. Don't chase opens on their own — they depend on the subject line and the mail client. Look at clicks after each email: that's where you see exactly where the sequence "sags," and that's the email you rewrite first.
Three things break trust. A frequency the person never chose. Emails with no sender you can reply to — use a real address and read the replies, it's the cheapest audience research there is. And promises in the subject line that aren't in the body. Every such open costs you one future ignore.
Where the sequence leads
An email sequence doesn't exist on its own. It's part of a funnel: it leads to an automated webinar, a video sales page, a consultation, or a page with a deadline. So you design the route first — where the person enters, what she sees, where she goes after the seventh email. Then you write the emails.
If you want to build that whole route, from the sign-up page to automated sales, it's broken down node by node in the Master of Automated Webinar Funnels course. And if you want someone walking alongside you toward your first systematic sales, that's what launch support is for.
In short
- A blast fires on your calendar, a sequence fires on the person's action. The sequence sells.
- The entry point is an honest promise about the person's problem, visible consent, and address confirmation.
- Seven emails: the promised thing, the story, the problem, the method, proof, the offer with a condition, the deadline.
- Subject lines are written with headline formulas, five to ten variants per email.
- SPF, DKIM, and DMARC on your own domain decide whether your emails arrive at all.
- Watch clicks after every email: that's where you see what to rewrite.
- The sequence leads to the next funnel node, so map the route first, then write the emails.
Questions people ask most often
My list is small. Is it worth building a sequence?
That's exactly when it's worth it. A sequence gets written once and works for every new subscriber, so the sooner it's in place, the fewer people slip past. List size affects how many sales you get, not whether you need the system.
How often should I email so people don't unsubscribe?
As often as you promised at the entry point. Inside a sequence, an email every day or two feels normal, because the person just asked for it. Outside the sequence, once a week or two. Unsubscribes after a useful email are normal — those are people who wouldn't have bought anyway.
Does a Telegram channel replace an email sequence?
No, they work as a pair. A channel gives you speed and closeness, email gives you long-form text, automated chains, and ownership of the list. The same sequence can run through both channels, but email drives it, because that's where action-triggered automation lives.
How many sales emails can I send in a row?
The offer and the deadline, two or three emails, after five useful ones. If sales emails outnumber useful ones, your list burns out after one launch.
