The Creative Clan
Production studio, London and Cape Town
The problemClient approvals scattered across email threads and versions.
A client review and sign-off portal. Their client opens a board, sees what is waiting on a decision, signs it off, and the work moves to invoicing. Live.
Before and after
- Before: Client approvals scattered across email threads and versions.Now: One board, a month at a time, with every shoot in one of three columns.
- Before: Sign-off could be a stray click.Now: Approving names the job again and says in words what it means.
- Before: Approved work waited to be noticed.Now: Sign-off routes the job straight to invoicing.
What we built
The Creative Clan shoot and edit campaign work, and the portal is where their client sees it. A month at a time, every shoot sits in one of three columns: being shot or edited, waiting on the client to look, or approved and closed. The client opens the review link from the card, decides, and signs off in the same place.
Underneath, automation moves the work. A new task scaffolds a named storage folder. Moving a card uploads the assets for review, mints a link for each one, writes the result back and emails the client. Sign-off routes the job to invoicing. No model anywhere in the runtime path.
See the month in three columns
A client opens the portal and sees the month. Every shoot sits in one of three columns, and only the one waiting on them is marked, with a rule, a dot and a count in the line under the month. Each card names the brand, says whether it is photo or video, and carries the shoot dates and the delivery date.
Approve on purpose, not by accident
Sign off sits on the card beside the link out to the review tool. Pressing it opens a confirmation that names the job again and says in words what approving it means, so nobody signs a deliverable off by catching the wrong button.
Sign it off, and it is recorded
The moment a client signs off, the board moves. The job leaves the review column and lands under signed off stamped with the name that approved it and the date, the count of what is waiting drops, and a message confirms the team has been told.
Lock a finished month
Step back a month and the board is marked archived and view only. The signed-off work stays where it is, so the record of what was delivered and approved survives and nothing can be approved twice.
The numbers
- tests green: 611 Python, 129 Worker
- 740
Stack used
- Astro
- Cloudflare Workers
- Cloudflare D1
- Python
- Asana API
- Frame.io API