Email & lifecycle with AI

<aside> 🛡️

+10% Revenue Per Visitor in 90 days. Or we refund the engagement. Book a teardown

</aside>

Claude drafts the campaign, writes every email, and pulls the benchmark to beat. You wire the flow logic in Klaviyo. This page is the workflow plus the prompts that do the work.

The pitch you keep seeing is "wire Claude into Klaviyo and it builds your flows for you." The connector reads flows; it does not write them. So the workflow below is built around what the Klaviyo connector actually does, which is still most of the job: the strategy, the copy, the templates, and the benchmark to measure against.

The setup, once, in Claude Code:

claude mcp add --transport stdio klaviyo -- uvx klaviyo-mcp-server@latest

Use a private API key scoped to Campaigns, Templates, Profiles, and Events. There is also a hosted endpoint at https://mcp.klaviyo.com/mcp if you prefer to connect from Claude Desktop. Verify with claude mcp list or /mcp.

Where each task lands

Task	What the connector does	Who does the wiring
One-off campaign (newsletter, promo, launch)	Writes it, builds the HTML template, can schedule it	Claude, end to end
Email templates (reusable layouts)	Generates and uploads them	Claude
Flow copy (welcome, abandoned cart, post-purchase)	Drafts every email, the triggers, the timing, the branching as a build spec	Claude drafts, you build the flow in Klaviyo
Flow logic itself (the automation)	Reads it, audits it, tells you what is broken	You, in Klaviyo's flow builder
Audience segments	Read-only via the connector; build the audience in Klaviyo's own Segments AI	You, in Klaviyo

The thinking and the writing get done by Claude. You do the final wiring by hand in Klaviyo's flow builder. That is the fast part once the spec is written.

The campaign recipe (Claude does this end to end)

Campaigns are where the connector writes, so this part runs without you touching Klaviyo until you hit send. Have Claude pull the performance of your existing welcome sequence in the same prompt, so the new version has a benchmark to beat instead of getting judged on vibes.

Create a 5-email welcome campaign in Klaviyo for [BRAND], matching the brand voice in
voice.md. Email 1: welcome + brand story. 2: hero product + social proof. 3: objection
handling (the top 3 from our reviews). 4: founder note + mission. 5: first-order offer
with urgency. Generate the HTML for each, upload the hero images, and pull the 30-day
performance of our existing welcome campaign as a benchmark so I can compare.

Three things make this prompt work:

It points at voice.md. Build a brand voice file once and aim every email prompt at it. Skip that and you get email that reads like every other AI email.
The five-email arc is a sequence. Welcome and story first, then product and proof, then the objections your actual reviews surface, then the founder note, then the offer last. The discount lands after the reader has a reason to want it.
The benchmark pull. Asking Claude to surface your current welcome numbers in the same breath means you ship the rewrite already knowing which number you are trying to move.

<aside> ✅

Steal this: never ship a rewrite without the benchmark. Add "pull the 30-day performance of the current version" to every campaign prompt so you know the number you are beating before you press send.

</aside>