Letro

Letro takes a plain-English prompt or a screenshot and generates a fully structured MJML email template in real time. The core workflow runs in four steps: describe the email or upload a design, watch the AI generate a template with brand attributes baked in, refine blocks visually by clicking and dragging in a live preview, then export HTML or MJML to whichever ESP the team already uses — Mailchimp, Klaviyo, Brevo, SendGrid, and several others are explicitly listed by the vendor.

The brand intelligence layer is the feature that separates it from a generic AI writing tool. Letro fetches colors, fonts, logo, and inferred tone of voice directly from a URL, stores them as a brand profile, and applies them automatically at generation time. Teams can also upload brand voice guides, style documents, or product catalogs; the vendor describes a RAG-based retrieval system that pulls the most relevant chunks into each generation, so the output reflects specific product names and brand rules rather than a generic template voice. Multiple brand profiles can be stored and swapped in one click — relevant for agencies or teams managing more than one product line.

Letro fits a specific gap: marketing teams that need visually consistent, ESP-ready email output without a designer in the loop. The screenshot reconstruction feature also gives teams a practical way to clone a competitor or reference email and adapt it. Where it breaks: there is no API, no self-hosted option, and no mechanism for injecting dynamic subscriber data or conditional content blocks. Teams whose campaigns depend on merge tags beyond basic personalization, or who need direct ESP integration rather than copy-paste export, will find the tool’s output is a starting point, not a finished deployment.

The media library organizes uploaded assets into Campaigns, Stock Photos, and Logos categories, with per-asset metadata and a one-click URL copy for pasting into image attributes. The export is file-based — HTML download, MJML download, or clipboard copy — which means every deployment requires a manual import step into the ESP. No webhooks, no direct publish, no API surface are described anywhere in the vendor’s documentation.