Category: Newsletters

Most newsletter operators believe that more touchpoints build more trust. Send twice a week instead of once. Add a Sunday bonus. Launch a daily tip series. The logic sounds reasonable: more contact equals more familiarity, and familiarity drives conversions.

But that logic ignores the infrastructure layer underneath every newsletter: deliverability.

The truth is that increasing send frequency without corresponding engagement gains doesn’t build trust—it destroys your sender reputation, tanks inbox placement, and turns your entire archive into spam fodder. You’re not building authority. You’re training inbox algorithms to ignore you.

How send frequency damages sender reputation

Email service providers track your sender reputation using a combination of signals: open rates, spam complaints, bounce rates, and engagement velocity. When you double your send frequency, you need to double your engaged audience to maintain the same reputation score.

Here’s what actually happens: you send twice as often, but your open rate drops by 30–40% because subscriber attention is finite. Your most engaged readers might open both emails, but your median subscriber opens one or neither. Your overall engagement rate falls. ISPs interpret that drop as a signal that your content is less relevant, and they adjust inbox placement accordingly.

The math is unforgiving. If you send once a week to 10,000 subscribers with a 40% open rate, that’s 4,000 engaged readers per send. Switch to twice a week with a 28% open rate (a realistic drop), and you’re down to 2,800 engaged readers per send—5,600 per week total. You’re sending twice as much for a 40% gain in absolute engagement, but your per-send reputation score is now 30% lower.

Gmail and Outlook don’t care about your weekly totals. They care about per-campaign signals.

The engagement cliff

Once your sender reputation drops below a certain threshold, inbox placement collapses non-linearly. You don’t gradually slide from inbox to promotions tab. You fall off a cliff into spam folders, and recovery takes months of disciplined list hygiene and reduced sending.

I’ve watched this happen to operators who went from weekly to daily sends without testing the transition. Within six weeks, their inbox placement rate dropped from 92% to under 60%. Their open rates fell further because fewer people saw the emails in the first place. The feedback loop is vicious: worse placement drives lower engagement, which drives worse placement.

The operators who recovered did so by cutting send frequency in half, removing unengaged subscribers, and rebuilding slowly over 90 days. Some never fully recovered their original inbox rates.

When frequency works—and when it doesn’t

High send frequency works in exactly one scenario: when you have an audience that actively wants daily or near-daily content, and you can prove it with engagement data.

If you’re running a news digest, a stock-tip service, or a highly segmented course drip, frequent sends can work—because your audience expects them and opens them. But even then, you need to monitor per-campaign open rates religiously and cut frequency the moment engagement drops.

For the rest of us—commentary writers, niche educators, solo operators building authority in a specific domain—frequency is a tax on reputation. Your subscribers don’t need to hear from you three times a week. They need to hear from you when you have something worth saying, and they need to open the email when it arrives.

One high-quality send per week with a 45% open rate will build more trust and deliver better long-term results than three mediocre sends per week with a 22% open rate. The total engaged-reader count might look similar in a spreadsheet, but the infrastructure consequences are not.

What to do instead

If you’re tempted to increase frequency, test it properly. Segment a portion of your list and send them the higher-cadence version for 30 days. Track per-campaign open rates, spam complaints, and unsubscribe rates. Compare those numbers to your control group.

If engagement holds or improves, roll out the change slowly. If engagement drops even slightly, revert immediately. A 10% drop in per-send open rate today becomes a 40% drop in inbox placement six months from now.

And if you’re already sending frequently and seeing declining engagement, the fix is simple but painful: send less. Cut your frequency in half, improve your content quality, and give your sender reputation time to recover. It’s not exciting, but it works.

Want to dig into deliverability mechanics and list-health strategies? Reply to this email with your biggest inbox-placement question—we’ll cover it in a future issue.

The operators who win the long game aren’t the ones who send the most. They’re the ones who still land in the inbox after two years.

ConvertKit includes a feature called the Incentive Email that most solo operators either overlook or misunderstand. It’s designed to deliver your lead magnet or opt-in bribe automatically—without building a separate automation sequence. But the way it fires, when it doesn’t fire, and how it interacts with existing automations can trip you up if you don’t know the rules.

Here’s what the Incentive Email actually does, when to use it, and one non-obvious gotcha that can double-send your lead magnet if you’re not careful.

What the Incentive Email Does

When you create a form in ConvertKit, you’ll see a checkbox labeled “Send incentive email.” Toggle it on, and you can draft a single email that fires immediately after someone confirms their subscription (if you’re using double opt-in) or submits the form (if you’re using single opt-in).

The email includes merge tags for the subscriber’s name and a custom download link. You write it once, and ConvertKit sends it to every new subscriber who joins via that specific form. No automation, no sequence, no visual canvas required.

It’s a faster setup than building a full automation if you’re just delivering a PDF, checklist, or Notion template. You don’t need to tag subscribers, filter them into a sequence, or manage conditional logic. The form handles everything.

When to Use It vs. When to Skip It

The Incentive Email makes sense when your funnel is simple: one form, one lead magnet, one confirmation email. If you’re running a single opt-in offer and you don’t plan to segment subscribers or trigger follow-up emails based on behavior, it’s the cleanest option.

Skip it if you’re doing any of the following:

• Segmenting subscribers by interest, source, or product intent at the point of opt-in
• Running A/B tests on lead-magnet delivery timing or copy
• Tracking open or click behavior in your automation reporting (Incentive Emails don’t appear in sequence stats)
• Delivering multiple resources in a welcome series

The Incentive Email doesn’t play well with complex funnels. It’s a one-and-done trigger. If you need to branch logic, delay delivery, or send a second email 24 hours later, you’re better off using a visual automation with tags and conditions.

The Double-Send Trap

Here’s the non-obvious problem: if you enable the Incentive Email and have an automation that triggers on the same form submission, both will fire. ConvertKit doesn’t suppress one in favor of the other. Your subscriber gets two emails—one from the Incentive Email, one from the automation—within minutes of each other.

This happens most often when you’re migrating from an old automation setup to the Incentive Email (or vice versa) and forget to disable the other. The form doesn’t warn you. The automation builder doesn’t flag the conflict. You only notice when a subscriber replies asking why they got the same PDF link twice.

The fix: audit your forms and automations before enabling the Incentive Email. Search for any automation that uses the form as a trigger. If you find one, decide which delivery method you want to keep, then disable the other. Don’t run both at once unless you’re intentionally sending different content in each email.

Editing and Timing Notes

Once you enable the Incentive Email, you can edit the subject line, body copy, and sender name at any time. Changes apply to all future sends, but they won’t retroactively update emails already delivered. If you need to fix a broken link or update the lead magnet, you’ll need to manually email past subscribers or rely on an automation to catch them.

Timing is immediate: ConvertKit sends the Incentive Email as soon as the subscriber confirms (double opt-in) or submits (single opt-in). There’s no built-in delay. If you want to wait 10 minutes or 24 hours, you need an automation instead.

The Incentive Email also doesn’t respect sending windows or time-zone adjustments. If someone opts in at 2 a.m., they get the email at 2 a.m. This usually doesn’t matter for lead magnets—people expect instant delivery—but it’s worth noting if you’re used to sequence-based sends that respect subscriber time zones.

When It’s Worth the Simplicity

If you’re launching a single opt-in offer and you don’t plan to iterate on delivery timing or segmentation, the Incentive Email is the fastest path to a working funnel. You skip the automation builder entirely. The trade-off: less flexibility, no reporting granularity, and no conditional logic.

For most solo operators, that trade-off is fine—until it isn’t. If you find yourself wanting to A/B test subject lines, track open rates in a dedicated sequence, or send a follow-up email two days later, you’ll outgrow the Incentive Email quickly. At that point, migrate to a visual automation and disable the Incentive Email on the form.

Just make sure you turn off one before you turn on the other. Your subscribers don’t need two copies of the same PDF.

One Two Three Send helps online operators make smarter tooling decisions. If you want sharp breakdowns like this in your inbox every week, subscribe below—or reply with a question you’d like answered next.

MailerLite offers a feature most solo operators ignore: auto-resend to non-openers. You send a campaign, wait a set number of days, then MailerLite automatically resends the same email to everyone who didn’t open it the first time—with a new subject line you provide.

It sounds like free engagement. Sometimes it is. Sometimes it’s a waste of deliverability budget. Here’s how to know the difference.

How Auto-Resend Works

When you schedule or send a campaign in MailerLite, you’ll see a checkbox: “Resend this campaign to non-openers.” Enable it, and you choose:

• How many days to wait before resending (minimum 1 day, maximum 10)
• A new subject line for the resend
• Whether to resend to people who didn’t open or didn’t click (two separate filters)

MailerLite tracks opens via a 1×1 pixel embedded in the email. If that pixel doesn’t load within your wait window, the subscriber gets the resend. The body content stays identical; only the subject line changes.

The feature is available on all MailerLite plans, including the free tier (up to 1,000 subscribers and 12,000 emails per month). No extra charge per resend—it just counts against your monthly send quota.

When Auto-Resend Actually Works

This feature pays off in three scenarios:

Time-sensitive content with a narrow window. If you’re promoting a webinar, sale, or limited offer, a resend 2–3 days before the deadline can recover 8–15% additional opens. The urgency justifies the repeat send, and the new subject line can emphasize scarcity (“Last chance” vs. your original angle).

Evergreen content you’re confident in. If your original open rate was below 30% and you believe the content itself is strong—tutorial, case study, resource roundup—a resend with a clearer or more specific subject line often pulls another 5–10% open rate. You’re not pestering; you’re giving the email a second chance to surface in a cleaner inbox.

Large lists with inconsistent engagement. If you have 5,000+ subscribers and your median open rate sits around 25–35%, auto-resend becomes a volume play. Even a modest 8% lift on the resend adds hundreds of opens you wouldn’t have captured otherwise, and the deliverability risk is minimal if your sender reputation is healthy.

When to Skip It

Auto-resend backfires when:

Your original subject line wasn’t the problem. If your open rate is consistently above 40%, the issue isn’t visibility—it’s relevance or timing. Resending won’t fix that. You’ll just train subscribers to expect duplicates and ignore both.

You send frequently. If you publish three or more emails per week, a resend starts to feel like spam. Subscribers who didn’t open the first time likely weren’t interested, and showing up again 48 hours later erodes trust faster than it recovers engagement.

You’re resending promotional content repeatedly. If every sales email gets auto-resent, subscribers notice the pattern. It signals desperation, and it trains them to wait for the resend (or unsubscribe). Reserve auto-resend for your strongest content, not every broadcast.

One Non-Obvious Tip

Most operators test two subject lines by running A/B splits on the initial send, then using the winner for the resend. Flip that logic.

Send your safer, clearer subject line first—the one that accurately describes what’s inside. Then use the resend to test a riskier, more curiosity-driven or emotional angle. If it flops, you’ve only burned the non-openers. If it works, you’ve discovered a subject-line style that breaks through inbox noise, and you can apply that learning to future campaigns.

This approach also avoids the common mistake of making the resend subject line worse than the original. I’ve seen operators rewrite a specific, compelling subject into a vague one just to make it “different.” The resend open rate craters, and they blame the feature instead of the execution.

MailerLite’s auto-resend costs you nothing but send volume. If you’re already paying for a plan and sitting below your monthly limit, the feature is pure upside—as long as you use it strategically, not reflexively. Test it on one high-value campaign, measure the lift, and decide from there.

Want more breakdowns like this? Subscribe to One Two Three Send for weekly deep-dives on the tools and tactics that actually move the needle for solo operators.

If you’re launching a newsletter or considering a platform switch in 2026, you’re probably weighing ConvertKit, Beehiiv, and Substack. All three handle the basics—sending email, growing a list—but the pricing models, feature sets, and ideal operators diverge fast.

Here’s the honest breakdown: what each does well, where each falls short, and who should pick which.

Pricing structures and where they hurt

ConvertKit bills on subscriber count. You’ll pay $29/month for up to 1,000 subscribers, $49/month for 3,000, and $79/month for 5,000. Every contact on your list counts, even if they never open. The free tier caps at 10,000 sends per month and strips out advanced automations.

Beehiiv uses a hybrid model: the free tier supports up to 2,500 subscribers with full feature access, but you’ll hit send limits and branding. The Scale plan ($49/month) removes caps and adds custom domains, referral programs, and ad network access. If you monetise through ads or premium subscriptions, Beehiiv takes a 3% cut on top of Stripe fees until you upgrade to $99/month.

Substack is free to send, forever. You pay nothing unless you charge readers. Then Substack takes 10% of gross subscription revenue, plus Stripe’s ~3%. No monthly fee, no subscriber caps. You’re trading platform fees for zero upfront cost.

The pain point: ConvertKit penalises list growth. Beehiiv’s ad-network cut eats margin if you’re earning through sponsors. Substack’s 10% hurts most once you’re above $5K/month in revenue—that’s $500/month in platform fees alone.

Feature depth and what’s actually useful

ConvertKit leads on automation. You can build complex sequences, tag based on link clicks, segment by custom fields, and trigger emails from Zapier events. The visual automation builder is clean, and subscriber scoring helps you identify engaged readers. It’s built for creators who run multiple funnels and need granular control.

Beehiiv focuses on growth tools. The referral program is native and easy to configure—readers unlock rewards by sharing your newsletter. The recommendation network cross-promotes you to other Beehiiv publishers. Polls, 3D analytics, and A/B testing on subject lines come standard. If you’re chasing rapid list growth and don’t need deep CRM features, Beehiiv’s toolset is optimised for that.

Substack strips features to the bone. You get a text editor, a paywall toggle, and threading for discussions. No automation, no tagging, no custom fields. The mobile app drives discovery and reader engagement, but you can’t segment sends or personalise beyond first name. It’s a deliberate trade-off: simplicity over power.

The decision point: pick ConvertKit if you’re running a business with lead magnets, courses, or multi-step onboarding. Pick Beehiiv if your primary goal is growing the list and monetising through ads or recommendations. Pick Substack if you want to write, charge, and ignore infrastructure.

Who each platform is actually built for

ConvertKit works best for course creators, coaches, and productised-service operators who treat email as the top of a conversion funnel. If you’re selling a $500 course or a $2K coaching package, the automation ROI justifies the monthly cost. You’ll use sequences to nurture cold leads and tags to segment buyers from browsers.

Beehiiv fits media-style publishers and newsletter-first businesses aiming for five- or six-figure subscriber counts. The referral mechanics and ad network make sense if you’re optimising for reach and CPM-based revenue. If you’re planning to sell sponsorships or run your own ad placements, Beehiiv’s analytics and testimonial exports help close deals.

Substack suits independent writers and commentary-focused creators who want readers to pay for the writing itself, not a product at the end of a funnel. The 10% fee is tolerable if you’re earning $2K–$10K/month and don’t want to manage infrastructure. Above $10K/month, the platform cut starts to sting, and migration becomes worth the effort.

Migration friction and lock-in risks

All three let you export your list as CSV. ConvertKit and Beehiiv support GDPR-compliant double opt-in imports; Substack requires you to email your list with a confirmation link before importing to another platform, which adds friction and drops some subscribers.

ConvertKit’s automation and tagging data exports cleanly, but you’ll need to rebuild sequences on the new platform. Beehiiv’s referral program data doesn’t port anywhere—if you’ve built a referral flywheel, leaving means starting over. Substack’s discussion threads and community features don’t migrate; you lose the social layer.

The lock-in hierarchy: Substack has the lowest technical lock-in but the highest social lock-in. Beehiiv locks you into growth mechanics. ConvertKit’s lock-in is workflow rebuilding, not data loss.

If you’re just starting, pick based on where you want to be in 12 months. If you’re switching, model the cost of recreating what you’ve built versus the cost of staying. ConvertKit at $79/month is cheaper than Substack’s 10% once you’re earning $800/month. Beehiiv’s $99/month makes sense if it replaces a separate referral tool and an analytics dashboard.

Want more tool breakdowns like this? Subscribe to One Two Three Send for weekly comparisons, no sales pitch.

Heads up — some links in this article are affiliate links. If you sign up through them, we may earn a small commission at no extra cost to you. We only recommend tools we use ourselves.

If you’re switching to Substack with an existing paid subscriber base, you’ll quickly discover that importing them isn’t a one-click operation. The platform treats free and paid subscribers very differently—and the tooling around paid imports is intentionally limited to protect both you and your readers from billing chaos.

Here’s how the process actually works, what limitations you’ll hit, and the non-obvious gotcha that can cost you a month of revenue if you’re not careful.

The two-path import: free vs. paid

Free subscribers upload via CSV without friction. You export from your old platform, map the columns, and Substack ingests them in minutes. Paid subscribers require a different workflow because Substack needs to connect each person to an active billing relationship—either a Stripe subscription ID or a comped status you manually assign.

If your previous platform used Stripe, Substack can import the subscription metadata directly—but only if both accounts share the same Stripe Connect relationship. That’s rare unless you were already using a Stripe-native platform like Ghost or a custom-built membership site. Most operators are coming from ConvertKit, Mailchimp, or Beehiiv, none of which expose raw Stripe subscription IDs in their CSV exports.

That means you’ll use the comped subscriber route: you import paid subscribers as free accounts, then manually apply a “complimentary subscription” that grants them full access without charging them. Substack treats comped subs identically to paid ones for content access, but they don’t appear in your MRR calculations and won’t auto-renew unless you later convert them to a paid plan.

The billing cutover problem

Here’s the edge case that catches people: if you comp your existing paid subscribers and tell them to re-subscribe at their next renewal date, you’ll lose anyone whose renewal falls in the window between your import and your announcement. They’ll get charged by your old platform, then hit a paywall on Substack, and assume something broke.

The safer approach is to cancel all subscriptions on your old platform before you import, refund any partial-month charges, and immediately comp everyone on Substack with an expiration date set to their original renewal. Then send a dedicated email explaining the transition and asking them to update their payment method before the comp expires. Substack will email them automatically seven days before expiration, but your own message converts better because it comes from you, not the platform.

Expect 10–15% of comped subscribers to churn during this transition. That’s normal. The ones who don’t update their payment info within 30 days probably weren’t engaged enough to stay long-term anyway.

The Stripe metadata you actually need

If you do have access to Stripe subscription IDs—either because you’re migrating from Ghost, or because you were running Stripe directly—you’ll still need to provide Substack support with a CSV that maps each email address to its subscription ID and current billing cycle anchor date. You can’t upload this yourself; Substack’s backend team handles it manually to avoid mismatched billing states.

Turnaround time is typically 3–5 business days, and they’ll only process it if your Stripe account is already connected to your Substack publication. If you’re switching Stripe accounts as part of the migration (common if you’re moving from a business entity to a personal one, or vice versa), you’ll need to use the comp method instead. Substack won’t connect a subscriber to a subscription ID that lives in a different Stripe account.

When to skip the import entirely

If you have fewer than 50 paid subscribers, the cleanest move is often to let them re-subscribe manually. Cancel their old subscriptions, refund the current billing period, and send a launch email with a discounted annual plan offer that offsets the hassle. You’ll lose some, but you’ll also avoid two weeks of support emails from people whose billing states didn’t migrate cleanly.

For lists above 200 paid subscribers, the comp-and-convert method is worth the effort. Between 50 and 200, it depends on how hands-on you want to be and whether you’re also changing pricing or plan structure as part of the move.

One last note: if you’re moving to Substack because you want their payment infrastructure to handle sales tax, VAT, and global compliance, make sure you’re not grandfathering in subscribers at old prices that don’t include tax. Substack’s tax automation only works on new subscriptions created after you enable it. Comped subscribers who convert will be charged tax, but anyone you migrate via Stripe ID handoff will keep their original tax treatment unless you manually update each subscription in Stripe. That’s a billing-support nightmare six months later when your accountant asks why half your EU subscribers aren’t remitting VAT.

If you’re planning a platform migration and want step-by-step breakdowns like this every week, subscribe to One Two Three Send. We cover the tooling decisions that actually matter when you’re running a one-person content business.

Heads up — some links in this article are affiliate links. If you sign up through them, we may earn a small commission at no extra cost to you. We only recommend tools we use ourselves.

Postmark ships with a feature most operators discover only after they’ve already mixed password resets with product announcements: message streams. They let you route different types of email through separate pipelines, each with its own delivery tracking, suppression list, and sender reputation.

If you’re running both transactional email—receipts, login links, account notifications—and broadcast messages like product updates or weekly digests, message streams keep the two from contaminating each other’s deliverability.

What message streams actually do

Every Postmark account starts with two default streams: Transactional and Broadcasts. When you send an email via API or SMTP, you specify which stream it belongs to. Postmark then tracks opens, clicks, bounces, and spam complaints separately for each stream.

This separation matters because transactional email—password resets, order confirmations—typically sees open rates above 60% and near-zero spam complaints. Marketing broadcasts might hit 20% opens and attract a handful of complaints, even when people opted in. If you mix them in one stream, a spike in broadcast complaints can drag down your overall sender reputation, which affects all your email, including the critical transactional stuff.

Each stream also maintains its own suppression list. If someone marks your newsletter as spam, Postmark adds their address to the Broadcasts suppression list—but they’ll still receive password resets and receipts from the Transactional stream. You don’t lose the ability to send account-critical email just because someone unsubscribed from marketing.

When to create custom streams

Beyond the two defaults, you can create additional streams for specific use cases. Here are three that make sense for solo operators and small teams:

Onboarding sequences. If you run a multi-email onboarding series—welcome, getting-started tips, feature walkthroughs—route it through a dedicated stream. Onboarding email sits between transactional and broadcast: it’s expected, but not urgent. Separating it lets you monitor completion rates and deliverability without muddying your core transactional metrics.

Digest emails. Weekly or monthly roundups often see lower engagement than one-off broadcasts. A separate stream lets you track digest-specific open rates and adjust frequency without affecting your main broadcast reputation.

Partner or affiliate sends. If you occasionally send email on behalf of a partner—joint webinars, co-marketing—isolate it. Partner sends introduce variables you don’t control: list quality, subject lines, content. A separate stream quarantines the risk.

Postmark allows up to ten streams per account. You don’t pay extra for them, but each stream requires its own API token and SMTP credentials, so there’s a small setup cost.

How to route messages to the right stream

If you’re using Postmark’s API, you specify the stream with a MessageStream parameter in your JSON payload. For SMTP, you set the stream by choosing the correct SMTP credentials during configuration—each stream generates its own username and password.

Most developers default to the Transactional stream for everything, then wonder why their welcome emails show up in spam. The fix: audit every email type your app sends, classify it as transactional or broadcast, and route accordingly. Receipts, password resets, and two-factor codes go to Transactional. Product updates, newsletters, and nurture sequences go to Broadcasts or a custom stream.

The non-obvious tip: use streams to test reputation recovery

If your broadcast deliverability tanks—inbox placement drops, spam complaints spike—create a new message stream, warm it with a small segment of your most engaged subscribers, and migrate your broadcast sends over two weeks. The new stream starts with a clean reputation. You can’t erase your domain’s history, but you can isolate future sends from past damage.

This works because Postmark treats each stream as a separate sender profile. ISPs still see your domain and IP, but the engagement patterns and complaint rates reset. It’s not a magic fix—if your content or list quality is broken, the new stream will degrade just as fast—but it buys you time to tighten your targeting and content.

One warning: don’t create streams just to dodge suppression lists. If someone complained about your email, they don’t want any of your marketing, regardless of which stream it comes from. Routing around suppressions will get your account suspended.

If you’re already using Postmark and haven’t set up separate streams for transactional and broadcast email, do it this week. The deliverability buffer alone justifies the ten minutes of setup. And if you’re evaluating Postmark against other ESPs, message streams are one of the features that separate it from basic SMTP relays.

Got a question about email infrastructure or a tool you’d like us to cover? Reply to this email—we read every response and use them to shape future articles.