Totally fair. You can build the first 10-minute demo with an LLM now.

The hard part is usually what comes after: editable state, templates, email-safe HTML, PDF/export pipelines, assets, permissions, custom blocks, previews, and all the rendering edge cases that show up once real users depend on it.

AI also makes structure more important, not less. That’s why we launched Unlayer Elements: instead of having an LLM generate a static blob of HTML, it can target structured components that map back into an editable email, web page or document.

So I'd use AI to prototype it. I'd use Unlayer when that content layer becomes production infrastructure you don't want to maintain yourself.

I see this question a lot. Not associated with OP but most companies don't want to maintain a bunch of vibed up apps they don't understand.

I work outside of SV in the southeast and most businesses know AI is being used for products they use but they want experts in that field behind that.

Not the OP, nor do I have any relationship to them, but I've had to build or maintain plenty of these in my time and sure, an LLM can knock out a basic one easily, but there are so many edge cases that need to be accounted for that it gets complex quickly.

Congrats on the launch - this looks like a genuinely useful tool. I look forward to checking it out.