Every lifecycle email on the platform starts as a Figma frame and ends as an assembled template inside Iterable. Between those two states sat a designer, a marketer, and usually a developer - plus a review cycle where “the padding is four pixels off” was a legitimate blocker to shipping.
The full study covers the Claude pipeline behind it - Figma MCP in, AWS asset handling in the middle, Iterable MCP out - the component registry that makes the output trustworthy, the LCM playbook encoded into the tool, the guardrails that keep it out of trouble, and how it was packaged so non-engineers could run it without a terminal.
Our work here covers internal architecture, tooling and numbers, so the full write-up is shared on request rather than published openly. Email us and we’ll send the passphrase - usually the same day.
That passphrase didn’t work. Try again, or email us for access.
One passphrase unlocks every study in this program.