.shock.LAB · deliver
.deliver.shock
In development
Send the finished work as a link, and get an approval you can prove.
The outcome .deliver.shock delivers.
Finished commercial work currently leaves a studio as a file-transfer link and a hopeful email. The client downloads a folder, asks two questions by phone, approves in a message that gets lost, and six months later nobody can say which version was signed off or what the licence was.
.deliver.shock makes the delivery itself the record. The client opens one private link and reads, before the images, exactly what they are receiving and what they may do with it — count, format, usage, territory, duration. They comment on individual frames, request changes, and approve the delivery as a whole; the approval is stamped with who, when, and which round.
- Send a private link, not a folder. Token-gated, an optional password, an expiry date, and revocable the moment you need it back.
- State the licence before the images. Usage, territory, duration and exclusivity read from the agreed brief, so the answer to “can we put this on a billboard?” is already on the page.
- Let the client mark up the work. Favourite, comment per frame, or request changes on the whole delivery — with no account and nothing to install.
- Get an approval you can prove. Who approved it, when, against which round, with a fingerprint of the exact set they signed off.
- Revise in rounds. Round two carries every prior approval forward and marks what changed. The round they approved in March stays readable in November.
- See unreleased faces before sending, using the same release-coverage rule .release.shock already applies.
- Nothing is copied. The client sees the same originals every other module works on — one file, referenced, never duplicated into a delivery folder.
Built for the studio whose client is a person, not an agency.
For photographers and studios delivering commissioned work to a brand, an agency or a marketing team — where the deliverable is not “uploaded to Shutterstock” but “signed off by the client, with the licence in writing.”
If your work is entirely microstock, .publish.shock already delivers it to the agencies and you will not need this. If a human has to say yes before you invoice, this is the module that gets you that yes on the record.
One link. No account. No app.
This is the only part of the software an outside client ever opens, so it is built as a brand surface rather than a file list. Your client gets a page with your name on it. It opens on a phone on a train. It says what they are receiving and what they may do with it before it shows them a single frame.
No sign-up, no password unless you set one, and no cookie banner — because the page sets no tracking cookies. Two actions: approve, or ask for changes. In Bosnian or English, whichever they wrote to you in.
What it will not do.
It is not built yet. This page describes a specified product, not a shipped one. Nothing here is available to use today, and no date is being promised.
It will not deliver to stock agencies. That is .publish.shock — a different receiver, over FTP, with per-agency verdicts. This is for one named client.
It will not claim a delivery is complete when it has not checked. Where no agreed brief is linked, the delivery is labelled unchecked rather than presented as matching a specification nobody recorded.
It will not hold your images. A delivery is a list of references to files that already exist. Revoking a link removes access, not the work.
Where .deliver.shock connects.
It takes the finished renditions from .retouch.shock, states the licence agreed in .plan.shock, checks the set against that brief, and turns the client’s approval into the moment .finance.shock can invoice. A parallel track, not a step every image passes through — a stock frame goes to agencies instead.