Map Your Lifecycle Emails End to End

    You are a lifecycle marketer mapping an email program. Most programs grow by accretion — someone builds an automation, leaves, and nobody knows what still sends.

My business and what I sell: {{business}}
The stages someone goes through from first contact to long-term customer: {{customer_journey}}
Automated emails that exist today, as far as I know: {{existing_emails}}
Where people commonly drop off or go quiet: {{drop_off_points}}
What data and triggers I can act on: {{available_triggers}}
My tooling: {{tools}}

Produce:

**The map.** For each stage of {{customer_journey}}, the emails that should exist. For each: the trigger, the timing, the one job it does, and the single action it asks for. Cover the stages people skip — the gap between signup and first use, the period after purchase but before value is felt, the quiet stretch in a long consideration cycle, and the run-up to renewal.

**Gaps.** Against {{existing_emails}}: where someone currently receives nothing. Line these up against {{drop_off_points}} — the correlation is usually obvious once it's drawn, and it's the fastest source of return in the whole program.

**Overlaps and collisions.** Where a person could receive several automated emails in the same day, or get a promotional message during a support problem, or be enrolled in two sequences at once. Define the suppression rules: who should be excluded from what, and which message wins when two fire together. This is the most common failure in a mature program and it's invisible until a customer complains.

**Behavior over schedule.** For each email, whether it should be triggered by something the person did or by elapsed time. Behavior-triggered messages outperform scheduled ones consistently, so flag every scheduled email that could be tied to an actual signal from {{available_triggers}}.

**Exit and entry conditions.** For each sequence: what puts someone in, what takes them out early, and what happens when they convert mid-sequence. A person who buys on email two should not receive emails three through six — this is the mistake that generates the most unsubscribes and complaints.

**Frequency ceiling.** A rule for the maximum number of emails per person per week across all sequences combined, and how it's enforced. Without a global cap, each individual automation is reasonable and the total is not.

**Audit the existing.** For each item in {{existing_emails}}: keep, rewrite, retire, or investigate. Include the question of whether it's still sending at all and whether anyone has read it in a year.

**Build order** for {{tools}}, sequenced by expected return against effort. Lead with the gaps at {{drop_off_points}}, then the suppression rules, then everything else.