Case Study

Case Study: Photography Studio CRM & Delivery Automation

We built a connected set of automations for a small wedding, portrait and commercial photography studio: an inquiry pipeline in the studio CRM, quotes, contracts and payment reminders, model releases and licensing records, and a post-shoot pipeline to gallery delivery. The photographer now sees every inquiry and job in one place, releases are signed before shoot day and galleries go out on the promised date.

Studio type
Wedding, portrait and commercial photography
Team involved
Owner and lead photographer, studio manager, second shooter, editor
Systems connected
Studio CRM, Google Calendar, Dropbox Sign, Stripe, Xero, ShootProof, n8n
Delivery
Scrum, 1-week sprints, about 7 weeks to full launch

The challenge

Where the practice started

Inquiries from the website, directories and Instagram reached three inboxes, and weekend inquiries waited until Monday while the photographer was shooting.

Quotes were rebuilt by hand, and the contract and invoice did not always match the quote. Balances were chased late.

Model releases for commercial shoots were paper forms collected on the day, and licence terms for brand work lived in email threads.

After busy weekends several jobs sat between backup and delivery, and clients emailed to ask when their galleries would be ready.

Goals

What the project had to change

  • Every inquiry lands in one pipeline with the date status and a next step.
  • Quotes, contracts and invoices match, and payments are reminded on time.
  • Releases are signed before the shoot and every licence is on record.
  • Galleries are delivered on the promised date with the studio's own email.

What we built

What we built, as one connected system.

01

Inquiry pipeline

We connected the website form, directory leads and Instagram lead forms to the studio CRM with date checks against the calendar, a scam filter, follow-up tasks and a monthly source report.

Service details
02

Quotes to payments

Package, travel and usage rules now produce quote drafts the owner approves, contracts are filled from the approved quote, and retainers and balances are reminded and synced to Xero.

Service details
03

Releases and licences

Commercial shoots send releases for e-signature at booking, unsigned ones are chased, and each brand delivery gets a licence record with a renewal reminder.

Service details
04

Post-shoot pipeline

Backups are confirmed, jobs are tracked against turnaround, galleries are delivered in ShootProof with the studio's email, and proofing, print and review reminders follow.

Service details

Architecture

How the studio's workflows connect

Inquiries Web, directories Calendar Shoot dates n8n Four workflows Studio CRM Leads and jobs Dropbox Sign Contracts, releases Stripe and Xero Payments, invoices Photographer Approves, edits ShootProof Gallery delivery
  • Input
  • Logic and services
  • Data
  • Output
  • People

How it flows

  1. 1 Inquiries and calendar dates feed one n8n instance.
  2. 2 Four workflows update the CRM, send contracts and releases, and handle payments and invoices.
  3. 3 The photographer approves quotes, decides on rights and selects and edits images.
  4. 4 Galleries are delivered in ShootProof, followed by proofing, print and review reminders.

How it behaves

How the system behaves day to day

What each person sees and what runs in the background, including what happens when something goes wrong.

What clients see

  • A prompt reply and a call from the photographer
  • A quote, contract and invoice that match
  • Releases to sign online before the shoot
  • Their gallery on the promised date

What the studio sees

  • One pipeline and one job tracker
  • Quote drafts to approve
  • A day-before list of unsigned releases
  • Turnaround warnings before dates slip

What the automation does

  • Captures inquiries and checks dates
  • Fills contracts and schedules payments
  • Chases releases and tracks licences
  • Delivers galleries and sends reminders with stop rules

Edge cases and fallbacks

An inquiry looks like a scam
No automatic reply; held for the owner.
A model has not signed by the day before
Flagged on the list, and a tablet signature completes the record on the day.
A turnaround date is at risk
The owner gets a warning in time to message the client personally.
Backup is not confirmed
The job stays blocked and the owner is alerted before cards are formatted.
n8n or a vendor is down
Runs are queued and retried, and the studio works from its tools as before.

Integrations

What we connected

All integrations

HoneyBook

Studio CRM

New clients, booked projects, payments and stage changes.

HoneyBook's Zapier app (Client Created, New Project Booked, New Payment Paid, Project Stage Changed triggers).

ShootProof

Galleries and orders

Galleries, photos and orders for delivery and reminders.

ShootProof Studio API (OAuth 2.0; client ID requested from ShootProof support).

Dropbox Sign

E-signature

Contracts and model or property releases from templates.

Dropbox Sign API (send with template).

Google Calendar

Calendar

Date checks and booked-date holds.

Google Calendar API.

Stripe

Payments

Retainers, balances and print payments.

Stripe Payment Links and the Stripe API.

Xero

Accounting

Invoices and payments synced from bookings.

Xero Accounting API.

n8n

Automation platform

Runs every workflow, self-hosted or on n8n Cloud.

Your own n8n instance; we hand over every workflow.

How we delivered it

Week by week, one workflow at a time.

Each workflow went live on its own after a shadow run and a sprint demo, so the team got used to one change before the next.

Delivery timeline

Typical time to launch: about 7 weeks, then support

  1. 01

    Discovery

    Week 1

    We followed one job from inquiry to album, mapped pricing rules, release and licence templates and turnaround promises, and set up vendor access.

  2. 02

    Sprint 1: inquiry pipeline

    Week 2

    Built and shadow-ran inquiry capture, date checks and follow-up tasks; demo and sign-off.

  3. 03

    Sprint 2: quotes and payments

    Week 3

    The pipeline went live. Built quote drafts, contract filling, payment reminders and Xero sync.

  4. 04

    Sprint 3: releases and licences

    Week 4

    Quotes went live for new bookings. Built release e-signature, chasing and the rights register.

  5. 05

    Sprint 4: post-shoot pipeline

    Week 5

    Releases went live. Built backup checks, the turnaround tracker and ShootProof delivery.

  6. 06

    Sprint 5: reminders and reports

    Week 6

    Delivery went live for new jobs. Added proofing, print and review reminders and the monthly report.

  7. 07

    UAT and handover

    Week 7

    The studio ran acceptance testing on every workflow, then we handed over the run book and trained the team.

  8. 08

    Support

    Ongoing

    Weekly check-ins through the next busy weekend, then monthly care.

Who does what

What the team does, and what automation does.

Automation does

  • Captures inquiries and checks requested dates
  • Drafts quotes and fills contracts from approved quotes
  • Schedules payments, sends reminders and syncs Xero
  • Sends and chases releases and tracks licence renewals
  • Confirms backups, tracks turnaround and delivers galleries

The team does

  • Reply to inquiries and run discovery calls
  • Answer payment and order questions
  • Check releases on shoot day
  • Cull and edit to the studio style

Photographer or owner decides

  • Decides which jobs to take and what to charge
  • Approves custom quotes and contract changes
  • Sets licensing terms and approves reuse
  • Chooses which images are delivered

Compliance handled

Privacy, consent and safety, built in.

Licences and transfers in writing

Contracts state whether the client receives a licence or an assignment; US transfers of ownership need a signed writing.

Source: www.law.cornell.edu

Owner metadata kept

Delivered files keep metadata identifying the studio as copyright owner, in line with UK guidance.

Source: www.gov.uk

Photos of people as personal data

Releases and the rights register are stored with access limited to the studio.

Source: gdpr-info.eu

Gallery face search off by default

Face recognition in galleries processes special category data, so it stays off unless the studio has a lawful basis.

Source: gdpr-info.eu

Honest review requests

Every eligible client is asked the same way with no incentives, in line with the FTC rule on fake reviews.

Source: www.ftc.gov

Outcomes

What changed for the practice

  • Weekend inquiries now land in one pipeline with the date status, ready for a personal reply.
  • Quotes, contracts and invoices match, and balances are reminded without the owner chasing.
  • Releases for commercial shoots are signed before shoot day.
  • Every brand licence has a record and a renewal reminder.
  • Galleries go out with the studio's own email on the promised date.

What we track

The measures the practice watches.

Inquiry response

Time to first reply and share of inquiries that book a call.

Booking flow

Days from call to signed contract and retainers paid on time.

Releases

Share of releases signed before shoot day.

Licensing

Licences on record and renewals offered before expiry.

Turnaround

Jobs delivered by the promised date and days from shoot to gallery.

Cost estimate

What a project like this costs

Estimates to plan with. Your fixed quote follows a free call, once we have seen your systems and volumes.
  • Discovery and design

    Job mapping, pricing rules, templates and the backlog.

    $800 – $1,600

  • Inquiry pipeline module

    Capture, date checks, scam filter and tasks.

    $700 – $1,700

  • Quotes and payments module

    Quote drafts, contracts, reminders and Xero sync.

    $800 – $2,000

  • Releases and licences module

    E-signature, chasing and the rights register.

    $600 – $1,600

  • Post-shoot module

    Backup checks, turnaround, delivery and reminders.

    $700 – $1,800

  • Testing, UAT and launch

    QA, acceptance testing, launch and training.

    $400 – $1,300

  • Total project estimate

    $4,000 – $10,000

Optional monthly care after launch is quoted with your proposal. Typical range for a project of this scope: four workflows at our fixed per-workflow range. Every studio gets its own fixed quote after a free call.

Monthly running costs you pay directly

Estimates from the vendors' published pricing, checked November 2026. Billed to you by each vendor, never marked up.

  • n8n: Self-hosted Community edition on the studio's server, or n8n Cloud from about €20 a month (Starter) or €50 (Pro), billed annually.
  • Studio tools: The studio CRM, ShootProof, Dropbox Sign and Xero plans.
  • Payments: Stripe's own published processing fees.

What pushes cost up

  • Systems without an API, or with integration access that must be requested from the vendor
  • Writing data back into your core system rather than only reading from it
  • Several locations, brands or very different processes to support
  • Custom apps, dashboards or a voice line on top of the workflows

What keeps cost down

  • One location and one clear process to start with
  • Cloud software with a documented API
  • Using tools you already pay for instead of adding new ones
  • Approved wording and sample data ready at the start
Get a fixed quote

How we deliver

Agile delivery, in 1 to 2 week sprints.

We deliver in short Agile sprints using Scrum, so you see working software every one or two weeks instead of waiting for a big reveal at the end.

Every sprint

  1. 1 Sprint planning. At the start of each sprint we agree which backlog items we will finish, each with written acceptance criteria you can check.
  2. 2 Daily stand-up. A short internal check-in on progress and blockers. You get a written update in your Slack or Teams channel, not another meeting.
  3. 3 Sprint review and demo. At the end of each sprint we demo what was built on test data or in a shadow run, and you accept it or ask for changes.
  4. 4 Retrospective. The team looks at what went well and what to change in the next sprint, and we share anything that affects you.

How scope stays under control

Product backlog
Every feature, fix and question in one prioritised list you can see at any time.
Acceptance criteria
Plain-language conditions for "done" on each item, agreed before work starts.
Change requests
New ideas go into the backlog with an estimate. Nothing changes scope or price without your written approval.
User acceptance testing (UAT)
Before launch your team tests the real workflow against the acceptance criteria and signs off.

Tools we use

Jira, ClickUp or Trello for the backlogSlack or Microsoft Teams for updatesGitHub for code and version historyLoom or a live call for demos

Project manager / Scrum master

Runs the sprints, keeps the backlog and timeline honest, and is your single point of contact.

Business analyst

Maps how the work runs today, writes the workflow specification and acceptance criteria with your team.

Automation engineer

Builds the n8n workflows, integrations, AI steps and error handling.

Backend developer

Writes custom code where a no-code step is not enough: APIs, data sync, secure storage.

Frontend / mobile developer

Builds forms, booking pages, dashboards, web apps or Android apps when the project needs them.

QA engineer

Tests every workflow against the acceptance criteria, including edge cases and failure paths.

DevOps engineer

Sets up hosting, access, backups, monitoring and alerts, and the deployment pipeline.

Who does what at each phase

Free call
Project manager, business analyst
Understand the problem, check it is worth automating and outline a rough range.
Discovery
Business analyst, automation engineer
Map the current process, systems and data, and agree success measures.
Design
Business analyst, automation engineer, backend developer
Write the workflow specification, data flows, compliance notes and backlog with acceptance criteria.
Sprints
Automation engineer, developers, QA
Build, test and demo in 1 to 2 week sprints; you accept or adjust after each demo.
UAT and launch
QA, DevOps, project manager
Your team tests and signs off, we switch on, monitor closely and train the team.
Support
Automation engineer, DevOps
Stabilisation window, then optional monthly care with monitoring and changes.

A point of contact

One person who can answer questions and approve decisions, with about an hour a week during the project.

Access

Admin or API access to the systems involved, created as separate accounts with the least access needed.

Sample data

Real but non-sensitive records (or de-identified ones) so we can design and test against reality.

Approved wording

Message templates, policies and consent wording (for SMS, your opt-in and opt-out text) reviewed by you.

Vendor agreements

Signed agreements with the software vendors that will handle personal data, such as a BAA or processor contract.

Time for testing

A few hours from the people who will use the system, for the demos and user acceptance testing.

Working system

Workflows, integrations and any apps running in your accounts, under your keys.

Documentation

Workflow specification, data-flow map, run book and exported workflow files.

Training

A walkthrough for the team and a short recorded video for new starters.

Handover

All access, credentials and code handed over; you can keep us or take it in-house.

Stabilisation window

Fixes for anything that does not meet the agreed acceptance criteria after launch.

Support options after launch

  • No plan

    You run it yourselves after the stabilisation window and contact us when you need a change.

  • Monthly care

    Monitoring, error alerts, small changes and updates each month, with an agreed response time.

  • Priority care

    Faster response times for business-critical workflows and a monthly review call.

How a project moves through our team

Free call PM and analyst Discovery Process and data Design Spec and backlog Sprints Build, test, demo Your review Accept or adjust UAT and launch Sign-off, go live Support Monitor and improve
  • Input
  • Logic and services
  • People
  • Output
  • Data

How it flows

  1. 1 A free call with the project manager and business analyst to understand the problem and whether it is worth building.
  2. 2 Discovery and design produce a written specification, data-flow map and a backlog with acceptance criteria.
  3. 3 The team builds in 1 to 2 week sprints; you review a demo at the end of each and accept or adjust.
  4. 4 Your team runs user acceptance testing, we launch, then monitor and improve under a support plan.

Free 20-minute call

Want this built for your photographers & creative?

Book a free 20-minute call. We will look at how the work runs today, tell you honestly whether it is worth building and give you a fixed quote if it is.

Book a free 20-minute call