A wedding party is not one appointment.

How the work runs

The path this business already walks.

Written for Hair and makeup artists who take wedding work, on their own or with a crew they bring in 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.

1. Inquiry

   A date, a venue and a party size arrive together

   A wedding inquiry is not a request for the next free slot. It carries a date months out, a venue, and a group of people who all have to be ready at the same hour. Those details belong on the client record from the first message, not in a mailbox someone has to search later. The reply is drafted for you and waits until you have read the exact wording.

   Human approval
2. Trial

   The trial is booked against the record that already holds the date

   The trial is its own session, often months before the wedding, and what comes out of it is a look the client has already agreed to. Booking it as an appointment on the same record means the trial and the day are one file rather than two, and the notes from the chair sit where the schedule will later be built. A spoken note after the trial becomes proposed changes to the record that wait for you to apply or reject them.

   Human approval
3. Party

   The party is counted as services, not as heads

   Hair and makeup are separate pieces of work with their own length, and some people in a party take one and not the other. Breaking the party down that way is what makes the rest of the wedding calculable: the same breakdown drives the proposal the client chooses from and the schedule the crew works to. A maintained catalogue of services for proposals and invoices to draw from is planned.

   Human approval
4. Booking

   The deposit is what turns a date into work

   Until the deposit is paid, a held date is a conversation. Once it clears, the wedding can become a card the whole crew can see, with a starter checklist that travels on it, and the balance stays on the same record as an invoice due before the day. Sending contracts for signature is still being built, so that step sits outside the workspace today.

5. Crew

   Extra artists are brought in for one morning

   A large party is worked by more than one pair of hands, and the people involved are often booked for that single morning rather than employed. Who is doing which slot, and in which role, is part of the wedding rather than a separate rota. Assigning people to an engagement by role, with their availability visible, is planned.

6. Event day

   One description of the morning, two schedules out of it

   The crew and the couple need different views of the same hours. From the start time, the venue and the party breakdown, the workspace derives a logistics schedule of setup, per-person hair and makeup slots and breakdown, and alongside it an experience schedule: the styling block, the point at which the photographer should be ready for getting-ready coverage, and the settling and final-touch time around it. The same input always produces the same schedule. Every length in it is a default the business sets, and the rate line is a placeholder until you fill it in. Saving the finished schedules for a business is switched off by default, and sending them to anyone is not built.

7. Changes

   Between booking and the day, the party changes

   A bridesmaid is added, the ceremony moves an hour earlier, someone drops the makeup and keeps the hair. Each of those changes the schedule and the amount owed at the same time, and the two have to move together or the morning runs short. Recording a change with the schedule and price adjustment it triggers, held for approval, is planned.

   Human approval