You direct a team you do not employ.

How the work runs

The path this business already walks.

Written for Wedding and event planners and coordinators, from full-service planning through to coordination of the day itself, working alone or with associates brought in for one event.

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.

1. Fit call

   The first conversation is about scope, not availability

   A planning enquiry arrives with a date, a venue that may or may not be held, and a couple who want to know what you would actually do for them. That conversation decides whether the work is full planning, partial planning or taking a finished plan over for the final stretch, and the answer belongs on the record from the first message rather than in a mailbox someone searches later. Replies to new enquiries are drafted from the incoming email and held until a person has approved the exact wording; sending the approved reply is still being built.

   Human approval
2. Scope

   Two planners quoting the same wedding are selling different work

   One is booking every supplier from nothing; the other is taking over a plan already made and running the day it happens. The proposal is where that line gets drawn, and the fee follows the line rather than the guest list. Clients review the options and choose in the portal; sending a proposal waits for a person to approve it, and delivery is still being built. The retainer is invoiced against the same record and payable by card, though connecting a payment account and emailing invoices are also in development. Sending contracts for signature is planned, so that step sits outside the workspace today.

   Human approval
3. Suppliers

   Most of the work is other people's, and you booked all of it

   A venue, a caterer, a florist, a band, a photographer: none of them on your payroll, all of them answering to you on the day. Each thread has its own state, from enquired through quoted and held to booked and paid, and holding them as cards on a board is what keeps a question about the caterer from becoming a search through an inbox. The board and its per-card checklists are in development. Assignable tasks with owners and due dates on each wedding are planned, and so is one record per wedding that every document and message links to, so today the board and the client record are still two places.

4. Run of show

   The timeline is the deliverable, and it is rebuilt all year

   When the styling team arrives, when the first look happens, when the band can load in, when the cake is cut: each of those moves at least once, and the walkthrough at the venue moves several at a time. From one description of the day the workspace derives a logistics view of setup, service slots and breakdown alongside an experience view for the couple, and the same input always produces the same schedule. That generator is exercised in tests; saving the schedules for a business is switched off by default, and delivering them to suppliers is not built yet. Recording a change with the schedule and price adjustment it triggers, held for approval, is planned.

   Human approval
5. Between meetings

   A couple does not save their questions for the next call

   They ask at night, at the weekend, in the middle of your other wedding, and the answer usually already exists somewhere you wrote it down. Clients sign in with an emailed link to see their invoices, their payment history, their proposals and the forms you publish, which takes the documents out of the reply queue; that portal is in development. Messaging inside the portal with the thread attached to the wedding is planned. Follow-up drafts are prepared and queued for a person to approve or reject, and sending the approved ones is not built yet, so those drafts stop at the review step.

   Human approval
6. On the floor

   The day is spent holding other people to a plan they agreed to

   Telling the band when to start, the caterer when to clear, the photographer where the family has gone. Whoever is running a part of the day needs the schedule in their hand, and an associate covering a room for you needs it more than you do. The crew schedule comes from the same description of the day as the couple's version, so the two cannot drift apart. Assigning people to a wedding by role, with their availability visible, is planned, and getting the schedule into their hands is not built yet.

7. Settling up

   The last hour of the night decides the last invoice

   Overtime agreed standing in a car park, a supplier who bills you later, a balance still outstanding, and the note to yourself about which caterer to recommend and which to stop calling. A spoken update after the day becomes proposed changes to the record that wait for a person to apply or reject them; the review screen for those is not built yet. Invoices and card payments sit on the same record as the wedding, and agents preparing payment reminders for a person to release are planned.

   Human approval