Product Update Notes — SaaS

A light, scannable changelog email with four color-coded update cards (New / Improved tags), a bug-fix summary, and a link to the full changelog.

Announcements saasminimalannouncementchangelogfeature-gridcta

The prompt

Paste the brief below into ChatGPT or Claude with Temway's MCP enabled — the agent builds the email step by step. Or adapt it for your own brand and copy.

  • An email is a top-to-bottom stack of blocks — the recipe follows that order.
  • A [layout] step becomes a single image (great for heroes); everything else stays live text and links.
  • Theme the footer to match — the recipe's last step does exactly that.

Want this exact email? Tell your agent to clone the Temway share dt0wh8qYs5yheTX0ppOt5, then rebrand it. For the full model, point it at get_conceptemail-structure, layouts-vs-emails, design-recipes.

A monthly product-update email for a SaaS product. A clean, all-native changelog: a heading, a run of color-tagged “New” and “Improved” entries separated by dividers, a bug-fix line, and a link to the full changelog. Informative and matter-of-fact — no marketing fluff.

Snapshot

  • Goal: tell existing customers what shipped this month, scannably.
  • Audience & tone: current users. Informative, plain, confident — one line per change.
  • Palette: page #f8fafc · container #ffffff · text #1e293b / #64748b (muted) · accent blue #2563eb · “Improved” green #16a34a
  • Font: "Trebuchet MS", Helvetica, sans-serif
  • Artwork: none — fully native blocks (a changelog reads best clean; skip the decorative hero).

Build recipe

Each step is one block in the flat stack, top to bottom. [native] = a real email block. [layout] = a free-form layout embedded as a single image.

  1. [native] Logo — “CIRRUS”, centered, blue #2563eb, letter-spaced.
  2. [native] Heading — text. “What’s new this month”. fontSize: 22, fontWeight: 700, color #1e293b, center.
  3. [native] Subheading — text. “6 improvements shipped in October”. fontSize: 15, color #64748b, center, tight top padding.
  4. [native] Entry 1 title — text. “NEW · Smart Insights Dashboard” — prefix “NEW” in blue #2563eb bold. fontSize: 16, fontWeight: 700, color #1e293b, left. (The colored tag replaces a “card” — the flat model stacks and tags, it does not box.)
  5. [native] Entry 1 detail — text. One-line description. fontSize: 14, color #64748b, left, tight top padding.
  6. [native] Divider — hairline #e2e8f0, generous vertical padding.
  7. [native] Entry 2 title — text. “IMPROVED · Dashboard loads 3× faster” — prefix “IMPROVED” in green #16a34a. Same type as step 4.
  8. [native] Entry 2 detail — text. As step 5.
  9. [native] Divider — as step 6.
  10. [native] Entry 3 title — text. “NEW · Team Workspaces” (blue tag). As step 4.
  11. [native] Entry 3 detail — text. As step 5.
  12. [native] Divider — as step 6.
  13. [native] Entry 4 title — text. “IMPROVED · Export to CSV & PDF” (green tag). As step 4.
  14. [native] Entry 4 detail — text. As step 5.
  15. [native] Bug-fix line — text. Italic “Plus 30+ bug fixes and stability improvements.” fontSize: 13, color #64748b, center.
  16. [native] CTA — button. Label “See full changelog”, blue #2563eb fill, white text, rounded, center.
  17. [native] Footer — social + address. Recolor: social.color = #2563eb, address.color = #94a3b8, address.fontFamily = "Trebuchet MS", Helvetica, sans-serif.

Make it yours

  1. Swap the four entries for your actual changes — keep the “NEW” / “IMPROVED” tag prefix.
  2. Adjust how many entries you list; each is a title + detail + divider triple.
  3. Recolor the blue/green tags to your brand.
Use this template