| Sector | Photography, video production and design studios |
|---|---|
| Common problems | Quotes rebuilt from the last one, approvals scattered across email, expired delivery links, licence end dates nobody tracks |
| Typical fix | A rate card that builds quotes, a client portal with an approval trail, delivery that does not expire, licence expiry alerts |
| Also relevant | Deposit and milestone invoicing, freelance crew scheduling and pay |
| Starts with | A free operational audit |
| Area served | Ireland |
The admin a studio does not think of as admin
Studios rarely describe themselves as having an admin problem. They describe themselves as busy. The work is creative, every job is different, and the paperwork feels like an unavoidable tax on doing interesting things.
That framing is what keeps it expensive. Because each job is bespoke, nobody notices that the same nine steps happen every single time, in the same order, and that most of them are being done by hand.
Where the hours actually go
- Quotes built by editing the last one. Open the most recent similar job, change the numbers, hope nothing from the old scope survives the edit. It usually does.
- Scheduling across people, kit and locations. A shoot needs a crew, equipment and a date that suits a client. Holding that in messages means a double-booking is a matter of time.
- Approvals spread across email. Feedback arrives in three threads from two people, referencing a version that is no longer current.
- Delivery through services that forget. Finished work goes out as a transfer link. The link dies. The client asks a year later. Somebody re-exports and re-uploads.
- Licences with no end date recorded. Usage agreed for twelve months, and nothing anywhere knows when those twelve months are up.
- Invoicing that waits for a quiet week. Deposits, milestones and final balances are all triggered by events, and all invoiced whenever somebody remembers.
- Releases and consent kept loosely. Model and property releases signed on paper, photographed, and stored wherever the photograph ended up.
What automating it looks like
A rate card that produces the quote
Day rates, crew, kit, licensing and post are entered once as a structured rate card. A quote is then assembled from selections rather than retyped, which makes it faster and stops last month's scope leaking into this month's job.
A client portal with an approval trail
Clients review the current version in one place, leave feedback against it, and approve explicitly. The approval is recorded with a timestamp against a specific version. See custom software and portals.
Delivery that stays retrievable
Finished work is delivered from, and stays attached to, the job record. A request a year later is answered by a lookup rather than an export.
Licence and release tracking
Usage periods, territories and renewal dates held per job, with alerts before a licence lapses. Releases and consent forms captured digitally at the point of signing and filed against the shoot automatically.
Invoicing triggered by events
The deposit invoices when the booking is confirmed, the balance when the work is delivered, and overdue invoices chase themselves. See Invoicer for the standalone version of that problem.
Where to start
Start with a free operational audit. We will follow one recent job from the first enquiry to the final payment and count every point where somebody moved information by hand. In most studios the surprise is not how much admin there is, but how much of it happens after the creative work is finished.
Frequently asked questions
Why is studio admin so hard to systematise?
Because no two jobs are the same, so nothing ever becomes a routine that a template can absorb. A wedding, a product shoot and a brand film share almost no structure. The trap is concluding that nothing can be automated. The job varies, but the steps around it do not: quote, deposit, schedule, shoot, proof, approve, deliver, invoice, chase. Those are identical every time and every one of them can be automated.
What does a client proofing portal actually change?
It gives approvals a record. Right now a client approves a cut in an email, changes their mind two weeks later, and there is no authoritative answer about what was signed off and when. A portal makes approval an event with a timestamp against a specific version. That ends most scope disputes before they start, and it stops clients reviewing an old cut because they scrolled to the wrong email.
Our delivery links keep expiring and clients come back a year later.
That is the single most common studio complaint, and it is a storage problem dressed as a delivery problem. Sending finished work through a transfer service means the file lives somewhere temporary while the client treats it as permanent. A studio portal keeps delivered work retrievable against the job it belongs to, so a request a year later is a lookup rather than a re-export.
Can you track licensing and usage rights?
Yes, and it is worth doing. Commercial work is frequently licensed for a period or a territory rather than sold outright, and when the licence lapses that is either a renewal conversation or an infringement nobody noticed. Expiry tracking with alerts before the date is the same mechanism behind FleetMain, just pointed at licences instead of vehicles.
We book freelancers for most jobs. Can that be handled?
Yes. Crew booking, confirmed rates, day counts and what each freelancer is owed is a scheduling and pay problem, and it is close to work Oxus already does. Getting it out of a spreadsheet also means a freelancer querying a payment can be answered from a record instead of from memory.