Buy the right email system.

Core is a £59 starter pack. Pro is the £179 full production archive. Team is Pro with commercial reuse rights, white-label use, priority support, and longer updates.

Buy Pro - £179 Compare editions

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

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.

Download complete sample

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 starts. Pro standardises. Team scales.

Core gives you a starter set of source files, compiled HTML, previews, setup docs, and 3 workflows. Pro unlocks the complete production archive: 82 components, 18 layouts, 13 workflows, token examples, advanced guidance, and updates. Team keeps the full Pro archive and adds permission, support, and a longer update window.

Start shipping.

3 workflows

Core

£59

Best when you need a small, self-serve starting point with real files: 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 the complete archive: 82 components, 18 layouts, 13 workflows, editable source, compiled HTML, token examples, advanced guidance, and 6 months of updates.

• Full source and output archive across lifecycle, transactional, and campaign email
• 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 plus commercial reuse rights, white-label/internal deployment, priority support, and 12 months of updates.

• Commercial reuse rights for the Pro archive
• White-label or internal deployment
• Reusable generation framework
• Priority support and 12 months of updates

Discuss Team

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 archive link fails, contact support with the Stripe receipt and the matching download can be resolved.

Refund reassurance

If the paid archive cannot be delivered 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.

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 3 starter workflows 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