Production email systems with handoff built in.

Template Hedgehog gives lifecycle, transactional, and campaign emails as editable MJML, compiled HTML, previews, QA notes, and platform handoff guidance, so your ESP receives a reviewed package instead of a fragile one-off build.

Inspect workflows Compare editions

Core from £59Pro full archive £179MJML plus compiled HTMLQA and handoff notes

Production workflow

Source, review, compile, QA, and handoff in one view

MJML source

editable

<mjml>
  <mj-body css-class="launch">
    <mj-section>
      <mj-column>
        <mj-text mj-class="eyebrow">
          Release bulletin
        </mj-text>
        <mj-text mj-class="h1">
          Launch email updates
        </mj-text>
        <mj-button href="{{cta_url}}">
          Review workflow
        </mj-button>
      </mj-column>
    </mj-section>
  </mj-body>
</mjml>

Rendered preview

ready

Product Launch Campaign rendered email preview

Mobile stack

Fallback copy

Footer route

Handoff

source.mjmlcompiled.htmlqa-notes.md

How modern email production works.

The work is not choosing a pretty block. The work is keeping source, intent, output, QA, and handoff connected from the first draft to the final send.

Author

Start with editable MJML blocks and workflow intent, not a blank email file.

Review

Keep trigger, audience, layout, variants, and risks attached to the send.

Compile

Turn source into production-safe HTML that can move into the delivery tool.

QA

Check structure, mobile behaviour, client risk, fallbacks, and handoff notes.

Ship

Hand over source, compiled output, preview, guidance, and update context.

Where Template Hedgehog fits.

Template Hedgehog is not Mailchimp, HubSpot, Salesforce, NetSuite, Klaviyo, Customer.io, or an ESP. It is the production layer before those tools: build, review, compile, QA, then hand off.

Production stack

Template Hedgehogproduction layer

Source, preview, compiled HTML, QA notes, and handoff package.

Your email platformdelivery layer

MailchimpHubSpotSalesforceNetSuiteKlaviyo

Audiences, consent, unsubscribe, automation, sending, delivery, and reporting stay here.

Template Hedgehog

Production before upload.

Build
Review
Compile
QA
Handoff

Email platforms

Delivery after upload.

Audiences
Automation
Sending
Reporting

Compatibility

Manual handoff, not replacement.

Compatibility means Template Hedgehog prepares production artefacts for the platform you already use. It does not run accounts, lists, automations, sends, or reports.

Mailchimp

Prepare reviewed HTML before import. Lists, segments, automations, sends, and reporting stay in Mailchimp.

HubSpot

Use the compiled artefact for handoff into HubSpot email production. CRM data, workflows, and reporting stay in HubSpot.

Salesforce

Hand over source, compiled HTML, and QA notes for Salesforce email tooling. Setup, audiences, journeys, and reporting stay there.

NetSuite

Prepare valid HTML for NetSuite marketing campaign use. Uploading, campaign setup, lists, and sending remain customer-owned.

Klaviyo

Prepare production HTML and handoff notes before Klaviyo import. Segments, flows, delivery, and reporting stay in Klaviyo.

Customer.io

Prepare source and HTML for handoff. Journeys, profile data, delivery, and reporting stay inside Customer.io.

Workflow proof before file inventory.

A useful email system shows how a send moves through production. Components matter, but only after the workflow proves where they fit.

New user created

Onboarding

Welcome, activation, and first-action send

Recovery requested

Password reset

Secure transactional email with support-safe close

Campaign ready

Product launch

Announcement email with hero, feature pair, and compliance footer

Recurring editorial send

Weekly digest

Repeatable digest structure for updates and links

Then the archive becomes valuable.

The archive is not sold as a gallery. It is the production material behind the workflow: source, compiled output, previews, QA, guidance, and examples that let teams repeat the process.

See what's included

MJML source

Editable production source files

Compiled HTML

Delivery-ready output

Rendered previews

Visual inspection before handoff

QA notes

Client risks and checks

Guidance

Implementation and setup notes

Workflow examples

Real sends to adapt from

What you actually receive.

Each edition is a handoff-ready email system: source, compiled output, preview, QA context, guidance, and workflow examples.

What is in the pack

The purchase is a production handoff, not a list of abstract features.

Preview

Open full-size preview

MJML source

source.mjml

Editable source files for each layout and workflow.

Compiled HTML

compiled.html

Production output ready for ESP upload or developer handoff.

Preview

preview.png

Rendered email previews so the structure can be inspected quickly.

QA notes

qa-notes.md

Client risks, responsive checks, and send-time caveats.

Implementation guidance

implementation-guide.md

Notes for variables, image hosting, compilation, and handoff.

Workflow examples

workflow-examples.md

Trigger, fields, variants, layout, and component stack context.

Workflow examples

Real send systems, not blank templates.

View workflows

Onboarding activation

Move new users from account creation to first product action without rewriting the same welcome flow.

Trigger

Sent after a user creates an account but before activation milestones are complete.

MJML sourceCompiled HTML5 blocks3 fields

Password reset

Handle account recovery with security-safe copy and a direct reset action that works across clients.

Trigger

Sent immediately after a user requests a password reset.

MJML sourceCompiled HTML4 blocks3 fields

Campaign launch

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

Trigger

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

MJML sourceCompiled HTML4 blocks3 fields

Weekly reporting digest

Share recurring product or campaign performance updates using a stable digest structure.

Trigger

Sent on a schedule to report weekly performance or operational metrics.

MJML sourceCompiled HTML4 blocks3 fields

Proof you can inspect before buying.

Open the previews, inspect workflow QA notes, download a sample archive, and check how the paid zip is organised before committing.

Full preview inspection

Open rendered layout previews before buying so you can inspect hierarchy, spacing, mobile stacking assumptions, and production fit.

Inspect layouts

QA and testing proof

Workflow notes call out responsive risks, Outlook caveats, long-content issues, image handling, and handoff checks before ESP import.

Read QA notes

Public sample pack

Download a complete workflow sample with real MJML source, compiled HTML, QA notes, testing notes, implementation guide, and licence reference.

Inspect sample

Built from email production work

Created by Artifexa from hands-on MJML and HTML email production experience, including campaign-template work for NetSuite campaign use.

Founder proof

Archive structure

The zip opens into a working handoff.

The paid archive is organised by source, output, workflows, docs, and version context so a buyer can inspect and implement without guessing where files live.

Inspect sample pack

components/

Reusable MJML blocks with compiled HTML output.

layouts/

Complete email systems assembled from production blocks.

workflows/

Trigger, fields, QA risks, variants, and handoff notes.

examples/

Reference sends showing how systems work in context.

docs/

Setup, editing, compilation, and implementation guidance.

README.md + changelog

Version, licence, update, and delivery notes.

Built by someone who has had to hand these files over.

Template Hedgehog comes from practical HTML email work: MJML source, compiled output, QA checks, and platform handoff pressure.

Founder proof

Why I built Template Hedgehog.

I built Template Hedgehog after years of working with HTML email, MJML source, compiled output, and campaign-template handoff. The same production patterns kept coming back: onboarding, resets, receipts, launches, digests, support routes, and operational alerts.

The useful work was rarely the empty template. It was source ownership, QA notes, preview checks, platform boundaries, and handoff context that made the email safe to change and ship.

Years of HTML email production

The archive comes from repeated hands-on HTML email work where the same lifecycle, transactional, campaign, and digest structures kept being rebuilt.

MJML source ownership

MJML is useful while building because teams can change source deliberately. Compiled HTML is useful at handoff because platforms and reviewers often need final markup.

NetSuite email work

The product is informed by campaign-template and email handoff work around NetSuite use cases, where source ownership and platform boundaries matter.

QA and handoff frustrations

Email work often fails at the edges: mobile stacking, Outlook caveats, long copy, missing image rules, unclear merge fields, and unclear ownership after export.

Reusable production systems

Template Hedgehog packages the source, output, preview, notes, and workflow context that usually have to be recreated project by project.

What happens after purchase.

The paid archive is delivered as a tier-matched zip with source, output, previews, workflow context, documentation, version metadata, and licence guidance.

After purchase

What arrives and how it is delivered.

Checkout confirms the tier

Stripe checkout records the selected Core, Pro, or Team archive and redirects back to the success page.

Signed download is issued

A signed download link is issued for the matching private archive, not a public source folder.

Archive opens into real artefacts

You receive source files, compiled HTML, previews, workflow notes, docs, version metadata, and licence guidance.

Implementation starts from handoff notes

Use the included guidance to edit copy, map variables, host images, compile output, and run client checks before upload.

Email-client QA

Testing proof is documented, not implied.

MJML source and compiled HTML are kept together for every sampled workflow.
Responsive inspection points: 320px, 375px, and 600px.
Seed-test guidance covers Gmail, Outlook Desktop, and Apple Mail where available.
QA notes call out long names, long URLs, blocked images, dark mode, and ESP HTML rewriting.
Final platform testing remains required after upload because ESP editors can alter HTML.

Choose the edition by operating need.

Core is the essential archive starter for the first production journeys. Pro is the main buying path: the full source-to-handoff archive, 82 components, 18 layouts, 13 workflows, and Studio waitlist priority while Studio is in development. Team is Pro plus commercial reuse, rollout support, and longer updates.

Core covers the first production journeys.

Core

£59

3 complete starter workflows for welcome, password reset, and order confirmation email, with 11 components, 3 layouts, editable MJML, compiled HTML, previews, and setup docs.

Compare editions

Pro standardises production.

Pro

£179

The complete source-to-handoff archive for recurring email production: 82 components, 18 layouts, 13 workflows, source, compiled HTML, previews, QA notes, handoff guidance, 6 months of updates, and Studio waitlist priority while Studio is in development.

Compare editions

Team adds rights, rollout, and support.

Team

£349+

Pro plus commercial reuse rights, white-label or internal deployment, reusable generation framework, priority support, 12 months of updates, and Studio waitlist priority while Studio is in development.

Compare editions

Template Hedgehog Studio is the future workspace direction for everything before send: choose workflows, edit content, compile, preview, QA, prepare handoff, and export ZIPs. It is not live product UI. The paid archive is complete without Studio and remains yours either way; your sending platform still handles audiences, consent, unsubscribe, automation, delivery, and reporting.

Join Studio waitlist

Licence, updates, and support.

The hesitation point is usually not the files. It is whether the licence fits, how updates are accessed, and what happens if delivery fails.

Licence and commercial use

Choose by what the archive is allowed to support.

The files change between Core and Pro. The permission model changes at Team. Use this to separate package depth from commercial reuse rights.

Starter use

Core

Your own small self-serve implementation

Archive: 11 components, 3 layouts, 3 workflows, MJML source, compiled HTML, previews, and setup docs
Commercial rights: Use inside your own implementation. Redistribution, resale, and white-label reuse are not included.
Updates: Standard fixes for the purchased archive version

Full archive

Pro

Recurring production email work for your organisation

Archive: 82 components, 18 layouts, 13 workflows, token examples, QA notes, advanced guidance, and compiled output
Commercial rights: Use the full archive for your own organisation's production email work. Client resale, redistribution, and white-label reuse are not included.
Updates: 6 months of versioned updates

Rights and support

Team

Client work, white-label use, or internal rollout across teams

Archive: Full Pro archive plus commercial reuse rights, white-label/internal deployment, reusable generation framework, and priority support
Commercial rights: Commercial reuse rights for approved client, white-label, or internal deployment workflows. Source archive resale is still not permitted.
Updates: 12 months of updates and priority support

Source archive resale is not permitted on any tier. Team adds approved reuse rights, white-label or internal deployment cover, priority support, and a longer update window.

Download support

If checkout succeeds but the signed archive link fails, email support with the purchase email or Stripe receipt so the matching tier can be checked and resolved.

Delivery and refund expectation

If the paid archive cannot be delivered, is inaccessible, or materially differs from the described tier contents, support will resolve the issue or refund the purchase.

Update access

Pro includes 6 months of versioned updates. Team includes 12 months. Version and changelog metadata ship inside the archive.

Licence questions

If you plan to reuse the archive across clients, white-label work, or internal deployment, ask before buying so Team is scoped correctly.

Buy when the workflow fits.

Inspect the workflows, download the sample pack, compare the editions, then choose the archive that removes the most repeated production work.

See what's included