One Two Three Send

Author: onetwothreeadmin

  • Your newsletter signup form is lying to subscribers before they join

    Your newsletter signup form is lying to subscribers before they join

    You’ve spent hours perfecting your welcome sequence. You’ve A/B tested subject lines. You’ve even hired a designer for your template. But there’s a gap opening up before any of that matters — right there on your signup form.

    Most newsletter operators don’t realise their signup form is making promises their actual newsletter doesn’t keep. Not through malice, but through drift. You wrote that form copy eighteen months ago when you were sending weekly roundups. Now you’re sending multi-part deep dives on Tuesdays and sponsor spotlights on Fridays. The form still says “weekly roundup.”

    This isn’t pedantry. It’s the difference between a subscriber who arrives prepared for what you’re actually sending and one who feels misled from send one.

    The three lies signup forms tell

    The first lie is frequency. Your form says weekly. You send twice a week during launch periods, once a fortnight during slow months, and three times the week you had that viral post. Subscribers don’t experience “roughly weekly.” They experience inconsistency, and inconsistency reads as either desperation or disorganisation.

    The second lie is format. You promised a curated list of links. You’re now sending 2,000-word essays with a single link to your own archive. Or you promised analysis and you’re sending news aggregation. The content might be good — better, even — but it’s not what they expected. Expectation violations trigger unsubscribes faster than quality issues.

    The third lie is identity. Your signup form is still positioned around your old job title, your old beat, or the audience you used to serve. You’ve moved on. Your newsletter has moved on. But your form is still recruiting people who want the old version.

    Why this happens (and why it compounds)

    Newsletter forms are set-and-forget infrastructure. You write them once, during setup, when you’re optimising for just getting the thing launched. Then they live on your site, in your Twitter bio, in guest post bylines, in podcast show notes. Everywhere except your regular editorial attention.

    Meanwhile, your newsletter evolves. You find your voice. You discover what your audience actually wants. You drop the Friday edition because nobody reads it. You add a midweek case study because engagement doubled. All of this is good. All of this is normal. None of it makes its way back to the form.

    The result: your best marketing asset — the archive your current subscribers share — is recruiting people who expect a product that no longer exists. They arrive confused. They disengage quickly. Your churn creeps up and you blame the content, when the real problem is the promise.

    How to audit your signup form against reality

    Open your last ten sent editions in one browser window. Open your primary signup form in another. Read the form copy out loud, then ask: would a stranger reading this know what those ten emails actually contain?

    Check frequency first. If you say weekly, count the sends. If you’re inconsistent, either commit to a schedule or change the promise to something true. “Regular” works. “When there’s something worth saying” works if your brand supports it. “Weekly” doesn’t work if you’re not weekly.

    Check format second. If you promise curation, make sure you’re curating. If you promise brevity, measure your word count. If you promise analysis, make sure you’re not just aggregating. Your form should describe the structure someone will encounter, not just the topic.

    Check identity third. Who is this newsletter for, right now, in your last ten editions? If you’ve pivoted from founder audience to operator audience, or from beginners to experienced practitioners, your form needs to reflect that. Specificity filters better than broad appeal.

    Rewriting the promise to match the product

    Once you’ve identified the gap, close it. This isn’t about writing better marketing copy — it’s about writing accurate copy. Tell people what they’re actually going to get.

    If your frequency varies, say that. “Sent every Tuesday, with occasional extra editions when something breaks” is a promise you can keep. If your format is mixed, describe the mix. “Long-form case studies, research breakdowns, and the occasional rant” sets clear expectations.

    If you’ve changed direction, say so explicitly on the form. Don’t bury the new positioning in the welcome email. Make sure anyone signing up today knows they’re getting the current version, not the version from your launch post that’s still ranking on Google.

    Your signup form isn’t a marketing page. It’s a contract. And right now, you might be in breach before you’ve sent a single email.

    If this resonated, reply and tell me what your signup form promised versus what you actually send now. I read every response, and the gap between promise and product is one of the most fixable retention problems in this entire industry.

  • Your newsletter isn’t a broadcast. Stop writing like it is.

    Your newsletter isn’t a broadcast. Stop writing like it is.

    If you grew up watching television or listening to radio, you absorbed a specific mental model: one person speaks, millions listen, nobody talks back. That model is burned into how most of us think about communication at scale.

    And it’s completely wrong for newsletters.

    The medium looks like broadcast—you write once, it goes to thousands—but it doesn’t behave like one. Email arrives in an inbox, not on a screen in a living room. It sits next to messages from your reader’s mum, their boss, and their bank. The context is intimate, not passive. Yet most newsletter writers still structure their prose like they’re reading the evening news.

    The broadcast instinct shows up everywhere

    You can spot broadcast thinking in the first three sentences of most newsletters. They open with sweeping statements, third-person observations, or—worst of all—preambles that contextualise the topic before getting to the point. “This week saw major developments in…” “Many people are asking about…” “It’s been a busy month for…”

    This isn’t just stylistic fussiness. Broadcast writing assumes a captive audience. It expects people to wait through the setup because they’ve already committed to watching or listening. But nobody is captive in an inbox. Your reader is one swipe away from something else, and they owe you nothing.

    Broadcast writing also avoids direct address. It speaks about things rather than to someone. It hedges with “one might consider” instead of “you should think about.” It uses the passive voice to create distance. All of this makes sense when you’re addressing a faceless mass. None of it makes sense when your words land in a personal space.

    What inbox writing actually requires

    Email isn’t broadcast and it isn’t conversation either—it’s correspondence. That’s a distinct form. Correspondence assumes a specific person on the other end, even if you’re sending the same message to ten thousand people. It’s written to someone, not at them.

    This shift changes everything. Correspondence gets to the point quickly because it respects the recipient’s time. It uses “you” and “I” freely because those pronouns reflect the actual relationship. It makes claims directly rather than cushioning them in caveats, because hedging in a one-to-one context feels evasive.

    The best newsletter writers sound like they’re writing to one person because, functionally, they are. Every reader experiences your email alone. They don’t see the list size or the open rate. They see words that either speak to them or don’t.

    This doesn’t mean being casual or chummy if that’s not your voice. Correspondence can be formal. But it’s always direct. It acknowledges the reader as a specific intelligence on the other end, not a demographic.

    How to audit your own broadcast instincts

    Pull up your last three newsletters. Read the first paragraph of each. Now ask: could this opening have appeared in a magazine article, a blog post, or a LinkedIn caption without changing a word? If yes, you’re probably writing in broadcast mode.

    Look for these patterns:

    • Third-person scene-setting before you get to the point
    • Rhetorical questions aimed at “people” rather than “you”
    • Passive constructions that obscure who’s doing what
    • Introductions that explain why the topic matters before saying anything useful

    None of these are capital offences. But they’re all signs that you’re writing for an audience in aggregate rather than a person in particular.

    The fix isn’t complicated: write your next newsletter as if you’re sending it to one specific subscriber. Picture them. Use their name in your head. Then remove the name before you send. The tone will stay.

    Why this matters more now

    Inbox competition has never been higher. Your readers aren’t just choosing between newsletters—they’re choosing between you and everything else that wants their attention in that same space. Broadcast writing feels like content. Correspondence feels like communication. One gets skimmed. The other gets read.

    The operators who figure this out don’t just get better open rates. They build different relationships entirely. Their readers reply. They forward emails to friends with a personal note. They renew paid subscriptions without hesitation because the experience doesn’t feel like consuming media—it feels like hearing from someone who’s talking to them.

    If you want that, stop writing like you’re on stage. Write like you’re in someone’s inbox. Because you are.

    What’s one broadcast habit you’ve noticed in your own writing? Hit reply and tell me. I read every response, and the good ones shape what I write next. That’s how correspondence works.

  • Your newsletter platform is tracking readers. Here’s what they know.

    Your newsletter platform is tracking readers. Here’s what they know.

    You chose your newsletter platform for deliverability, ease of use, maybe price. But every send generates a second data stream you probably didn’t budget for: the one your platform keeps about your readers.

    Not the opens and clicks you see in your dashboard. The other stuff. Device fingerprints. ISP relationships. Engagement velocity. Re-send behaviour. Some of it powers features you rely on. Some of it trains models you’ll never see. And unless you read the DPA appendix, you might not know where the line is.

    What gets tracked at platform level

    When someone opens your email, your ESP doesn’t just log a timestamp. Most platforms record the mail client, device type, operating system, and IP geolocation. They track when the email was opened relative to send time, whether it was forwarded, and if links were clicked in a specific sequence.

    Some platforms use this to build recipient profiles that span all senders on their infrastructure. If a reader subscribes to twelve newsletters on the same ESP, that platform can see their aggregate engagement pattern—even if you, the sender, only see your own metrics.

    This isn’t necessarily sinister. It’s how spam filters learn. It’s how send-time optimisation gets trained. But it does mean your subscriber data isn’t just yours.

    The training data question

    A growing number of ESPs now use machine learning to optimise delivery, subject line performance, and content recommendations. The models need training data. Your sends are part of that set.

    In most cases, this is anonymised or aggregated. But the definition of “anonymised” varies. And if your contract doesn’t explicitly limit secondary use, your newsletter’s performance data might be feeding a recommendation engine, a benchmark report, or a feature you’re not even using.

    Ask your platform: is my data used to train models for other customers? Can I opt out? What happens to historical data if I leave?

    Most won’t have a public answer. That’s the point. If you’re sending anything remotely sensitive—HR updates, student communications, legal advice—you need to know before the contract renews.

    What your readers don’t see

    Your subscribers agreed to your privacy policy, not your platform’s. But platform-level tracking happens upstream of that relationship. A reader might disable tracking pixels, use Apple Mail Privacy Protection, or block third-party cookies—and still generate behavioural data the moment their mail client pings your ESP’s server.

    Some platforms strip IP addresses after geolocation lookup. Others log them indefinitely. Some share data with parent companies or affiliates. A few sell aggregated insights to third parties.

    If your newsletter mentions privacy as a value, your platform’s data practices are part of your brand. A reader who discovers your ESP shares engagement data with advertisers won’t distinguish between you and them.

    What you can do

    Start with your Data Processing Agreement. It’s the boring document you signed when you onboarded. Look for clauses about “legitimate interest,” “service improvement,” or “aggregated analytics.” Those are often where secondary use lives.

    Then audit your dashboard. If your platform offers predictive features—send-time AI, content scoring, churn prediction—ask what data powers them and whether it’s siloed to your account.

    If you’re in the EU or UK, you have a legal right to ask how personal data is processed, even by your subprocessor. If you’re elsewhere, you have leverage: ESPs don’t want to lose customers over a documentation request.

    And if the answers aren’t satisfactory, consider whether a platform with a smaller feature set but tighter data boundaries might be the better trade. Not every newsletter needs machine learning. Most need trust.

    Want more on the operational mechanics behind the newsletters you send? Subscribe to One Two Three Send and we’ll send you one article like this each week—no tracking beyond what you’d expect, no upsell sequences, just the work.

  • The forwarding problem: why viral growth breaks your newsletter

    The forwarding problem: why viral growth breaks your newsletter

    Someone forwards your newsletter to a friend. That friend loves it, forwards it to three more people. One of those people screenshots your best bit and shares it on Twitter. Suddenly you’ve got reach you didn’t pay for.

    Sounds brilliant, right?

    It’s not. Or at least, it’s more complicated than the growth-hackers-turned-newsletter-gurus would have you believe. Because every forward creates a reader you don’t control, can’t measure, and—most importantly—can’t convert.

    The ghost audience problem

    Here’s what happens when your newsletter gets forwarded: you get phantom readers. People consuming your work without appearing in your subscriber count, your open rates, or your engagement metrics. They’re invisible.

    That might sound like a victimless situation—free exposure, right?—but it creates three specific problems. First, you’re making editorial decisions based on incomplete data. You think 40% of your list cares about topic X because that’s what your engaged subscribers click on, but you’re missing the forwarded audience that’s actually more interested in topic Y.

    Second, you can’t build a relationship with people you don’t know exist. They’re not getting your welcome sequence, your occasional subscriber-only perks, or your asks for feedback. They’re just… there. Lurking in someone else’s inbox.

    Third—and this is the one that actually costs you money—you can’t convert them. Can’t sell them your course, your consulting, your premium tier, your anything. They’re permanently locked outside your business model.

    Why “just add a subscribe link” doesn’t work

    The standard advice is to stick a subscribe link at the bottom of every email. “If you were forwarded this, subscribe here!” Done, problem solved.

    Except no one clicks it.

    Think about your own behaviour. When someone forwards you a newsletter, you’re reading it in a specific context—usually because the forwarder said “thought you’d find this interesting” or “this reminded me of you.” You read that one piece. You don’t immediately stop, scroll to the bottom, and subscribe to a publication you’ve seen exactly once.

    The conversion rate from forwarded reader to subscriber is abysmal because the friction is enormous and the trust hasn’t been built yet. They haven’t opted in to hearing from you. They opted in to hearing from their mate Dave, who happened to pass along your work.

    The economics of forwardability

    Here’s the uncomfortable bit: making your newsletter “forwardable” and making it valuable to your business are often opposing forces.

    Highly forwardable content tends to be standalone, evergreen, and broadly appealing. It’s the stuff that works out of context. A great essay, a useful framework, a properly funny observation. But that’s not usually what builds a sustainable newsletter business.

    What builds a business is specificity, continuity, and insider value. It’s the running jokes, the callbacks to previous issues, the stuff that only makes sense if you’ve been paying attention. It’s the “you had to be there” quality that makes subscribers feel like they’re part of something, not just consuming isolated chunks of content.

    The more forwardable you make each individual issue, the less you’re rewarding the people who actually subscribed. You’re optimising for the wrong audience.

    What to do instead

    Stop trying to engineer virality through forwards. If it happens organically, fine—but don’t structure your editorial strategy around it.

    Instead, focus on making your newsletter talkable rather than forwardable. Give people a reason to say “you should subscribe to this” rather than “let me send you this one issue.” That’s a small shift in language but a massive shift in outcome. One creates subscribers. The other creates forwarded emails that go nowhere.

    Build continuity into your structure. Reference previous issues. Create throughlines. Reward people for having been there from the start, or at least for having read the last few editions. Make your newsletter something that benefits from context.

    And if you’re worried about discovery—about how new people will find you if you’re not optimised for forwards—focus on your archive strategy, your SEO, your partnerships, your literally-anything-else. Because forwards feel like free growth, but they’re growth you can’t compound.

    If you found this useful, you’ll probably want to read the rest of what we publish. Subscribe to One Two Three Send for more operator-level thinking about what actually works in newsletter publishing—no fluff, no growth hacks, just the trade craft.

  • Why your reply-to address is quietly destroying trust

    Why your reply-to address is quietly destroying trust

    There’s a configuration field in your email platform you probably set once and never thought about again. It sits there, invisible to you, but your subscribers see it every single time they try to respond to your newsletter.

    It’s your reply-to address. And if it’s set to noreply@yourdomain.com or something equally unwelcoming, you’re sending a message louder than anything in your carefully crafted copy: Don’t talk to me.

    The signal you’re actually sending

    When someone replies to your newsletter, they’re doing something valuable. They’re engaged enough to open a compose window, type out thoughts, and hit send. That’s rare behaviour. Less than 0.5% of subscribers ever reply to a typical newsletter.

    But when that reply bounces back with an automated “this mailbox is not monitored” message—or worse, fails silently—you’ve just punished your most engaged readers. You’ve told them that despite asking for their attention every week, you’re not interested in a two-way conversation.

    The excuse is usually operational: “We can’t handle the volume” or “We don’t have resources to monitor replies.” But here’s the thing—if you’re getting enough replies that it’s genuinely unmanageable, that’s a signal your content is working. And if you’re not getting many replies? Then a noreply address is solving a problem you don’t have.

    What actually happens when you open replies

    Most newsletter operators imagine a flood. In reality, when you switch from noreply to a monitored address, you’ll typically see:

    • A small uptick in replies—usually 5-15 per week for every 10,000 subscribers
    • Roughly half will be genuine engagement: questions, stories, feedback
    • A quarter will be unsubscribe requests (people who couldn’t find the link)
    • The rest will be out-of-office replies and the occasional spam

    That’s manageable. Even at 50,000 subscribers, you’re looking at maybe 30-75 replies per week. That’s 10 minutes a day, maximum, even if you respond to every single one.

    And you don’t have to respond to every one. A simple filter can catch out-of-office replies. Unsubscribe requests take five seconds. What’s left are the messages from people who actually care—the ones who’ll become paid subscribers, who’ll share your work, who’ll tell you what’s resonating.

    The technical bit that matters

    Your reply-to address doesn’t need to be the same as your from address. In fact, it often shouldn’t be.

    If you’re sending from hello@yournewsletter.com via your ESP’s infrastructure, you can set the reply-to to your actual work email—the one you check. Most platforms make this a single field in your sender settings.

    What matters: make it an address you actually monitor. Not a shared inbox that becomes a graveyard. Not an alias that forwards into a folder you never check. An actual mailbox where replies become part of your workflow.

    If you’re genuinely worried about volume, set up a dedicated address like replies@yournewsletter.com and commit to checking it twice a week. Put it in your calendar. Treat it like the editorial feedback mechanism it actually is.

    Why this matters more than you think

    Email is already swimming against a tide of automation, AI-generated content, and parasocial one-way broadcasts. The newsletters that cut through aren’t necessarily the ones with the best design or the cleverest subject lines. They’re the ones that feel like they come from an actual human who might—possibly—care what you think.

    A reply-to address that works is a tiny signal. But tiny signals compound. They’re the difference between a newsletter that feels like a person and one that feels like a marketing channel.

    And occasionally, someone will reply with exactly the insight you needed for next week’s issue. Or they’ll point out an error before 10,000 other people see it. Or they’ll just say thanks, and you’ll remember why you started this thing in the first place.

    Check your reply-to settings this week. If it’s set to noreply or an unmonitored address, change it. See what happens. If you want to talk about what you find—or if this article rang true—hit reply. We actually read them.

  • Your newsletter doesn’t need a content calendar. It needs a decision tree.

    Your newsletter doesn’t need a content calendar. It needs a decision tree.

    You’ve seen the advice everywhere: plan your newsletter content weeks in advance. Build a content calendar. Map out themes. Schedule everything.

    And if you’re like most newsletter operators, you’ve tried it. You spent an afternoon colour-coding a spreadsheet, blocking out topics for the next six weeks, feeling incredibly organised.

    Then Monday arrived. The topic you’d planned felt stale. A better idea surfaced. Your carefully constructed calendar became just another thing to ignore.

    The problem isn’t your discipline. It’s that content calendars optimise for the wrong thing.

    What calendars actually optimise for

    Traditional content calendars are built around scheduling certainty. They answer “what am I sending on Thursday?” brilliantly. They give you the comfort of a plan, the appearance of strategy.

    But they don’t answer the questions that actually matter when you sit down to write:

    • Is this the right thing to say right now?
    • Does this serve my readers better than the other idea I had?
    • Am I writing this because it’s planned, or because it’s necessary?

    Worse, they create artificial pressure. You feel obligated to publish the planned piece even when something more timely, more urgent, more true is sitting right there. The calendar becomes a constraint, not a tool.

    Decision trees over deadlines

    Instead of planning what you’ll write, build a framework for deciding what deserves to be written. Think of it as a decision tree rather than a calendar—a set of criteria that helps you evaluate ideas in real time.

    Here’s what that might look like:

    Start with urgency. Is there something your readers need to know now? A platform change, a seasonal deadline, a common mistake you’re seeing repeatedly this week? Timely topics almost always outperform evergreen ones because they carry inherent urgency. If you’ve got something genuinely time-sensitive, that’s your topic.

    Then check for pattern recognition. Have you had the same conversation three times this week? Answered the same question from multiple subscribers? Noticed the same confusion cropping up? When you spot a pattern, you’ve found a topic that’s already proven itself relevant.

    Default to reader questions. Keep a running list—a note on your phone, a label in your inbox, whatever works—of questions subscribers actually ask. When nothing urgent surfaces and no patterns emerge, pull from this list. You’re solving a real problem for at least one person, which is infinitely better than inventing problems to solve.

    Only then consider your backlog. Those evergreen ideas you’ve been collecting? They’re your fallback, not your foundation. They’re what you write when nothing more pressing exists. And that’s fine—some of your best work will come from this category. Just don’t let the backlog dictate your schedule.

    What to actually plan

    This doesn’t mean you plan nothing. But instead of planning content, plan the infrastructure that makes good decisions easier.

    Block writing time, not topics. Protect Tuesday morning for writing, but don’t commit to what you’re writing until Monday night. Give yourself decision space.

    Build idea capture systems. You need somewhere frictionless to dump thoughts, questions, observations. The decision tree only works if you’re feeding it good inputs.

    Set standards, not schedules. Decide how often you send, what length you aim for, what quality bar you’re holding. Then trust yourself to meet those standards with whatever topic best serves readers this week.

    Create fallback frameworks. Have a few reliable formats you can deploy when you’re stuck: subscriber Q&A, case study breakdowns, contrarian takes on common advice. These aren’t planned in advance, but they’re ready when needed.

    When rigidity actually helps

    There’s one scenario where traditional calendars shine: publications with multiple writers, external contributors, or sponsorship commitments. If you’re coordinating with other people or honouring commercial obligations, you need the structure.

    But even then, build in flexibility. Reserve slots for reactive content. Keep buffer topics ready. Don’t let the calendar eliminate your ability to respond to what’s actually happening.

    If this approach feels uncomfortably unstructured, that’s the point. The discomfort comes from trading false certainty for real responsiveness. Most newsletter operators don’t have a planning problem—they have a deciding problem. And you can’t solve a deciding problem with a calendar.

    Subscribe to One Two Three Send for more operator-to-operator thinking on running newsletters that people actually want to read.

  • WordPress hosting for newsletter operators — a thorough comparison

    WordPress hosting for newsletter operators — a thorough comparison

    Most “best WordPress host” articles are SEO-driven affiliate roundups that recommend whichever provider pays the highest commission that quarter. This isn’t one of them. We have run our newsletter on three of these hosts personally, and migrated between them more than once. What follows is what actually matters when you’re running a newsletter on WordPress — and which hosts handle it well.

    The criteria that matter for a newsletter site (and what doesn’t)

    Standard hosting reviews talk about page-load speed, uptime, and CDN coverage. For a newsletter site those are baseline — every host on this list passes them. The criteria that actually decide your experience, in order:

    1. Plugin upload freedom — you need to upload custom plugin zips. Some “managed WordPress” tiers explicitly disable this. Check before you sign up, not after.
    2. Outbound HTTPS & DNS reliability — your plugin will call Anthropic’s API, your email provider’s API, and possibly external image services. Some restrictive hosts allowlist only a handful of outbound destinations. This is the single most overlooked criterion and the one most likely to bite you.
    3. Reliable WP-Cron — newsletter sending is cron-driven. Hosts that disable internal cron and replace it with an external trigger usually do it well, but it’s worth verifying.
    4. SMTP / port 465 outbound — if you use SMTP rather than an HTTP-based email API like Resend, port 465 needs to be open. A few hosts block it by default.
    5. PHP 8.1+ available — required by One Two Three Send. Every modern host has this, but ancient shared-hosting boxes don’t.
    6. Real human support — when something breaks at send time you want a chat window with a human, not a 48-hour ticket queue.

    Speed and uptime are the easy parts. The list above is what separates a host that “works for newsletters” from one that fights you every step.

    The six hosts we actually have an opinion on

    BigScoots — top pick for managed WordPress

    What you’re paying for: a small team that genuinely knows WordPress, support that responds in minutes via chat, custom plugin uploads allowed without restriction, and a stack tuned for performance.

    • Pricing: Plans start ~$35/month, scaling to $150+ for high-traffic sites
    • Plugin uploads: Yes, no restrictions
    • WP-Cron: Reliable, runs as expected
    • Worth checking before committing: outbound network policy. We have seen one BigScoots-hosted site where outbound DNS resolution from PHP was failing — likely a per-account firewall configuration, but worth raising with their support before signup if your plugin needs to make external API calls (which One Two Three Send does, to Anthropic and to your email provider). Their support resolved similar issues quickly when reported.
    • Worth knowing: the entry tier is more expensive than budget hosts, but the support response time alone justifies the difference once you’ve had your first 11pm “why isn’t my newsletter sending” panic

    Best for: newsletter operators who want minimal fuss and have the budget. Avoid if: you’re under $50/month total tooling budget and willing to manage more yourself.

    SiteGround — the reliable mid-tier choice

    The host most “best WordPress hosting” lists put first because their support is genuinely good and their entry pricing is approachable. Plugin uploads work without restriction, outbound network is generally permissive, PHP 8+ available everywhere.

    • Pricing: ~$2.99/month introductory rate, ~$15/month renewal. The renewal price is what matters.
    • Plugin uploads: Yes, no restrictions
    • WP-Cron: Reliable on shared plans, with their own cron scheduler tooling
    • Watch for: the introductory pricing is an aggressive teaser. Renewal at year two is roughly 5× the first-year rate. Budget for the renewal price, not the sticker.
    • Worth knowing: their dashboard is genuinely well-designed — staging sites, WP installs, SSL, backups all in one panel

    Best for: first-time WordPress users who want sensible defaults at a moderate price. Avoid if: you’ll panic at the year-two renewal — set a calendar reminder to evaluate then.

    Cloudways — managed-cloud middle ground

    Cloudways isn’t a host in the traditional sense — it’s a management layer that runs your WordPress install on top of cloud providers (DigitalOcean, Vultr, Linode, AWS). You pay them for the management; the underlying server is whichever cloud you pick. This sounds complicated but the result is excellent: real cloud-grade performance with a familiar managed-WordPress dashboard.

    • Pricing: ~$11/month for a basic DigitalOcean droplet via Cloudways, scaling smoothly
    • Plugin uploads: Yes, no restrictions
    • WP-Cron: Disabled by default, replaced with their server-side cron — works reliably once configured
    • Watch for: the dashboard is power-user-friendly but has a bigger learning curve than SiteGround. You’ll see terms like “vertical scaling” and “Varnish” that wouldn’t appear on a typical managed-WP host’s UI.
    • Worth knowing: the same money buys you noticeably more raw server power than at SiteGround. Better fit for sites that grow and don’t want to migrate

    Best for: operators comfortable with a slightly more technical dashboard who want serious performance per dollar. Avoid if: you want a one-click setup and never to think about server config again.

    DreamHost — the genuine budget option

    DreamHost is the budget host that doesn’t feel cheap. Pricing is honest (the renewal rate is the same as the intro rate), plugin uploads work, support is responsive enough.

    • Pricing: ~$3–5/month for the basic shared plan, with no aggressive renewal markup
    • Plugin uploads: Yes
    • WP-Cron: Reliable
    • Watch for: shared hosting performance ceiling. Once you cross ~10,000 newsletter subscribers, send batches start to feel slow. You’ll outgrow this tier and want to upgrade.
    • Worth knowing: they’re employee-owned and have been around since 1996 — the unfashionable kind of stability

    Best for: launching on a tight budget when you’re not yet sure the newsletter will stick. Avoid if: you already have audience momentum and need performance headroom from day one.

    Kinsta — premium alternative to BigScoots

    Kinsta runs on Google Cloud Platform’s premium tier. Performance is excellent, the dashboard is the best in this category, support is good. The catch: pricing.

    • Pricing: Plans start ~$35/month for one site, scaling steeply for traffic
    • Plugin uploads: Yes, no restrictions
    • WP-Cron: Reliable, with their own scheduler
    • Watch for: visit-based pricing. Hit the visit cap of your plan and you’re forced to upgrade. For a newsletter site (low traffic, mostly subscribers reading email) this is rarely a problem, but for a content-heavy site it can be.
    • Worth knowing: their dashboard has APM (application performance monitoring) included — useful for diagnosing slow sites without third-party tools

    Best for: sites that prioritise dashboard polish and Google Cloud infrastructure. Avoid if: you don’t see specific value over BigScoots at the same price point.

    WP Engine — popular but ask the question

    WP Engine is one of the largest managed-WordPress hosts. The product is solid, the dashboard is good, the performance is competitive. But there’s a specific catch that matters for our use case: their lower-tier plans have historically restricted custom plugin uploads.

    • Pricing: Plans start ~$20–30/month
    • Plugin uploads: Verify per plan — entry tiers have restricted custom plugin uploads in the past. Their list of “disallowed plugins” has also been long enough to break some legitimate setups.
    • WP-Cron: Replaced with their own scheduler, generally reliable
    • Watch for: the disallowed-plugins list. Before signing up, send their pre-sales chat the question: “Can I upload a custom plugin zip on plan X?” Get the answer in writing.
    • Worth knowing: if you need a host purely for one of WP Engine’s specialty integrations (e.g. their Genesis themes), this might still be the right choice

    Best for: sites already in WP Engine’s ecosystem. Avoid if: you haven’t yet verified your plan tier permits custom plugin uploads — newsletter sending depends on it.

    Quick comparison

    HostEntry priceCustom plugin zipsBest fit
    BigScoots~$35/moYesPremium managed, top support
    SiteGround~$15/mo (renewal)YesFirst-time WP users, solid all-rounder
    Cloudways~$11/moYesPerformance per dollar, slightly technical
    DreamHost~$3–5/moYesGenuine budget, no renewal markup
    Kinsta~$35/moYesPremium, GCP-based, polished UI
    WP Engine~$20–30/moVerify per planExisting ecosystem users, after verifying plugin policy
    A road sign with multiple direction arrows
    Photo: Wikimedia Commons (CC)

    Honest recommendation by situation

    • Just launching, want zero fuss, $35+/month is fine: BigScoots
    • Just launching, $15/month budget, want a familiar managed dashboard: SiteGround
    • Slightly technical, want best performance per dollar: Cloudways
    • Tight budget, prepared to migrate later: DreamHost
    • Already inside the Google Cloud ecosystem or want premium dashboard polish: Kinsta
    • Already on WP Engine and happy: stay (after verifying plugin policy)

    Three things to ask any host’s pre-sales chat before paying for a year:

    1. “Can I upload custom plugin zip files on plan X?” — verify in writing
    2. “Are there any outbound network restrictions from PHP?” — specifically ask about API calls to api.anthropic.com and api.resend.com
    3. “Is internal WP-Cron enabled, or replaced with an external scheduler?” — either is fine; you just need to know which

    If their pre-sales team can’t or won’t answer those three questions clearly, that’s information too.

    What about WordPress.com Business and Hostinger?

    Two we deliberately excluded:

    • WordPress.com Business (Automattic-hosted) is technically WordPress but practically a different product. Plugin freedom is heavily restricted, the editor is overlaid with their own UX, and the pricing tier needed to upload custom plugins is steep. Skip unless you have a specific reason.
    • Hostinger at the entry tier is genuinely cheap (~$2/month) and the performance is acceptable, but support is automated-first and the renewal markup is steeper than DreamHost’s. If you need budget hosting and don’t mind chasing answers via tickets, it’s an option — but DreamHost gives you better support for similar money.

    Subscribe to the daily newsletter for more honest takes on the tools in your stack — and the pro plugin in your welcome email so you can ship your first issue this week.

    Subscribe to One Two Three Send

    Daily tactics, templates, and stories for running a newsletter — and the pro WordPress plugin delivered free in your welcome email.

  • How to get more subscribers for your newsletter — without spending a cent

    Launching a newsletter is the easy part. The first hundred subscribers come from family, friends, and three Twitter posts. The second hundred is harder. The first thousand is the wall most newsletters never get past.

    Most growth advice tells you to go viral, write better headlines, post on LinkedIn five times a day, hire someone to do TikTok. Some of that works. None of it works as reliably as the most underrated growth lever in the newsletter business: cross-promotion with other newsletters.

    Why cross-promotion converts so well

    The maths is straightforward. A reader of another newsletter you respect is already someone who:

    • Reads emails (you’re competing with their inbox, not with cat videos)
    • Has demonstrated they will pay attention to a single sender’s writing for more than 30 seconds
    • Is interested in the broad topic the newsletter covers
    • Trusts the publisher’s recommendation enough to click through

    That stack of pre-qualifications is why subscribers from cross-promotion convert at 5-10× the rate of cold social traffic. The same thousand impressions in a Facebook ad and a peer newsletter recommendation will produce roughly one and ten subscribers respectively. The peer recommendation is also free.

    The friction that has stopped you doing this until now

    If cross-promotion is so good, why isn’t every newsletter doing it constantly? Because the manual version is a pain. You need to:

    • Find newsletters in your space
    • Email each publisher individually pitching a swap
    • Negotiate placement, copy, dates
    • Track who promoted whom and how it converted
    • Repeat for every new partner

    Existing cross-promotion tools solve this at the cost of $50–$300 a month. Some hosted newsletter platforms have internal cross-promotion networks, but they are limited to their own customers and don’t work if your newsletter lives on WordPress.

    The Newsletter Network — built into the One Two Three Send pro plugin

    Every site running One Two Three Send Pro can join a free cross-promotion network. You list your newsletter once. You drop a shortcode somewhere on your site. From that moment on, your readers see other newsletters from the network — and other sites in the network show yours back. Reciprocal, automatic, free.

    Selection is random with daily rotation, so the same visitor sees consistent picks per day but gets fresh ones the next. Click attribution is tracked automatically — you can see exactly how many impressions and click-throughs each side of the trade is producing.

    Quality control is handled by an AI auditor that reviews every new listing within minutes — coherent description, plausible category match, no spam markers. Borderline cases land in a manual review queue. You’ll never have someone else’s adult content or crypto-pump scheme rendered alongside your trusted brand.

    How to set it up — five minutes

    Step 1 — Verify your subscription

    You need to be an active subscriber to the free One Two Three Send daily newsletter for the network to accept your listing. Newsletter → Settings → Subscriber — paste the email you signed up with, click Verify subscription. Green badge appears.

    If you haven’t subscribed yet, the form at the bottom of this page handles it.

    Step 2 — Fill in your listing

    Newsletter → Settings → Newsletter Network. Tick Join the network. Four fields:

    • Newsletter name — the name your readers know it by
    • 1–2 sentence pitch — what lands in their inbox, what makes it worth reading. Up to 280 characters. Treat this like a tweet — make it earn the click
    • Subscribe URL — your signup page
    • Category — Operators / Marketing / Travel / Food / Sports / etc. Pick the closest match

    Click Save listing. Your listing goes to pending. The AI auditor reviews it within ten minutes; once approved, it’s live in the network and starts appearing in widgets on other sites.

    Step 3 — Embed the widget on your site

    Drop this shortcode into any page, post, or sidebar block:

    		
    
			
    Other newsletters you might like
    
			
    
									
    
						
    Love Ireland
    
													
    Everything great about the green emerald isle of Ireland.
    
												
							Subscribe						
					
    
									
    
						
    Love France
    
													
    Your guide to travelling in France — itineraries, regional guides, food, wine, and everything you need to plan your trip.
    
												
							Subscribe						
					
    
									
    
						
    Love Netherlands
    
													
    Canal towns, hidden villages, Dutch stories — a slow, loving look at the Netherlands, written by the people who love it most.
    
												
							Subscribe						
					
    
									
    
						
    Springbokfans
    
													
    The best Springbok updates, straight to your inbox. Only when something worth reading actually happens.
    
												
							Subscribe						
					
    
							
    
			
    
				Newsletters via the One Two Three Send network.				 · 
				Want your newsletter featured here? Click here

    The widget renders up to ten cards from the network — newsletter name, pitch, Subscribe button. Click-throughs go via our redirect endpoint so attribution data is reliable on both sides.

    The two highest-performing placements we have seen so far:

    • Below the fold of every blog post — your most-read content also has the longest dwell time, which is when readers are most receptive
    • On a dedicated /newsletters page linked from your main nav — anyone who clicks that link is by definition curious about other newsletters

    Step 4 — Watch the stats

    The same Newsletter Network settings tab shows lifetime impressions and clicks for your listing, refreshed daily. If your pitch isn’t converting, edit the description and save again — the auditor re-reviews automatically.

    What to expect

    Network volume scales with the number of participating sites. In the early days you’ll see a few impressions per day. As more newsletters join, the impression count grows linearly and the variety of cards each visitor sees gets richer.

    Conversion rate from impression to click typically lands at 1-3 percent for well-pitched listings. Conversion from click to subscribe depends on your signup page — anywhere from 20 percent for a clean dedicated landing page down to 5 percent for a generic homepage. So a hundred impressions on a good day produces somewhere between zero and one new subscriber. Stack a few hundred impressions a day across pages, and the compounding gets serious fast.

    The single biggest lever on your conversion rate is the pitch. Generic (“A newsletter about marketing”) performs much worse than specific (“Daily case studies on what changed open rates last week, with the numbers”). Treat the description like ad copy, because that is what it is.

    Why this is in the plugin

    Building any of the major paid cross-promotion tools alone takes a six-figure engineering team. Building it once, free, into the same WordPress plugin you already use to send your newsletter is closer to a weekend’s work — and it benefits everyone in the network proportionally to how much they participate. That is the only reason it exists. There is no premium upsell. The pro plugin is free if you are subscribed to our daily newsletter, and the network is included.

    Subscribe below to get the pro plugin and join the network — your first hundred new subscribers from cross-promotion start the day you opt in.

    Subscribe to One Two Three Send

    Daily tactics, templates, and stories for running a newsletter — and the pro WordPress plugin delivered free in your welcome email.

  • The archive page nobody reads is quietly tanking your growth

    The archive page nobody reads is quietly tanking your growth

    Your newsletter archive sits there, quietly indexed by Google, visited by exactly nobody except that one person who missed an issue three months ago. You’ve probably never looked at the analytics. Why would you? It’s just a dumping ground for old emails.

    Except it’s not. Your archive is doing one of two things right now: it’s either turning casual visitors into subscribers, or it’s convincing them you’re not worth their inbox space. There’s no neutral ground here.

    What your archive actually does

    Here’s what most operators miss: your archive is often the first branded touchpoint people have with your newsletter. They don’t find you through a viral post or a recommendation. They Google something specific, land on an issue from six months ago, read it, and then… what?

    If you’re lucky, they scroll to find a subscribe form. If you’re not, they bounce in twelve seconds because your archive page is a wall of text with no context, no branding, and a signup box shoved in the footer next to your registered address and unsubscribe policies.

    The difference between these two outcomes is almost never about the quality of your writing. It’s about whether you’ve treated your archive like a publication or like a legal requirement.

    The four things killing your archive

    No clear value proposition at the top. Someone lands on Issue #47 about email authentication. Do they know what else you write about? Do they know who you are? Or is it just a headline, body copy, and then nothing?

    The signup form is an afterthought. Footer-only forms convert at maybe a tenth the rate of contextual forms placed mid-content or at the top. Your best writing is doing the selling—put the form where people are actually paying attention.

    Ancient content with no freshness signals. If your most recent issue in the archive is from three weeks ago, visitors assume you’ve stopped publishing. Update frequency matters. If you publish weekly, your archive should reflect that within days, not whenever you remember to log into your CMS.

    Zero internal linking. Each issue should connect to related past issues. Not in a “you might also like” widget that looks like spam, but inline, naturally. It signals depth, keeps people on-site longer, and gives Google more to index and rank.

    What good looks like

    A working archive doesn’t need to be fancy. It needs to answer three questions the moment someone lands: what is this publication, why should I care, and how do I get more?

    That means a short, visible bio or masthead at the top of every issue page. It means a signup form placed where people will actually see it—usually right after the first few paragraphs, or in a sticky sidebar if your layout supports it. And it means showing recent issues prominently so people can see you’re active.

    Some operators go further: they add category tags, curated “start here” collections, or even light paywalls that tease premium content. All of that can work. But the baseline—clear identity, obvious signup path, visible recency—is non-negotiable.

    The simplest test

    Open an incognito window. Google a topic you’ve written about. Click through to one of your archive issues. Now pretend you’ve never heard of your newsletter.

    Can you figure out what it’s about in five seconds? Can you subscribe without scrolling past three screenfuls of text? Does it look like something published this year?

    If the answer to any of those is no, you’re leaking subscribers every single day. Not because your writing isn’t good enough, but because your archive is doing the opposite of its job.

    If this hit home, you’ll want the next issue. Reply with “archive” and I’ll send you the follow-up: how to structure your archive for SEO without turning it into a content farm. Or just subscribe here and get every issue delivered.

  • You’re segmenting wrong — and it’s killing your inbox placement

    You’re segmenting wrong — and it’s killing your inbox placement

    Ask any email marketer about segmentation and they’ll tell you it’s about sending the right message to the right person. Better targeting, higher engagement, more conversions. All true.

    What they won’t tell you—because most don’t realise it—is that how you segment can directly damage your deliverability, sometimes irreparably.

    The problem isn’t segmentation itself. It’s that most operators treat it purely as a content exercise when it’s actually an infrastructure decision with serious technical consequences.

    The engagement trap nobody talks about

    Here’s the pattern: you create a segment for your most engaged subscribers. Makes sense. You want to reward the people who actually open and click. Maybe you send them early access, exclusive content, or your best offers.

    Meanwhile, your less-engaged segment gets… what? Re-engagement campaigns? Less frequent sends? Or worse, they stay on your main list getting everything, slowly tuning out.

    The damage happens quietly. Each send to unengaged subscribers teaches mailbox providers that your mail isn’t wanted. Your sender reputation isn’t calculated per-segment in your ESP—it’s calculated by domain and IP address. That disengaged segment you’re still mailing? They’re poisoning deliverability for everyone, including your best subscribers.

    Most operators discover this backwards. Their open rates drop across all segments. They check their deliverability, find themselves in the spam folder, and can’t figure out why their “good” emails aren’t landing—even to people who’ve opened every message for months.

    Volume patterns matter more than you think

    Mailbox providers are pattern-matching machines. They’re looking at volume, frequency, and consistency as signals of legitimacy.

    When you create segments and start sending different volumes to different groups, you create volatility. Send 50,000 emails on Monday to your full list, then 5,000 on Wednesday to a segment, then 30,000 on Friday to a different slice—you’ve just told Gmail and Outlook that your sending behaviour is erratic.

    Erratic senders get scrutinised. Consistent senders get trusted.

    This doesn’t mean you can’t segment. It means you need to think about segment architecture, not just segment criteria. If you’re going to split your list, plan for predictable send volumes. If you’re testing a new segment strategy, warm it up like you would a new domain. Don’t just flip a switch in your ESP and hope for the best.

    The suppression problem hiding in plain sight

    Most segmentation advice tells you to suppress unengaged users. Stop sending to people who haven’t opened in 90 days, 180 days, whatever your threshold is.

    Sounds sensible. Except here’s what actually happens: you remove your least engaged subscribers, which increases your open rate percentage—but decreases your absolute engagement volume. If you were getting 10,000 opens from 100,000 sends, and you suppress 40,000 inactive subscribers, you might now get 8,000 opens from 60,000 sends. Your rate went from 10% to 13%. Your volume dropped 20%.

    Mailbox providers don’t care about your rate. They care about absolute signals. Fewer opens, fewer clicks, less forwarding, less time spent reading—that’s a negative trend, even if your internal dashboard shows green arrows.

    The fix isn’t to keep mailing dead addresses. It’s to understand that suppression is a last resort, not a first move. Re-engagement should come first. Frequency reduction should come second. List hygiene should be ongoing, not a quarterly purge. And when you do suppress, do it gradually so the volume change doesn’t trigger algorithmic red flags.

    What good segmentation actually looks like

    Good segmentation starts with a map. Not a Venn diagram of interests, but a sending architecture: how many segments, what volume each gets, how often, and how those volumes interact with your overall sender reputation.

    You should be able to answer: if this segment gets throttled or blocked, does it affect the others? If engagement drops in one segment, how quickly does it drag down the whole domain? If you scale one segment, do you have the IP reputation and infrastructure to support it?

    Most operators can’t answer these questions because they’ve bolted segmentation onto their programme without thinking about the plumbing underneath.

    Start small. Test one segment with consistent volume and frequency before you carve up your list into a dozen pieces. Monitor deliverability metrics—inbox placement, spam folder rate, domain reputation—not just engagement metrics. And if you’re running multiple brands or products from the same domain, for the love of inboxes, understand that they share a reputation.

    If you’re rethinking your segmentation strategy or just want to stay ahead of shifts like this, subscribe to One Two Three Send. We dig into the operator-level details that actually matter—no fluff, no beginner basics, just the things that break at scale.

    Segmentation isn’t wrong. But if you’re doing it without considering how mailbox providers see your sending behaviour, you’re optimising for the wrong scoreboard.

Powered by
►
Necessary cookies enable essential site features like secure log-ins and consent preference adjustments. They do not store personal data.
None
►
Functional cookies support features like content sharing on social media, collecting feedback, and enabling third-party tools.
None
►
Analytical cookies track visitor interactions, providing insights on metrics like visitor count, bounce rate, and traffic sources.
None
►
Advertisement cookies deliver personalized ads based on your previous visits and analyze the effectiveness of ad campaigns.
None
Powered by