Client Delivery Packaging

Build a download package that names every file, states the usage terms, and stops at a size the client can actually receive.

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

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.

Ready-made: Delivery Manifest Build

The job, and what good looks like.

### What breaks A delivery folder is zipped and sent with no note of which version it is or what the client may do with it, and a year later nobody can answer either question. Full-size files stall on the client connection, so the whole set gets resent. ### What the workflow does - Write a manifest naming every file with its version, size, and date. - State the usage terms on the manifest and send them with the files, not separately. - Make a web-sized copy of each file for email, proofing, and the web store. - Keep the full-resolution set behind a link that expires after the agreed window. - Log who received which version, and when. ### What a human still approves The account lead signs the terms, and the client confirms the file list before anything is sent. No delivery link goes out until a person has read the manifest and agreed the version.

When it is handled

  • Every delivery carries a version and a date
  • Usage terms travel with the files
  • Web-sized previews beside full resolution
  • Every send logged per client

Works with tools like

  • Cloudinary
  • Bunny.net
  • imgix
  • SmugMug

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.

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

Delivery Receipt Log

When a delivery link is sent, log the client, the version, the file count, and the date, then email the client a copy of what was sent.

When a delivery link is sent

Web Preview Set Build

When the full-resolution files are packed, publish a web-sized copy of each one to the client link, keep the full set private, and post the count.

When full-resolution files are packed

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.

Delivery Manifest Build

Approve before it saves the document and sends the email?

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.

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.

Related workflows.

Client Proofing and Selection

Give the client a small, decidable set of proofs and record exactly what they picked.

3 automations

RAW to Delivery Color

Apply one agreed look across a shoot and export delivery files that match the proof the client approved.

2 automations

Video transcoding

Render every delivery version of a finished video from one master and play-test each one, so a broken file is found before the client opens the link.

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