← Back to VeloCMS Learn

newsletter · Oct 18, 2026

What makes a really good newsletter?

A practical, sourced guide to what makes a newsletter good: promise, cadence, welcome email, deliverability and consent, plus seven tools compared.

A really good newsletter makes one specific promise, keeps it on a schedule people can rely on, and lands in the inbox because the boring technical parts (authentication, easy unsubscribe, a clean list) are done right. Everything else, from subject lines to design, is secondary to those three things. The tool you pick matters less than most comparison posts suggest, but it can make the boring parts either automatic or annoying.

Full disclosure: I work on VeloCMS, which is one of the seven tools I compare near the end. It isn't first, it isn't the right pick for most people reading this, and it gets the same treatment as the others, weaknesses included.

Last verified: 2026-10-18.

What promise should a newsletter make?

Before cadence or design, you need a sentence a stranger could repeat. "Every Thursday, one practical lesson on pricing for freelance designers" is a promise. "Thoughts on business and life" isn't, and it's the reason a lot of newsletters stall after issue six: neither the writer nor the reader knows what an issue is supposed to be.

A useful test is to finish the sentence "Subscribe if you want..." without using the words "updates" or "insights." If you can't, the readers can't either. The promise also tells you what to leave out. A newsletter about pricing for designers doesn't need your holiday photos, however nice the holiday was.

How often should you send, and how long should an issue be?

Pick a cadence you can keep for a year, not the one that sounds impressive. A fortnightly issue you never miss beats a weekly one that slips to "whenever." Readers learn your rhythm, and the rhythm is part of the promise. If you have to skip, say so in one line rather than going quiet; silence is how people forget they subscribed, and forgotten subscribers are how spam complaints happen.

Length follows the promise. A short note with one idea and a link can be a perfectly good issue, and so can a long essay people save for the weekend. What doesn't work is the in-between: a long email with six loosely related items, where nothing gets room to land. There is no magic word count, and I'm not going to invent one.

What should the welcome email do?

The welcome email is the one message nearly every new subscriber opens, because they've just asked for it. Waste it and you've wasted your best attention of the whole relationship.

Good welcome emails do four plain things. They confirm the promise (what's coming, how often, from whom). They deliver something immediately, such as your best past issue or a short guide, so the first experience is a reward and not a receipt. They ask for a reply with one easy question ("what are you working on right now?"), which tells mailbox providers that real people talk to you. And they tell people how to leave. That last one feels counterintuitive, but making unsubscribing obvious is cheaper than being reported as spam, as the deliverability section below explains.

How do subject lines and preview text work best?

The subject line is a headline for one reader in a crowded inbox, and the preview text is the second line of it. Treat them as a pair. If the subject asks a question, let the preview start answering it. If the subject names the topic, let the preview add the angle.

Specific beats clever. "The invoice template I stopped apologising for" says more than "Quick thought." And be honest: the FTC's CAN-SPAM guide says "the subject line must accurately reflect the content of the message" (FTC, accessed 2026-10-18). That's a legal line, but it's also just good manners, because a subject that over-promises trains readers to stop trusting the next one.

What does one good issue look like?

One main idea. Everything in the issue either sets up that idea, proves it, or tells the reader what to do with it. If you have a second idea, it's next week's issue, and you've just solved next week's blank page.

Structure it for skimmers who might become readers: a first line that earns the second, short paragraphs, descriptive links (not "click here"), and one clear thing to do at the end, whether that's replying, forwarding, or reading the full post.

Should a newsletter be plain text or designed, and what about mobile?

Both can be good. A plain, text-led layout reads like a note from a person, loads instantly, and is hard to break. A designed layout (header, images, buttons) suits a publication, a shop, or anything with a visual identity. The usual mistake is designing for the desktop mockup. Check every issue on a phone-sized screen: a single column, readable text, thumb-sized buttons, and alt text on images so the message survives when they're blocked. Start plain and add design only where it earns its place.

Which metrics can you still trust?

Be careful with open rate. Apple's iCloud documentation says Mail Privacy Protection "prevents senders from seeing if you've opened the email they sent you" and "hides your IP address so senders can't link it to your other online activity" (Apple, accessed 2026-10-18). There's a side effect for senders: Litmus explains that Apple routes email through a proxy server that pre-loads content, including tracking pixels, which "makes the ESP think the email has been opened" even if the reader didn't open it (Litmus, accessed 2026-10-18). That article, last updated in September 2021, dates the feature's arrival in Mail on iOS 15 and iPadOS 15 to 20 September 2021.

I'd treat opens as a rough signal at best, and never as a number to optimise against. Better signals are the ones that need a human: replies, clicks on links, forwards, and unsubscribes (yes, unsubscribes are useful; they tell you who the issue wasn't for). Track those over weeks, not issue by issue, because any single send is noisy.

What deliverability basics does a newsletter need?

Deliverability sounds like a specialist topic, but the entry-level version is three DNS records and one header.

Google's sender guidelines apply to senders who send more than 5,000 messages a day to Gmail accounts, and they require authentication: "Set up SPF and DKIM email authentication for your domain" and "Set up DMARC email authentication for your sending domain," where the DMARC policy can be "set to none" (Google, accessed 2026-10-18). Marketing and subscribed messages "must support one-click unsubscribe" as well as a visible unsubscribe link in the body, and the spam rate shown in Postmaster Tools should stay "below 0.30%." Google's FAQ defines a bulk sender as one that sends "close to 5,000 messages or more to personal Gmail accounts within a 24-hour period" and adds that bulk sender status doesn't expire: a sender that meets the criteria at least once is permanently considered a bulk sender (Google FAQ, accessed 2026-10-18). The requirements started in February 2024.

Yahoo's rules are similar. Its sender hub says bulk senders should "Implement both SPF & DKIM," publish a DMARC policy of at least p=none, support one-click unsubscribe, "keep your spam rate below 0.3%," and "honor unsubscribes within 2 days" (Yahoo, accessed 2026-10-18). Google's page names the RFC 8058 method for one-click unsubscribe, which uses two headers: List-Unsubscribe with an HTTPS address, and List-Unsubscribe-Post containing List-Unsubscribe=One-Click (RFC 8058, accessed 2026-10-18). The RFC exists because mail software sometimes fetches URLs in headers, which could unsubscribe people by accident.

A small newsletter may never hit 5,000 Gmail messages a day, but I'd still follow all of this. It costs almost nothing, and "we're below the threshold" is a bad plan for a list you hope to grow. In practice: send from a domain you control, add the authentication records your tool asks for, and check that the tool adds the one-click headers. Ask the vendor; I wouldn't assume.

How do you keep a list healthy?

A smaller list of people who want your email beats a large list of people who don't. Remove hard bounces promptly. Honour every unsubscribe quickly (Yahoo's two days is a sensible outer limit). Consider a double opt-in confirmation if you get bot signups. And think about people who haven't opened or clicked in a long time: given the open-rate problem above, "hasn't clicked in six months" is a more honest test than "hasn't opened." Send those readers a plain "do you still want this?" email, and let them go if they don't answer.

I'm not a lawyer and this isn't legal advice; the rules vary by country and by how you collect addresses. These are the official starting points.

In the US, the CAN-SPAM Act requires accurate header information, honest subject lines, a valid physical postal address, a clear explanation of how to opt out, and that you honour opt-outs within 10 business days. It also says you can't contract away your responsibility by hiring a tool to send for you. The FTC page, last edited January 2024, lists civil penalties of up to $53,088 per violating email; the FTC adjusts that figure for inflation, so check the current number before relying on it (FTC, accessed 2026-10-18). If your newsletter promotes anything (products, paid tiers, sponsors), assume it applies to you.

In the EU, GDPR consent must be an actual opt-in: Recital 32 says "Silence, pre-ticked boxes or inactivity should not therefore constitute consent," and Article 7(3) adds: "It shall be as easy to withdraw as to give consent" (EUR-Lex, accessed 2026-10-18). In the UK, the ICO's email marketing guidance says you must not send marketing email to individuals unless they have specifically consented, allows a narrower "soft opt-in" for existing customers (it does not cover prospective customers or new contacts), and says the opt-out must be offered when you collect details and in every message you send (ICO, accessed 2026-10-18).

The practical rule that satisfies all three: unticked signup box, plain words about what they're signing up for, a postal address in the footer, and an unsubscribe that works in one click.

Why keep a public archive, and why read your replies?

An archive turns every issue into something a search engine, a link, or an AI assistant can find. Subscribers lose emails; the web keeps pages. A public archive also doubles as a signup pitch: a visitor can read three of your issues before deciding to trust you with an address.

Replies are the cheapest research you'll ever get. Send from a real address that accepts replies, not a no-reply mailbox. Answer them, and notice which questions repeat; those are your next three issues. Replies also help deliverability: people writing back is the opposite of a spam signal.

Which tools make it easier to run a good newsletter?

Seven tools, each checked against its own pages on 2026-10-18. The order isn't a ranking. A few pricing pages only show real numbers after you move a slider, so figures are for the default or smallest size I could read (usually 1,000 subscribers), and your list size will change them. "Billed yearly" prices are per month. Substack's help center blocked my automated fetch, so I only use Substack facts that its going-paid and features pages state.

Substack

Substack is the lowest-friction way to start. Its features page says Substack is free to use, with no monthly fees and no subscriber limits on the free tier, and that it takes a 10% revenue share only when you earn money from paid subscriptions. Its going-paid page puts it this way: "Writers keep 90% of their revenue minus credit card fees." I'm not quoting card-processing percentages, because I couldn't read them on a Substack page. The features page also lists custom domains, subscriber CSV import and export, a visual theme editor, Notes, native podcast and video hosting, and publication chat.

The real strength is discovery. Substack's support articles describe recommendations that show readers other publications right after they subscribe, optionally on a publication's homepage, and in recommendation digest emails sent to subscribers. A newsletter that fits the network can grow with no marketing budget.

The trade-off is the permanent 10% on paid revenue (a flat cost that grows with your success) and a product shaped around Substack's own network. If you want your newsletter to live inside a bigger site with your own pages, shop and structure, you'll probably outgrow it.

beehiiv

beehiiv describes itself as "the all-in-one newsletter platform for creators, publishers, and brands," with no-code website hosting, custom domains, a recommendations network and a native ad network (beehiiv, accessed 2026-10-18). On its pricing page, Free covers up to 2,500 subscribers with unlimited sends and the recommendation network, but no automations or paid subscriptions, and beehiiv branding stays on. Lite is $49 a month billed yearly at 1,000 subscribers ($59 monthly), with up to 10 live automations; Pro is $95 yearly ($109 monthly), adds unlimited automations and removes beehiiv branding. It takes 0% of paid subscription revenue, though Stripe's 2.9% + $0.30 still applies.

It's a strong pick if growth tooling matters: recommendations on the free plan, an ad network from Lite (not during trials or in all regions), and the website bundled in. The weak spot is the price climb. Removing the branding means moving to Pro, and at 1,000 subscribers its Lite and Pro prices sit above the entry paid plans of Ghost, Kit and MailerLite. It's built for growing and monetising a newsletter, not for running a blog with a newsletter attached.

Ghost

Ghost calls itself "open source, independent, and funded 100% by its users" and carries a Non-Profit Foundation badge (Ghost, accessed 2026-10-18). Its pricing page shows, on the yearly-billing view, Starter at $18 a month, Publisher at $29 and Business at $199, with Starter and Publisher including 1,000 members. "All plans include unlimited email sends with no restrictions." Starter doesn't offer paid subscriptions; Publisher and up list 0% transaction fees from Ghost, with payment-processor fees still applying. It also lets you run Ghost on your own server, though the page puts it bluntly: "if you self-host then you're the one who loses sleep."

Ghost suits publishers whose newsletter and membership are the whole business. It's a full publishing platform, with themes and a real site, not an email tool bolted onto one. The limits: no free plan (each paid plan has a "Try for free" button, and the page doesn't state the trial length), and the paid tier you need for subscriptions is a step up from the entry plan.

VeloCMS

VeloCMS is a blog CMS with a newsletter built in. You send a blog post to a segment (everyone, free members, paid members, or a tag) through Resend, so the post is already on your blog when the email goes out. On velocms.org/pricing, Pro is $9 a month ($86.40 billed annually) with newsletter tag segmentation and up to 5,000 subscribers; Business is $29 ($278.40 annually) with up to 50,000 subscribers and a custom sender domain; Agency is $69 ($662.40 annually) with unlimited subscribers. Paid memberships use your own Stripe key with no platform transaction fee, and Stripe's own fees apply. Every plan starts with a 14-day trial, a card is required, and nothing is charged until day 15. There is no free plan.

The honest limits: it's a young product with a much smaller ecosystem and community than Ghost or Substack, and there's no cross-publication discovery network like Substack's or beehiiv's recommendations. The automation editor is basic (a trigger on signup or on a tag, then emails with delays), not a visual branching builder. The custom sender domain, which matters for authentication, is on Business, not Pro. The one-click unsubscribe headers described earlier were only added to its campaign and automation mail in October 2026 (I checked the code, not a third-party audit), so it's newer to this than the others.

Kit

Kit (formerly ConvertKit) is built for creators who sell. Its pricing page offers a Free plan for up to 10,000 subscribers with unlimited broadcasts, landing pages, forms, tagging and segmentation, and the ability to sell digital products and subscriptions. Visual automations and email sequences start on Creator, which is $33 a month billed yearly ($390) at 1,000 subscribers. Pro lists at $66 with a limited-time $50 first-year offer. Creator and Pro have a 14-day trial with no card required, and the page advertises free migrations.

Kit's strength is the automation builder and creator tooling, and the free tier is generous in list size. The catch is that the first welcome sequence you build is the thing that pushes you onto a paid plan. One more honest note: the page quotes two different commerce fees ("0.6%" in one section and "3.5% + 30c" in its comparison table), so read the fine print before you plan on selling through it.

Buttondown

Buttondown is a small independent: its pricing page says it's a fully remote team, "profitable, self-funded," and running since 2017. The first 100 subscribers are free. The base price already includes a rich text or markdown editor, sending from a custom domain, and hosted newsletter archives. Tagging and segmentation, paid subscriptions, comments and surveys, analytics, RSS-to-email and attachments are each +$9 a month; sponsorships, archives on a custom domain, multiple newsletters and automations are +$29; whitelabeling and teams are +$79. It charges for active subscribers rather than every contact, and the prices assume at most one email a day to your whole list. The base price depends on a subscriber slider, so check your own number.

It's a good fit for writers who want a straightforward tool, a markdown-friendly editor and an API, and who like independent vendors. The à la carte model is the trade-off: each feature is cheap, but a list that needs segmentation, paid subscriptions and automations adds up to more than the sticker price suggests.

MailerLite

MailerLite's pricing page lists a Free plan (250 subscribers, 2,500 monthly emails), Comfort from $12 a month and Power from $25 (the starting prices in its FAQ; the price rises with your list, and paying yearly saves 10%). Comfort allows monthly sends of 10 times your subscriber tier, 50 automations, 10 forms and 3 seats; Power has unlimited emails (subject to fair use), automations, forms and seats. All plans offer a 14-day trial with no card required.

It's the tool I'd price first for a small list that wants real automation without a big bill. The weaknesses: the free plan is small, Comfort has an email cap tied to your list size that a growing list will notice, and it's a marketing-email platform first, so the blog-and-archive side is something you bring yourself.

Who is each option best for?

Substack: writers who want the lowest-friction start and a discovery network, and don't mind a 10% cut on paid revenue.

beehiiv: newsletter-first operators who want growth tools (recommendations, ads, a built-in site) and can afford the higher tiers.

Ghost: publishers whose newsletter and membership are the business, who want a real site and no platform cut on payments from Publisher up.

VeloCMS: people who want a blog, newsletter and membership in one login, and don't need a discovery network or a visual automation builder.

Kit: creators selling digital products who want visual automations and a free start for a large list.

Buttondown: writers who want a simple, independent, markdown-friendly tool and are happy to add features one by one.

MailerLite: small lists that want a full automation builder at a low monthly price.

When is VeloCMS the wrong choice?

Often, honestly. If you want readers to discover you through a network of other newsletters, Substack and beehiiv have that and VeloCMS doesn't. If you need branching automations, SMS or A/B testing, pick Kit or MailerLite. If you already have a site you love on WordPress or Webflow and just need to send email, moving the whole site for a newsletter is a lot of work for a small gain; a standalone tool fits better. If you need a free tier, there isn't one, only the 14-day trial. And if you rely on a big library of third-party integrations or a large community for help, the ecosystem here is much smaller than Ghost's or WordPress's.

FAQ

Do I need SPF, DKIM and DMARC for a small newsletter? Google's rules apply to senders reaching roughly 5,000 or more Gmail messages a day, and Yahoo's to bulk senders, but both ask for authentication and one-click unsubscribe (Google, Yahoo). Setting them up early is cheap insurance.

Is open rate still worth watching? Only loosely. Apple says Mail Privacy Protection stops senders from seeing whether you opened an email (Apple), so watch replies and clicks instead.

Is there a free option for a new newsletter? Substack is free to use (Substack), and Kit, beehiiv, MailerLite and Buttondown have free tiers of different sizes (see their pricing pages above). Ghost and VeloCMS have no free plan.

Sources (all accessed 2026-10-18)

Google sender guidelines · Google sender FAQ · Yahoo sender best practices · RFC 8058 · Apple iCloud: Mail Privacy Protection · Litmus on Mail Privacy Protection · FTC CAN-SPAM guide · GDPR, EUR-Lex · ICO email marketing · Substack going paid · Substack features · Substack recommendations · beehiiv · beehiiv pricing · Ghost · Ghost pricing · Kit pricing · Buttondown pricing · MailerLite pricing · VeloCMS pricing

Share this post
Report
What makes a really good newsletter? | VeloCMS Learn