MJML source
Editable layout source for adapting copy, block order, imagery, and CTA destinations.
Template Hedgehog
Open navigation
Deployable workflow package
Upgrade Confirmation System
Upgrade confirmation email that confirms the plan change, reinforces product value, and keeps the app close to hand.
Workflow type
Lifecycle workflow
When to use it
Use it when a product or SaaS team needs an onboarding, activation, retention, or upgrade email that is ready to adapt.
What you receive
Source, compiled HTML, rendered preview, QA notes, component structure, and handoff context.
Source to handoff
Supports customer lifecycle journeys from trigger to handoff. Template Hedgehog prepares the artefact. The sending platform handles audiences, consent, automation, unsubscribe, reporting, and delivery.
- MJML available
- Compiled HTML available
- Rendered layout proof
- QA and implementation notes
Rendered preview
Complete production package preview before upload, QA, and handoff.
What arrives after purchase
This is the full workflow package framing: editable source, compiled output, rendered proof, QA guidance, implementation notes, and a component stack your team can inspect. Template Hedgehog Pro keeps the archive local for teams that want source and handoff files together.
Compiled HTML
Production output for ESP upload, QA review, or developer handoff.
Rendered preview
Visual proof of the complete email before it moves into a sending platform.
QA notes
Practical checks for links, images, mobile stacking, footer/legal copy, and platform tokens.
Implementation guidance
How to move from editable source to compiled output and final platform handoff.
Component breakdown
The reusable production blocks that make up the workflow package.
Assembled from reusable production blocks
The layout is not a static screenshot. It is a workflow-ready stack of reusable blocks that can be inspected together or opened individually when a section needs source-level adjustment.
Creates a cleaner product-led frame.
Carries the main confirmation state.
Keeps the next product action visible after confirmation.
Closes with platform-safe legal language.
Message order
- Centred header. Keeps the email product-led rather than purely invoice-like.
- Upgrade confirmation card. Confirms the plan or product change.
- Product follow-through. Points users back into the product after the change.
- App footer. Supports platform and product legal copy.
Ready to prepare, not ready to send by itself
Template Hedgehog prepares the artefact. Mailchimp, HubSpot, Salesforce, NetSuite, Klaviyo, Customer.io, or your ESP still handle audiences, consent, automation, unsubscribe, reporting, and sending.
Layout QA checks
- Review every CTA href after tracking or ESP link wrapping.
- Review image assets and alt text before export or ESP upload.
- Check the mobile stack so the message order still makes sense on narrow screens.
- Confirm footer, legal, preference, and support copy before handoff.
- Confirm platform-specific merge fields, personalisation tokens, and fallback values.
- Check lifecycle timing, user state assumptions, and activation links before automation setup.
- Confirm audience rules and journey triggers are handled inside the sending platform.
Platform boundary
- Template Hedgehog prepares
- MJML source, compiled HTML, preview, QA guidance, component structure, and handoff context.
- Audiences, segmentation, consent, automation, unsubscribe, personalisation merge fields, scheduling, sending, and reporting.
Copy source after the workflow is understood
MJML and HTML remain available for implementation, but the package value is the complete production workflow: preview, structure, QA, handoff, and source together.
Editable source
Layout MJML
Editable workflow source for adjusting message order, copy, imagery, and destination URLs.
Formatting code preview...Compiled output
Compiled HTML
Final output for ESP upload, QA review, and handoff workflows.
Formatting code preview...Workflow package
Move from source to handoff with the complete system attached.
Layout pages show the deployable artefact, the underlying blocks, and the handoff boundary before your team moves into an ESP.