Every contract pre-read.
Every call still yours.

Take a ready-made automation or write down your playbook in plain sentences. It compares incoming paper with your positions, quotes the deviations and watches every notice date, then hands you a short summary. Legal decisions stay with you.

Example instruction: Pre-review each contract that arrives at legal@acme.inc: compare it with our review checklist, quote any deviations, and send me a summary. ## Check every contract for | Clause | Our standard | |---|---| | Liability | Capped at 12 months of fees | | Notice period | 30 days or more | | Governing law | Our home jurisdiction | ## Rules - Quote the clause for each deviation. - Flag missing **renewal dates**. - Leave every legal decision to me.

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 compares and flags. Every legal call stays yours.

  • It never signs or advises

    It quotes deviations against your playbook. Accepting, signing and advising stay with a lawyer.

  • Every flag shows its source

    Each deviation quotes the clause it is about, every step is recorded, and a file change can be put back.

  • Confidential stays contained

    Each automation reaches only the folders you connect for it, and a local model keeps processing on your machine.

Ready-made for legal and compliance teams. Pick one and run it.

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

Contract pre-review

Pre-review each contract that arrives at legal@acme.inc: compare it with our review checklist, quote any deviations, and send me a summary.

Each new contract

Standard Paper Checklist

When standard paper arrives, check it against the playbook checklist and return only the clauses that differ, not the whole contract.

When standard paper is uploaded

Renewal Notice Reminder

90 days before a renewal date, open a notice task, email the contract owner, and write the notice deadline into the tracker.

90 days before a contract renewal date

Data Request Deadline Watch

Every day at 8:00am, list the open data subject requests and email privacy a warning for any deadline inside five days.

Every day at 8:00am

Redline Version Tracker

When a redline comes back, list the clauses still open, the last change to each, and who owes the next turn.

When a new redline version is received

Evidence Gap List

Every Monday at 9:00am, pull the failed control checks and email each owner the specific evidence still missing.

Every Monday at 9:00am

Every stage of the work. Every recurring job.

The recurring work legal and compliance teams do every week, grouped the way it happens.

  1. 01

    Intake

    Getting requests to the right person with the facts attached. It breaks when the queue is a folder of files named by whoever uploaded them.

  2. 02

    Review

    Reading paper against the playbook. It breaks when standard documents wait behind complex ones for the same lawyer.

  3. 03

    Negotiate

    Tracking redlines and who owes the next turn. It breaks when versions multiply across inboxes.

  4. 04

    Obligate

    Renewals, notice windows and obligations. It breaks when a date is right the day the list is built and wrong a month later.

  5. 05

    Record

    Holds, redactions and the record of what was done. It breaks when the log lives apart from the document.

  6. 06

    Prove

    Audit evidence and filings. It breaks when evidence is gathered after it is asked for.

Compared with what you use today.

Contract management systems

Storing signed contracts and running approval routes.

Their rules can't read new paper against your playbook or explain a deviation in plain words.

Flowchart automation tools

Moving records between apps.

Clause-level judgment does not fit into branches, and every exception becomes another one to maintain.

AI chat assistants

Summarizing a contract when you paste it in.

Nothing happens until someone asks, and the playbook lives in a chat instead of a document you control.

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
CLM
IcertisDocuSign CLMIroncladAgiloftConga
Contract AI
ContractpodAiLuminanceRobin AI
E-signature
DocuSignAdobe Acrobat SignDropbox Sign
GRC
OneTrustVantaDrataAuditBoard
Policy
HyperionLawToolBox
Records
Microsoft PurviewiManage
E-discovery
RelativityEverlaw
Legal hold
Exterro
Research
Thomson Reuters CoCounsel
Privacy
TrustArcFairNow
Corporate records
Diligent
Matter mgmt
LegalOnward
Legal spend
Zilliqa

What legal and compliance teams ask before handing anything over.

Where does confidential material go?
The app runs on your computer, and each automation reaches only the folders and apps you connect for it. A cloud AI model receives what the job needs; choose a local model to keep that processing on your machine.
Will it give legal advice or sign anything?
No. The legal automations here compare, quote and flag against positions you write down. Approving, signing and advising stay with a lawyer, and you choose which steps wait for your OK.
Can we trust what it flags?
Each flag quotes the clause it is about and the position it was compared with, so a reviewer checks the source instead of trusting a summary. Every run is recorded.
Do we need a contract management system first?
No. It works on the documents, inboxes and trackers you already keep, and alongside a contract system if you have one.
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.

macOS — coming soon