What it does
Lifecycle and Email Campaign Agent solves the quiet failure of email programmes: a drip series gets built once, ships, and then nobody touches it for two years while the product it describes moves on. Give it a target segment, a campaign goal and a step count, and it designs the whole series: the entry condition that puts someone into the flow, a per-step cadence, email drafts with A/B subject-line variants, the exit criteria that take someone out, and an expected conversion impact against the engagement baseline you supply. The cadence is shaped by the flow family rather than the step count, which is the detail most templates get wrong. A cart-recovery sequence runs on hours; a win-back sequence runs on weeks. Each step carries a day offset, an hour offset and a suggested send window in the recipient's local time, so the same series does not arrive at 3am for half your list. The exit criteria are equally deliberate. Converted, unsubscribed, no longer matching the entry condition, or reached the final step without converting — and that last one routes to a monthly human review rather than another automated send, which is how a lapsed contact avoids being emailed forever. The hard guardrail: this agent never sends. Every run returns the flow marked as requiring human approval with send authority explicitly withheld, and that finding is raised as critical in the output rather than tucked into a footnote. The draft goes into your ESP for a person to review. For a system that can reach your entire contact list in one action, that boundary is not negotiable. It also refuses to project from a self-contradictory funnel rather than producing a confident number from impossible inputs. Each step is callable alone: `plan_cadence` when the copy exists but the timing is wrong, `draft_emails` for the copy, `estimate_impact` for the projection, `build_exit_criteria` for the flow logic. No connectors and no credentials. Built for lifecycle and CRM marketers.
Example prompts
- Design a 5-step activation series for trial users
- What cadence should a cart-recovery flow run on?
- Draft the emails with A/B subject lines for this segment
