About

I run a wedding and events photography studio in Toronto. I’ve been doing it for about a decade. Shootlog started because I got tired of my own bookings living in two places: a board that tracked where each job stood, and a notes column that held everything the board couldn’t ask about properly.

Team names went into the notes, because there was nowhere else for them to go. So did lines like “editor not paid yet,” because that was the only place left to put it. A wedding is rarely one day, and a multi-day booking meant hours split across days by guesswork, because nothing in the board asked me to be more precise than that. And profit — what a booking actually made once everyone was paid — was something I worked out at the end of the year, if I worked it out at all. Not because I didn’t care. Because nothing I was using was built to show it to me as I went.

I built Shootlog to fix that for my own studio: log a booking, add its days, pick who’s shooting each one from a proper team list instead of typing a name into a notes field, record what the client paid and what team and editors cost, and watch the profit update as it happens — for that booking, the month, the year.

Once it was working for me, it was obvious the problem wasn’t unique to wedding photography. Any creative business that books a date, brings people, and needs to know what the job made runs into the same thing — videographers, content creators, proposal and decor companies, anyone whose work looks like a string of jobs rather than one steady contract.

Shootlog is built for that: a private back office that answers “who’s shooting, what’s owed, what did it make” without a spreadsheet held together with formulas only you understand.

It’s deliberately not everything. It isn’t a client portal — your clients never see it. It isn’t an invoicing tool — keep using whatever you already send invoices with. It’s the back office, not the front door.

Sarfaraaz Kara, Founder