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.