How to build a community around your newsletter

Start with reply culture

You don't need a new tool to learn whether readers want to talk. End each issue with one specific question, answer every reply, and quote the best ones (with permission) in the next issue.

Ask new subscribers to add your sending address to their contacts, too. Google's sender guidelines say "messages sent from an address in the recipient's contacts are less likely to be marked as spam," and Kit says asking subscribers to add you to their contacts "helps your emails reach their primary inbox."

Deliverability basics matter as you grow. Senders of more than 5,000 messages a day to Gmail have needed SPF, DKIM, DMARC and one-click unsubscribe since February 1, 2024, and Google says to keep spam rates in Postmaster Tools below 0.10% and never reach 0.30%.

Tip: Put your reply question in the welcome email, right next to the request to add your address to contacts.

Open comments on your web archive

Email replies only reach you. Comments on the web version of each issue let readers see and answer each other, and the archive keeps those discussions findable. If you're still choosing a tool, our best newsletter platforms guide compares them.

• CommentCamp on your own site: if your archive lives on WordPress or any HTML or CMS site, CommentCamp turns each issue into a discussion page with free comments and community spaces, through an official WordPress plugin or a universal embed script.
• Substack: turn comments on in Settings, under Community, then choose per post: Everyone, free or paid subscribers, paid subscribers only, founding members or no one. Free subscribers can't comment on paid posts, and you can pin comments.
• Ghost: native comments are limited to logged-in members, and you can open them to all members or paid members only. Ghost's May 27, 2026 changelog, "Comment threads, votes and pins," added a dislike button alongside likes.

CommentCamp (our product) adds threaded replies, automated spam filtering, a moderation queue and optional member levels and quests, and one reader account works across every CommentCamp site. Site owners pay $0, readers never pay to comment, and there are no ads. It's in private early access, so join the waitlist for an invite.

Add a subscriber chat or feed

When the same names keep showing up in your comments, some readers will want to talk between issues.

On your own site, CommentCamp community spaces give them threads between issues, sharing replies, profiles and notifications with your archive comments.

Substack has two tools for this. Chat is a private space for subscribers: a publication can run up to 16 chats, including the main subscriber chat, each open to all subscribers, paid subscribers or founding members, and threads can go out as email. Notes are public short posts on Substack profiles and the Home feed, and you can limit who replies.

beehiiv's pricing page lists community features too, including feed posts, channels, DMs and group chats, member profiles, moderation and access control by tier. Its free plan covers up to 2,500 subscribers; Lite costs $49 a month and Pro $95 a month, billed annually.

When to add Discord, Slack or Circle

A separate community app makes sense when readers share an ongoing job, hobby or problem they'd discuss daily without waiting for your next issue. The trade-off: members join another app, and the conversation lives off your site.

Lenny's Newsletter shows how this works at scale. A paid subscription costs $20 a month or $200 a year ($400 a year for the founding tier), and paid subscribers get "a thriving private Slack community (30k+ members strong!)" plus meetups, AMAs and mentorship.

Discord gives you servers, channels and roles for real-time chat. Circle suits structured spaces: Professional costs $89 a month billed yearly ($99 monthly) and Business $199 ($219 monthly), with a 14-day free trial. Our guide on how to build an online community covers the wider trade-offs.

Note: Start with one ritual you can keep every issue, like a reader question or a monthly AMA, before adding more channels.

Paid community tiers

Many writers keep the newsletter free and put the community in a paid tier. Fees then matter:

• Substack is free to publish on but keeps 10% of subscription revenue, plus Stripe's 2.9% + $0.30 per US card payment and a 0.7% Billing fee on recurring payments.
• Ghost says "Ghost charges 0% transaction fees." You pay Stripe (2.9% + 30 cents) and hosting, from $15 a month billed yearly on Starter for up to 1,000 members, or you self-host the open-source version.
• beehiiv takes 0% of paid subscription revenue; Stripe fees still apply.

Paid perks can be simple: comments limited to paid or founding members, a chat for paid subscribers only, or a private Slack with AMAs, as Lenny's Newsletter does.

Newsletter community formats compared

Metrics that show a community is forming

Don't judge your community by open rates. Google says "Google doesn't track open rates" and "low open rates aren't necessarily an accurate indicator of deliverability or spam classification issues."

Track what readers do instead:

1. Replies per issue
2. Comments per post on your web archive
3. Distinct members who post each month
4. The share of paid members active in chat or community spaces

When readers start replying to each other instead of only to you, you have a community. More ideas are in our reader engagement guide.