Sonaris for photographers and video editors
Client galleries, bookable packages, a project for every shoot and the automation between them. A two-person studio can run the whole business from one workspace, with every client as a guest.
- Client galleries and review cuts1 / 14Files
- A site that sells packages and takes deposits6 / 14SitesCommercePaymentsCRMForms
- A project, checklist and room for every shoot10 / 14ProjectsChecklistsChatProfiles
- Bookings, deliveries and orders connected12 / 14FlowsMessages
An illustrative workspace. The business, people and figures are fictional.
Deliver galleries and cuts from one place
Every shoot gets a folder. Edits keep their version history and previews, and each gallery or review cut goes out on a share link with an expiry date that you can revoke at any time.
- Folders per workspace and per project, with versions on every file
- Share links with an expiry, revocable whenever you like
- Attachments from tasks, messages and orders land in the same place
A portfolio that sells packages and books dates
Sites builds the portfolio on your own domain. Packages are Commerce services, booking pages in the CRM take a deposit through your own Stripe account, and the enquiry form creates a contact and a deal before you have read the email.
- Portfolio and gallery sections, custom domain, SEO and redirects
- Services with packages, and booking pages that take deposits
- Enquiries arrive as a contact and a deal, tagged by source
- Prints as physical products with variants, presets as digital downloads
Every booking becomes a project the client can see
Each wedding or brand shoot runs from a project template with phases for prep, shoot day, edit and delivery. The kit checklist attaches to the shoot-day task, and the client joins the project's chat room as a guest to give notes on cuts.
- Templates with phases, owners, and board, list and timeline views
- Reusable checklists for kit, shot lists and backups
- A chat room per project, and guests who see their project and nothing else
Shoot day
Edit
Deliver
The admin between bookings runs itself
Flows listens to bookings, project phases and orders, and acts on the other modules. Messages adds a shared inbox, so reminders and delivery emails go out from your own address and every thread is filed on the client's contact.
- Triggers from booking pages, phases, orders and contacts that went quiet
- Branch on any field, such as the package or the order contents
- Every run has a log, and every edit to a flow is versioned
- Trigger · CRMDate booked, deposit paidwhen
- Action · ProjectsCreate project from “Wedding” templatethen
- Action · ChecklistsAssign “Kit and backups” to Rosathen
- Action · MessagesSend the planning guide from hello@then
- Action · ChatPost to #bookingsthen
- Trigger · ProjectsPhase advanced to Deliverwhen
- Action · MessagesSend the gallery and film linksthen
- Action · PaymentsIssue the balance invoicethen
- Action · CRMTag contact “delivered-2026”then
- Trigger · CommerceOrder placedwhen
- ConditionOrder contains the preset packif
- Action · CommerceSend digital downloadthen
- Action · CRMTag contact “print-buyer”then
- Action · ChatPost to #ordersthen
Two seats, one workspace, every client on one record
Enquiries, bookings, shoots, deliveries, print orders and payments all write to the same contacts and projects, so either of you can pick up any job without asking where anything is.
Edit
Deliver
Done
- FormsEnquiry from Fernhill Coffee
- CRMDeal created · brand half-day
- CRMHollis & Kemp booked 6 Sept
- ChecklistsKit and backups 12/12
- FilesHighlight film v4 shared
- CommerceTwo A3 prints ordered
- PaymentsBalance paid · £2,700
Start with one module. Add the rest as you grow.
Every module works with every other from the day you switch it on, and your data exports whenever you want.