Drafts, checks, reports.
Ready before Monday.

Take a ready-made automation or write down how your team runs campaigns. It drafts briefs and newsletters in your voice, checks every launch and builds the weekly report, then leaves it all for your review. Nothing is published without you.

Example instruction: Every Tuesday, prepare a newsletter draft from the week's launch briefs, suggest three social posts, and send the drafts to me for review. ## Tone - Follow our **voice guide**: clear, warm, no jargon. - Flag any claim that needs a source. ## Channels | Channel | Length | When | |---|---|---| | Newsletter | 200 words | Tuesday 9 a.m. | | Social | 3 variants | Launch day | - Keep everything in draft until I approve.

In your own words.
Built for real work.

One sentence is enough to begin. The same document grows into a full procedure when the job needs it.

  • Plain language

    Write it the way you would brief a colleague. No flowcharts, no code.

  • Rules, tables and exceptions

    Add limits, scoring tables and edge cases as they come up, right in the same document.

  • Judgment, not just steps

    Say what good looks like and when to ask you. It follows the intent, not a rigid path.

Browse advanced workflows

Your files. Your tools.
No new system.

AUTOMATE.md is just another file in your folder. Nothing to migrate, nothing to replace.

  • Starts on its own

    A new email, a schedule, a changed folder or an edited file starts it. No one has to remember.

  • Your apps, connected

    Email, calendars, drives and team apps. Connect only what the job needs.

  • Next to the work

    It sits beside the invoices, CVs and sheets it works on, and reads them like you would.

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.

Every stage of the work. Every recurring job.

The recurring work marketing teams do every week, grouped the way it happens.

  1. 01

    Plan

    Calendars, dates and dependencies. It breaks when two launches land in the same week and nobody saw it coming.

  2. 02

    Produce

    Briefs, content and assets. It breaks when the brief is rewritten from scratch every time and the files have five versions.

  3. 03

    Launch

    Getting campaigns live without broken pieces. It breaks when a form fails after paid traffic arrives.

  4. 04

    Always-on

    Mentions, comments, competitors and email health. It breaks when a complaint waits until someone checks.

  5. 05

    Measure

    Reporting and pacing. It breaks when the meeting starts from five screenshots instead of one set of numbers.

  6. 06

    Optimize

    Refreshing what decays. It breaks when nobody notices a page losing traffic until the quarter is over.

Compared with what you use today.

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.

Around the tools you already run.

Connect only what a job needs. Your inbox, calendar, files and the systems below stay where they are, with nothing to migrate.

Everyday
GmailOutlookGoogle CalendarSlackMicrosoft TeamsGoogle DriveGoogle SheetsExcel
Marketing automation
HubSpot Marketing HubMarketoKlaviyo
Lifecycle
Customer.io
Email
Mailchimp
SEO
Google Search ConsoleSemrushAhrefs
Analytics
Google Analytics 4
Product analytics
Amplitude
CDP
Segment
Attribution
Dreamdata
Ads
Google AdsMeta AdsLinkedIn AdsThe Trade Desk
Social
BufferSprout Social
Social listening
Brandwatch
CMS
Contentful
Landing pages
WebflowUnbounce
Experimentation
HotjarOptimizely
DAM
Bynder
Design
Canva
Survey
Typeform
Events
Zoom
Collaboration
SlackNotion

What marketing teams ask before handing anything over.

Will it publish off-brand or unchecked content?
No. The marketing automations here leave drafts for review, and you choose which steps wait for your OK. Write your voice guide and claim rules into the file and every draft follows them.
How is this different from the AI writer we already use?
A writing tool waits for you to ask. An automation starts on its own when a brief lands, a week ends or a form breaks, and follows the procedure your team wrote down.
Does it work with our marketing tools?
It works around what you already use: the analytics, the email platform, the content calendar and the shared drive. Connect only what each job needs.
Who owns what it produces?
You do. Drafts and reports land in your files and drafts folders, and the instructions are a document your team can read and change.
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.

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.