Future product direction

Template Hedgehog Studio.

A planned production workspace for modern email teams: author, review, compile, QA, and hand off email systems before they reach Mailchimp, HubSpot, Salesforce, NetSuite, Klaviyo, Customer.io, or another ESP.

Join Studio waitlist View the current archive

Studio is not live product UI and does not replace the current Template Hedgehog archive. The archive is the product you can inspect and buy today.

Future workspace concept

Concept preview only. Not live product UI.

Source

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

Handoff state

concept

Compiled HTML

Kept with the workflow before send.

Preview

Kept with the workflow before send.

QA notes

Kept with the workflow before send.

Platform handoff

Kept with the workflow before send.

Why it exists

Email production breaks between source and send.

Template Hedgehog already gives teams production-ready artefacts. Studio is the future workspace idea for keeping the same artefacts connected while a send is being prepared.

Author

Start from workflow-ready MJML and structured content, not an empty email file.

Review

Keep audience, trigger, copy intent, preview state, and risk notes together.

Compile

Turn source into production-safe HTML before it moves into the sending platform.

QA

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

Handoff

Prepare source, compiled output, preview, QA notes, and guidance as one package.

The archive is live. Studio is the future workflow layer.

Today, Template Hedgehog sells production-ready MJML and HTML email systems. Studio would make that source-to-handoff process easier to run inside one workspace.

What you can buy today

Production-ready MJML source
Compiled HTML
Rendered previews
QA notes
Workflow examples
Implementation guidance

What Studio is intended to help with

Choose a workflow and edit the email content in one place.
Compile MJML and inspect the output before platform upload.
Track QA checks against the same source and preview.
Prepare a clean handoff package for Mailchimp, HubSpot, Salesforce, NetSuite, Klaviyo, Customer.io, or another ESP.

Product boundary

Studio would sit before your sending platform.

It would not send email, manage subscribers, run automations, process consent, unsubscribe people, or report campaign performance.

Template Hedgehog Studio

Author
Review
Compile
QA
Handoff

Email platforms

Audiences and segments
Automation and journeys
Consent and unsubscribe
Sending and deliverability
Reporting and analytics

Studio waitlist

Register interest in the future workspace.

Join if you want updates on the Studio direction, private review opportunities, and notes about source-to-handoff email production.