Goal
Increase paid conversion before trial access lapses.
Template Hedgehog
Open navigation
Trial ending reminder
Prompt trial users to convert with clear usage context and a direct upgrade path.
Workflow assembly
Trigger to production output
01
Trigger
Real send event
02
Workflow
Message journey
03
Layout
Complete structure
04
Components
Reusable blocks
05
Production output
Workflow structure
Sent as a timed reminder before trial expiry.
Layout
Trial Ending Reminder System
Pro archive
This workflow is part of the Pro archive. Use it when this send is recurring enough that source ownership, QA notes, variants, and handoff context matter more than a one-off template.
Workflow pages expose the production shape before purchase: trigger, goal, required fields, variants, QA risks, handoff steps, and linked layout. The paid archive adds the editable source and compiled output for the workflows included in your tier.
What the production package needs.
A workflow is useful when the implementation contract is visible before anyone starts editing markup.
trial.days_remaining
Countdown value used in urgency messaging.
account.plan_name
Current plan reference in copy.
billing.upgrade_url
Conversion destination.
Variant routes
- Final day reminder: Short urgency-focused variant for day-of-expiry.
- Trial extended: Alternative when support grants additional trial time.
Package access
- Public workflow page: intent, trigger, required fields, variants, QA risks, handoff steps, and linked layout.
- Full MJML source for this workflow
- Compiled HTML output ready for ESP upload
- Variant-ready workflow pack files
- Versioned workflow updates inside Template Hedgehog Pro
Linked production layout
Trial Ending Reminder System
Trial-ending lifecycle email using an alert block, usage summary, benefits reinforcement, and support-aware close.
Component stack
Header, Trial Expiry Alert, Usage Summary Strip, Direct Benefits List Dark, Footer Onboarding Legal
Source file
trial-ending-reminder.mjml
QA and handoff.
The value is not only the rendered email. It is knowing what has to be checked before the ESP takes over.
QA risks to review
- Countdown values can desynchronise if scheduled send timing is offset.
- Upgrade CTA hierarchy must stay clear when discount messaging is introduced.
Handoff steps
- Edit copy and block order in MJML, keeping utility and footer sections unchanged unless requirements demand it.
- Compile MJML to HTML and run client checks in Gmail, Outlook Desktop, and Apple Mail before handoff.
- Import compiled HTML into the ESP, map merge variables, and send an internal seed round for QA sign-off.
Template Hedgehog prepares the source, compiled output, preview, QA notes, and handoff context. Mailchimp, HubSpot, Salesforce, NetSuite, Klaviyo, Customer.io, or your ESP still handle audiences, consent, unsubscribe, automation, sending, delivery, and reporting.
Use this workflow inside Pro.
Pro is the archive for teams that keep rebuilding production emails and need repeatable workflows, editable MJML, compiled HTML, QA notes, implementation guidance, and updates.