One Two Three Send

Author: onetwothreeadmin

The five subject-line formulas that train readers to ignore you

You’ve got a subject line formula. Maybe it’s [Topic] + [Number]. Or “This week in [Category].” Or the classic emoji + question format. It works—your open rates are steady, maybe even good—so you keep using it.

Here’s the problem: your readers have learned the pattern. And patterns don’t create curiosity. They create autopilot behaviour.

When your subject lines follow the same structure week after week, you’re not building brand recognition. You’re training your audience to make snap judgements about whether this edition is worth their time based purely on the formula, not the substance. And increasingly, the answer is no.

The comfort trap of templated subject lines

Subject line templates are seductive. They’re efficient. They remove decision fatigue. Your Monday edition always starts with “Monday Briefing:” and your readers know what to expect.

Except “knowing what to expect” is precisely the problem. The inbox isn’t a reliable delivery mechanism anymore—it’s a battleground for attention. And attention doesn’t go to the predictable; it goes to the unexpected.

When your subject line follows a formula, your reader’s brain doesn’t need to engage. It can categorise and dismiss in milliseconds. “Oh, it’s the Friday roundup. I’ll catch it later.” Later never comes. The pattern has done its job: it’s helped your reader feel informed without actually opening.

This isn’t about your open rate dropping off a cliff. It’s about the slow, invisible erosion of engagement. Your most loyal readers still open out of habit. But new subscribers? They’re learning the pattern before they’ve learned the value. And they’re gone before you notice.

Why variability beats brand consistency here

There’s a persistent myth that subject line consistency builds trust. That readers need to recognise your email in the inbox before they’ll open it.

That’s confusing two different jobs. Your from name builds recognition. Your subject line’s job is to create a reason to open this particular edition. Not your newsletter in general. This one.

The operators seeing the strongest sustained open rates aren’t the ones with the tightest templates. They’re the ones whose subject lines feel hand-written for each edition. They vary sentence structure. They shift tone. They surprise.

One week it’s a statement. The next, a fragment. Then a question that doesn’t follow the usual format. The through-line isn’t structural—it’s voice. And voice can flex without breaking.

Your readers don’t need a formula to recognise you. They need a reason to stop scrolling. And repetition, no matter how on-brand, isn’t a reason.

What to do instead

This doesn’t mean every subject line needs to reinvent the wheel. It means breaking the autopilot cycle—for you and your readers.

Start by auditing your last twenty subject lines. If you can predict the structure of number twenty-one before you’ve written it, your readers can too. And if they can predict it, they can dismiss it.

Try writing three subject lines per edition instead of one. Not A/B test variations—three genuinely different approaches. Different lengths, different tones, different structures. Then pick the one that feels most true to this edition’s content, not your brand template.

Give yourself permission to break your own rules. If you always ask questions, make a statement. If you always go short, stretch long. If you never use a colon, use one. The point isn’t chaos—it’s that each subject line should feel like it was written for the thing inside, not pulled from a drop-down menu.

And pay attention to your replies. Not your open rate—your replies. Because the readers who hit reply are the ones who were genuinely surprised, delighted, or provoked by what they found. That’s the signal. If your subject line formula is working, you’ll see it there first.

The real cost of efficiency

Templates save time. But they cost attention. And in the inbox, attention is the only currency that matters.

Your subject line isn’t a label. It’s a promise that this edition is worth interrupting whatever else your reader was doing. And promises that sound identical every time stop feeling like promises. They start feeling like noise.

If you want your newsletter to feel essential rather than routine, your subject lines need to feel written, not generated. That takes more time. It takes more thought. But it also means your readers can’t predict—and therefore can’t ignore—what you’re about to say.

If this resonated, reply and tell me what subject line formula you’re trying to break. I read every response, and the best operator insights end up shaping future editions of One Two Three Send.

4 May 2026
Send frequency is a retention decision, not a content one

You’ve been thinking about send frequency backwards. Most newsletter operators treat cadence as a content problem: “Do I have enough to say twice a week?” or “Will people get annoyed if I send daily?”

But frequency isn’t a content question. It’s a retention engineering decision that shapes how subscribers relate to your newsletter, how they process your subject lines, and whether they remember you exist between sends.

The operators who crack this understand something counterintuitive: the gap between sends does more to determine your open rate than what’s inside them.

Expectation decay starts the moment you send

Every time you send, you’re making a promise about when you’ll appear again. Send on Tuesday three weeks running, then go quiet for nine days, and you’ve just taught your subscribers that your schedule is unreliable background noise.

This isn’t about perfectionism. It’s about recognition patterns. Your subscribers aren’t keeping a spreadsheet of your send dates—they’re building a subconscious model of when you show up. Break that model, and your next subject line gets processed differently. It doesn’t trigger the same “oh, it’s them” recognition. It gets treated like a cold email from a half-remembered sender.

The retention damage happens silently. People don’t unsubscribe when you go from weekly to whenever-you-feel-like-it. They just stop opening. Your newsletter drifts from habit to clutter, and you never see the metrics that tell you why.

Frequency determines who self-selects in

Here’s what most operators miss: your send frequency is a filter that determines your audience composition before anyone reads a word.

Daily senders attract a different subscriber psychographic than monthly senders. Not better or worse—different. Daily trains people to skim, to expect brevity, to treat your newsletter like a morning ritual. Monthly trains people to expect depth, to set aside time, to feel like they’re missing something if they skip.

When you’re inconsistent, you don’t get a blend of both. You get people who don’t know what to expect, which means they don’t build the behaviour patterns that drive retention. Your opens become dependent entirely on subject line performance, because there’s no habit layer underneath.

The smartest move isn’t finding the “optimal” frequency. It’s picking one that matches the subscriber behaviour you want to encourage, then defending it ruthlessly. If you say weekly, send weekly. If you go daily, don’t skip Tuesday because you had a slow news cycle. The consistency is the content strategy.

The real cost of “whenever it’s ready”

Publishing when you’ve got something worth saying sounds principled. In practice, it’s a slow-motion retention disaster.

Irregular cadence destroys your ability to build anticipation. Anticipation is what keeps engaged subscribers engaged—it’s the gap between “I know this is coming” and “it’s here.” Without predictable timing, there’s no gap. There’s just surprise, and surprise doesn’t compound into habit.

Worse, irregular sending makes every edition a re-introduction. You’re not picking up a conversation; you’re restarting one. That’s why sporadic newsletters lean so hard on recap sections and “it’s been a while” throat-clearing. You’re spending words rebuilding context that consistent senders get for free.

The operators who send “whenever it’s ready” eventually notice their open rates trending down and blame content quality. But the content isn’t the variable that changed. The expectation environment around it did.

How to pick (and hold) your frequency

Start by asking what behaviour you’re trying to build, not what you can sustain content-wise. Do you want to be a daily habit, a weekend read, a monthly deep-dive? Let that answer set your frequency, then reverse-engineer the content format to fit it.

If daily feels unmanageable, the solution isn’t “weekly-ish.” It’s daily with a format so constrained that you can’t fail to ship: three links, one paragraph, done. If monthly feels right but you worry about being forgotten, add a mid-month brief check-in that doesn’t break the expectation of your main edition.

Once you pick, commit for at least twelve weeks. Frequency changes are retention resets. Every time you shift cadence, you’re asking subscribers to relearn when you exist. Do it too often and they stop trying.

And if you’re currently inconsistent, don’t grandfather yourself into “flexible.” Pick the frequency you can actually hold, announce it in your next send, and start the clock. Your open rates will tell you within a month whether you’re building a habit or just adding to the pile.

If this shifted how you’re thinking about your send strategy, reply and tell me what frequency you’re committing to. I read every response, and the answers always surprise me.

3 May 2026
The plain-text version that secretly halves your delivery

Every HTML newsletter you send includes a hidden twin: the plain text version. You’ve probably never looked at it. Your ESP auto-generates it, strips out the formatting, and sends it along for the ride. Job done.

Except it’s not done. That plain text version isn’t just a technical formality for ancient email clients. It’s read by spam filters before your message hits the inbox. It’s served to subscribers using assistive technology. And roughly 10–15% of your list has their client set to display plain text by default, either for bandwidth, security, or simple preference.

When your plain text version is broken, illegible, or littered with rendering artefacts, you’re not just offering a poor experience to a minority of readers. You’re sending mixed signals to the infrastructure that decides whether your newsletter gets delivered at all.

What auto-generated plain text actually looks like

Most platforms generate plain text by stripping HTML tags and guessing at structure. The results are predictably bad. Link URLs appear in full, often mid-sentence. Navigation elements, social icons, and footer legalese appear in random order. Image alt text may vanish entirely, leaving contextless gaps. If you’ve used buttons, they often render as naked URLs with no explanatory text.

Even worse: if your HTML uses tables for layout (still common in email templates), the plain text version can scramble reading order completely. A two-column layout might interleave sentences from both columns, making the whole message unintelligible.

Spam filters notice. A newsletter where the plain text version is drastically shorter, structurally garbled, or filled with broken formatting signals a sender who isn’t paying attention to technical hygiene. It’s a small red flag, but reputation is built from small flags.

Why accessibility isn’t optional

Screen readers don’t parse your beautifully art-directed HTML. They consume the plain text version, or read the HTML semantically if no plain text exists. If your auto-generated version is a mess, you’ve just made your newsletter inaccessible to blind and low-vision subscribers.

This isn’t a niche concern. Assistive technology users are overrepresented among newsletter audiences, particularly in professional and educational niches. They’re also among your most loyal readers—if you don’t chase them away with illegible formatting in the first three sends.

Even subscribers without disabilities sometimes switch to plain text mode when travelling, on poor connections, or using privacy-focused clients that block remote images by default. If your plain text version assumes they’ll see the HTML, you’ve lost them.

How to fix it without doubling your workload

Start by actually looking at the plain text version your platform generates. Most ESPs show it in the send preview. If yours doesn’t, send yourself a test and check your client’s view options. What you’re looking for: legibility, logical reading order, and whether calls-to-action still make sense.

If it’s a disaster, you have two options. First: clean up your HTML structure. Use semantic headings, keep layouts simple, avoid complex tables, and write descriptive link text instead of “click here.” Many rendering problems fix themselves when the source HTML is cleaner.

Second: write a custom plain text version. Most platforms let you override the auto-generated one. This sounds like extra work, but it’s faster than you think. You’re not redesigning the newsletter—you’re just ensuring the message makes sense in a linear, unformatted reading. Strip theNav. Shorten footer legalese. Make link context explicit. A tight 400-word plain text version often works better than a bloated 800-word HTML piece.

One operator trick: use your plain text version as an editing tool. If the message doesn’t hold up without formatting, images, and design crutches, the HTML probably isn’t as clear as you think.

Test it like you test subject lines

You’d never send a newsletter without checking the subject line. The plain text version deserves the same scrutiny. Build it into your pre-send checklist: preview the plain text, read it top to bottom, verify links make sense in context.

If you’re running a team, assign plain text QA to someone who isn’t the designer or writer. Fresh eyes catch the assumptions and context gaps that slip through when you’ve been staring at the HTML for an hour.

And if you’re using dynamic content blocks, personalisation, or conditional sections, test the plain text version with different audience segments. Auto-generation handles conditionals poorly, and you may discover entire sections rendering out of order.

Take five minutes this week: pull up your last three sends and look at the plain text versions. If you wince, your subscribers already did. Fix it before your next send, and keep fixing it. The readers who notice won’t say anything—they’ll just stay subscribed.

3 May 2026
What your image-heavy emails cost you in deliverability

You spent twenty minutes finding the perfect header image. You exported it at high resolution because you want it to look crisp. You embedded three more throughout the body to break up the text. And now your open rates are down 14% and you’ve no idea why.

Images aren’t neutral. Every kilobyte, every file format choice, every decision about hosting affects whether your newsletter reaches the inbox—and whether anyone bothers reading it once it arrives.

The weight problem nobody talks about

Email clients don’t wait for heavy emails. Gmail truncates messages over 102KB, clipping everything below that threshold behind a “view entire message” link. Apple Mail on iOS often fails to load images over cellular connections when the total payload exceeds certain thresholds. Outlook still renders images inconsistently depending on file size and format.

But the real damage happens before any of that. Spam filters look at email size as a signal. A 600KB email with multiple high-resolution images patterns-matches with the kind of promotional blasts that recipients ignore. It doesn’t matter that your content is thoughtful and your list is engaged. The structure of your email is whispering “bulk sender” to every filter between you and the inbox.

Most newsletter operators export images at whatever size their design tool suggests. That’s usually 2x or 3x resolution for retina displays—which means a 600-pixel-wide image ships at 1800 pixels and gets scaled down by the email client. You’re sending triple the data for zero perceivable quality gain in an email context.

Alt text isn’t just for accessibility anymore

Roughly 43% of Gmail users have images blocked by default. Apple Mail Privacy Protection loads images through a proxy that strips tracking pixels but doesn’t guarantee the image itself renders on the user’s screen if they’re skimming with images off.

If your newsletter relies on images to communicate key information—your call-to-action is a button graphic, your main point is in an infographic, your brand identity lives in a masthead—then nearly half your readers see broken boxes and alt text. Except most newsletter operators write alt text like this: “Image” or “Header” or nothing at all.

Alt text is now doing double duty. It’s an accessibility requirement and a reading experience for a massive segment who’ll never enable images. Write it like you’d write a caption: descriptive, useful, complete. If the image disappeared tomorrow, would your reader still understand the email? If not, the image is doing structural work that belongs in HTML text.

Hosting images inline vs. external links

You have two choices: encode images directly into the email (Base64 embedding) or host them externally and link to them. Both have costs.

Base64 increases email size by roughly 37%. A 100KB image becomes 137KB of encoded text embedded in your HTML. That pushes you toward clipping thresholds faster and makes your email source code a bloated mess that some spam filters flag as suspicious.

External hosting keeps the email lightweight, but introduces dependencies. If your image host is slow, the email feels slow. If your CDN goes down, your images disappear. And every externally hosted image is another DNS lookup, another HTTP request, another opportunity for something to break on a flaky mobile connection.

The correct answer isn’t one-size-fits-all. Small logos and essential brand elements can be embedded if they’re optimised under 20KB. Everything else should be externally hosted on a fast, reliable CDN with aggressive caching. If you’re just getting started and need dependable infrastructure that won’t collapse under traffic, BigScoots is worth considering for hosting your asset library.

What actually works

Start with this assumption: your newsletter should be fully readable with images off. Everything else is enhancement.

Optimise every image before it goes in. Use tools like ImageOptim or Squoosh to compress without visible quality loss. Export at 1x resolution, not 2x—email clients aren’t photo galleries. For photographs, use JPEG at 60–80% quality. For graphics and logos, use PNG-8 when possible, not PNG-24. SVG works in some clients, but support is inconsistent enough that you’re better off sticking with raster formats.

Keep total email size under 80KB including all images and HTML. If you’re regularly exceeding that, you’re either embedding too much or not compressing aggressively enough.

Test your newsletter with images disabled in Gmail, Apple Mail, and Outlook. If it’s unreadable or confusing, restructure. Move key content into text. Use images to support, not replace, your message.

And for the love of deliverability, stop using a giant hero image at the top of every send. It’s a pattern spammers love, it increases size, and it trains readers to scroll past the first screen before they see anything substantive. If you must use one, make it small, make it fast, and make sure your first paragraph of real text loads above it.

If this changed how you think about images in your sends, reply and let me know what you’re adjusting. I read every response, and your questions shape what we cover next.

3 May 2026
Why a missing line break ruins comprehension faster than typos

Most newsletter operators think about line breaks the way they think about breathing—automatic, barely conscious, definitely not strategic. But the vertical rhythm of your newsletter is doing cognitive work whether you’re paying attention or not.

Every time you hit return, you’re making a decision about how your reader’s brain will process the next thought. Get it wrong consistently, and you’re not just making your newsletter harder to read. You’re making it harder to understand.

The density problem

Open your sent folder. Look at your last five newsletters. Count the number of times you have paragraphs longer than four lines on a mobile screen. If the answer is “often,” you’re creating walls of text that trigger an instant cognitive assessment: this will require effort.

That assessment happens before comprehension even starts. Your reader hasn’t decided your idea is complex—they’ve decided your formatting is demanding. And they’re right. Dense paragraphs require more working memory. They obscure the logical structure of your argument. They make it harder to resume reading after an interruption (and every newsletter gets interrupted).

The fix isn’t to write shorter paragraphs. It’s to break where the idea breaks. One thought, one paragraph. When you shift angle, add evidence, or pivot tone—that’s your line break. Not after some arbitrary sentence count.

The opposite mistake

Then there’s the staccato newsletter.

Every sentence its own paragraph.

Dramatic pauses everywhere.

This isn’t rhythm. It’s a typography gimmick pretending to be emphasis. Real emphasis requires contrast. If everything is emphasised, nothing is. When every thought gets its own island of white space, you’re not aiding comprehension—you’re fragmenting it.

Readers need to see which ideas are connected. Keeping related sentences together signals relationships. This belongs with that. These three points are all evidence for the claim above. When you break those connections for purely visual reasons, you’re making your reader rebuild the logical structure you’ve just dismantled.

White space is a signal, not decoration

The space between your paragraphs isn’t there to make your newsletter look approachable or modern. It’s functional architecture. It tells the reader when to pause, when to connect, when to shift mental gears.

A single line break says: same thread, new sentence.

A double break (paragraph separation) says: related but distinct thought.

An H2 subheading says: we’re changing sections entirely, reset your context.

If you’re using these inconsistently—breaking mid-thought for visual variety, or jamming connected ideas together because you’re worried about length—you’re sending mixed signals. Your reader’s brain is working overtime to figure out what actually belongs together.

This is why some newsletters feel effortless to read even when they’re covering complex ideas, and others feel like work even when they’re simple. It’s not the vocabulary. It’s the information design.

What to do about it

After you write your next newsletter, before you schedule it, do this: read it on your phone. Not to check typos. To check shape.

Where do your eyes hesitate? Where do you lose the thread? Where does a paragraph look like it’s three different thoughts crammed together? Where have you broken up a single thought into artificial fragments?

Then edit for structure, not just prose. Move your line breaks to match your logic. Keep connected ideas together. Separate distinct points. Use subheadings to mark major shifts, not just to break up long sections.

Your newsletter’s readability isn’t just about word choice or sentence length. It’s about whether the visual structure matches the logical structure. When those two things align, comprehension becomes effortless. When they don’t, even simple ideas feel hard.

If this kind of structural thinking changes how you edit your newsletter, reply and tell me. I read every response, and the best operator insights end up in future issues.

2 May 2026
The footer that’s quietly turning into a legal liability

You copied your newsletter footer from a template three years ago and haven’t looked at it since. It’s got an unsubscribe link, a physical address (possibly your old flat), and some vague language about why people are receiving this email. Job done, right?

Not quite. Your footer isn’t just boilerplate—it’s a legal document that sits at the bottom of every send. And if you’re operating in multiple jurisdictions, sending commercial content, or simply grown beyond a hobby list, there’s a decent chance yours is putting you at risk.

What the law actually requires (and it’s not universal)

There’s no single set of footer rules. GDPR, CAN-SPAM, CASL, PECR—each has different requirements, and which ones apply depends on where your subscribers are, not where you are.

Under CAN-SPAM (US), you need a valid physical postal address, a clear identification that the message is an advertisement (if it is), and a functioning unsubscribe mechanism that processes requests within 10 business days. Under GDPR (EU/UK), you need to explain the lawful basis for processing, provide clear identity information, and honour withdrawal of consent immediately. CASL (Canada) requires clear identification of the sender and a working unsubscribe that’s free and simple.

Most operators assume one disclaimer covers everything. It doesn’t. If you’re sending to a mixed list—say, subscribers in London, Toronto, and Texas—you need to meet the strictest requirements that apply to anyone on that list.

The bits that get you in trouble

The postal address requirement trips up a lot of people. CAN-SPAM requires it. If you’re a solo operator working from home, you might not want to publish your home address at the bottom of every email. You’ve got options: a registered agent service, a PO box, or private mailbox rental. But “123 Main Street” or a obviously fake address isn’t compliant, and regulators do check.

Then there’s the unsubscribe mechanism itself. It needs to work. It needs to be easy to find. It can’t require a login. It can’t ask people to confirm their choice across multiple pages. Some platforms default to a two-step process (click, then confirm on a landing page)—that’s fine. But if you’re adding friction beyond that, or burying the link in grey text on a grey background, you’re begging for complaints.

Another common mistake: using the footer to explain why someone is on your list, but getting the reason wrong. If someone signed up for a lead magnet two years ago and you’ve been sending them product updates ever since, your footer shouldn’t say “You’re receiving this because you subscribed to our weekly newsletter.” It should reflect reality—or you should fix your segmentation so it does.

What good looks like

A solid footer is clear, accurate, and doesn’t try to hide anything. It identifies who’s sending (company name, not just a brand), provides a real contact method (not just a no-reply address), includes a valid postal address, and explains the legal basis for sending in plain language.

If you’re sending different types of content—editorial, transactional, promotional—your footer should reflect that. A receipt doesn’t need the same unsubscribe flow as a marketing campaign. But if you’re mixing content types in a single send, the most restrictive rules apply.

It’s also worth reviewing your footer every time your business changes. New entity structure? Update the name and address. Moved to a new platform? Check the unsubscribe flow still works. Expanded into a new market? Make sure you’re compliant with local rules.

Stop thinking of it as a formality

The footer is where trust goes to die—or gets reinforced. It’s the last thing people see, and often the first thing they look for when something feels off. A sloppy footer signals a sloppy operation. A clear, honest one does the opposite.

Take ten minutes this week and actually read your footer. Click the unsubscribe link. Check the address is current. Make sure the language matches what you’re actually doing. If you’re not sure whether you’re compliant, you probably aren’t.

If this resonated, you’ll want the next one. Reply to this email and let us know what footer questions you’re still sitting on—or subscribe to One Two Three Send if someone forwarded this your way.

2 May 2026
How much money does your newsletter lose in spam?
You check your dashboard. Open rate looks fine. Click rate is steady. Unsubscribes are low. Everything seems healthy.

Meanwhile, 11% of your list never sees your newsletter. Not because they don’t want it—they signed up, after all—but because it’s landing in spam. And because spam is invisible, you’re flying blind on the actual cost.

Let’s fix that.

The revenue you can’t see

Spam folder placement isn’t a binary technical failure. It’s a gradient tax on every send. A 5% spam rate sounds negligible until you multiply it by subscriber lifetime value, send frequency, and conversion rate.

Here’s the maths most operators skip: if you’re sending to 10,000 subscribers twice a week, and 8% land in spam, that’s 1,600 impressions per week that generate zero opens, zero clicks, and zero revenue. Over a year, that’s 83,200 completely wasted sends.

If your newsletter drives £2 in monthly value per engaged subscriber—through affiliate commissions, product sales, or client leads—that 8% spam rate is costing you roughly £16,000 annually. And that’s conservative.

The problem isn’t just lost revenue. It’s that spam folder subscribers still count against your billing tier, your engagement benchmarks, and your sender reputation. You’re paying to send to ghosts.

Why spam rates hide in plain sight

Most platforms report deliverability as a boolean: delivered or bounced. But “delivered” just means the receiving server accepted the message. It doesn’t tell you where it went after that.

Inbox placement—the percentage that actually reaches the primary folder—requires separate tooling. Seed list testing, postmaster data, and third-party monitors like 250ok or GlockApps can surface the truth, but they cost money and require regular audits.

So most operators don’t look. They assume their 40% open rate means 40% of their list is seeing the newsletter. In reality, if 10% is in spam, the true engaged denominator is smaller—and your real open rate among inbox recipients might be 44%. Better, but you’re still leaving 10% on the table.

The fix isn’t what you think

Authentication—SPF, DKIM, DMARC—is table stakes now, not a fix. If you’re still missing any of those three, you’re not just risking spam placement; you’re risking full rejection at major providers.

The levers that actually move inbox placement are behavioural, not technical:
- Engagement velocity: Gmail and Outlook track how quickly recipients open, delete, or ignore your mail. A slow burn-off in engagement signals declining relevance, which degrades placement over time.
- Complaint rate: Even a 0.1% spam complaint rate is high. If you’re above 0.08%, you’re in the danger zone. Every “mark as spam” click is a vote against your sender reputation.
- List hygiene cadence: Suppressing unengaged subscribers isn’t just about open rates—it’s about protecting your reputation with mailbox providers who watch how many of your recipients ignore you consistently.
Most importantly: spam placement isn’t evenly distributed. One provider might love you while another bins 30% of your sends. Yahoo, Microsoft, and Google all use different filters, and what works for one won’t necessarily work for another.

What to do Monday morning

Start by measuring what you can’t see. Set up a seed list test with addresses at Gmail, Outlook, Yahoo, and Apple. Send your next newsletter and manually check placement. If more than 2–3% land in spam or promotions tabs, you’ve got a problem worth solving.

Next, pull a report of subscribers who haven’t opened in 90 days. Segment them into a re-engagement campaign—one or two last attempts—then suppress anyone who still doesn’t bite. Yes, your list size shrinks. Your inbox placement improves, and so does your revenue per send.

Finally, monitor your complaint rate monthly. If it’s ticking up, your content, frequency, or expectations are misaligned with what subscribers actually want. Fix the editorial problem, not just the technical one.

If this resonated, reply and tell us what your spam rate actually is—if you know it. We read every response, and the stories often turn into future articles.

Spam folder revenue loss isn’t a catastrophic failure. It’s a quiet leak. But quiet leaks sink ships just as surely as loud ones.
2 May 2026
The newsletter template that’s making readers work too hard

You’ve spent hours on your subject line. Your preview text is crisp. The open happens. Then your reader arrives in their inbox and immediately has to work.

They’re pinching to zoom on mobile. They’re hunting for the actual content amongst a sea of social icons, navigation menus, and decorative whitespace. They’re squinting at 12px grey text on a white background. And most of the time, they just close it.

Your template isn’t helping you. It’s creating friction between the open and the read.

The invisible tax of template complexity

Most newsletter platforms offer templates that look impressive in the preview. Multi-column layouts, hero images, carefully branded headers, elaborate footers with every possible link. They look like websites, because that’s what we’ve been conditioned to think “professional” means.

But newsletters aren’t websites. Your reader isn’t browsing. They’re not exploring navigation. They opened an email because you promised them something specific, and now they want to know if you’re going to deliver.

Every visual element that isn’t your core message is a small cognitive tax. A logo they don’t need to see again. A navigation menu that goes nowhere useful. A three-column layout that collapses awkwardly on mobile. Each one whispers: “This might not be worth your time.”

The operators who retain readers aren’t the ones with the fanciest templates. They’re the ones who’ve ruthlessly eliminated everything that isn’t the message.

What actual readability looks like

Readability isn’t about dumbing things down. It’s about reducing the gap between intent and comprehension. When someone opens your newsletter, how quickly can they start reading?

Line length matters more than you think. The ideal measure for comfortable reading is 50–75 characters per line. Most newsletter templates blow past 100 characters on desktop, forcing the eye to work harder to track from line to line. On mobile, the opposite happens—templates with too much padding create awkwardly short lines that feel choppy.

Font size is where most templates fail hardest. Fourteen pixels is the minimum for body text, but 16–18px is where readability actually starts. If your reader has to zoom, you’ve already lost momentum.

Contrast isn’t negotiable. Grey text (#666, #888, even #999) has become a design trend that actively punishes readers. True black on white can feel stark in a brand guide, but in an inbox it’s a gift. Your reader’s eyes are already tired.

Whitespace is valuable, but only when it’s functional. A massive header graphic might look premium, but if it pushes your opening paragraph below the fold on mobile, it’s working against you. The first thing a reader should see after opening is the beginning of what you promised them.

The mobile-first reality you can’t ignore

Somewhere between 40–80% of your readers are opening on mobile, depending on your audience. But most newsletter templates are still designed desktop-first and then “made responsive” as an afterthought.

This shows up in predictable ways. Multi-column layouts that stack clumsily. Buttons that become impossible to tap because they’re too close together. Images that blow out to full width and dominate the screen. Text that reflows in unexpected ways, breaking your carefully considered rhythm.

The solution isn’t a separate mobile template. It’s designing for mobile as the primary experience and letting desktop be the easy case. Single column. Generous touch targets. Font sizes that don’t need adjustment. Images sized to support the text, not overwhelm it.

Test your template by forwarding it to yourself and opening it on your phone. Don’t just glance at it—actually try to read it while standing in a queue or sitting on the bus. If you find yourself pinching, scrolling past large blocks of non-content, or losing your place, your readers are experiencing the same thing every time you send.

Strip it back, then add only what earns its place

The best newsletter template is the one your readers don’t notice. They should arrive, start reading, and forget they’re in an email at all.

Start with plain text in your head. What would you write if formatting wasn’t an option? That’s your foundation. Then add HTML styling only where it genuinely improves clarity. Subheadings that create logical breaks. Emphasis on key phrases. Links that are obviously clickable. Nothing else is mandatory.

Your logo doesn’t need to be 600 pixels wide. Your footer doesn’t need twelve links. Your social icons don’t need to be above the fold. The unsubscribe link is legally required, but it doesn’t need a decorative border.

Every element should answer a single question: does this make it easier for the reader to absorb what I’m saying? If the answer is no, or even “maybe,” cut it.

If this resonated, reply and tell me what you’ve cut from your template. I read every response, and the best ones shape what we cover next in One Two Three Send.

The newsletters that people actually finish reading aren’t the ones with the best design systems. They’re the ones that get out of their own way.

1 May 2026
Your unengaged subscribers are worth more than you think

There’s a moment in every newsletter operator’s life when they stare at their dashboard and see it: 40% of subscribers haven’t opened in six months. The advice is unanimous—scrub them. Purge the dead weight. Protect your deliverability.

But here’s what nobody tells you: those silent subscribers might be the most honest signal you have about what’s working and what isn’t.

The problem with the purge-everything doctrine

Yes, unengaged subscribers can hurt deliverability. Mailbox providers notice when large chunks of your list ignore you. That’s real, and it matters.

But the standard advice—delete anyone who hasn’t opened in 90 or 180 days—treats your list like a leaking bucket. Patch the hole, move on. What it misses is that why someone goes quiet tells you more than whether they’ve gone quiet.

Did they sign up during a product launch and only care about that one topic? Are they opening on a device that doesn’t load images, so they look inactive but aren’t? Did your editorial direction shift and leave them behind? Did they get promoted and lose the problem your newsletter solves?

When you delete without diagnosing, you lose the signal. You can’t fix what you can’t see.

What dormancy actually measures

Unengaged subscribers are a lagging indicator of four things, and only one of them is about the subscriber:

Topic drift. When engagement drops across a cohort that joined around the same time, it often means your content evolved away from what you promised when they subscribed. They’re not broken—your contract with them is.

Frequency mismatch. Someone who loved your monthly recap but goes dark when you shift to twice a week isn’t unengaged. They’re over-contacted. The absence is feedback.

Life-cycle transition. B2B newsletters especially suffer from this. Your reader changed jobs, got promoted out of the weeds, or sold their company. They’re not ignoring you—they’ve graduated. That’s not a failure. It’s entropy.

Technical invisibility. Image-blocking, corporate firewall stripping, privacy features in Apple Mail—plenty of people read without triggering an open. Treating them as dead just because they’re invisible is bad arithmetic.

A better framework than delete-or-keep

Instead of a blanket purge, try a diagnostic segmentation. Create three buckets:

The recently quiet: 90–180 days of silence. These people are worth a targeted win-back. One well-written re-engagement email that acknowledges the silence and asks a question often pulls 15–25% back into activity. If they don’t bite, then consider removal.

The long dormant: 180+ days, no engagement at all. Segment these separately and send at lower frequency or not at all—but keep them on the list in a suppressed state. They don’t hurt you if you’re not mailing them, and they’re available for future segmentation experiments.

The device-invisibles: No recorded opens but they’re still subscribed after a year-plus. Some of these people are reading every word in text-only clients or plain-text mode. Try a single plain-text email asking, “Still reading?” You’ll be surprised how many reply.

When a purge actually makes sense

There is a time to delete: when you’re seeing sustained deliverability problems—consistent spam-folder placement, rising bounce rates, or throttling from major providers—and you’ve ruled out authentication, content, and infrastructure issues.

At that point, yes: cut the long-dormant segment and watch your metrics for two weeks. If open rates climb and inbox placement improves, the purge worked. If nothing changes, the problem wasn’t your unengaged subscribers. It was something else, and you just deleted potential future readers for no reason.

Before you do any of this, make sure your sending infrastructure is sound and your domain reputation is healthy. If you’re just getting started and need reliable performance from the ground up, BigScoots handles email hosting with proper DNS setup and none of the throttling headaches that come with oversold shared environments.

Your list is a dataset, not a scoreboard

Engagement rate feels like a performance review. High is good, low is bad. But your newsletter isn’t a test you pass or fail. It’s a communication system, and unengaged subscribers are system feedback.

If 40% of your list has gone quiet in the last year, don’t just delete them and celebrate a tidier metric. Ask what changed. Did you? Did they? Did the world?

The answers will tell you more about where to take your newsletter than any engagement score ever will.

If this resonated, reply and tell me what percentage of your list is dormant right now—and whether you’ve ever actually tried to win them back. I read every response.

1 May 2026
Your newsletter’s ‘from’ name is doing more work than your subject line

You’ve spent twenty minutes testing subject lines. You’ve A/B tested emojis, punctuation, and whether to capitalise every word or just the first. Meanwhile, the field that’s actually doing the heavy lifting—the one that decides whether your email even gets considered—is something you set once and never think about again.

Your from name isn’t just a label. It’s the first trust signal, the primary filter, and for most subscribers, the only thing they actually read before deciding to open, delete, or ignore.

The inbox is a recognition game, not a curiosity game

Here’s what actually happens when your email lands: your subscriber glances at their inbox, scans a wall of sender names, and makes a split-second decision based on whether they recognise and trust the source. Subject lines only matter after that recognition happens.

If your from name is unclear, generic, or doesn’t match what they remember signing up for, your subject line never gets read. It doesn’t matter how clever it is.

This is why ‘Newsletter’ or ‘Team’ or ‘Info’ as a from name is such a quiet killer. It’s not that these are wrong—it’s that they’re invisible. They don’t trigger recognition. They look like every other bulk email, every automated receipt, every bit of inbox noise your subscriber is already trained to ignore.

Personal name vs brand name isn’t the real question

The most common advice is to use either a personal name (“Sarah Chen”) or your publication name (“The Morning Briefing”). But the actual rule is simpler: use whatever they’ll recognise fastest.

If you’re a solo operator and your writing voice is personal, your name works. If you’ve built a brand and people know the publication, use that. If you’re somewhere in between, the hybrid format (“Sarah from The Briefing”) tends to win because it gives two chances at recognition instead of one.

But here’s what most people miss: the from name you think you’re using isn’t always what subscribers see. Mobile mail clients truncate aggressively. Gmail cuts off after roughly 20–25 characters depending on font rendering. Apple Mail on iPhone is even less forgiving.

If your from name is “Sarah Chen – The Morning Briefing for Product Managers”, most of your readers see “Sarah Chen – The Morni…” and have no idea what that is.

Test it the way subscribers actually see it

Send yourself a test email. Check it on your phone. Open it in Gmail’s mobile app, Apple Mail, Outlook on iOS—whatever your audience actually uses. Look at your inbox, not the open email. That truncated, half-visible string? That’s your real from name.

If it’s not immediately clear who it’s from, you’ve got a problem that no subject line can fix.

Also check what happens when someone saves you as a contact or when their mail client auto-suggests your address. Some platforms let you set a “friendly from” that’s different from your sending domain, but if those don’t align, you create confusion. Confusion kills opens.

What actually works

The best from names are short, distinct, and stable. You want subscribers to recognise you in under a second, and you want that recognition to be consistent every time you send.

If you change your from name frequently—switching between your personal name, your brand, and “The Team” depending on the topic—you’re training people not to recognise you. Every change resets the clock on familiarity.

Consistency isn’t boring. It’s strategic. The publications with the highest open rates aren’t the ones with the cleverest subject lines—they’re the ones people recognise instantly and have learned to trust.

If you haven’t looked at your from name in six months, look at it now. Send a test, check your phone, and ask yourself honestly: if this landed in your inbox among fifty other emails, would you know what it was?

If the answer’s no, fix it before you write another subject line.

What does your from name actually say? Reply and tell us—or if this hit home, subscribe to One Two Three Send for more like this every week.

1 May 2026

► Necessary Cookies Always Active

Necessary cookies enable essential site features like secure log-ins and consent preference adjustments. They do not store personal data.

► Functional Cookies Remark

Functional cookies support features like content sharing on social media, collecting feedback, and enabling third-party tools.

► Analytical Cookies Remark

Analytical cookies track visitor interactions, providing insights on metrics like visitor count, bounce rate, and traffic sources.

► Advertisement Cookies Remark

Advertisement cookies deliver personalized ads based on your previous visits and analyze the effectiveness of ad campaigns.