Lifecycle Email Hygiene and Deliverability

Keeps welcome, nurture, and win-back sends deliverable by pruning dead addresses and retiring the flows that stopped working.

macOS — coming soonSee the 3 automations
Marketing / AUTOMATE.md

Each morning at 8:00am, check the bounce and complaint rates in the sending report and post anything outside its usual range.

Ready-made: Deliverability Watch

The job, and what good looks like.

### What breaks Flows are switched on in a launch week and never looked at again, so a welcome series keeps emailing people who already bought, and a discount flow runs years after its reason expired. Lists grow unchecked, bounces climb quietly, and inbox placement suffers long before anyone connects it to the list. ### What the workflow does - Check bounce, complaint, and unsubscribe rates each morning, per list and per flow, not just in total. - Trace a spike to one send, one segment, and one subject line before the rate has time to settle. - Prune hard bounces and long-unengaged addresses on a schedule, and keep the suppression list as the single source of truth. - Review flows with no conversions in sixty days and recommend a fix, a rewrite, or a shutdown date. - Hold SMS sends to the same suppression list, so someone who opted out is not reached on another channel. ### What a human still approves The lifecycle owner decides which flows to rewrite and which to retire, and signs off on any change to send volume or frequency. Nobody is unsubscribed or re-permissioned without a person agreeing to it.

When it is handled

  • Bounce and complaint rates watched every morning
  • Dead addresses pruned on a schedule
  • Flows with no results retired with a date
  • Unsubscribe spikes traced to a single send

Works with tools like

  • Klaviyo
  • Customer.io
  • Mailchimp
  • Marketo
  • Segment

Ready-made automations. Pick the one that fits.

Each one is a plain-language document. Run it as it is, or change the timing, the rules and the tools to match your team.

Deliverability Watch

Each morning at 8:00am, check the bounce and complaint rates in the sending report and post anything outside its usual range.

Every weekday at 8:00am

Flow Sunset Review

Mid-month, list the welcome and win-back flows with no conversions in sixty days and email a recommendation for each one.

On the fifteenth of each month

Unsubscribe Spike Check

When unsubscribes spike, pull the send report, name the segment and subject that drove it, and post the short read.

When unsubscribes spike on a send

You stay in charge.
At every step.

It drafts and checks. You decide what goes out.

  • Nothing published without you

    Drafts wait for your review, in your voice and within your claim rules.

  • Undo what you don't want

    Every step is recorded, and a file it changed can be put back.

  • Only the channels you connect

    Each automation reaches only the apps and folders you give it.

Deliverability Watch

Approve before it posts in Slack?

ReviewApprove

Before you download.

Where does it run?
On your Mac or Windows computer, in the background. It keeps working after you close its window, and only reaches the folders and apps you connect for each automation.
How does it connect to our CRM and other tools?
Through each app's own connection where it offers one, signed in once by you, or by using the app in a browser the way you would. Each automation gets only the connections you give it, and the tools a page names are examples you can swap for your own.
Does it run when my computer is asleep?
It keeps your computer awake while a job runs and just before a scheduled one. While the computer is closed or off, nothing runs; when it wakes, it checks the inbox, calendar and other sources it watches for anything that arrived meanwhile.
How does my team use it?
Each person who runs automations installs the app. Keep a project in a shared folder, such as Google Drive or a network drive, and teammates can open it and follow every run, while one person owns it and runs it.
Do I need anyone technical to set it up?
No. Download the app, add an automation in plain words, and connect only what that job needs. Nothing runs until you switch it on.

Already have tools for this? Here is the difference.

Your marketing platform's workflows

Sending sequences and scoring contacts inside one tool.

They stop at that tool's edge, and can't draft from a brief or explain a drop in results.

Flowchart automation tools

Moving data between apps at high volume.

Every exception becomes another branch someone has to build and maintain.

AI chat and writing assistants

Drafting copy when you ask.

Nothing happens until you ask again, and your brief, voice and checks live in a chat.

AUTOMATE.md

Your routine, written in plain words. It runs on its own, follows your rules, handles the exceptions a flowchart can't, and asks you when it matters. The file stays yours, whichever AI model runs it.

Related workflows.

Campaign reporting

Builds the weekly campaign report from one agreed set of channel numbers, so the meeting starts from the same figures instead of five screenshots.

2 automations

Brand mention alerts

Sorts every mention of the brand by how it reads and puts the ones that need a person today in front of the team, so a complaint is answered the day it appears.

1 automation

Social media digest

Turns the previous day's comments, mentions, and per-post results into one short morning read with a reply queue attached, so questions are answered the same morning and last week is still findable.

1 automation

Start with one job.
Make it your own.

macOS — coming soon
  1. 1

    Get the app

    It runs on your computer, next to your files.

  2. 2

    Add the automation

    Paste the instructions into the app, or save them as a file next to your work.

  3. 3

    Try it, then turn it on

    Run it once and check the result. It only runs on its own once you switch it on.

macOS — coming soon