Client Proofing and Selection

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

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

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.

Ready-made: Proof Gallery Build

The job, and what good looks like.

### What breaks A client is sent 900 proofs and replies with 40 file names, half of which are not even in the set. Six weeks later nobody can tell whether they approved version one or version three, so the retouch happens twice. ### What the workflow does - Send a curated gallery, not the whole card, with previews sized to load quickly. - Keep a low-resolution preview of everything so the client can still see context. - Record favorites as a list with the version number and the date they arrived. - Expire the link after the delivery window instead of leaving it open. - Hold the unselected files out of the retouch queue. ### What a human still approves The photographer chooses what goes in the gallery and reads the selection before work starts. A written yes on a named version is what counts as approval, not a reaction on a draft.

When it is handled

  • Clients choose from a curated set
  • Selection stored as a list, not a comment thread
  • Approval tied to a version and a date
  • Unselected files never get retouched

Works with tools like

  • Frame.io
  • SmugMug
  • Dropbox Replay
  • Adobe Lightroom

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.

Favorites To Approval Sheet

When a client marks a proof as a favorite, add it to the selection sheet with the version and the date, and post the total so the retoucher can start.

When a client marks a proof as a favorite

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

Proof Round Reminder

When a gallery has been open for five days with no selection, email the client a short reminder naming the two files we still need, and post the update to the producer.

When a gallery has been open for five days with no selection

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.

Proof Gallery Build

Approve before it 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.

Culling and Retouch Queue

Turn a finished shoot into one ordered list of the frames worth retouching, with the rest set aside on purpose.

3 automations

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.

3 automations

Video editing

Keep every cut, review copy, and note under one version number, so the next pass starts from the thing the client actually approved.

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