Example client · 📷 photography studio
How “North Shore Photo” runs on one portal.
A portrait & wedding photographer was booking shoots by DM, delivering galleries through a separate host, and chasing invoices by email. Here's the same studio on one The Ship portal.
Before & after
😵 Before
- Enquiries in DMs, email and texts — easy to miss
- Shoots booked back-and-forth, sometimes double-booked
- Galleries on a separate paid host with its own login
- Invoices typed by hand and chased manually
- No list of past clients to re-market to
✅ After — one portal
- A website enquiry form that never sleeps
- Shoots booked in one schedule — each becomes a lead
- Access-code galleries clients open with a link
- Invoices raised in a click; paid ones become income
- Every client in the Lead Book, ready for the next season
Their module stack
Five modules, one login, all connected. Try each — they're live.
How it all connects
Nothing is re-typed. One action flows to the next.
A couple enquires on the site → the shoot lands in the schedule and drops into the Lead Book → an invoice goes out and, once paid, counts as income → the finished gallery is delivered by access code. One thread, no re-typing.
Build one like this.
Start from this exact stack — Gallery, Website, Bookings, Invoicing, and CRM — pre-loaded in the Builder. Tweak it for your studio.
Open this stack in the Builder →Prefer a different trade? See the gelato-shop, real-estate brokerage, service & trades or sports club examples, the starter-site example, or browse all starter stacks →