The 4 email formats every operator uses — broadcast, newsletter, trigger-based nurture, transactional — mapped to the job each one wins, the deliverability rules that govern them, real ESP pricing to run them, and how to architect all four together without cannibalizing each other. The honest 2026 decision framework, not a glossary.
There are four email formats, each winning a different job. Broadcast is a one-time send for launches and time-sensitive announcements. Newsletter is a recurring content-driven send that builds and retains an audience. Trigger-based nurture is an event-driven sequence built to convert (lead to trial, trial to paid, churn-risk to retained). Transactional is system-generated utility — receipts, resets, alerts — and must stay non-promotional to protect deliverability. Most teams over-index on one format and under-build the rest; compounding programs run all four on the right cadence off one segmentation layer.
Most "email vs newsletter" articles answer the wrong question. The real question is not which format is better — it is which job you are trying to do, because the four email formats are not competitors, they are different tools for different jobs. A newsletter cannot convert a trial user the way a nurture sequence can; a nurture sequence cannot build an audience the way a newsletter can; and a launch announcement that goes out as a recurring newsletter slot lands a day late to the wrong list.
The failure mode is almost always over-reliance on one format. Creators run a weekly newsletter and never build a single conversion sequence, so subscribers accumulate and never get systematically asked to buy. B2B SaaS teams build elaborate trigger-based nurture and never ship a newsletter, so they have no audience-building flywheel and no warm surface for launches to land into. Both leave most of the program's value uncaptured.
This is the operator-grade framework: what each format is for, the deliverability and cadence rules that govern it, the ESP pricing reality of running them (verified from each vendor on 2026-06-18), and the architecture that wires all four together off a single segmentation layer. Pairs with our [email-marketing-tools-2026](/ai-email-marketing/email-marketing-tools-2026) platform comparison and [email-list-growth-ai](/ai-email-marketing/email-list-growth-ai) growth playbook.
Email is not one channel — it is four formats with four different jobs, four different cadences, and four different deliverability profiles. Most programs treat them as interchangeable and pay for it: a launch buried in a newsletter slot, a nurture sequence that reads like a content digest and converts nobody, a receipt stuffed with upsells that drags the whole sending domain into spam. The honest mapping, before any of the nuance:
| Format | Job it wins | Cadence | Typical length | Primary metric |
|---|---|---|---|---|
| Broadcast | Launches, announcements, time-sensitive offers | Ad-hoc (1-3/mo) | 100-300 words, single CTA | Click + conversion on the offer |
| Newsletter | Audience-building, retention, thought leadership | Recurring (weekly/biweekly) | 400-1,500 words, multi-section | Open + long-term retention/unsubscribe |
| Trigger nurture | Conversion — lead to trial, trial to paid, churn-risk to retained | Event-driven, 1-7 days apart, 7-60 day window | 100-250 words, single CTA each | Sequence conversion rate |
| Transactional | Utility — confirmations, receipts, resets, alerts | Real-time on user action | As short as possible | Delivery rate (must be ~100%) |
Read the table as a job-to-be-done allocation, not a ranking. You do not pick one format; a mature program runs all four, each doing the one job it is shaped for. The rest of this guide walks each format, then collapses them into a single architecture and a cadence plan that keeps them from cannibalizing each other or torching your sending reputation.
A broadcast is a one-time send to a segment, fired when there is a specific reason — a product launch, a price change, an event invite, a time-sensitive offer, a major company update. It is not scheduled and it is not recurring, which is exactly what separates it from a newsletter. The discipline that makes broadcasts work is restraint: a single, clear CTA, 100-300 words, and a reason the recipient can feel in the first line. The moment a broadcast tries to carry three asks, its click rate collapses.
The classic broadcast mistake is using it as a content channel ("here are five tips") when that content belongs in a newsletter, or as a conversion channel (a five-email drip) when that belongs in a nurture sequence. Broadcast is for the thing that is true today and not true next week. Cadence matters more than operators expect: 1-3 broadcasts a month reads as a brand with news; above 4-5 a month, the same list starts reading every send as promotional and engagement decays across all four formats, because the inbox provider scores your whole domain, not your individual sends.
A newsletter is a recurring, scheduled, content-driven send. Its job is not to convert this week — it is to build and retain an audience that will still be opening in a year, which is the asset every other format draws against. That is why the metric on a newsletter is open rate and long-term unsubscribe rate, not immediate conversion. A newsletter that converts hard every week stops being a newsletter and becomes a promotional broadcast on a schedule, and subscribers learn to ignore it. The 80/20 rule holds: roughly 80% genuine content, 20% offer.
Cadence is the single most consequential newsletter decision. Weekly is the dominant 2026 cadence and the one most audiences attach to; biweekly works in slower niches; monthly sits at the edge where audience attachment fades, because subscribers forget who you are between sends. The platform you run it on follows from your business model, not the other way around — and the cost curve is steep enough to matter. Newsletter-first creators run Beehiiv (free to 2,500 subscribers, then Scale at $49/mo for 1,000 paid-tier features, climbing to roughly $109/mo at 10,000 and $169/mo at 25,000) or Kit (Newsletter free to 10,000 subscribers; Creator at $39/mo for 1,000, $59/mo at 3,000, $89/mo at 5,000). The full platform-by-platform breakdown lives in [email-marketing-tools-2026](/ai-email-marketing/email-marketing-tools-2026); the point here is that newsletter is the format whose cost compounds with list size, so the platform choice is a multi-year commitment, not a this-quarter one.
A nurture sequence is event-driven, not scheduled. It fires when a subscriber does something — signs up, starts a trial, hits a usage milestone, abandons a cart, lapses into churn risk — and runs a short, tight sequence aimed at one conversion. Cadence inside a nurture is far tighter than a newsletter (every 1-7 days), and the whole sequence has a window (7-60 days) after which the subscriber either converted or rolls back into the regular newsletter. Each email is short (100-250 words) with a single CTA, because a nurture email that offers three next steps converts on none of them.
The defining nurture mistake is writing nurture like a newsletter — shipping content with no conversion ask, which wastes the trigger entirely. The trigger is the most valuable signal email gives you: the subscriber just told you exactly where they are in the lifecycle. A nurture that responds with a generic "thanks for subscribing, here is some content" throws that signal away. The flip side is that nurture is where segmentation pays back hardest, because the trigger already tells you the lifecycle stage; layering persona and behavior on top is what separates a 12% sequence conversion from a 30% one. The mechanics of that layering are in our [email-marketing-tools-2026](/ai-email-marketing/email-marketing-tools-2026) automation-depth comparison — ActiveCampaign, Klaviyo, and HubSpot lead on exactly this, while newsletter-first tools trail.
Cold outbound is a special case of trigger-based sending with inverted rules — the recipient has no relationship with you, so warm-list tactics actively hurt. It runs on a different tool stack entirely (Smartlead Base $39/mo, Pro $94/mo, Unlimited Smart $174/mo; Instantly Growth $47/mo, Hypergrowth $97/mo) and a different deliverability discipline. If your "nurture" is actually cold acquisition, treat it as its own program — the full playbook is in [cold-email-2026](/ai-email-marketing/cold-email-2026).
Transactional emails are system-generated and tied to an account action: order confirmations, receipts, password resets, security alerts, shipping updates. The job is pure utility — get the user the operational information they need, as fast and as short as possible. Transactional emails have the highest engagement of any format (people open their receipts and reset links at near-100% rates) precisely because they contain nothing but the thing the user asked for.
That high engagement is exactly why the temptation to bolt marketing onto transactional is so destructive. A "your order shipped" email with three product recommendations underneath mixes your transactional sending reputation with your marketing reputation, and inbox providers increasingly score the blend as marketing — which drags deliverability on the emails users genuinely need. Worse, in many jurisdictions it converts a transactional email into a commercial one with the consent and unsubscribe obligations that follow. Keep transactional purely functional; if you have something to sell, that is a broadcast or a nurture email, sent separately. Many serious operators send transactional from a separate subdomain entirely to wall off the reputation.
When operators ask "should this be a newsletter or a broadcast," the honest answer is a function of three things: is the content recurring, is there a conversion ask, and is it triggered by a user action. The matrix below resolves the four formats off those axes.
| Your situation | Format | Why | Common wrong pick |
|---|---|---|---|
| Recurring content with no hard conversion ask | Newsletter | Builds the audience asset every other format draws on | Broadcast (burns the news framing on routine content) |
| One-time, time-sensitive, single ask | Broadcast | Lands now, to a segment, with one clear CTA | Newsletter (arrives a week late on the wrong cadence) |
| Triggered by a user action, aimed at a conversion | Trigger nurture | Uses the lifecycle signal the trigger just gave you | Newsletter (wastes the trigger, no conversion ask) |
| System event the user needs to know about | Transactional | Utility, ~100% delivery, walled-off reputation | Marketing email dressed as transactional (deliverability damage) |
| Reaching people with no prior relationship | Cold outbound (nurture variant) | Inverted rules + separate sending stack | Treating it as a warm broadcast (spam complaints) |
The four formats are not a menu you pick from — they are a system. Run correctly, each one feeds the others: the newsletter builds the audience, intent signals from that audience drop people into nurture, broadcasts land into a warm list the newsletter has kept engaged, and transactional quietly does its job without dragging anyone's reputation down. The architecture, in order of dependency:
The connective tissue under all four is a single segmentation layer. The same lifecycle, persona, and behavior tags that route a subscriber into the right nurture sequence also decide which segment a broadcast goes to and which newsletter variant a subscriber sees. Building four separate segmentation schemes per format is how programs become unmaintainable. The content side is the same story: a single brand voice has to hold across a launch broadcast, a weekly newsletter, and a 9-email nurture, or the program reads as four different companies. That voice-consistency problem across formats is exactly what [content-repurposing](/repurpose) and a defined brand voice solve — one source of truth feeds every format instead of each being authored from scratch.
AI does not change the architecture — it changes the production cost of three of the four formats. Newsletter, broadcast, and nurture are all content problems: someone has to write them in a consistent voice, on cadence, without sounding like generic AI slop. Transactional is the exception; it is a templated utility and AI adds nothing there. The leverage is in collapsing the authoring cost of the content-bearing three so a small team can actually run the full architecture instead of defaulting to whichever one format they have time for.
This is where Kompozy sits — upstream of the ESP, not competing with it. Inside Kompozy's Newsletter bucket, the engine produces the full email payload (subject-line variants, preview text, body copy in your brand voice, inline images, CTA blocks) from your input sources, then ships it to whichever platform you send on. The same Persona Brief that voices the newsletter also voices the broadcast and the nurture copy, which is what keeps all four formats sounding like one company. Kompozy Creator ($49/mo, 2,500 credits) covers a solo or small operation running the full architecture; Pro ($299/mo, 18,000 credits) is the pick once monthly output crosses roughly 120 pieces across formats and platforms; the Founding tier is $39/mo bring-your-own-key. See [pricing](/pricing) for current tiers. The division of labor is clean: Kompozy answers "what do I send and how do I keep it on-voice across four formats," and your ESP answers "deliver it and track engagement."
Running all four formats without a cadence plan produces over-mailing, which is the fastest way to torch a sending reputation — the inbox provider scores total volume and complaint rate across your whole domain, so a heavy week of broadcasts can suppress your newsletter open rate for a month. The honest cadence ceilings per format:
Get the cadence plan right and the four formats compound: the newsletter keeps the list warm, nurtures convert the warm list, broadcasts land because the list is warm, and transactional stays clean. Get it wrong and they cannibalize — over-mailing on one format suppresses deliverability on all four at once.
A broadcast is a one-time send to a segment, fired ad-hoc when there is a specific reason (launch, event, time-sensitive offer) with a single CTA. A newsletter is a recurring scheduled send (weekly/biweekly) that is content-driven and built for audience retention, not immediate conversion. The tell: if you would send it again next week on a schedule, it is a newsletter; if it is true today and not next week, it is a broadcast.
Both, for different jobs. Trigger-based nurture out-converts newsletters on every conversion metric for B2B SaaS, so nurture is non-optional. But a newsletter is the audience-building flywheel and the warm surface that launches land into — skip it and you have no top-of-funnel asset. The common SaaS failure is building deep nurture and never shipping a newsletter; the common creator failure is the reverse.
No. Mixing marketing into transactional emails blends your transactional and marketing sending reputations, and inbox providers increasingly score the blend as marketing — which hurts deliverability on the operational emails users actually need. In many jurisdictions it also converts a transactional email into a commercial one with consent and unsubscribe obligations. Keep transactional purely functional, ideally on a separate subdomain, and send any offer as a separate broadcast or nurture email.
Weekly is the dominant cadence and the one most audiences attach to. Biweekly works in slower niches. Monthly sits at the edge where attachment fades because subscribers forget you between sends. Daily is unsustainable for most operators and accelerates unsubscribes. Whatever you pick, consistency beats frequency — a reliable monthly newsletter outperforms an irregular "weekly-ish" one.
A new subscriber who just signaled intent (started a trial, downloaded a lead magnet, booked a demo) belongs in a trigger-based nurture aimed at the next conversion step. A new subscriber who simply joined the list with no specific intent belongs in the newsletter flow, optionally after a short welcome sequence. The trigger is the deciding factor: if a user action fired the signup, nurture; if not, newsletter.
All four, but built in order of leverage. Start with transactional (it is non-negotiable utility) and one newsletter to anchor the audience. Add a welcome nurture and a single conversion nurture next, because that is where revenue is. Layer broadcasts last for launches and announcements. The mistake is trying to run elaborate versions of all four at once; the bigger mistake is running only one for years.
Yes — directly. Inbox providers score total volume and complaint rate across your entire sending domain, not per-format. A heavy broadcast week can suppress your newsletter open rate for weeks afterward, and uncapped marketing volume can even drag transactional deliverability if they share a domain. Watch total touches per subscriber per week, use cross-format suppression, and wall transactional off on its own subdomain.
AI collapses the authoring cost of the three content-bearing formats (newsletter, broadcast, nurture); it adds nothing to transactional, which is templated utility. The leverage is letting a small team actually run the full architecture instead of defaulting to one format. A tool like Kompozy generates the newsletter, broadcast, and nurture copy from one Persona Brief so the voice holds across all three, then ships to your existing ESP for delivery and tracking.