Lifecycle & Email Marketing

Designs segmented win-back email sequences for dormant users - dormancy tiers, a three-beat sequence with a single proportional incentive, and a suppression rule - and measures success by re-activation, not opens. Use when someone says "our users went quiet", "design a win-back campaign", "how do I re-engage lapsed customers", "should we email people who haven't logged in for months", or lifecycle messaging has stopped landing with a lapsed segment. Do NOT use for recovering an unfinished checkout - use abandoned-cart-sequence instead. Do NOT use for diagnosing and fixing why active customers cancel - use churn-reduction instead. Do NOT use for building always-on onboarding or nurture flows - use email-drip-builder instead.

Builds a behavioral segmentation system for lifecycle messaging - RFM-based segments, event-driven membership triggers, one next action per segment, size audits, and send-time suppression rules. Use when someone asks "how should I segment my users", "our emails get ignored, who should get what", "how do I message at-risk users differently", or is personalizing lifecycle campaigns to cut unsubscribes and lift click-through. Do NOT use for building ad-platform audiences - use audience-targeting instead; for narrative customer personas use user-persona or icp-persona-builder; for mapping the full lifecycle stages and journeys use lifecycle-journey-map.

Writes push and in-app notification copy that survives lock-screen truncation, ties every send to a user-specific trigger, deep-links to the exact destination, and respects frequency caps. Use when someone asks "write a push notification for this event", "why is our push opt-out rate rising", "draft re-engagement push copy", or is planning lifecycle, transactional, or re-engagement notifications. Do NOT use for implementing the delivery pipeline, tokens, or notification infrastructure - use push-notification-wirer instead; for deciding which lifecycle stage should send push at all, start with lifecycle-journey-map.

Audits and protects sender reputation and inbox placement for permissioned marketing and lifecycle email - SPF, DKIM, and DMARC authentication, domain warmup, bounce and complaint thresholds, and engagement sunsetting - and delivers a scored deliverability audit checklist with a remediation order. Use when someone asks "why are my newsletters going to spam", "how do I set up SPF, DKIM, and DMARC", "is my bounce rate too high", "should I send marketing from a subdomain", or is launching a new sending domain or auditing an existing opted-in email program. Do NOT use for cold outbound infrastructure - lookalike sending domains, mailbox pools, per-mailbox volume caps - use cold-email-deliverability instead; do NOT use to write the emails themselves - use email-drip-builder or email-newsletter-pro instead.

Write recurring email newsletters - subject lines that earn the open, preview text that extends them, a body structure readers finish, and cadence rules that keep the list healthy. Use when someone asks "write my newsletter", "give me subject line options", "why is my open rate dropping", "should I send weekly or monthly", or "help me structure this issue". Do NOT use for automated onboarding or behavior-triggered sequences - use email-drip-builder instead. Do NOT use for inbox placement and spam-folder problems - use email-deliverability instead.

Diagnoses SaaS churn root causes through cohort analysis and a seven-category taxonomy, then builds segmented intervention playbooks ranked by frequency, revenue at stake, and addressability - including save-offer economics. Use when someone asks "why is our churn so high", "build a churn reduction plan", "should we offer discounts to cancelling customers", or when NRR/GRR is slipping and the team needs a diagnosis before prescriptions. Do NOT use for gym or fitness-studio member retention - use retention-and-churn-killer instead. Do NOT use for re-acquiring customers who already left - use win-back-campaign instead. Do NOT use for growing existing accounts - use expansion-revenue instead.