LinkedIn newsletters bring reach—but at what cost?
The café two doors down replaces its menu boards every Monday morning; you can hear the drill through the office wall at half-seven, then smell the espresso grind an hour later when the queue forms.
LinkedIn newsletters bring reach you don’t own—here’s when that trade-off works
LinkedIn’s newsletter feature delivers cold impressions faster than your owned list, but you’re building on rented land.
LinkedIn newsletters put your content in front of followers’ inboxes and surface it to non-followers through algorithmic distribution. That’s the promise: write once, reach people who’ve never heard of you. The cost is control. You can’t export the subscriber list, you can’t customise the send time or segmentation, and LinkedIn owns the relationship. If the platform changes its terms or throttles distribution, your reach evaporates overnight.
The decision isn’t binary. LinkedIn newsletters work best when you’re building authority in a professional niche and discovery matters more than list portability. Your owned list—Substack, Beehiiv, Kit, MailerLite—gives you deliverability control, segmentation, and the ability to migrate or monetise without platform approval. Cross-posting makes sense when you can repurpose the same editorial without doubling your workload, but only if you’re clear about which audience you’re optimising for. LinkedIn rewards frequent, platform-native engagement; your ESP rewards deeper relationships and conversion paths you design. Most operators should run both, but lead with the owned list and treat LinkedIn as distribution, not infrastructure.
TACTIC
MailerLite’s auto-resend feature sends to non-openers automatically
MailerLite can resend a campaign to anyone who didn’t open the first time, with a different subject line, on a schedule you set. It sounds efficient—one setup, two chances at the inbox—but it only works if your list hygiene is solid and your content justifies a second attempt. Resending to a cold segment or a weak offer just burns another send and risks suppression. The feature costs nothing extra, but timing and segmentation determine whether it lifts opens or trains readers to ignore you.
READER QUESTION
Postmark’s message streams separate transactional logs from broadcast sends
If you send password resets and welcome sequences through the same ESP as your weekly newsletter, you’re mixing two reputations that shouldn’t touch. Postmark’s message streams let you isolate transactional email with its own delivery stats, suppression list, and IP reputation. That separation matters when a broadcast campaign triggers spam complaints—your login emails keep landing. Most operators don’t set this up until deliverability drops, but the configuration takes ten minutes and the cost is identical whether you use one stream or five.
WORTH READING
GA4 samples your reports when traffic crosses 500,000 sessions
Google Analytics 4 doesn’t analyse every session once your property exceeds half a million sessions in the selected date range—it samples. The dashboard doesn’t warn you; it just switches to modelled estimates. That’s fine for directional trends, but it breaks attribution analysis and cohort comparisons when you’re trying to isolate which campaign drove revenue. The fix involves either exporting raw data to BigQuery or tightening your date ranges, but most operators don’t notice sampling until the numbers stop adding up across reports.
Know someone who would like this? Forward today’s email—every operator we reach is one closer to running an online business with a little less friction.