A lean event photography stack: bookings to gallery delivery

A corporate photographer can finish an event with thousands of files and still lose time to the work around the shoot: confirming the brief, getting terms signed, collecting a deposit and sending the final gallery. A lightweight operational stack separates those jobs instead of forcing them into a heavyweight CRM.

The practical split is straightforward. Use a booking workflow for the commercial commitment, then a gallery delivery platform for the finished images. Build My Event can handle proposals, digital contracts and deposit collection in one workflow. A separate gallery platform takes over when edited photographs are ready to share. These are distinct jobs, and photographers should not assume the tools connect automatically.

Start with the booking, not the camera roll

Take a typical enquiry: a company asks a freelance photographer to cover a conference. Before confirming the date, turn the request into a priced proposal. Spell out the coverage and what the client receives, such as the agreed event coverage and edited image delivery. Set out any options as separate line items where relevant. A clear scope gives both sides something concrete to check before signing.

Build My Event is designed to process that proposal, a digital contract and a deposit as one booking workflow. The contract records the agreed price, what is included and cancellation terms, and both sides sign online. Payments are processed directly via Stripe. The supplier decides the commercial terms; the software does not decide whether the fee or cancellation policy suits the assignment.

For a photographer whose leads arrive through referrals, email or social messages, a single booking process also avoids treating a conversation as a confirmed job. The practical point is the sequence: scope, proposal, signed terms, deposit. The guide on turning an informal enquiry into a secured booking covers that handoff in more detail.

Check the date before making a promise

Corporate work often competes with other shoots, editing days and travel. Check the diary before committing. Build My Event includes live diary checking that warns against double-bookings. That warning is useful, but it is not a substitute for keeping the diary accurate. Put existing commitments in the system you rely on and verify any travel or setup constraints yourself.

A warning also does not settle whether two jobs are operationally possible. A photographer might be free on paper but unable to cover a venue change, an early setup or a second event across town. Treat the diary check as a guardrail against date clashes, not a scheduling decision-maker.

Keep payment administration with the booking

Collect the deposit as part of the agreed booking process rather than relying on a message thread and a later manual chase. Build My Event supports deposit collection and instalments, with payments processed through Stripe. Stripe Identity is used for identity checks. Those checks and payment processing do not remove the need to confirm the company contact, purchase-order requirements or any client-specific procurement steps.

For a freelancer, this is a useful boundary: the booking workflow tracks the commercial commitment, while the photographer still owns the brief, the fee and the relationship. Build My Event is free for event organisers. Suppliers can use a free tier or choose Pro at £29 per month with a 0% platform fee. The right choice depends on the supplier’s workflow and volume; a flat fee is not automatically cheaper for every business. The earlier comparison of UK booking platform fee models is relevant when weighing that cost.

Hand off to the gallery platform after the shoot

Once images are edited and ready, use a gallery delivery platform for the client-facing delivery. Its role is to present the finished work and give the client a route to view and receive it. Keep the booking record as the source for the agreed scope and client details; keep the gallery as the delivery destination. Do not assume that a gallery service collects the deposit, records contract acceptance or checks whether the shoot date is free.

Make the handoff deliberate. Match the gallery to the booking using the client or event name, then send the delivery details through the channel agreed with the client. Record that delivery has happened in your own working process. If the client requests extra edits or images beyond the original scope, treat that as a commercial change and agree it before doing the additional work.

What this stack does not solve

This setup avoids buying a broad CRM just to manage a small number of corporate shoots. Its trade-off is a manual boundary between booking and image delivery. Without a confirmed integration, someone must carry the right event name, contact and delivery status across the gap. That is manageable at low volume, but it can become a source of errors as bookings increase.

Keep the stack small: one place for proposals, contracts and deposits; one place for finished galleries; and a consistent naming and handoff routine between them. Review the process after a few assignments. If duplicate data entry or missed delivery steps become frequent, look for a specific integration or add a lightweight tracking step. Do not buy an enterprise CRM before identifying which recurring failure it is meant to prevent.