Client records
In developmentClient records with contact details, lifecycle stage and tags, with wedding details such as date, venue and party size stored alongside.
Andiamo SMB · Photography and videography
A single day that can only be booked by one couple, and a job that runs on long after the cameras have gone back in the bag.
How the work runs
Written for Wedding and event photographers and videographers, working alone or as a small studio that brings in a second shooter for the day.
Steps marked for approval wait for a person. Andiamo SMB is not yet offered to customers; the parts each step leans on, and how far along they are, are listed further down.
First contact
The first message names a day, sometimes a venue, usually nothing else. What matters is whether that day is still free, because a Saturday in autumn is the thing being sold and it can only be sold to one party. Putting the date, the venue and the coverage asked for on the client record with the first reply keeps that answer out of a mailbox someone has to search later. The reply itself is drafted for you and held until you have read the exact wording; sending approved replies is still being built.
Pencil
The money this trade loses is the date that was held informally and then let go. A retainer is what turns a pencil mark into work, and the invoice for it belongs on the same record as the date it protects. When the automation is switched on for a business, a paid retainer opens the shoot as a card the studio can see, with a starter checklist on it. Sending the agreement for signature is planned rather than built, so that paperwork sits outside the workspace today, and keeping the held date in step with the calendar you actually check is planned as well.
Brief
Family groupings, the first look, the speeches, the drone the venue will not allow, the aunt who has to be in a photograph. All of it agreed once and then remembered differently by everybody. Held as coverage options the client reviews and chooses from in the portal, the brief stops being a thread of messages. Proposals are in development and releasing one waits on a person. A maintained catalogue of coverage and add-ons for proposals and invoices to draw from is planned, and so is recording a change of timing or coverage together with the price adjustment it triggers.
Call sheet
The person carrying the other body is booked for that day alone, often months ahead, and what they need is small and specific: where to be, when, which half of the day they cover, whose name to ask for at the door. That is part of the shoot rather than a separate rota. Assigning people to a shoot by role and seeing who is free is planned, so today the board is what tells the studio which job belongs to whom.
Shoot day
From the start time, the venue and what was agreed, the workspace derives a logistics view of setup, the blocks of coverage and breakdown, and alongside it an experience view for the people being photographed, including when to expect a camera in the getting-ready room. The same description of the day always produces the same schedule. The generator is exercised in tests; saving the schedules for a business is switched off by default, and delivering them to anyone is not built. One record per shoot that every task, document and message links back to is planned.
Edit
Culling, a first pass, a client selection, a second pass, the film cut and the revisions after it: weeks of work with nobody in the room and nothing to show until the end. It is the stretch where a studio loses track of which shoot sits at which stage, and where the chasing email goes out far too late. Assignable tasks with owners and due dates on each shoot are planned. Follow-up drafts prepared for a person to approve or reject are in development, and sending the approved ones is not built yet.
Delivery
The workspace holds the record and the money, not the frames: footage and finished galleries live wherever you host them. What it can hold is the part that usually slips, which is the balance owed, the album selections that come back late and the print order behind them. Clients sign in with an emailed link to see their invoices and payment history; connecting a payment account and emailing invoices are still being built. Payment reminders prepared for a person to release are planned, and so is a message thread attached to the shoot rather than to a personal inbox.
What the work leaves behind
What this leans on
Each card carries its own status. Parts in development are partly built and exercised in testing; planned parts are designed and not built yet. The full list for Andiamo SMB is on the product page.
Client records with contact details, lifecycle stage and tags, with wedding details such as date, venue and party size stored alongside.
Replies to new client inquiries are drafted from incoming email and held until a person reviews and approves the exact message; sending approved replies is still being built.
Create invoices and let clients pay them by card through Stripe checkout; connecting a payment account and emailing invoices are still being built.
When turned on for a business, a paid deposit creates the job card on the team board with a starter checklist; the checklist content and team notifications are still being built.
Send contracts for electronic signature and keep the signed copy with the client; electronic signing is still being built.
Keep bookings and claimed jobs in step with the team's Google Calendar.
Proposals with options that clients can review and choose from in the portal; sending a proposal waits for a person's approval, and delivery is still being built.
A maintained catalog of services and prices that proposals and invoices draw from.
Track scope and schedule changes with the approval and price adjustment they trigger.
Assign team members to an engagement by role and see their availability.
A drag-and-drop board of jobs with stages and a checklist on each card; letting team members claim open jobs is built but switched off by default.
From one description of an event day, two schedules are derived: a logistics view of setup, per-person service slots and breakdown for the crew, and an experience view for the person being served. The generator is exercised in tests; saving the schedules for a business is switched off by default, and delivering them is not built yet.
One record per wedding or job that every task, document and message links to.
Assignable tasks with owners and due dates on each engagement, beyond the per-job checklists on the board.
An agent prepares client follow-up drafts and queues them for a person to approve or reject; sending approved follow-ups is not built yet.
Clients sign in with an emailed link to see their invoices and payment history, view their contracts and proposals, and fill in forms their provider publishes; online signing is still being built.
Agents prepare payment reminders and appointment confirmations for a person to release.
Message clients inside the portal with the thread attached to their engagement.
Questions this work asks
What it runs on today
Where the date, the venue and the hoped-for budget arrive, and where they wait to be found again months later.
The only record of which Saturdays are gone, kept apart from the people who took them.
The retainer at booking and the balance before delivery, recorded away from the shoot itself.
Terabytes of footage and the client-facing gallery, versioned by folder name and understood only by whoever made them.
Call times, the venue address and who is covering the getting-ready room, scrolled back through on the morning itself.
Which shoot is culled, which is delivered, and which album selection has been outstanding since the summer.