Danielle from Ramp
Healthier businesses run on Ramp
The headline and subheadline create a clear focus, with the card image and data points supporting it.
SaaS email examples
Browse complete SaaS emails and compare how software teams turn product detail into a message a busy reader can scan and act on.
The Metabase Team
AI Analytics Week - Bring your questions
Clear hierarchy with the hero image and headline drawing the eye first, followed by the list of sessions and the primary CTA.
The Ramp Team
How CFOs are leading the AI discussion
The headline and a prominent CTA create a clear focal point, with supporting details organized logically below.
Productboard
Your Productboard newsletter subscription is confirmed!
The headline is large and followed by a bulleted list, creating a clear reading order.
Modern Treasury
Welcome to The Vault
Clear hierarchy with a strong title and distinct content blocks.
Cynthia at Metabase
See how teams actually use Metabase — in person this October
The headline and the single prominent CTA create a strong visual focus, guiding the eye effectively.
SaaS email inspiration
SaaS emails translate product behaviour into a reason to act. Strong examples make the audience and use case clear, explain the feature without reproducing documentation, and use interface imagery only when it helps the reader understand what will happen after the click.
How does a SaaS onboarding email differ from a feature update?
Onboarding helps a new user reach an early useful outcome, so it should reflect their stage and next task. A feature update explains what changed, who benefits, and how an existing user can try or understand the new behaviour.
How should a SaaS email explain a product feature?
Start with the job the feature helps someone complete, then describe the change in concrete language. Use technical detail when the audience needs it, and link to documentation for depth instead of forcing every condition into the campaign email.
When should a SaaS email show the product interface?
Show the interface when it clarifies a workflow, reveals where to find something, or makes a change easier to recognise. Crop around the relevant area and support it with a plain explanation; an unexplained dashboard image creates more work for the reader.