Production layout system
Trial Ending Reminder System
Trial-ending lifecycle email using an alert block, usage summary, benefits reinforcement, and support-aware close.
5 production blocksPart of the SaaS lifecycle systemSource, output, and handoff contextBuilt from the public production email system
Rendered email preview
System sequence
Message structure in order
- Header. Introduces the lifecycle reminder cleanly.
- Expiry alert. Explains what is changing and when.
- Usage summary. Reminds the user what they have been doing in the product.
- Benefits list. Reinforces why staying on the paid plan matters.
- Onboarding footer. Keeps support and preference handling simple.
Production guidance
How this moves into delivery
- Edit the MJML recipe when you want to adjust structure, copy order, imagery, or CTA destinations.
- Use the compiled HTML when your ESP, QA handoff, or review process needs final delivery markup.
- Review the system order below before customising so the message hierarchy stays intact across clients.
Stack map
Production stack
Each layout is assembled from reusable production blocks. Inspect the system as a whole here, then open individual blocks only when you need source-level changes.
Keeps the lifecycle message recognisable.
Carries the timing and urgency message.
Adds context before the upgrade ask.
Summarises the reasons to keep access or upgrade.
Closes with support-safe lifecycle copy.