Email Automation + Custom Code

Engineering a 365-email automation and replacing Zapier with custom code.

Dr. Sage Breslin runs a high-ticket transformational coaching brand. Her email infrastructure needed to match the sophistication of her offer.

Client
Dr. Sage Breslin, Sage Wisdom Institute
Engagement
Ongoing automation + systems
Stack
ActiveCampaign, Python, Flask, Stripe

The problem.

Sage runs a membership called Daily Pearls where each of the 365 emails is tied to a real calendar date. The date is written into the content itself. A subscriber joining on May 18 cannot start from email one. They need to enter the sequence at exactly the right day, automatically, forever.

Standard autoresponder logic cannot do this. On top of that, her existing welcome sequences were outdated, her Stripe-to-CRM flow ran on a fragile Zapier connection, and her newsletter lacked consistent formatting and conversion logic.

What I built.

  • Date-aware 365-email automation using a multi-automation architecture with Goals and If/Else branching in ActiveCampaign
  • Subscribers enter mid-sequence based on join date with 100 percent date accuracy and no manual intervention
  • Full welcome sequence rebuild preserving the brand voice and signature language
  • Python Flask webhook replacing Zapier: Stripe payments now create and tag ActiveCampaign contacts directly
  • 3-email Calendly contact migration sequence triggered by booking behavior
  • Re-engagement sequences targeting dormant subscribers
  • Wisdom Wednesday newsletter formatting with consistent CTAs
  • Ongoing sequence maintenance and copy refinement

The stack.

ActiveCampaign Python Flask Stripe API Calendly Webhooks Behavioral Tagging

The original brief.

This is the email Sage sent that started the engagement. She described the problem in two paragraphs. The solution took ten automations.

Sage Breslin original brief email
The brief, verbatim

The result.

Sequences that sound like the founder wrote them personally. Members receive the right email on the right day regardless of when they joined. The payment-to-CRM flow runs on owned code instead of a third-party subscription. Sage loved it enough to record a video testimonial.