Newsletter Email for SaaS Teams

Most SaaS newsletters read like a press release, and engineers stop reading within two lines. Engineers skim for the version number and the metric. Hand them both in the first two lines and they finish the email.

The trigger is your release train. Ship a flagged feature on Tuesday, then send the digest that Thursday. Monthly beats weekly when your releases are small, because a weekly cadence burns out the list with thin issues. Aim for 9:00 to 10:30 in the morning, recipient local, midweek. Monday is inbox triage. Friday is PTO.

The offer is information, not a discount. One lead release takes the hero block and carries one concrete number. The rest are three to five changelog links, terse and semver-aware, that point at the real changelog and the real docs. Engineers trust email that does not hide the source.

The copy stays engineering-credible. Name the feature, name the improvement, link to docs, and never write "excited to announce." Open with "Shipped:" or "Now in GA:" instead. In the demo, the lead reads: Incident Roles and auto-paged responders. Median ack time dropped from 4m12s to 2m31s. MTTR fell 38 percent.

The CTA is singular. "Read the changelog" outperforms "Learn more" because it promises specifics. The changelog entries below it are text links rather than buttons, because engineers click the version they actually care about.

The subject line is "Relaybeam v3.4: Incident Roles + 6 changes." It is versioned and scannable. The preheader is "Ack times down 41 percent. Here is what shipped this sprint."

Email HTML is not web HTML. Outlook 2007 through 2019 renders with the Microsoft Word engine. Gmail clips messages over roughly 102kb and strips linked CSS in some clients. Apple Mail inverts colors in dark mode. This template handles all three.

The layout uses nested tables, not divs or flexbox. The outer container is a 600px table, and the columns are nested table cells. This is the only layout model the Outlook Word engine draws correctly.

Every element carries inline CSS. Klaviyo inlines styles on send, but paste-your-own HTML in Mailchimp does not. Inline from the start so the email renders the same in both paths.

The hero button is bulletproof VML. Outlook draws a real rounded rectangle with VML and mso styles, so the button keeps its pixel dimensions in Outlook 365 on Windows instead of flattening into an image.

Headlines and body copy are live text, not images. Retina screens and dark mode break image-only headlines. The logo is the only image in the build.

A color-scheme meta tag in the head tells Apple Mail and Outlook.com how to recolor for dark mode. The dark hero strip and footer keep contrast when a client inverts the palette.

One mobile media query does the responsive work. A single max-width 600px block overrides font sizes and side padding. Inline styles are the default, and the media query only narrows them on phones.

Web fonts fall back gracefully. The stack loads Inter where the client supports web fonts and falls back to the native system stack everywhere else. Gmail ignores web fonts, so the fallback stack carries the design.

Copy the HTML from Mailwright, or export the MJML and compile it.

In Klaviyo, open a campaign in the drag-and-drop editor. Drag a Text block into the email, click the source icon, and paste the HTML. For a full custom layout, build the campaign as an HTML email and paste the whole document. Save the block as a Master Template so your next release reuses it.

In Mailchimp, start a campaign, choose Code Your Own, then Paste in code. Drop in the full HTML document. Mailchimp preserves your inline styles on send.

Two hex values drive the palette. #4f46e5 sets the accent and the button. #0f172a sets the dark header and footer. Find-replace the word Relaybeam with your company name and update every href. Update the issue number and the version in the top strip while you are in there.

Wire your merge tags next. In Klaviyo, greet the admin by name with {{ first_name|default:'there' }} and reference their workspace with a custom property such as {{ person|lookup:'workspace_name' }}. In Mailchimp, use *|FNAME|* and a custom field such as *|WORKSPACE|*. For a SaaS list, segment by plan, for example *|PLAN|* equals Team versus Enterprise, so the digest hits active workspaces instead of expired trials.

Test the send before it goes out. Run the email through Email on Acid or Litmus. Send live tests to Gmail web, Apple Mail in light and dark, and Outlook 365 on Windows. Confirm the VML button draws as a button, confirm the logo does not invert to an invisible color in dark mode, and confirm every changelog link resolves.