Every shoot in order.
From card to client.

Take a ready-made automation or write down how you handle a shoot. It verifies every card, files each shoot by your naming pattern and checks deliveries against what the client approved, right where your files already live.

Example instruction: When a card is offloaded to the working folder, check each file against the card listing, post the count per card, and list anything that did not copy whole. ## Check every card | Check | If it fails | |---|---| | File count matches the card | List the missing files | | Every file opens | Flag the broken ones | | A second copy exists | Don't mark the card safe | - Never format or delete a card — only report.

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 checks and files. Every creative call stays yours.

  • It never deletes on its own

    It checks, lists and files. Deleting or formatting anything waits for your OK.

  • Undo a move you don't want

    Every step is recorded, and files it moved or renamed can be put back.

  • Your drives stay yours

    It works on the folders you point it at, on your computer. Nothing is uploaded to a new library.

Ready-made for photographers and video 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.

Offload Checksum Verify

When a card is offloaded to the working folder, check each file against the card listing, post the count per card, and list anything that did not copy whole.

When a card is offloaded to the working folder

Card Folder Pattern

When a new card folder appears in the working folder, move the images into the job folder using our naming pattern, then post how many files moved and from which card.

When a new card folder appears

Proof Gallery Build

When a retouch batch is finished, build a gallery from the selected frames plus a lower-resolution preview of the full shoot, then email the link and say when it expires.

When a retouch batch is finished

Starred Keeper Digest

Every evening at 7:00pm, pull the frames marked as picks from the shoot log and post a count per subject, with the first ten to start on.

Every evening at 7:00pm

Export Settings Check

When a set is marked ready, check each file in the delivery folder against the agreed size, color space, and file type, then email me the mismatch list before anything is packed.

When a set is marked ready to export

Delivery Manifest Build

When a delivery folder is created, write a manifest that names every file with its version and date, says what the client may do with it, and email it with the link.

When a delivery folder is created

Every stage of the work. Every recurring job.

The recurring work photographers and video teams do every week, grouped the way it happens.

  1. 01

    Ingest

    Cards, copies and folders. It breaks when a card is formatted before anyone checked that every file copied whole.

  2. 02

    Edit

    Culls, versions and looks. It breaks when the next pass starts from a file the client never approved.

  3. 03

    Review

    Proofs and client selections. It breaks when picks arrive by email and nobody records exactly which version.

  4. 04

    Deliver

    Exports, packages and handoff. It breaks when a broken file or the wrong size reaches the client first.

Compared with what you use today.

Presets and actions in your editor

Repeating the same edit across many files.

They can't check a delivery against an approval or tell you a card didn't copy.

Flowchart automation tools

Moving data between cloud apps.

They rarely reach local drives, and every exception becomes another branch.

Doing it by hand

Knowing exactly what happened.

It is the part of the job that waits until midnight.

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
Photo editing
Adobe LightroomAdobe PhotoshopCapture One
Product imaging
PhotoRoom
Photo library
Photo Structure
Photo delivery
SmugMug
Video editing
Adobe Premiere ProDaVinci Resolve
Motion graphics
Adobe After Effects
Encoding
AWS MediaConvert
Video platform
Mux
Video delivery
Cloudflare Stream
Video hosting
Vimeo
Media delivery
Cloudinary
CDN
Bunny.net
Image delivery
imgix
DAM
BynderBrandfolder
Stock
Getty ImagesAdobe Stock
AI tagging
Amazon RekognitionGoogle Cloud Vision
Generative AI
Adobe Firefly
Color
ColorChecker
Captions
Descript
Transcription
Whisper
Screen recording
Loom
Review
Frame.ioDropbox Replay

What photographers and video teams ask before handing anything over.

Does it work on my folders and large files where they are?
Yes. It runs on your computer and works on the folders and drives you point it at. Nothing has to be uploaded to a new library.
Will it touch my edits or delete anything?
Only what you write into the file. Most of these automations check, list and report, and you choose which steps wait for your OK, like moving or renaming files.
Do I have to change my editing software?
No. It works around the tools you already use: your editor, your gallery service, your drives and your email.
I work alone. Is it worth it?
That is where it helps most. The checks a team would split between assistants run on their own, and you get a short list of what needs you.
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