Announcement Email Template — Public Beta Launch
A product-launch announcement email introducing a feature moving from waitlist to public beta. Designed for SaaS product teams.
Preview unavailable — view the prompt below.
The prompt
Two ways to build this email in plain language. The fastest is Temway's in-editor assistant — open the chat drawer in the email editor and paste the recipe below. Or connect Claude or ChatGPT via Temway's MCP and paste it there; the agent builds the email step by step. Either way, adapt the copy and colors to your brand.
- 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? Click Use this template below to clone
it into your workspace, then ask the in-editor assistant to rebrand it. Over MCP, tell
your agent to clone the Temway share ivDEpmi4yy0q-XzQixL2k and rebrand. For the
full model, point an MCP agent at get_concept — email-structure,
layouts-vs-emails, design-recipes.
A product-launch announcement that celebrates the waitlist ending. A dark gradient hero with a teal halo and an orange star badge carries the “Public beta is open” headline and a CTA, then the native body explains what’s new in three divided sections, who can access it, and a closing “expect rough edges” note that earns trust before the second CTA.
Snapshot
- Goal: move waitlist signups into the beta by showing what shipped and who can turn it on.
- Audience & tone: SaaS users on or near a beta waitlist. Excited, concrete, honest about rough edges.
- Palette: page
#e4e2de· container#f6f3ee· text#161a2c/#676972(muted) · accent#f0973d - Font:
Trebuchet MS, Helvetica, sans-serif - Artwork: none — fully native blocks.
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.
- [native] Logo — logo. Brand mark, left-aligned.
- [native] Kicker — text. “Public beta is open”, fontSize: 14, color
#905b25, left, uppercase. - [native] Headline — text. “What’s new in AI Workflows”, fontSize: 28, color
#161a2c, left. - [native] Body copy 1 — text. “It is the most-requested feature from our waitlist, and it is now open for everyone to try.”, fontSize: 16, color
#161a2c, left. - [native] Story title 1 — text. “Visual pipeline builder”, fontSize: 20, color
#161a2c, left. - [native] Body copy 2 — text. “Drag steps into place and watch each one run in real time — no code required to wire a workflow together.”, fontSize: 16, color
#161a2c, left. - [native] Story title 2 — text. “Shareable templates”, fontSize: 20, color
#161a2c, left. - [native] Body copy 3 — text. “Publish a workflow once, and your whole team can clone and customize it from the shared library.”, fontSize: 16, color
#161a2c, left. - [native] Story title 3 — text. “Usage-based cost preview”, fontSize: 20, color
#161a2c, left. - [native] Body copy 4 — text. “See the estimated run cost before you hit save — no surprise bills at the end of the month.”, fontSize: 16, color
#161a2c, left. - [native] Body copy 5 — text. “Every paid workspace can turn it on today from Settings. This is a beta, so expect a few rough edges.”, fontSize: 16, color
#676972, left. - [native] Primary CTA — button. Label “Join the public beta”, fill
#f0973d, color#161a2c, shapeStyle: ‘0_1’, left. - [native] Footer rule — divider. short (96px) rule, 1px, color
#e9e9e9. - [native] Footer social — social. Icon row, social.color
#905b25, style circle-outline, center. - [native] Footer address — address. Postal address + unsubscribe, address.color
#676972, address.fontFamilyTrebuchet MS, Helvetica, sans-serif, center.
Make it yours
- Swap the feature titles and bodies for what your beta actually ships — keep three sections so the rhythm holds.
- Recolor the orange star badge and CTA to your brand — keep the halo low-opacity so the headline reads first.
- Keep the “expect rough edges” line; it sets expectations and cuts support tickets on day one.
About announcements email templates
An announcement earns its own send when it's time-sensitive or significant enough to need full attention on its own subject line — a launch, a leadership change, a funding round, or a policy update, rather than one more line in the next newsletter issue.
See all announcements templates →What kind of news deserves a standalone announcement email instead of a newsletter mention?
Anything time-sensitive or significant enough to need its own subject line and full attention — a launch, a leadership change, a funding round, or a policy update that changes how customers use your product.
How long should a product-update announcement be?
Long enough to explain what shipped and why it matters, short enough to read in under a minute — the templates below separate a short "what's new" summary from optional deeper detail below it.
How do I announce a leadership change without it feeling like a press release?
The new-CEO and leadership templates below lead with a short, human bio and a direct quote rather than a formal title-and-tenure rundown.
Should an announcement email include a call to action?
Not always — a policy update or leadership announcement can stand on its own, while a product-launch announcement should point to one clear next step, like trying the feature or booking a demo.