
- Client
- Phantom
- Place
- Belfast
- What we built
- Shoot management, from request to invoice
- Live site
- wearephantom.co.uk
45% lower coordination cost per completed shoot.
Measured over the 12 months after launch against the 12 months before, while shoot volume grew.
The system Phantom runs on is Kerb Appeal, a product we built and run. About Kerb Appeal
The briefEvery shoot touched an estate agent, a photographer and the office, and every one had to end in an invoice.
A single shoot starts with an estate agent asking for photography. It then needs a photographer's time, somewhere for the files, delivery back to the agent and a bill. Across many agency clients, each with several branches, the coordination between those steps becomes the bottleneck.
Requests arrived from estate-agency teams, from spreadsheets of properties and from photographers' own calendars. The system had to bring all three into one place, and make sure every shoot reached a billable record.
The mapSix stages, one record. This is how a shoot moves through Phantom now.
About this system
About the platform
- Sector
- Property marketing
- Role
- Architecture, development and evolution
- Core platform
- Automation
- Result
- 45% reduction in operating costs while scaling
Controls
- Branch-restricted access
- One project record per shoot
- Core platform: automation only
The key
Hover a station, or select it by touch or keyboard, to inspect its role and controls. Select a route to highlight it; select it again or press Escape to clear.
Read the map in words
Job requests, CSV imports and photographer calendars feed one project record per shoot. Each branch sees only its own records. The record triggers calendar synchronisation and automatic project folders. Client-specific pricing connects to invoicing, delivery and a billable record. The core platform uses automation. Commercial objective: higher shoot volume within existing coordination capacity. Result: 45% reduction in operating costs while scaling.
- Request
Shoot requests from estate-agency teams, CSV imports and photographer calendars all create the same thing, one project record per shoot.
- Booking
Photographer calendars connect availability to the project, and the booking is synchronised to the calendar from the record.
- Set-up
The record creates the project folders automatically, so nobody builds a folder structure by hand for each shoot.
- Delivery
Delivered work connects to a billable record, where scheduling, files and pricing meet.
- Invoice
Client-specific pricing carries from the project into invoicing, so each estate-agency client is billed at its own rates.
- Repeat
Once a shoot is delivered, repeat business is prompted automatically from the same record.


Each branch sees its own work, and nothing else.
Estate agencies with several offices request shoots from more than one branch. Access to each project record is restricted by branch, so a branch sees only its own shoots.
Scheduling and folder creation follow fixed rules rather than anyone's memory. When a record is created, the calendar is synchronised and the folders exist, ready for the photographer.
Pricing works the same way. Each estate-agency client can have its own rates, and the right rate follows the shoot through to the invoice.


The figureHow the 45% was measured.
The figure compares coordination and administration cost per completed shoot in the 12 months before launch with the 12 months after. Shoot volume grew over the same period, so the saving held while the work increased.
DeliverablesWhat we built for Phantom.
- One project record per shoot
- Shoot requests from estate-agency teams
- CSV import for shoots in bulk
- Photographer calendar synchronisation
- Automatic project folders
- Access restricted by branch
- Client-specific pricing
- Invoicing from the project record
- Delivery tied to a billable record
- Repeat business prompted automatically


