How to Automate Studio Ninja

Studio Ninja holds every job from enquiry to gallery

Studio Ninja is business management software for photographers: wedding and portrait shooters, family and newborn studios, event and commercial photographers, mostly running as one person or a very small team.

It holds the shape of a job. An enquiry arrives, becomes a lead, gets a quote and a contract, turns into a booked shoot on a date, then a set of deliverables and an invoice with a balance on it.

What makes photography awkward as a business is that the product is a date. A Saturday in October can be sold exactly once, and it is usually sold nine months before it happens. Between the deposit and the gallery there is a long quiet stretch in which the client hears nothing, worries, and emails.

So the software is not really about pictures. It is about the year-long relationship wrapped around one afternoon, and about making sure the contract is signed and the balance is paid before anybody stands in a field with a camera.

Editing is finished long before the job is

Ask a photographer where the week goes and it is not the shooting, and increasingly it is not the culling either.

It is the tail. The album proof sent to the client three weeks ago that nobody has approved. The print order placed with the lab, which has a status page you have to go and look at, and a client who wants to know whether it arrives before Christmas. The gallery uploaded to a delivery platform that will tell the client and will not tell Studio Ninja. The venue that changed its vendor rules and now wants a certificate of insurance and a meal count. The second shooter who has not confirmed for the twelfth.

Each of those is two minutes. There are forty jobs open at once, in different stages, and every one has a different two-minute thing outstanding.

That is the actual work of running a studio, and none of it is photography.

Studio Ninja

Album and print orders tracked The lab's own order page checked and the shipped date written back onto the job, so nobody has to email to find out.

Galleries that report back Who viewed, who downloaded and who has bought nothing three weeks in, which is the only list worth a nudge.

Client messages drafted, not sent A wedding client is nine months of trust, so anything reaching them is prepared and waits for you to read it.

Workflows tick themselves as a job moves

Studio Ninja automates the job pipeline properly, and a photographer who sets it up once gets most of the chasing back.

Workflows are reusable task lists applied to every job, running through Lead, Production and Post-Production. Tasks tick themselves when something happens: a lead is created, a job is accepted, a contract is signed, an invoice is paid, the main shoot date passes. An automation task can send an email, a contract or a questionnaire on its own when it falls due, using your saved templates. An appointment task drops the date on your calendar and sends the client an auto-reminder. Invoices chase their own balances with automated payment reminders, and the client portal gives a client somewhere to look instead of emailing.

All of that turns on events inside Studio Ninja.

Which is the limit. Studio Ninja knows the job is marked complete. It does not know the lab shipped the album, that the client opened the gallery and downloaded nothing, that the venue posted a new vendor packet in March, or that the payout for last week's deposits actually reached the bank.

The job can update itself from outside the studio

A photographer who never opens the lab's order page still knows when the album shipped. The tail of every job gets shorter.

Print and album orders followed on the lab's own order page, with a shipped date written back onto the job, so whether the parents' album lands before the anniversary has an answer without an email. Galleries checked on the delivery platform: who has viewed, who has downloaded, who has bought nothing three weeks in.

Venue requirements checked before the week of the wedding, so the certificate of insurance and the vendor meal are paperwork rather than a Friday crisis. Deposits in the payment processor compared against the balances Studio Ninja believes are outstanding, which is the reconciliation nobody does until tax time.

And the quiet one. Enquiries that arrived through a directory or a marketplace inbox rather than your own contact form, pulled in so they land in the same pipeline as everything else instead of sitting unread for a week while somebody books the other photographer.

Keep the client side supervised. A wedding client is nine months of trust, and an automated message that lands wrong, on a date that cannot be repeated, does damage no refund covers.

The chasing happens between shoots

The lab's order page, the gallery platform and the venue's vendor site each change without telling the job they belong to. Checking them has been the photographer's job, at eleven at night, in the middle of editing season.

WebRun is an agent that works a real Chrome browser, signed in as you. It opens the lab, the gallery host or the payment processor, reads the status, and updates the job in Studio Ninja to match.

It runs on your schedule in your own private environment, and you can watch a run and stop it. Anything going to a client is drafted and left for you.

The workflows below are already built, and each one names what it opens.