Buy the right email system.

Core is the £59 archive essentials pack. Pro is the £179 production system for recurring source-to-handoff work. Team is Pro with commercial reuse rights, onboarding, priority support, and longer updates.

Buy Pro - £179 Find your path

Workflow assembly

Trigger to production output

Trigger

Real send event

Workflow

Message journey

Layout

Complete structure

Components

Reusable blocks

Email

Production output

The price buys production artefacts.

Before comparing counts, inspect the actual handoff: editable MJML, compiled HTML, previews, QA notes, implementation 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

Choose by the job you need done.

The archive stays the same product. These paths simply help lifecycle, technical, and founder buyers find the workflows that match their first use case.

Buyer path

Lifecycle marketer

You own onboarding, launches, digests, and lifecycle sends, but every campaign still becomes a copy, review, QA, and handoff scramble.

Desired outcome: Start from workflow-ready email systems with source, preview, QA notes, and handoff context already attached.

Relevant workflows

Onboarding activation Campaign launch Newsletter digest

Useful layouts

Onboarding Activation Flow Product Launch Campaign Weekly Digest System

Useful components

Welcome Email Hero Product Update Digest Weekly Digest List

Recommended edition: Pro

View lifecycle workflows Compare edition

Buyer path

Email developer

You need reusable MJML, compiled HTML, QA notes, and predictable handoff, not another visual-only template library.

Desired outcome: Use the archive as a source-owned production system: inspect components, assemble layouts, compile, QA, then hand off clean HTML.

Relevant workflows

Password reset Billing receipt Security notification

Useful layouts

Password Reset System Receipt System Security Alert System

Useful components

Password Reset Card Receipt Line Items Security Alert Card

Recommended edition: Pro, or Team for client reuse

Inspect source-ready layouts Compare edition

Buyer path

SaaS founder

You need credible product emails before a full lifecycle or email engineering function exists, and you cannot afford fragile one-off sends.

Desired outcome: Start with the essential customer journeys, then upgrade when email production becomes a recurring operating system.

Relevant workflows

Onboarding activation Password reset Campaign launch

Useful layouts

SaaS Welcome System Password Reset System Product Launch Campaign

Useful components

Header Brand Row Welcome Email Hero Primary CTA Button

Recommended edition: Core first, Pro when recurring

Start with Core Compare edition

What arrives after purchase.

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

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.

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.

Core ships first journeys. Pro standardises. Team scales.

Core is the essential archive starter: three complete workflows with source files, compiled HTML, previews, and setup docs. Pro is the main buying path for recurring email production: the complete archive, 82 components, 18 layouts, 13 workflows, QA, handoff guidance, updates, and Studio waitlist priority while Studio is in development. Team keeps Pro, then adds permission, onboarding, support, a longer update window, and Studio waitlist priority.

Start shipping.

3 workflows

Core

£59

Best when you need the first production journeys covered cleanly: welcome, password reset, and order confirmation systems with 11 components, 3 layouts, 3 workflows, MJML source, compiled HTML, previews, and setup docs.

• SaaS welcome, password reset, and order confirmation systems
• Editable MJML and compiled HTML outputs
• Setup docs for first implementation

Standardise delivery.

13 workflows

Pro

£179

Best when email production is recurring and you need a repeatable source-to-handoff system: 82 components, 18 layouts, 13 workflows, editable source, compiled HTML, previews, QA notes, implementation guidance, 6 months of updates, and Studio waitlist priority while Studio is in development.

• Full source and output archive across lifecycle, transactional, and campaign email
• Studio waitlist priority while Studio is in development
• Token examples, QA notes, and implementation guidance
• Versioned workflow updates for 6 months

Scale operations.

Reuse rights

Team

£349+

Best when the same production artefacts will be reused across clients, teams, or internal systems: Pro archive, commercial reuse rights, onboarding, white-label/internal deployment, priority support, 12 months of updates, and Studio waitlist priority while Studio is in development.

• Studio waitlist priority while Studio is in development
• Commercial reuse rights for the Pro archive
• White-label or internal deployment
• Reusable generation framework
• Priority support and 12 months of updates

Discuss Team

Why Pro becomes the default production choice.

Core is useful when the first workflows are enough. Pro is the commercial choice when email production is recurring and mistakes in source, QA, or handoff cost more than the licence.

More workflows, fewer rebuilds

Pro is for teams who keep rebuilding onboarding, launch, digest, transactional, and lifecycle sends from scratch. The full workflow set gives you repeatable starting points instead of one-off templates.

Source, output, and QA stay together

Every production package keeps MJML source, compiled HTML, previews, QA notes, and handoff guidance connected, so review does not depend on tribal memory or screenshots in chat.

A safer handoff to your ESP

Pro helps you catch copy, link, mobile, image, footer, token, and platform-boundary issues before the email reaches Mailchimp, HubSpot, Salesforce, NetSuite, Klaviyo, or Customer.io.

Buy Pro - £179 Inspect workflows

Studio is the future before-send workspace direction.

Template Hedgehog Studio is not live product UI. It is a planned workspace direction for preparing email packages locally without turning Template Hedgehog into a sending platform.

Template Hedgehog Studio

Everything before send.

The intended Studio workflow is to choose workflows, edit content, compile MJML, inspect the preview, complete QA, prepare platform handoff, and export ZIPs. Studio is in development, not part of the live product experience. The paid archive remains complete without Studio.

Join Studio waitlist View Pro

Studio handles

Choose workflow
Edit content
Compile
Preview
QA
Prepare handoff
Export ZIP

Sending platform handles

Studio does not send emails.
Studio does not manage audiences, consent, unsubscribe, automation, delivery, or reporting.
Your sending platform handles the live campaign, audience, compliance, and results.

When Team is the commercially safer choice.

Team is not a bigger template pack. It is the route for reuse rights, onboarding, support, and operating confidence when Template Hedgehog becomes part of client delivery or internal email infrastructure.

Client and multi-brand reuse

Team is for agencies, consultants, and internal platform teams who need to reuse the Pro archive across clients, business units, brands, or implementation programmes without renegotiating every project.

Onboarding for real production use

Team adds a practical implementation conversation around workflow fit, archive structure, source ownership, update handling, and how the package should move into your team or client handoff process.

Support when email is operational

When production email is part of your operating rhythm, the value is not more templates. It is permission, support priority, a longer update window, and confidence that the system can be reused cleanly.

Discuss Team

Review support

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.

What happens after the first purchase.

Template Hedgehog should feel like an owned production system with a clear update path, not a file dump that quietly goes stale.

Owned archive, not SaaS lock-in

The files you buy remain yours inside the licence terms. Update access improves the archive over time, but the source and compiled output do not disappear when an update window ends.

Versioned updates protect production work

Updates are tied to source, compiled output, workflow guidance, QA notes, docs, and archive structure, so buyers can see what changed before pulling a newer package into production.

A renewal path for serious teams

When an included update window ends, teams can keep using the owned archive, renew update access, or move to Team when reuse rights, onboarding, and priority support become commercially safer.

Review changelog Ask about updates

Why upgrade?

The upgrade path is about archive depth first, then reuse rights and support. Pro changes what you receive. Team changes what you are allowed and supported to do with it.

Core to Pro

Move to Pro when the 3 Core workflows are not enough and you need the full set of lifecycle, transactional, and campaign systems.

Pro to Team

Move to Team when reuse rights, white-label delivery, priority support, or a longer update window matter.

Team difference

Team does not add more templates than Pro. It adds permission, support, and operational cover.

Start small if the workflow is still being proven.

Buy Core when the first three production journeys are enough. Buy Pro when you need the full archive. Discuss Team when reuse rights, white-label use, or priority support matter.

Buy Pro - £179