Create an event (project) for each booking - optionally linked to a CRM enquiry so names, dates, and city carry over. On the event page you manage team, payments, the project gallery, the couple website shortcut, and a full activity log instead of chasing threads across apps.
Each event is a single page in your studio: the same client context as your CRM, plus the operational tabs you actually use week to week.
The product is not a separate Gantt-style planner - it is the same event workspace your team opens after a booking: members, money, gallery, the couple site, and a chronological activity log.
Colour-coded Google Sheets and shared notes only feel organised. The moment you have 6 weddings overlapping, everything breaks down. Here's what changes when you use a real tool.
Tie an event to a CRM enquiry so client name, wedding date, city, and contact fields stay connected. One enquiry can only map to one project - duplicates are blocked.
Add studio accounts or name-only crew with roles. Where your workspace supports it, store agreed fees per member and compare them to staff payments logged on the event.
Record project payments with category, amount, currency, method, reference, and date. Keep a clear history alongside contract amount on the event.
Folders and uploads scoped to the event, plus share gallery and optional theme or cover customisation - the same delivery surface you use for clients, anchored to the booking.
When the enquiry has a couple website, open it from the event. No copy-pasting slugs between tools.
Owners and project members see the full hub; employees of the studio can use a gallery-focused view without owner tabs. Activity lists what happened on the event.
One page per wedding.
Team, money, gallery, log.
Start free - Trial includes up to two events alongside two CRM clients; upgrade for unlimited projects.
