Build lifecycle email campaigns

Lifecycle/CRM/retention marketer / e-commerce owner · Assemble in ~20 min; complete campaign package ready in <90 min once brand and ESP data are supplied.

GTMEdit flowon X◆ new (unverified) 89

step 1ready

Translate prompt to campaign brief

campaign-brief14 alts

step 2ready

Design lifecycle journey and segment rules

lifecycle-marketing-campaigns14 alts

step 3connector

Pull audience segments from ESP/CDP

⚡ bring your own tool

step 4ready

Establish brand voice profile

brand-voice11 alts

step 5ready

Write email automation flows

ecommerce-email-marketing-builder15 alts

step 6partial

Extend flows to SMS and add send-time schedule

afrexai-email-marketing6 alts

step 7ready

QA and go/no-go validation

campaign-launch-qa18 alts

step 8connector

Upload flows and segments to ESP

⚡ bring your own tool

Did this recipe work for you?

What you get

▸Structured campaign brief (goal, audience, KPIs, channels) derived from a plain-English prompt
▸Lifecycle journey map with branching logic and segment membership rules
▸Full email + SMS copy for every touchpoint, ESP-ready with subject lines, bodies, CTAs, and opt-out language
▸QA report with go/no-go score across 10 execution layers, plus an upload-ready automation flow spec

tools: ESP subscription (Klaviyo from $45/mo, Braze enterprise) — already in your stack; no new tool required for the AI assembly session

tokens: ~$2-6 per full campaign build (brief → QA) depending on flow depth and copy volume

≈ $5-15/mo in tokens for 2-4 campaign builds/month; ESP cost is pre-existing

What stays yours

· Review all generated copy for brand accuracy and legal compliance before uploading — AI copy must be approved by a human who owns the brand voice
· Activate the flows in the ESP and monitor deliverability, open rates, and unsubscribe rates for the first 48 hours after launch
· Tune segment definitions and branching conditions after the first campaign run based on actual performance data — the agent cannot close this feedback loop without you

The problem

When I run lifecycle/retention for an e-commerce or SaaS brand, I want to describe a campaign or play in plain English and get ready-to-send segments, copy, and multi-step branching flows across email/SMS with optimized per-person send timing, so I launch hyper-personalized programs without manually building each flow over several days.

Cybernetic layers

Memorybyo

Campaign history, A/B test results, and past send performance live in the ESP — not in the agent. Use a local context file or shared doc to carry brand voice and segment definitions across sessions. No harvested memory artifact covers this yet.

Background-schedulingpartial

Once flows are uploaded to the ESP, the ESP itself handles the scheduling (trigger-based and time-based sends). The assembly session is batch, not continuous — no background agent loop needed for this recipe. A cron to regenerate seasonal campaigns monthly is possible with Claude Code's CronCreate but is not part of this recipe.

Harnessready

Claude Code is the runtime. Drop each skill into ~/.claude/skills/ and invoke by name. The session runs start-to-finish in one conversation; byo-tool steps require you to paste exported data or provide API credentials.

Click any step to see what fills it — and the ranked alternatives you can swap in.