|
|
|
|
|
|
by mushufasa
38 days ago
|
|
|
This is cool! I looked for this in the past. This is the main reason we bothered with mailchimp/hubspot -- simply the ability for nontechnical marketing people to put together nice emails, and the trust that we won't need an engineer to troubleshoot email formatting on their behalf. I remember trying some OSS tools at the time (8 years ago?) and there were some templates we used but then when we wanted to modify them, the broken-ness of email html/css standards made it really hard to test. I know the standards and practice around this are a moving target, though, so I hope you can find a model to sustain and expand this, without charging for delivery/contact list numbers like MailChimp or other incumbents. |
|
|
The cross-client rendering thing is why Templatical outputs MJML instead of raw HTML. MJML was built to abstract all the table-based, Outlook-2007-quirks, Gmail-strips-style nonsense — you write semantic blocks, MJML compiles to table HTML that works across every major email client. So when your marketing person moves a block or changes a button color, it doesn't silently break in Outlook two weeks later.
On sustainability — same concern. Even while I was building it, multiple times I caught myself asking "is this even worth theeffort? Maybe not with all the functionalities I've built, but someone could vibe-code a lightweight version of it in a day." But at the same time, I see and personally used SaaS products with the same or fewer features selling for $2,500/mo, which seems ridiculous.
I'm currently working on a subscription-based Cloud version, but only for things that actually need an infrastructure and backend: AI chat/rewrite, image-to-template conversion, MCP integration, hosted media gallery, saved modules, commenting, real-time collab, email testing, version history, etc. Sending stays your own provider — no per-contact, per-email, or per-delivery charges.