Campaign launch

Launch a campaign send from a stable layout that keeps offer hierarchy and CTA placement consistent.

Open linked layout View Pro

Workflow assembly

Trigger to production output

Trigger

Real send event

Workflow

Message journey

Layout

Complete structure

Components

Reusable blocks

Email

Production output

Workflow structure

Sent for product launches, seasonal pushes, or planned campaign announcements.

Goal

Ship campaign messaging quickly without rebuilding launch structure from scratch.

Layout

Product Launch Campaign

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.

campaign.headline

Example: Spring release is live

Primary message shown in the hero block.

campaign.primary_cta_url

Example: https://app.example.com/launch

Main conversion destination for the send.

campaign.supporting_cards

Example: Feature highlights array with title, copy, and link

Secondary highlights rendered below the hero.

Variant routes

Pre-launch teaser: Shorter copy variant used before release day.
Post-launch recap: Follow-up version with adoption proof and usage links.

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

Product Launch Campaign

Launch-focused email stack composed from a brand header, campaign hero, feature grid, and compliance footer.

Component stack

Header, Hero Overlay Modern, Dual Image, Footer

Source file

product-launch.mjml

Open layout

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

Hero copy can overflow if campaign headlines are not length-capped before send.
Multiple secondary cards need consistent image ratios to avoid uneven stacking on mobile.

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.

View Pro